From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "David Wales" <daviewales@disroot.org>, zsh-workers@zsh.org
Subject: Re: CSS for Zsh website?
Date: Thu, 03 Mar 2022 11:19:48 +0000 [thread overview]
Message-ID: <8cc569f1-106d-4495-96b4-bd3fd92d430a@www.fastmail.com> (raw)
In-Reply-To: <19afce8d-8efe-5d9b-2fce-e0cabbf6d768@disroot.org>
David Wales wrote on Wed, 02 Mar 2022 13:08 +00:00:
> I noticed that the Zsh website and user guide don't have any CSS.
> I've come up with a minimal bit of CSS which makes a big difference,
> especially for the user guide:
>
What URL specifically do you mean? "The user guide" could be referring
to either of several documents:
https://zsh.sourceforge.io/Doc/
https://zsh.sourceforge.io/FAQ/
https://zsh.sourceforge.io/Guide/
https://zsh.sourceforge.io/Intro/
> body {
> margin: auto;
> max-width: 80ch;
> font-family: Arial, sans-serif;
> padding: 5px;
> }
>
> pre {
> overflow: auto;
> }
>
> I think this makes the user guide look much more modern and readable.
I use the equivalent of max-width with man(1) [1], so that one certainly
sounds reasonable to me.
However, I wonder whether we're reinventing a wheel here. There ought
to be a manual out there whose CSS we can simply borrow (with
attribution, subject to license, etc., of course). E.g., skimming
Python's docs' CSS, they seem to set max-width differently for wide and
narrow displays. Reusing someone else's CSS would mean we won't have
to think about such issues.
> I've set my browser to auto-inject it on the Zsh pages, but thought I
> should share it in case there's interest to include it the website.
>
Thanks!
> Is there a preference for no CSS? Or is this something the Zsh web
> maintainers would consider including, especially for the user guide?
As pws says, I think it's just that no one ever got around to styling
the HTML.
The HTML is compiled from yodl/texinfo, so we'll want to do this the
right way and patch the build scripts to add CSS. The code for this
should be in zsh.git:Doc/Makefile.in or zsh-web.git:**/Makefile, depending
on what "user guide" referred to.
Cheers,
Daniel
[1] on Linux: MANWIDTH=80 man --no-hyphenation
next prev parent reply other threads:[~2022-03-03 11:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 13:08 David Wales
2022-03-02 14:26 ` Peter Stephenson
2022-03-03 11:19 ` Daniel Shahaf [this message]
2022-03-03 22:15 ` David Wales
2022-03-04 13:12 ` Daniel Shahaf
2022-03-05 8:47 ` David Wales
2022-03-10 15:37 ` Vincent Lefevre
2022-03-10 16:23 ` Vin Shelton
2022-03-10 16:31 ` Peter Stephenson
2022-03-10 17:17 ` Clinton Bunch
2022-03-10 21:12 ` Lawrence Velázquez
2022-03-10 21:30 ` Clinton Bunch
2022-03-10 21:39 ` Bart Schaefer
2022-03-10 22:43 ` Vin Shelton
2022-03-10 23:26 ` Lawrence Velázquez
2022-03-10 19:20 ` Vin Shelton
2022-03-03 23:27 ` Lawrence Velázquez
2022-03-03 22:37 ` Axel Beckert
2022-03-03 23:23 ` Lawrence Velázquez
2022-03-04 0:12 ` Bart Schaefer
2022-03-04 2:44 ` Lawrence Velázquez
2022-03-04 13:26 ` Daniel Shahaf
2022-03-05 6:34 ` Lawrence Velázquez
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=8cc569f1-106d-4495-96b4-bd3fd92d430a@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--cc=daviewales@disroot.org \
--cc=zsh-workers@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).