help / color / mirror / code / Atom feed
From: Clinton Bunch <cdbunch@zentaur.org>
To: zsh-workers@zsh.org
Subject: Re: CSS for Zsh website?
Date: Thu, 10 Mar 2022 15:30:46 -0600	[thread overview]
Message-ID: <d73d3f9c-c469-85ad-afd5-d7f5cbd7e6c3@zentaur.org> (raw)
In-Reply-To: <441ea678-3832-430f-af31-8d59bf9af22e@www.fastmail.com>

On 3/10/2022 3:12 PM, Lawrence Velázquez wrote:
> On Thu, Mar 10, 2022, at 12:17 PM, Clinton Bunch wrote:
>> A web page should mostly be left in the hands of the user
> A nice thought, but in practice the vast majority of users only
> ever see the defaults chosen by the website author.
But some don't, like people who prefer dark backgrounds or need a 15pt 
font to read.  Browsers have customizable defaults for a reason.  
Overriding those should require a reason other than it's what I like.
>> 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.
> I do not think projecting the sensibilities of an operating system
> onto a website is a recipe for making a good website.

Flexibility is a key and often overlooked aspect to a website. People 
have different width screens, so setting things in pixel (or character) 
widths can make a web page look like crap.  It's quite frustrating when 
a website says "Best viewed at 1024x768" or some such.

What fancy design do you see the Zsh Website needing?  Drop down menus?  
Floating ads?  The fanciest thing I can see us needing is a side bar 
with a width set in ems.  We don't need to control every aspect of the 
user experience to get our message out there.

  reply	other threads:[~2022-03-10 21: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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d73d3f9c-c469-85ad-afd5-d7f5cbd7e6c3@zentaur.org \
    --to=cdbunch@zentaur.org \
    --cc=zsh-workers@zsh.org \


* 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


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).