all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51000@debbugs.gnu.org
Subject: bug#51000: The Web manual situation is still needlessly confusing
Date: Mon, 04 Oct 2021 00:12:55 +0200	[thread overview]
Message-ID: <87ilydycps.fsf@nckx> (raw)

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

Good evening Guix!

Nary a literal week goes by that someone doesn't post confusion 
about this or that not being in ‘the manual’, where the manual 
turns out to be <https://guix.gnu.org/manual/en/guix.html> instead 
of the one actually shipped with their Guix.

The current solution is pointing them to 
<https://guix.gnu.org/manual/devel/en/guix.html> and resetting the 
timer.

Instead:

- We should make <https://guix.gnu.org/manual/en/guix.html> the 
  ‘devel’ version, and move the stable version to to a versioned 
  URL like <https://guix.gnu.org/manual/1.3.0/en/guix.html>.

- Both manuals should have a gorgeous CSS box at the very top 
  clearly explaining their nature.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

             reply	other threads:[~2021-10-03 22:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 22:12 Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-10-04  4:19 ` bug#51000: The Web manual situation is still needlessly confusing John Kehayias via Bug reports for GNU Guix
2021-10-04  6:31 ` Efraim Flashner
2021-10-04  6:58 ` zimoun
2023-05-22  1:59 ` bug#51000: Please drop web manuals for released versions Felix Lechner via Bug reports for GNU Guix
2023-09-27  9:26 ` bug#51000: The Web manual situation is still needlessly confusing Simon Tournier

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=87ilydycps.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=51000@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.