public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang 2/5] docs: include the manual link over the manual
Date: Sat,  7 Sep 2024 00:35:16 -0300	[thread overview]
Message-ID: <20240907033519.293370-3-carlos@maniero.me> (raw)
In-Reply-To: <20240907033519.293370-1-carlos@maniero.me>

There are two main reasons for this change:

  1. consistency: no other page has this behavior, the specification and
     the home still enabled even when they are the current page.
  2. texinfo navigation is not so intuitive and I'm not confident the
     people will understand that if they click on the "[ Contents ]"
     link they will be redirected to the manual home page, so I believe
     that is convenient to have the manual link enabled.

Signed-off-by: Carlos Maniero <carlos@maniero.me>
---
 docs/manual/_header.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/manual/_header.html b/docs/manual/_header.html
index 41eae20..9e25295 100644
--- a/docs/manual/_header.html
+++ b/docs/manual/_header.html
@@ -4,7 +4,7 @@
   </h1>
   <nav>
     [ <a href="/">Home</a> ]
-    [ <strong>Manual</strong> ]
+    [ <a href="/manual/">Manual</a> ]
     [ <a href="/pages/language-specification.html">Specification</a> ]
     [ <a href="https://sr.ht/~johnnyrichard/olang/sources" target="_blank">Sources &UpperRightArrow;</a> ]
     [ <a href="https://sr.ht/~johnnyrichard/olang/lists" target="_blank">Mailing list &UpperRightArrow;</a> ]
-- 
2.34.1


  parent reply	other threads:[~2024-09-07  3:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07  3:35 [PATCH olang 0/5] docs: some improvements on the website Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 1/5] docs: unify manual and site style Carlos Maniero
2024-09-07  3:35 ` Carlos Maniero [this message]
2024-09-07  3:35 ` [PATCH olang 3/5] docs: make the olang visuals a w3m like website Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 4/5] docs: prevents the menu items to break line Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 5/5] docs: home page: transform the unfinished software warn into a notice Carlos Maniero
2024-09-07 10:38 ` [PATCH olang 0/5] docs: some improvements on the website Johnny Richard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240907033519.293370-3-carlos@maniero.me \
    --to=carlos@maniero.me \
    --cc=~johnnyrichard/olang-devel@lists.sr.ht \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.johnnyrichard.com/olang.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox