From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Axel Beckert" <abe@deuxchevaux.org>,
"David Wales" <daviewales@disroot.org>
Cc: zsh-workers@zsh.org
Subject: Re: CSS for Zsh website?
Date: Thu, 03 Mar 2022 18:23:33 -0500 [thread overview]
Message-ID: <53018a28-cbdc-497d-af96-e3fbbf9c4d61@www.fastmail.com> (raw)
In-Reply-To: <20220303223727.m6ta53ljytlnxfjz@sym.noone.org>
On Thu, Mar 3, 2022, at 5:37 PM, Axel Beckert wrote:
> Hi,
>
> On Thu, Mar 03, 2022 at 12:08:11AM +1100, David Wales wrote:
>> max-width: 80ch;
>
> Please don't artificially restrict the width of text on websites for
> no need! This is a waste of screen space. Please leave it to the user
> if a restriction of text width is needed or not.
Hard disagree. Legibility decreases with line length.
https://practicaltypography.com/page-margins.html#on-the-web
> Additionally, I'd leave the decision of serif vs sans-serif to the
> user. (And reading normal text is usually easier to read with serif
> fonts.)
If everything is just going to degrade to "let the user decide",
then there's not much point in adding CSS at all.
--
vq
next prev parent reply other threads:[~2022-03-03 23:31 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
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 [this message]
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=53018a28-cbdc-497d-af96-e3fbbf9c4d61@www.fastmail.com \
--to=larryv@zsh.org \
--cc=abe@deuxchevaux.org \
--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).