From: Drew Adams <drew.adams@oracle.com>
To: John Wiegley <johnw@gnu.org>, Nicolas Petton <nicolas@petton.fr>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: RE: Improving the presentation of Emacs user documentation
Date: Mon, 8 Feb 2016 08:22:01 -0800 (PST) [thread overview]
Message-ID: <9ff11760-cbde-41f4-ae88-55a643e629e1@default> (raw)
In-Reply-To: <m2y4avur8c.fsf@newartisans.com>
> > Couldn't we just style the HTML pages?
> > (If so, you just got a volunteer to do it)
>
> Awesome. Feel free to dig into texi2html, plus better CSS. Double bonus if
> it looks great in eww and on mobile.
On this topic, and not contradicting what others have said AFAIK, this is
my thought:
It would be good to start with _accessibility_ and only later go on to
visual styling, making sure that it doesn't mess up accessibility.
Starting with making things look cool, if paying no attention to at least
minimal accessibility concerns, is not particularly stylish or cool. ;-)
(Just one opinion.)
next prev parent reply other threads:[~2016-02-08 16:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 23:19 Improving the presentation of Emacs user documentation John Wiegley
2016-02-08 2:49 ` Xue Fuqiao
2016-02-08 2:55 ` Xue Fuqiao
2016-02-08 8:22 ` Andreas Röhler
2016-02-08 13:02 ` Richard Stallman
2016-02-08 13:12 ` Nicolas Petton
2016-02-08 14:27 ` Stefan Monnier
2016-02-08 16:00 ` John Wiegley
2016-02-08 16:22 ` Drew Adams [this message]
2016-02-08 16:43 ` Marcin Borkowski
2016-02-08 16:44 ` Marcin Borkowski
2016-02-08 16:55 ` Nicolas Petton
2016-02-08 17:04 ` Drew Adams
2016-02-08 16:54 ` Nicolas Petton
2016-02-09 12:13 ` Richard Stallman
2016-02-09 13:16 ` Nicolas Petton
2016-02-08 14:23 ` Stefan Monnier
2016-02-08 14:34 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2016-02-10 11:18 Julius Pfrommer
2016-02-11 18:17 ` Richard Stallman
2016-02-11 18:23 ` Marcin Borkowski
2016-02-11 21:12 ` Eli Zaretskii
2016-02-12 12:34 ` Richard Stallman
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=9ff11760-cbde-41f4-ae88-55a643e629e1@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=nicolas@petton.fr \
--cc=rms@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.