Christopher Allan Webber <cweb...@dustycloud.org> skribis: > Ludovic Courtès writes: > >> Christopher Allan Webber <cweb...@dustycloud.org> skribis: >> >>> Chad Albers writes: >> >> [...] >> >>>> b. More robust documentation system - texinfo is not the greatest. And >>>> it's non-trivial to generate any documentation (including texinfo) for >>>> modules. >>> >>> Texinfo is pretty nice to use if you're an emacs user... in fact, if >>> you're an emacs user, it's the best documentation reading system in the >>> world. But not everyone's an emacs user. >> >> I think Texinfo is OK even if you’re not an Emacs user, no? Especially >> with the just-release 6.1 where menus can (finally!) be automatically >> generated. >> >>> 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! > > Relatedly, see this very conversation happening about theming in > emacs-land right now! > > https://lists.gnu.org/archive/html/emacs-devel/2016-02/msg00361.html
Fun, we should keep an eye on it. The Emacs manual currently has its own CSS, separate from what gendocs.sh does. Ludo’.