From: Tom Lane <tgl@sss.pgh.pa.us>
To: niels@thinkiq.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Version 13 documentation layout is harder to read than version 12
In-reply-to: <160135280918.659.8300614023795573502@wrigleys.postgresql.org>
References: <160135280918.659.8300614023795573502@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Tue, 29 Sep 2020 04:13:29 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <608343.1601387551.1@sss.pgh.pa.us>
Date: Tue, 29 Sep 2020 09:52:31 -0400
Message-ID: <608344.1601387551@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> Compare:
> * https://www.postgresql.org/docs/13/functions-json.html
> * https://www.postgresql.org/docs/12/functions-json.html

> I know it is just my opinion, but the version 12 layout is easier to read
> than version 13.

IMO, table 9.47 (JSON Processing Functions) is pretty much the poster
child for why we had to redesign the table layout.  In the old layout,
it's close to unreadable in any normal-size browser window, despite
wasting lots of whitespace and having large amounts of important info
shuffled off into "Note" blocks.  The new layout is far more adaptable
to viewing windows that aren't full-screen-width; and the "Note" text has
all been merged into the table, so that you don't have to scroll down and
back to find all the info about a function.

I'll concede that it's a bit of a shock at first if you are used to the
old layout.  But the developer community has been looking at this format
for six months or so now, and I think people grew accustomed to it fairly
quickly.

			regards, tom lane