all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: swedebugia <swedebugia@riseup.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	L p R n d n <guix@lprndn.info>
Subject: Re: Communication and Design at Guix
Date: Wed, 09 Jan 2019 22:45:25 +0100	[thread overview]
Message-ID: <877efd1p56.fsf@gnu.org> (raw)
In-Reply-To: <705CB66B-E8D5-4119-9F70-D429E1B174B2@pretty.Easy.privacy> (swedebugia's message of "Wed, 09 Jan 2019 07:11:28 +0100")

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.

> Talking about CSS and the manual I would like to add patens highlighting.
> The chicken documentation has this (on mouse over) and it is really nice to be able to see how complicated expressions are composed.

Yes I’d love that too!  It should be doable for the “@lisp” Texinfo
bits.

Thanks,
Ludo’.

  reply	other threads:[~2019-01-09 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 [this message]
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
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=877efd1p56.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix@lprndn.info \
    --cc=swedebugia@riseup.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 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.