help / color / mirror / code / Atom feed
From: David Wales <daviewales@disroot.org>
To: Daniel Shahaf <d.s@daniel.shahaf.name>, zsh-workers@zsh.org
Subject: Re: CSS for Zsh website?
Date: Fri, 04 Mar 2022 09:15:31 +1100	[thread overview]
Message-ID: <EE206D0D-AFDC-4689-BF78-F40FDE665A9C@disroot.org> (raw)
In-Reply-To: <8cc569f1-106d-4495-96b4-bd3fd92d430a@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

>What URL specifically do you mean?  "The user guide" could be referring
>to either of several documents:

I was thinking of /Guide. However, I think the CSS is general enough to work across the whole site.

>However, I wonder whether we're reinventing a wheel here. 

Quite probably. I got a minimalist vibe from the existing site, so I tried to match that with minimalist CSS!

If there's appetite for fanciness, then adapting fancy CSS from somewhere else might work. My CSS for example will not give you fancy code boxes.

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


>[1] on Linux: MANWIDTH=80 man --no-hyphenation

I leant something new!

If there's consensus that we don't want to use my minimal CSS, and that we do want to adapt fancy CSS from a compatibly licensed project I'm happy to do a bit of research for something suitable.

[-- Attachment #2: Type: text/html, Size: 1354 bytes --]

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

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

  git send-email \
    --in-reply-to=EE206D0D-AFDC-4689-BF78-F40FDE665A9C@disroot.org \
    --to=daviewales@disroot.org \
    --cc=d.s@daniel.shahaf.name \
    --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).