Обсуждение: Update to docs root pages and navigation
I think it requires a silly number of steps to get to our documentation today. It's not huge, but it's "click documentation, click "current manuals", click 13". And the actual /docs/ page is mostly empty, which makes it a waste. PFA a patch that changes this: * The /docs/ page now gets direct links to all supported documentation versions, including PDFs * The /docs/ page gets a big button that sends you directly to /docs/current/ -- that link wasn't available at all before * Translated manuals were listed both on the left and right sidebar on the root docs page, but not on the manuals page. Remove them from the left sidebar, leave them on the right one since it's now on the root docs page. Unrelated to the restructuring, but while at it: * Make the left column in the manuals table not take 50% of the width when all it has is a number * Add a link to the developer docs * Remove the repetitive "comprehensive manual" text (it's no more comprehensive than the other manual, it's just a different format), and insert a proper separator between the two PDF versions * Remove some redundant and incorrect template tags probably resulting from previous copy/paste mistakes I'm also attaching a screenshot of the main docs page with the changes, for those that can't easily test a website patch. (Nevermind the actual versions listed, as this is off a dev version of the database and not up to date) Thoughts? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
Вложения
On Mon, Nov 23, 2020 at 05:01:10PM +0100, Magnus Hagander wrote: > I'm also attaching a screenshot of the main docs page with the > changes, for those that can't easily test a website patch. (Nevermind > the actual versions listed, as this is off a dev version of the > database and not up to date) Yes, this makes a lot of sense. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
On Mon, Nov 23, 2020 at 9:08 AM Bruce Momjian <bruce@momjian.us> wrote:
On Mon, Nov 23, 2020 at 05:01:10PM +0100, Magnus Hagander wrote:
> I'm also attaching a screenshot of the main docs page with the
> changes, for those that can't easily test a website patch. (Nevermind
> the actual versions listed, as this is off a dev version of the
> database and not up to date)
Yes, this makes a lot of sense.
+many
This is a larger complaint than this patch should resolve but I find that having links to other resources only appear in the Quick Links sidebar makes them very easy to overlook. Adding a small blurb informing the reader of the existence of additional pages and pointing out the sidebar would improve usability IMO. For the documentation page I'd add that blurb between the button and the manuals section. The "What will you find here?" on the Developers page is a good example.
David J.
On 11/23/20 8:01 AM, Magnus Hagander wrote: > I think it requires a silly number of steps to get to our > documentation today. It's not huge, but it's "click documentation, > click "current manuals", click 13". And the actual /docs/ page is > mostly empty, which makes it a waste. > > PFA a patch that changes this: > > * The /docs/ page now gets direct links to all supported documentation > versions, including PDFs > > * The /docs/ page gets a big button that sends you directly to > /docs/current/ -- that link wasn't available at all before > > * Translated manuals were listed both on the left and right sidebar on > the root docs page, but not on the manuals page. Remove them from the > left sidebar, leave them on the right one since it's now on the root > docs page. > > Unrelated to the restructuring, but while at it: > * Make the left column in the manuals table not take 50% of the width > when all it has is a number > > * Add a link to the developer docs > > * Remove the repetitive "comprehensive manual" text (it's no more > comprehensive than the other manual, it's just a different format), > and insert a proper separator between the two PDF versions > > * Remove some redundant and incorrect template tags probably resulting > from previous copy/paste mistakes > > I'm also attaching a screenshot of the main docs page with the > changes, for those that can't easily test a website patch. (Nevermind > the actual versions listed, as this is off a dev version of the > database and not up to date) > > Thoughts? > +1 -- Adrian Klaver adrian.klaver@aklaver.com
Greetings, * Magnus Hagander (magnus@hagander.net) wrote: > I think it requires a silly number of steps to get to our > documentation today. It's not huge, but it's "click documentation, > click "current manuals", click 13". And the actual /docs/ page is > mostly empty, which makes it a waste. +many Thanks, Stephen
Вложения
On 11/23/20 11:01 AM, Magnus Hagander wrote: > I think it requires a silly number of steps to get to our > documentation today. It's not huge, but it's "click documentation, > click "current manuals", click 13". And the actual /docs/ page is > mostly empty, which makes it a waste. > > PFA a patch that changes this: > > * The /docs/ page now gets direct links to all supported documentation > versions, including PDFs > > * The /docs/ page gets a big button that sends you directly to > /docs/current/ -- that link wasn't available at all before I would bikeshed the text on this slightly, perhaps: "Current Documentation" or "Latest Documentation". I'd be ok with "View Current Documentation" as well. > > * Translated manuals were listed both on the left and right sidebar on > the root docs page, but not on the manuals page. Remove them from the > left sidebar, leave them on the right one since it's now on the root > docs page. > > Unrelated to the restructuring, but while at it: > * Make the left column in the manuals table not take 50% of the width > when all it has is a number > > * Add a link to the developer docs > > * Remove the repetitive "comprehensive manual" text (it's no more > comprehensive than the other manual, it's just a different format), > and insert a proper separator between the two PDF versions > > * Remove some redundant and incorrect template tags probably resulting > from previous copy/paste mistakes > > I'm also attaching a screenshot of the main docs page with the > changes, for those that can't easily test a website patch. (Nevermind > the actual versions listed, as this is off a dev version of the > database and not up to date) I could not verify the PDF changes as I don't have them built locally at the moment, but everything else looks fine. +1, Jonathan
Вложения
On 2020-Nov-23, Magnus Hagander wrote: > I'm also attaching a screenshot of the main docs page with the > changes, for those that can't easily test a website patch. (Nevermind > the actual versions listed, as this is off a dev version of the > database and not up to date) .. I find it a bit annoying that if I want the current docs, I have to avoid looking at the table, or I'll get confused until I see the button sitting above. IMO it would be better to include "13" in the table as well as the button to avoid this effect (I realize this is redundant). Maybe if the button had red text that said "13" it would not be necessary. Alternatively: remove the button, include "13" in the table, and have it contain a blue tag-looking label that says "current" or something like that. (While at it, and to make the current dev cycle less of an exception: change the "Development version" row to have text "14dev" in red plus a blue label that says "In development".)
On 11/23/20 4:24 PM, Alvaro Herrera wrote: > On 2020-Nov-23, Magnus Hagander wrote: > >> I'm also attaching a screenshot of the main docs page with the >> changes, for those that can't easily test a website patch. (Nevermind >> the actual versions listed, as this is off a dev version of the >> database and not up to date) > > .. I find it a bit annoying that if I want the current docs, I have to > avoid looking at the table, or I'll get confused until I see the button > sitting above. IMO it would be better to include "13" in the table as > well as the button to avoid this effect (I realize this is redundant). I think that has to do with the data on Magnus' machine -- it should load 13 in the table. Jonathan
Вложения
On 2020-Nov-23, Jonathan S. Katz wrote: > On 11/23/20 4:24 PM, Alvaro Herrera wrote: > > On 2020-Nov-23, Magnus Hagander wrote: > > > >> I'm also attaching a screenshot of the main docs page with the > >> changes, for those that can't easily test a website patch. (Nevermind > >> the actual versions listed, as this is off a dev version of the > >> database and not up to date) > > > > .. I find it a bit annoying that if I want the current docs, I have to > > avoid looking at the table, or I'll get confused until I see the button > > sitting above. IMO it would be better to include "13" in the table as > > well as the button to avoid this effect (I realize this is redundant). > > I think that has to do with the data on Magnus' machine -- it should > load 13 in the table. Oh! Never mind that, then.
On Mon, Nov 23, 2020 at 2:24 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2020-Nov-23, Magnus Hagander wrote:
> I'm also attaching a screenshot of the main docs page with the
> changes, for those that can't easily test a website patch. (Nevermind
> the actual versions listed, as this is off a dev version of the
> database and not up to date)
.. I find it a bit annoying that if I want the current docs, I have to
avoid looking at the table, or I'll get confused until I see the button
sitting above. IMO it would be better to include "13" in the table as
well as the button to avoid this effect (I realize this is redundant).
Maybe if the button had red text that said "13" it would not be
necessary.
Alternatively: remove the button, include "13" in the table, and have it
contain a blue tag-looking label that says "current" or something like
that. (While at it, and to make the current dev cycle less of an
exception: change the "Development version" row to have text "14dev" in
red plus a blue label that says "In development".)
FWIW I noticed this to, the re-read the email and noticed:
"(Nevermind the actual versions listed, as this is off a dev version of the
database and not up to date)"And figured the two were related.
An idea while I'm here - It is still a couple of clicks and screen searching to get to the current docs. How about an icon on the main page, next to the search icon (more useful for frequent users), that takes you immediately to the current documentation webpage? And/Or a third button in the banner (download, new?) for "Current Manual" (more useful for newer readers)?
David J.
On Mon, Nov 23, 2020 at 10:33 PM David G. Johnston <david.g.johnston@gmail.com> wrote: > > On Mon, Nov 23, 2020 at 2:24 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: >> >> On 2020-Nov-23, Magnus Hagander wrote: >> >> > I'm also attaching a screenshot of the main docs page with the >> > changes, for those that can't easily test a website patch. (Nevermind >> > the actual versions listed, as this is off a dev version of the >> > database and not up to date) >> >> .. I find it a bit annoying that if I want the current docs, I have to >> avoid looking at the table, or I'll get confused until I see the button >> sitting above. IMO it would be better to include "13" in the table as >> well as the button to avoid this effect (I realize this is redundant). >> >> Maybe if the button had red text that said "13" it would not be >> necessary. >> >> Alternatively: remove the button, include "13" in the table, and have it >> contain a blue tag-looking label that says "current" or something like >> that. (While at it, and to make the current dev cycle less of an >> exception: change the "Development version" row to have text "14dev" in >> red plus a blue label that says "In development".) >> > > FWIW I noticed this to, the re-read the email and noticed: > > "(Nevermind the actual versions listed, as this is off a dev version of the > database and not up to date)" > > And figured the two were related. That is indeed exactly what I was referring to :) > An idea while I'm here - It is still a couple of clicks and screen searching to get to the current docs. How about anicon on the main page, next to the search icon (more useful for frequent users), that takes you immediately to the currentdocumentation webpage? And/Or a third button in the banner (download, new?) for "Current Manual" (more useful fornewer readers)? Yeah, it makes sense to do something like that, I agree. I'll take a look at that as a separate patch later, and post a separate proposal. //Magnus
On Mon, Nov 23, 2020 at 6:23 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > > On 11/23/20 11:01 AM, Magnus Hagander wrote: > > I think it requires a silly number of steps to get to our > > documentation today. It's not huge, but it's "click documentation, > > click "current manuals", click 13". And the actual /docs/ page is > > mostly empty, which makes it a waste. > > > > PFA a patch that changes this: > > > > * The /docs/ page now gets direct links to all supported documentation > > versions, including PDFs > > > > * The /docs/ page gets a big button that sends you directly to > > /docs/current/ -- that link wasn't available at all before > > I would bikeshed the text on this slightly, perhaps: "Current > Documentation" or "Latest Documentation". > > I'd be ok with "View Current Documentation" as well. I had that first, but then realized that we have least previously separated out "documentation" (all of it) from "Manuals" (explicitly the stuff built from the SGML sources). I didn't want to change that terminology as part of a restructure, as it would probably have effects on other places too. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
On 11/23/20 5:49 PM, Magnus Hagander wrote: > On Mon, Nov 23, 2020 at 6:23 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: >> >> On 11/23/20 11:01 AM, Magnus Hagander wrote: >>> I think it requires a silly number of steps to get to our >>> documentation today. It's not huge, but it's "click documentation, >>> click "current manuals", click 13". And the actual /docs/ page is >>> mostly empty, which makes it a waste. >>> >>> PFA a patch that changes this: >>> >>> * The /docs/ page now gets direct links to all supported documentation >>> versions, including PDFs >>> >>> * The /docs/ page gets a big button that sends you directly to >>> /docs/current/ -- that link wasn't available at all before >> >> I would bikeshed the text on this slightly, perhaps: "Current >> Documentation" or "Latest Documentation". >> >> I'd be ok with "View Current Documentation" as well. > > I had that first, but then realized that we have least previously > separated out "documentation" (all of it) from "Manuals" (explicitly > the stuff built from the SGML sources). I didn't want to change that > terminology as part of a restructure, as it would probably have > effects on other places too. "Current Manual", "Latest Manual", or "View Current Manual" then :) Jonathan
Вложения
On Tue, Nov 24, 2020 at 12:03 AM Jonathan S. Katz <jkatz@postgresql.org> wrote: > > On 11/23/20 5:49 PM, Magnus Hagander wrote: > > On Mon, Nov 23, 2020 at 6:23 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > >> > >> On 11/23/20 11:01 AM, Magnus Hagander wrote: > >>> I think it requires a silly number of steps to get to our > >>> documentation today. It's not huge, but it's "click documentation, > >>> click "current manuals", click 13". And the actual /docs/ page is > >>> mostly empty, which makes it a waste. > >>> > >>> PFA a patch that changes this: > >>> > >>> * The /docs/ page now gets direct links to all supported documentation > >>> versions, including PDFs > >>> > >>> * The /docs/ page gets a big button that sends you directly to > >>> /docs/current/ -- that link wasn't available at all before > >> > >> I would bikeshed the text on this slightly, perhaps: "Current > >> Documentation" or "Latest Documentation". > >> > >> I'd be ok with "View Current Documentation" as well. > > > > I had that first, but then realized that we have least previously > > separated out "documentation" (all of it) from "Manuals" (explicitly > > the stuff built from the SGML sources). I didn't want to change that > > terminology as part of a restructure, as it would probably have > > effects on other places too. > > "Current Manual", "Latest Manual", or "View Current Manual" then :) Oh, I thought your issue with it was specifically the use of the word Manual and not Documentation :) While that may be further nitpicking, but those aren't correct are they? That is, *all* the manuals we put up are the current (or latest) ones, they're just for different versions. Even in our archive we only keep the very latest ones for each version, not actually older manuals. So "current" is only really correct if it also includes "version".. I assume what you were after, without saying so, was to make it shorter? We could make it just "current version", but I'm not sure that's really an improvement? Or just "view the manual" and assume that anybody who actually cares about a specific version will go directly to the table, maybe with an ingress text of "To view the manual for an older version, pick your version in the table below" above the table? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net> wrote: > Or just "view the manual" and assume that anybody who actually cares > about a specific version will go directly to the table, maybe with an > ingress text of "To view the manual for an older version, pick your > version in the table below" above the table? +1 cheers ./daniel
On 11/24/20 4:55 AM, Daniel Gustafsson wrote: >> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net> wrote: > >> Or just "view the manual" and assume that anybody who actually cares >> about a specific version will go directly to the table, maybe with an >> ingress text of "To view the manual for an older version, pick your >> version in the table below" above the table? > > +1 Sure, that works. Jonathan
Вложения
On Tue, Nov 24, 2020 at 5:15 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > > On 11/24/20 4:55 AM, Daniel Gustafsson wrote: > >> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net> wrote: > > > >> Or just "view the manual" and assume that anybody who actually cares > >> about a specific version will go directly to the table, maybe with an > >> ingress text of "To view the manual for an older version, pick your > >> version in the table below" above the table? > > > > +1 > > Sure, that works. Thanks, I've pushed this version. For the suggested changes to the frontpage, I suggest the attached. Or should it link directly to the /docs/current/ url? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
Вложения
On 11/24/20 11:27 AM, Magnus Hagander wrote: > On Tue, Nov 24, 2020 at 5:15 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: >> >> On 11/24/20 4:55 AM, Daniel Gustafsson wrote: >>>> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net> wrote: >>> >>>> Or just "view the manual" and assume that anybody who actually cares >>>> about a specific version will go directly to the table, maybe with an >>>> ingress text of "To view the manual for an older version, pick your >>>> version in the table below" above the table? >>> >>> +1 >> >> Sure, that works. > > Thanks, I've pushed this version. > > For the suggested changes to the frontpage, I suggest the attached. > > Or should it link directly to the /docs/current/ url? +1 for just /docs/ -- good for all users. If we're adding the documentation button there to the homepage, I would drop the "New to PostgreSQL" button from it. We have a section on "New to PostgreSQL" just below there, and it is still above the proverbial fold (at least on a non-mobile device). Jonathan
Вложения
On Tue, Nov 24, 2020 at 5:29 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > > On 11/24/20 11:27 AM, Magnus Hagander wrote: > > On Tue, Nov 24, 2020 at 5:15 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > >> > >> On 11/24/20 4:55 AM, Daniel Gustafsson wrote: > >>>> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net> wrote: > >>> > >>>> Or just "view the manual" and assume that anybody who actually cares > >>>> about a specific version will go directly to the table, maybe with an > >>>> ingress text of "To view the manual for an older version, pick your > >>>> version in the table below" above the table? > >>> > >>> +1 > >> > >> Sure, that works. > > > > Thanks, I've pushed this version. > > > > For the suggested changes to the frontpage, I suggest the attached. > > > > Or should it link directly to the /docs/current/ url? > > +1 for just /docs/ -- good for all users. > > If we're adding the documentation button there to the homepage, I would > drop the "New to PostgreSQL" button from it. We have a section on "New > to PostgreSQL" just below there, and it is still above the proverbial > fold (at least on a non-mobile device). That's a good point -- in particular the "just below" part. So yeah, let's drop that one. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
On Tue, Nov 24, 2020 at 9:29 AM Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 11/24/20 11:27 AM, Magnus Hagander wrote:
> On Tue, Nov 24, 2020 at 5:15 PM Jonathan S. Katz <jkatz@postgresql.org> wrote:
>>
>> On 11/24/20 4:55 AM, Daniel Gustafsson wrote:
>>>> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net> wrote:
>>>
>>>> Or just "view the manual" and assume that anybody who actually cares
>>>> about a specific version will go directly to the table, maybe with an
>>>> ingress text of "To view the manual for an older version, pick your
>>>> version in the table below" above the table?
>>>
>>> +1
>>
>> Sure, that works.
>
> Thanks, I've pushed this version.
>
> For the suggested changes to the frontpage, I suggest the attached.
>
> Or should it link directly to the /docs/current/ url?
+1 for just /docs/ -- good for all users.
If it doesn't go directly to /current I don't think including it is worthwhile - the main navigation gets you to the full page.
All users benefit from reading the current version documentation even if they are running older versions.
David J.
On 11/24/20 12:30 PM, David G. Johnston wrote: > On Tue, Nov 24, 2020 at 9:29 AM Jonathan S. Katz <jkatz@postgresql.org > <mailto:jkatz@postgresql.org>> wrote: > > On 11/24/20 11:27 AM, Magnus Hagander wrote: > > On Tue, Nov 24, 2020 at 5:15 PM Jonathan S. Katz > <jkatz@postgresql.org <mailto:jkatz@postgresql.org>> wrote: > >> > >> On 11/24/20 4:55 AM, Daniel Gustafsson wrote: > >>>> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net > <mailto:magnus@hagander.net>> wrote: > >>> > >>>> Or just "view the manual" and assume that anybody who actually > cares > >>>> about a specific version will go directly to the table, maybe > with an > >>>> ingress text of "To view the manual for an older version, pick your > >>>> version in the table below" above the table? > >>> > >>> +1 > >> > >> Sure, that works. > > > > Thanks, I've pushed this version. > > > > For the suggested changes to the frontpage, I suggest the attached. > > > > Or should it link directly to the /docs/current/ url? > > +1 for just /docs/ -- good for all users. > > > If it doesn't go directly to /current I don't think including it is > worthwhile - the main navigation gets you to the full page. > > All users benefit from reading the current version documentation even if > they are running older versions. Except that /docs/current/ does not contain links to the translations, nor the PDFs. The docs root page also contains links to other materials as well that serve as documentation. Jonathan
Вложения
On Tue, Nov 24, 2020 at 10:42 AM Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 11/24/20 12:30 PM, David G. Johnston wrote:
> On Tue, Nov 24, 2020 at 9:29 AM Jonathan S. Katz <jkatz@postgresql.org
> <mailto:jkatz@postgresql.org>> wrote:
>
> On 11/24/20 11:27 AM, Magnus Hagander wrote:
> > On Tue, Nov 24, 2020 at 5:15 PM Jonathan S. Katz
> <jkatz@postgresql.org <mailto:jkatz@postgresql.org>> wrote:
> >>
> >> On 11/24/20 4:55 AM, Daniel Gustafsson wrote:
> >>>> On 24 Nov 2020, at 10:45, Magnus Hagander <magnus@hagander.net
> <mailto:magnus@hagander.net>> wrote:
> >>>
> >>>> Or just "view the manual" and assume that anybody who actually
> cares
> >>>> about a specific version will go directly to the table, maybe
> with an
> >>>> ingress text of "To view the manual for an older version, pick your
> >>>> version in the table below" above the table?
> >>>
> >>> +1
> >>
> >> Sure, that works.
> >
> > Thanks, I've pushed this version.
> >
> > For the suggested changes to the frontpage, I suggest the attached.
> >
> > Or should it link directly to the /docs/current/ url?
>
> +1 for just /docs/ -- good for all users.
>
>
> If it doesn't go directly to /current I don't think including it is
> worthwhile - the main navigation gets you to the full page.
>
> All users benefit from reading the current version documentation even if
> they are running older versions.
Except that /docs/current/ does not contain links to the translations,
nor the PDFs. The docs root page also contains links to other materials
as well that serve as documentation.
Have the button read:
"Current English Web Manual"
?
Someone who doesn't want that can click "Documentation" in the navigation.
David J.
On 11/24/20 12:48 PM, David G. Johnston wrote: > On Tue, Nov 24, 2020 at 10:42 AM Jonathan S. Katz <jkatz@postgresql.org > <mailto:jkatz@postgresql.org>> wrote: > > On 11/24/20 12:30 PM, David G. Johnston wrote: > > On Tue, Nov 24, 2020 at 9:29 AM Jonathan S. Katz > <jkatz@postgresql.org <mailto:jkatz@postgresql.org> > > <mailto:jkatz@postgresql.org <mailto:jkatz@postgresql.org>>> wrote: > > > > On 11/24/20 11:27 AM, Magnus Hagander wrote: > > > For the suggested changes to the frontpage, I suggest the > attached. > > > > > > Or should it link directly to the /docs/current/ url? > > > > +1 for just /docs/ -- good for all users. > > > > > > If it doesn't go directly to /current I don't think including it is > > worthwhile - the main navigation gets you to the full page. > > > > All users benefit from reading the current version documentation > even if > > they are running older versions. > > Except that /docs/current/ does not contain links to the translations, > nor the PDFs. The docs root page also contains links to other materials > as well that serve as documentation. > > > Have the button read: > > "Current English Web Manual" > > ? > > Someone who doesn't want that can click "Documentation" in the navigation. I poked around some other examples from OSS projects around, and it does appear their homepage links tend to go to the equivalent of the "current" documentation (though some make it easier to get to translations, etc. from within the current documentation). So this appears to be an acceptable workflow. However, now that we'd be giving the "Documentation" URL prominent real-estate on the home page, and given we made the Documentation root page much more readable / navigable, I think we do our users a slight disservice by putting them in the latest manual. First, there tends to be a delay when users start running the latest PostgreSQL, supported by traffic numbers. And again, there are all sorts of resources on the documentation root page beyond just the manual. It also helps to ensure a consistent workflow, whether you click on the "Documentation" button on the homepage or the top bar. This also coincides with the present verbiage we have on the site, where "documentation" is the collection of manuals, books, resources, etc. Anyway, I won't strongly object if the final decision is "/docs/current/" as I don't have sufficient quantitative data to do so, however, I would still +1 "/docs/" Jonathan
Вложения
On Tue, Nov 24, 2020 at 01:02:28PM -0500, Jonathan Katz wrote: > However, now that we'd be giving the "Documentation" URL prominent > real-estate on the home page, and given we made the Documentation root Are there any other places on our website where the main text really just references a sidebar, as our docs used to do? -- Bruce Momjian <bruce@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee