unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, L p R n d n <guix@lprndn.info>
Subject: Re: Communication and Design at Guix
Date: Sun, 13 Jan 2019 22:45:45 +0100	[thread overview]
Message-ID: <87k1j81bau.fsf@gnu.org> (raw)
In-Reply-To: <87r2dk4m4g.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 10 Jan 2019 15:34:39 +0100")

Hi!

Ricardo Wurmus <rekado@elephly.net> skribis:

> L p R n d n <guix@lprndn.info> writes:
>
>>>> What about guix.info? We can do whatever we want there I suppose and just link
>>>> to it from the gnu site.
>>>
>>> Well in general we can always do whatever we want.  :-)  I do think
>>> there’s value in presenting GNU manuals in a consistent way, though,
>>> especially since Guix’ manual has cross-references to many other
>>> manuals.
>>
>> That would be nice though. Even if consistency is enjoyable, I think
>> the benefits of a nicely shaped and organised documentation easily beat
>> what we could get from being consistent with non-Guix manuals. IMHO
>> GNU manuals are ok when you know what you're searching for, I find them
>> unreadable. + I think they're intimidating for newcomers. :/

I think it’s hard to generalize.  What I do like about some GNU manuals
is that they’re well written and well structured; they can serve both as
a reference and as a way to get started.  Examples of these include the
libc and the Emacs manuals.  These are really book-quality, and are
actually published as such.

I understand it’s a very different approach from what people do
nowadays, which is often more “quick-start” but also short-term-ish, but
I like the idea of working to help users understand what they’re doing,
as opposed to just throwing at them the minimum they need to know to get
things done.  It’s about emancipating users, after all.

> It’s fine to deviate from the consistent style.  We do that already for
> the style sheet that’s used for our HTML documentation.  Compare this:
>
>     https://www.gnu.org/software/sharutils/manual/html_node/index.html
>
> with this:
>
>     https://www.gnu.org/software/guix/manual/en/html_node/index.html
>
> It’s fine to change our style sheet, but let’s stay with Texinfo.

Note that our manual uses https://gnu.org/software/gnulib/manual.css,
which is the standard CSS produced by Gnulib’s gendocs.sh, and this CSS
is used by many (most?) manuals at gnu.org, not just Guix.

My suggestion was to improve this CSS, if L p R n d n is willing to make
the extra social effort to get changes accepted.  If that doesn’t work,
we can depart from that.

Thanks,
Ludo’.

  reply	other threads:[~2019-01-13 21:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès
2019-01-09  6:11   ` swedebugia
2019-01-09 21:45     ` Ludovic Courtès
2019-01-10 12:09       ` L p R n d n
2019-01-10 13:20         ` swedebugia
2019-01-10 14:34         ` Ricardo Wurmus
2019-01-13 21:45           ` Ludovic Courtès [this message]
2019-01-14 15:02             ` L p R n d n
2019-01-15 10:36               ` zimoun
2019-01-15 18:03                 ` nly
2019-01-15 22:08                   ` Ricardo Wurmus
2019-01-16 11:00                     ` Giovanni Biscuolo
2019-01-15 22:28               ` Ludovic Courtès
2019-01-14 23:25             ` swedebugia
2019-01-15 13:56               ` Ricardo Wurmus
2019-01-15 17:39                 ` Julien Lepiller
2019-01-15 22:30                   ` Ludovic Courtès
2019-01-10 12:17     ` L p R n d n
2019-01-10 12:57   ` L p R n d n
2019-01-10 14:30     ` Ricardo Wurmus
2019-01-13 21:50     ` Ludovic Courtès
2019-01-14 14:36       ` L p R n d n
2019-01-15 22:31         ` Ludovic Courtès
2019-01-16 16:31       ` George Clemmer
2019-01-17  0:10         ` swedebugia
2019-01-17 10:58         ` L p R n d n
2019-01-17 11:10           ` Ricardo Wurmus
2019-01-17 14:08             ` swedebugia
2019-01-17 16:24               ` L p R n d n

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=87k1j81bau.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix@lprndn.info \
    --cc=rekado@elephly.net \
    /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).