Documentation pages are down

[jbotuck]

Describe the issue
readme.md references https://jdbc.postgresql.org/documentation/head/ which is returning 404 for me. Half the doc links returned by google are returning 404

To Reproduce
Steps to reproduce the behaviour:
hit https://jdbc.postgresql.org/documentation/head/ in a browser

Expected behaviour
page loads with status of 200

[davecramer]

https://jdbc.postgresql.org/documentation/

[davecramer]

Readme has been updated. Which pages are missing ?

[davecramer]

This is sort of a soft launch of our new website. Thanks for finding the bug so fast :)

[jbotuck]

where's the javadoc?

[jbotuck]

https://jdbc.postgresql.org/documentation/reading/ has a link to docs for further reading. The link is less than helpful

[jbotuck]

https://jdbc.postgresql.org/index.html has a link on the bottom to publicapi which returns 404

[davecramer]

https://jdbc.postgresql.org/index.html has a link on the bottom to publicapi which returns 404

fixed

[davecramer]

https://jdbc.postgresql.org/documentation/reading/ has a link to docs for further reading. The link is less than helpful

Yes, saw that... thanks

[jbotuck]

Also, consider somehow taking all the old links that are now returning 404, and turn them into redirects. You might be able to unbreak Google and stack overflow links

[davecramer]

Also, consider somehow taking all the old links that are now returning 404, and turn them into redirects. You might be able to unbreak Google and stack overflow links

Interesting... Might be able to do it on the site, but not individual links

[ianjevans]

Another vote to add at least site-level redirects when totally refactoring your docs pages. The CockroachDB docs have a fair number of links into your docs that we recently discovered are now broken.

[davecramer]

Feel free to provide me with a PR.

[ianjevans]

I don't know your publishing pipeline or deployment environment for your doc site. That level of configuration is not checked into this code repo anyway, so even if I engaged with your suggestion at face value I wouldn't be able to proceed.

I see on Twitter that you were upset about my comment, which was intended to help external users of your docs find the info that they need, NOT to fix our own docs. Broken links from non-commercial blog posts, forum posts, Stack Exchange questions, Reddit threads, etc. are bigger issues when refactoring docs, because there's nobody to get paid to go and fix broken links, unlike our commercial docs.

[ianjevans]

As I said, I can't give you a PR, but I did take a little time to write these permanent redirect rules for you on the off chance you use Apache and mod_rewrite. I tested them with an htaccess tester. These were based on our own fixes to our commercial docs, but this might help others in the larger PostgreSQL ecosystem, I dunno.

RewriteRule "^documentation/head/connect.html" "/documentation/use/" [R=301,L]
RewriteRule "^documentation/head/query.html" "/documentation/query/" [R=301,L]
RewriteRule "^documentation/head/setup.html" "/documentation/setup/" [R=301,L]
RewriteRule "^documentation/head/ds-ds.html" "/documentation/datasource/" [R=301,L]
RewriteRule "^documentation/head/index.html" "/documentation/" [R=301,L]

[davecramer]

OK, so the simplest way is to use hugo redirects.