unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-devel@gnu.org
Subject: Re: Contributions to Guile
Date: Mon, 08 Feb 2016 21:28:33 +0100	[thread overview]
Message-ID: <87oabruetq.fsf@gnu.org> (raw)
In-Reply-To: <87oabruhw1.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 08 Feb 2016 20:22:22 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>
>>>> If the html export was nicely themed
>>>
>>> It can be nicely themed.  FWIW, Gnulib’s gendocs.sh, which is what most
>>> projects use to export their HTML to gnu.org, now includes a CSS by
>>> default (see <https://gnu.org/s/guix/manual> as an example.)  We can
>>> change this CSS anytime, and in fact, I would love it if someone
>>> talented would come up with improvements!
>>
>> Ok, yeah
>>   https://gnu.org/software/guix/manual/html_node/Derivations.html#Derivations
>> does look a lot nicer!  I think it could look nicer still; eg, Racket's
>> docs using Scribble and anything using Sphinx tends to seem more nicely
>> themed:
>>
>>   https://hy.readthedocs.org/en/latest/tutorial.html
>>   https://docs.racket-lang.org/guide/define.html
>>
>> I think maybe the left-hand bar kind of helps, and some tweaks to the
>> coloring might help too.
>
> I would like to note that a while ago I prepared a *very simple* style
> sheet for GNU manuals to make it easier for me to read them online:
>
>     https://userstyles.org/styles/108215/gnu-manuals

Oh right, I had forgotten.  I like it!

In the meantime, I managed to overcome resistance on bug-gnulib to have
gendocs.sh default to a CSS at all (!).  Now, “all we need to do” is to
get the new CSS approved.

Could you look again at the feedback at
<https://lists.gnu.org/archive/html/bug-gnulib/2014-12/msg00161.html>
and put up an example manual somewhere (thus not requiring Stylish)?  We
can then lobby for the new CSS again.  :-)

Thanks,
Ludo’.



  reply	other threads:[~2016-02-08 20:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 18:43 Contributions to Guile Chad Albers
2016-02-05  9:32 ` Ludovic Courtès
2016-02-05  9:56   ` Sergi
2016-02-07 19:25   ` Chad Albers
2016-02-07 22:23     ` Christopher Allan Webber
2016-02-08  2:25       ` Mike Gerwitz
2016-02-08 11:31         ` Alex Sassmannshausen
2016-02-08 17:55           ` Christopher Allan Webber
2016-02-08  8:06       ` Ludovic Courtès
2016-02-08 18:17         ` Christopher Allan Webber
2016-02-08 19:22           ` Ricardo Wurmus
2016-02-08 20:28             ` Ludovic Courtès [this message]
2016-02-08 22:06               ` Ricardo Wurmus
2016-02-08 22:58                 ` Ludovic Courtès
2016-02-08 19:05         ` Christopher Allan Webber
2016-02-08 20:31           ` Ludovic Courtès
2016-02-08 21:28           ` Chad Albers
2016-02-08 21:37             ` Thompson, David
2016-02-09 16:09     ` Chad Albers

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oabruetq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --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.
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).