From: swedebugia <swedebugia@riseup.net>
To: L p R n d n <guix@lprndn.info>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Communication and Design at Guix
Date: Thu, 10 Jan 2019 14:20:06 +0100 [thread overview]
Message-ID: <309F9FF7-FE89-4935-9D08-ECC62937D95F@pretty.Easy.privacy> (raw)
In-Reply-To: <cuc5zuzaybu.fsf@lprndn.info> <87k1jfuk26.fsf@gnu.org> <705CB66B-E8D5-4119-9F70-D429E1B174B2@pretty.Easy.privacy> <877efd1p56.fsf@gnu.org>; <cuctvigvhmb.fsf@lprndn.info>;
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
L p R n d n <guix@lprndn.info> skrev: (10 januari 2019 13:09:48 CET)
>Hello,
>
>Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi swedebugia,
>>
>> swedebugia <swedebugia@riseup.net> skribis:
>>
>>>>> By the way, I wanted to start working on the documentation.
>>>>> IMHO, it might benefit from a little graphical enhancement for
>>>>> newcomers. The thing is that it's currently hosted on
>>>>> gnu.org so it's probably not possible to modify the design. So I
>>>>wanted
>>>>> to ask, first, if that's something that would be welcome? What
>could
>>>>be
>>>>> the possibilities? And what would be the technical limitations?
>>>>
>>>>The HTML pages at gnu.org/s/guix/manual are generated from Texinfo.
>>>>The
>>>>CSS there is shared with all the GNU manuals, which is nice for
>>>>consistency. Ideally modifications of the CSS would be submitted to
>>>>the
>>>>GNU webmaster or bug-gnulib@gnu.org (I forgot which one). However,
>be
>>>>aware that you may encounter misplaced conservatism if you take that
>>>>route, so don’t lose your hair on it.
>>
>> [...]
>>
>>> 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 agree with you to some degree. I like the design of both the racket documentation and readthedocs. Especially the left menu gives a nice overview and searchability on page is also nice.
--
Sent from my p≡p for Android.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3825 bytes --]
next prev parent reply other threads:[~2019-01-10 13:20 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 [this message]
2019-01-10 14:34 ` Ricardo Wurmus
2019-01-13 21:45 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=309F9FF7-FE89-4935-9D08-ECC62937D95F@pretty.Easy.privacy \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=guix@lprndn.info \
/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.