From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Cleaning up the books page |
Date: | 2023-07-17 11:23:47 |
Message-ID: | BC1764D6-5739-4C54-B34D-E956905FC963@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> On 17 Jul 2023, at 13:07, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2023-Jul-17, Daniel Gustafsson wrote:
>
>> While adding the latest books to the books page I (re-)realized how much cruft
>> that page has accumulated. A lot of books have links which are dead, some are
>> listed multiple times in different editions, and many of them cover long since
>> EOL version of postgres. On top of that, the indentation is quite creative.
>>
>> The attached set cleans up that page to make the content IMO more relevant and
>> helpful to our users. As we've never claimed to have a complete list of all
>> books ever published, keeping the old stuff on-line has no historical interest
>> since Google, Amazon and others do a much better job at keeping such things
>> available.
>
> I don't object to your cleanups, but would it make more sense to move
> the book listing to the pgweb database instead?
I think that would make a lot of sense, and is a good next step once the data
(and markup) is reasonably clean. Even better if we can make it such that new
books are submitted to the backend with moderator approval like
announce/organizations, but I don't know Django well enough to know how much
work that would be.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2023-07-17 11:26:30 | Re: Cleaning up the books page |
Previous Message | Alvaro Herrera | 2023-07-17 11:07:20 | Re: Cleaning up the books page |