Re: Usability ideas: text width and headers that are links - Mailing list pgsql-docs

From Maciek Sakrejda
Subject Re: Usability ideas: text width and headers that are links
Date
Msg-id CAOtHd0C+HObo78n2c7MeYCrTVKwoK2VqZ-m1t_s7fXqKKbTvAQ@mail.gmail.com
Whole thread Raw
In response to Re: Usability ideas: text width and headers that are links  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-docs
On Mon, Nov 7, 2022 at 1:41 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> On 2022-Oct-21, Niels Bom wrote:
> > Setting a max-width on regular textual content is good for
> > readability, which in turn increases accessibility. See this W3C a11y
> > documentation (1) and an a11y page by the US government (2) for more
> > detailed info.
> >
> > Using the CSS max-width property makes narrower sizes possible (for
> > smaller screens) but sets an upper limit. The newer `ch` unit in CSS
> > is a good-enough approximation of the average width of a character.
> > I've seen 66ch as the "ideal" width for regular text. For the docs
> > code examples need to have enough width too of course. But we can have
> > those be wider than their containing element if need be.
>
> +1 for this idea.  (I often open multiple windows just so that I end up
> with the right width in the one containing text to read, as a substitute
> for this.)

For what it's worth, I've also often wished for a max-width on the
docs. Another +1.

66ch ends up rather stark, though: I think we should go with something
considerably wider.



pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possibly Incorrect Data Return
Next
From: "David G. Johnston"
Date:
Subject: Re: 64.4.2. Bottom-up Index Deletion