From: Clinton Bunch <cdb_zsh@zentaur.org>
To: zsh-workers@zsh.org
Subject: Re: CSS for Zsh website?
Date: Thu, 10 Mar 2022 11:17:40 -0600 [thread overview]
Message-ID: <846ae7a2-0f9e-a3ba-f37b-9cdb361e0af5@zentaur.org> (raw)
In-Reply-To: <1858778006.301177.1646929881537@mail2.virginmedia.com>
[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]
A width should be set to a percentage, not a character width, if set at
all. It really should only be set when you have sidebars you want to
display. Too many web designers are or want to be graphic designers and
want the kind of control they have on a printed page. This is why they
set white backgrounds, which look great on paper, but are like staring
into a light bulb on an LED display. That's just one example of taking
choice out of the users hands.
A web page should mostly be left in the hands of the user unless you
have specific reasons to force a certain display. Don't try to choose
the general font, don't limit the width, and don't force the foreground
and background colors for general text. And if you do set one, for
God's sake, set the other. It's one thing to set a foreground and
background to set off a certain section of text, it's another to force
the user to view it in the way that works best for *you*.
Code boxes should probably have a width set to 98%, so it doesn't
require scrolling the whole page to see the extra long lines. (Though
the writers of code should keep their code to a reasonable width and use
line continuation rather than run-on lines for readability)
We are Unix people, a platform built on flexibility. You have created
one of the most flexible shells in existence. (Which is why I've used
it for 25+ years) The website should reflect that flexibility.
On 3/10/2022 10:31 AM, Peter Stephenson wrote:
>> On 10 March 2022 at 16:23 Vin Shelton<acs@alumni.princeton.edu> wrote:
>> I routinely use fullscreen to browse the web (without custom CSS), but line
>> lengths > 100 characters are unreadable for me, so a width limitation on
>> text would make sense for me.
> For what it's worth, and without implying this is a definitive answer,
> the state of the art for this seems to be a "reader" mode in browsers.
> I clicked on the reader mode icon in Vivaldi on the randomly chosen
>
> https://zsh.sourceforge.io/Guide/zshguide02.html#l6
>
> and this seems to be doing a good job.
>
> pws
>
[-- Attachment #2: Type: text/html, Size: 2919 bytes --]
next prev parent reply other threads:[~2022-03-10 17:18 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 [this message]
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=846ae7a2-0f9e-a3ba-f37b-9cdb361e0af5@zentaur.org \
--to=cdb_zsh@zentaur.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).