unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Josefsson via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 62160@debbugs.gnu.org
Subject: bug#62160: Guix reference manual link from guix.gnu.org?
Date: Mon, 13 Mar 2023 13:11:41 +0100	[thread overview]
Message-ID: <06c03ed58df9c9419ed11e45a8a95bb5666e97b2.camel@josefsson.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

Hi

I often go to guix.gnu.org to read the (excellent!) Guix manual.  This
leads to this click pattern: guix.gnu.org -> Help -> GNU Guix Manual
1.4.0 which leads me to a page (written in english) to chose language
of the manual -- https://guix.gnu.org/en/manual/ -- and when I chose
English I get a page to chose format of manual --
https://guix.gnu.org/en/manual/en/ -- and that choice takes a split
second cognitive load.

How about these changes to improve user experience?

1) The link guix.gnu.org -> Help -> GNU Guix Manual 1.4.0 goes directly
to the split-node https://guix.gnu.org/en/manual/en/html_node/

  1b) The link could respect the language-choice for the web-site,
i.e., so if I'm browsing https://guix.gnu.org/de/ it should directly
link me to https://guix.gnu.org/de/manual/de/html_node/ instead.

2) Add links to the PDF variant and full-HTML variants in the top-right
menu where different languages are shown.

What do you think?  Then you quickly get into the manual, and there is
still a simple way to chose other languages, and to get PDF/full-HTML
variants.  I don't see any significant disadvantage with this change.

/Simon


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2023-03-13 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 12:11 Simon Josefsson via Bug reports for GNU Guix [this message]
2023-03-14 11:29 ` bug#62160: Guix reference manual link from guix.gnu.org? Simon Tournier
2023-03-14 17:35   ` bokr
2023-03-14 21:38     ` Bengt Richter

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=06c03ed58df9c9419ed11e45a8a95bb5666e97b2.camel@josefsson.org \
    --to=bug-guix@gnu.org \
    --cc=62160@debbugs.gnu.org \
    --cc=simon@josefsson.org \
    /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.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).