all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Reference manual + tutorials
Date: Tue, 29 May 2018 23:53:59 +0200	[thread overview]
Message-ID: <877enmqgaw.fsf@elephly.net> (raw)
In-Reply-To: <87muwiuu9u.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hello!
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> It would be great to have both!  I’d like the existing reference manual
>> to remain as the canonical description of all features of Guix, so that
>> an additional story-centered document (whether that be a dedicated
>> section or a separate file) can guide readers to more information if
>> they might need it.
>
> I think it’s not all-or-nothing though.  Our manual could be better
> structured and it could include more examples.
>
> I like the “traditional” GNU manuals (libc, Emacs, Gnus, etc.), which
> work very well for me, even though they’re only “locally
> user-story-based”, so to speak.

Yes, this can work.  It’s hard for me to imagine where one would put
prose that resembles a tutorial in our current manual.  It currently
leans very heavily towards a reference manual, which discourages me from
adding elaborate examples.

There’s also the danger of interrupting the flow with too many big
inline examples.  Currently, it is easy to understand the big picture
because the prose isn’t separated by step for step instructions.

It would be sad to miss out on good tutorials just because they don’t
fit into the current manual; and it would be just as sad to clutter the
manual by filling it with tutorials that would seem out of place.

It’s difficult to strike the right balance.

--
Ricardo

  reply	other threads:[~2018-05-29 21:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26 15:23 Customize GuixSD: Use Stock SSH Agent Everywhere! Ludovic Courtès
2018-05-28 11:16 ` Pierre Neidhardt
2018-05-28 11:28   ` Ricardo Wurmus
2018-05-28 15:28     ` Joshua Branson
2018-05-28 15:31       ` Pierre Neidhardt
2018-05-29 12:51     ` Catonano
2018-05-29 13:42       ` Ricardo Wurmus
2018-05-29 14:35         ` Catonano
2018-05-29 14:57           ` Reference manual + tutorials (was: Customize GuixSD: Use Stock SSH Agent Everywhere!) Ricardo Wurmus
2018-05-29 15:14             ` Catonano
2018-05-29 15:19               ` Reference manual + tutorials Julien Lepiller
2018-05-29 15:30                 ` Ricardo Wurmus
2018-05-29 19:38             ` Ludovic Courtès
2018-05-29 21:53               ` Ricardo Wurmus [this message]
2018-06-03 20:40                 ` Ludovic Courtès
2018-05-28 20:11 ` Customize GuixSD: Use Stock SSH Agent Everywhere! Divan Santana
2018-05-31 10:47   ` Divan Santana

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=877enmqgaw.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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 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.