I appreciate the update, but it's interesting from a design perspective how many technically amazing products have dated website design. I do appreciate not trying to force a fashionable design template onto every site, but there are some really slick minimal ones that can be used that will bring the design up to the current decade at least.
Re:PostgreSQL website – new design now live
by ken on Wednesday April 18, 2018 @08:52PM
(#16872549)
I find it quite convenient that all of the best database systems I've used (Postgres, SQLite, Redis) also have the most boring webpages, and the worst databases have the most trendy webpages.
I could have saved a lot of time, over the past 20 years, if I'd simply followed the rule: Is this the most boring webpage I've seen all week? Yes => it's going to be a good database.
Re:PostgreSQL website – new design now live
by btown on Wednesday April 18, 2018 @09:08PM
(#16872602)
One important characteristic of a database, though, is that it remains commercially supported and has developer continuity. To that end, competence in modern enterprise sales can be correlated with modern web design, no?
CockroachDB, for instance, is able to simultaneously focus on Jepsen-style distributed systems verification and agile administrative interfaces, whose design aesthetic is reflected in the website. And there are plenty of unsupported academia-made databases that are essentially abandonware. I would not advocate for overreliance on this heuristic.
Re:PostgreSQL website – new design now live
by btown on Wednesday April 18, 2018 @10:11PM
(#16872840)
Wasn't referring to Postgres at all (it's the most solid RDBMS I've worked with). And I may have been unfair to other databases - was just saying that like most tech products, there are varying degrees of business-readiness in the database space.
Re:PostgreSQL website – new design now live
by hitekker on Wednesday April 18, 2018 @11:29PM
(#16873122)
In my view, you weren't referring to Postgres. Rather, the cognitive dissonance brought on by the shortcomings of the redesign are making some supporters extra-sensitive to criticism.
Re:PostgreSQL website – new design now live
by TeMPOraL on Thursday April 19, 2018 @12:09AM
(#16873273)
> The design went from looking like 1997 to looking like 2007.
Good. I hope someone in the team was saying, "The line must be drawn here! This far, no further!" - because it's some time after 2007 when the web went entirely to shit.
Re:PostgreSQL website – new design now live
by dspillett on Wednesday April 18, 2018 @07:23PM
(#16872140)
They can't really control that as a number of external factors part into Google's rankings (i.e. links from elsewhere), other than to make navigation to the right version easy which they seem to have managed (in, my, admittedly limited, experience there is always a version selection in the page head and the links go where you'd expect).
Re:PostgreSQL website – new design now live
by codetrotter on Wednesday April 18, 2018 @10:08PM
(#16872826)
They could straight up disallow the versioned pages in their robots.txt and for the current version they could have a full copy of the docs without version number in the URL that instead has .../current/... and those pages would be allowed for crawlers to index. Then people could jump to older versions manually from there if they needed to instead of everyone having to endure the land-on-an-arbitrary-version-number-page annoyance.
That really is my only problem with the postgresql docs though and that’s saying something. The content itself of the postgresql docs is of stellar quality.
Re:PostgreSQL website – new design now live
by slavik81 on Thursday April 19, 2018 @07:07AM
(#16874853)
Blocking the pages in robots.txt will remove them from the Wayback Machine. That sucks.
Qt did that for their documentation when they changed ownership and moved their website. They didn't migrate the old documentation, either. This made updating broken links much more difficult because I couldn't easily read the pages they originally pointed to.
Re:PostgreSQL website – new design now live
by h1d on Thursday April 19, 2018 @01:05AM
(#16873458)
Not sure how exactly Google works but if you just block versioned pages out, won't they just not show up instead of somehow pulling the latest static URL in the same ranked position?
Maybe better to specify canonical URL as the latest one.
Re:PostgreSQL website – new design now live
by ximeng on Wednesday April 18, 2018 @09:54PM
(#16872761)
The above comment is one of my most upvoted ever. It's annoying to have to click twice to get to the latest version. Maybe they make it too easy to get to old versions - I don't think I've ever seen a link to Wikipedia that points to an old version of a page.
Not saying this is an easy problem to solve, and the documentation is mostly pretty great, but this definitely bugs me and apparently a bunch of other people too.
Re:PostgreSQL website – new design now live
by marcosdumay on Wednesday April 18, 2018 @10:21PM
(#16872874)
Old Wikipedia pages are just dated and not useful as a starting point. Documentation for old versions of Postgres are the most up to date page for anybody using that version.
I am one of the people that gave you an upvote, but this is not a fair comparison at all.
Re:PostgreSQL website – new design now live
by ximeng on Wednesday April 18, 2018 @10:33PM
(#16872921)
Not aiming to be unfair to postgres - it's not an easy problem and the documentation is great, and it is different to Wikipedia where old content is generally objectively worse.
I guess for postgres 80% of people would be happy with always landing on the current version, and making an extra click or adding a version to their search if they really need documentation for older versions. Maybe adding a brief version history at the bottom of documentation pages would reduce the need for old versions even further.
Re:PostgreSQL website – new design now live
by kingbirdy on Wednesday April 18, 2018 @10:55PM
(#16873016)
I think a solution might be to make links to the latest version redirect to a v/latest/ which redirects to the new latest version across upgrades. For each url v/1.2/docs if 1.2 is the new version, then it redirects to v/latest/docs and when copy-pasted to e.g. stack overflow, when someone comes along later when it's in version 1.5, it serves the v1.5 docs. So the latest Google crawl will see mostly v/latest/docs links, it will always serve those at the top of search results for docs, and then no matter what those search results at the latest version of docs.
Re:PostgreSQL website – new design now live
by jimktrains2 on Friday April 20, 2018 @11:04AM
(#16885339)
I wonder if this could be "done" or managed in some way using a sitemap or via google's site search admin (I forget its exact name). Using robots to disallow old versions seems like an awfully big hammer.
Re:PostgreSQL website – new design now live
by siruncledrew on Wednesday April 18, 2018 @11:24PM
(#16873112)
Idk, the examples are really the best part of the documentation to me personally, but they are all the way at the bottom of the page. The description and options sections just remind me of man pages. I would prefer more of a readthedocs style.
Re:PostgreSQL website – new design now live
by Someone on Thursday April 19, 2018 @04:01AM
(#16874132)
Sites aimed at the enterprise message “trustworthy” by looking distinguished and a bit grey along the temples. Sites for databases and file systems doubly so. You don’t want to trust your data to a kid, no matter how smart.
Similarly, a site for a cheap grocery store must look cheap. Customers shouldn’t think millions were spent on it. Examples: https://aldi.com, https://www.lidl.com
Re:PostgreSQL website – new design now live
by hitekker on Wednesday April 18, 2018 @11:02PM
(#16873034)
Did they hire a designer to do... this?
Before people say "OSS must look bad" or "It's a minimal style", I encourage looking at https://www.djangoproject.com/. Aesthetically pleasing without sacrificing clarity, this website sets the standard for a technical project's homepage redesign.
Re:PostgreSQL website – new design now live
by TeMPOraL on Thursday April 19, 2018 @12:13AM
(#16873283)
> Did they hire a designer to do... this?
I hope so, and if I'm ever in need of a webpage design, I'd love to hire that same designer.
Seriously, the site is close to perfect. It looks nice enough, it's clean, fast and full of content - instead of being full of useless eye candy and short on actual information.
Re:PostgreSQL website – new design now live
by hitekker on Wednesday April 18, 2018 @11:40PM
(#16873161)
I'd be forgiving if Postgres was a few-year-old project struggling for legitimacy. But Postgres is all grown up now, and shouldn't resort to the excuses of the unsuccessful and immature.
If they didn't care for design, then they should have stuck with the old look, like http://sqlite.org or http://www.berkshirehathaway.com/. Both are perfect examples of "we know exactly what we want to be and we don't need to worry about design".
But a half-baked result that pretends to be finished, suggests a lack of confidence in the software that it champions. Which is, frankly, unbecoming.
Re:PostgreSQL website – new design now live
by untog on Thursday April 19, 2018 @12:01AM
(#16873241)
To be honest, if you're judging the quality of Postgres by the design of their web site then, well, maybe you should steer clear of it. The rest of us will be just fine.
Re:PostgreSQL website – new design now live
by abrkn on Wednesday April 18, 2018 @10:11PM
(#16872837)
I felt great anxiety clicking into docs, fearing some radical change. They're the same and I love them just the way they are. I read them several times a day.
Re:PostgreSQL website – new design now live
by kristianp on Wednesday April 18, 2018 @11:14PM
(#16873075)
Shitty website UI that is commercially motivated, e.g. Email harvesting popups, flickering ads and auto-playing videos, etc. Don't go away by themselves. They usually need to be blocked.
Re:PostgreSQL website – new design now live
by elmigranto on Wednesday April 18, 2018 @08:30PM
(#16872458)
It's fine, I guess, as long as docs are plain HTML/CSS and use 0 JS. And I think we are all safe on that front, since those pages are Perl generated or something, so…
Neat update, old site had its charm, but w/ever.
Love to everyone in PG community (even those responsible for PgAdmin4 :)
Re:PostgreSQL website – new design now live
by osrec on Wednesday April 18, 2018 @08:18PM
(#16872398)
A much needed update, but the design is still a little rough round the edges. E.g. excessive use of caps everywhere makes the page look untidy and makes certain things harder to read.
Re:PostgreSQL website – new design now live
by pedalpete on Wednesday April 18, 2018 @06:43PM
(#16871914)
I'd love to be supportive of this and just say what an awesome job PostgreSQL have done.
I don't expect an open-source project with the scale and demands of Postgre to have some sort of cutting edge website. But I don't see a big improvement on usability (though I haven't spent a lot of time on the last site), the documentation is still of the old design.
The starkness is glaring, and I feel this will look very dated in the very near term. Postgre's color scheme itself doesn't help things.
I suspect the most important page is probably documentation, is that not right? And yet, there is almost no content on the main documentation page, you have to link out to the old documentation.
You can still see the old design in the docs: https://www.postgresql.org/docs/10/static/index.html
I appreciate the update, but it's interesting from a design perspective how many technically amazing products have dated website design. I do appreciate not trying to force a fashionable design template onto every site, but there are some really slick minimal ones that can be used that will bring the design up to the current decade at least.
I could have saved a lot of time, over the past 20 years, if I'd simply followed the rule: Is this the most boring webpage I've seen all week? Yes => it's going to be a good database.
CockroachDB, for instance, is able to simultaneously focus on Jepsen-style distributed systems verification and agile administrative interfaces, whose design aesthetic is reflected in the website. And there are plenty of unsupported academia-made databases that are essentially abandonware. I would not advocate for overreliance on this heuristic.
Absolutely not. Design and Sales in Enterprise has as much to do with each other as Sales and Code Quality, almost none.
whoa - you are setting yourself up, if that is any reference to Postgres..
It's interesting from a user perspective how many nice websites have been ruined in an attempt to not look dated.
Good. I hope someone in the team was saying, "The line must be drawn here! This far, no further!" - because it's some time after 2007 when the web went entirely to shit.
That really is my only problem with the postgresql docs though and that’s saying something. The content itself of the postgresql docs is of stellar quality.
Qt did that for their documentation when they changed ownership and moved their website. They didn't migrate the old documentation, either. This made updating broken links much more difficult because I couldn't easily read the pages they originally pointed to.
Maybe better to specify canonical URL as the latest one.
Not saying this is an easy problem to solve, and the documentation is mostly pretty great, but this definitely bugs me and apparently a bunch of other people too.
I am one of the people that gave you an upvote, but this is not a fair comparison at all.
I guess for postgres 80% of people would be happy with always landing on the current version, and making an extra click or adding a version to their search if they really need documentation for older versions. Maybe adding a brief version history at the bottom of documentation pages would reduce the need for old versions even further.
There are no direct links between the urls below which both have the same content.
https://www.postgresql.org/docs/current/static/index.html https://www.postgresql.org/docs/10/static/index.html
You have to click to another page and back again to change to the "current" link if you're on the "10" link.
https://www.google.com/search?q=postgres+functions+9.1
Incidentally, UNIX/Linux man pages also put the examples section near the end.
Similarly, a site for a cheap grocery store must look cheap. Customers shouldn’t think millions were spent on it. Examples: https://aldi.com, https://www.lidl.com
So we can see the PregreSQL and the PostgreSQL ;-)
Before people say "OSS must look bad" or "It's a minimal style", I encourage looking at https://www.djangoproject.com/. Aesthetically pleasing without sacrificing clarity, this website sets the standard for a technical project's homepage redesign.
Boring and half-hearted UI's should be relegated to the likes of https://www.oracle.com/database/index.html than to a lauded and respected database like Postgres.
I hope so, and if I'm ever in need of a webpage design, I'd love to hire that same designer.
Seriously, the site is close to perfect. It looks nice enough, it's clean, fast and full of content - instead of being full of useless eye candy and short on actual information.
Fancy is good, fast is better.
It's expected of them to have a better looking website.
Please remember that this is all volunteers. I'm pretty much sure Postgres community would love if you help them on this.
If they didn't care for design, then they should have stuck with the old look, like http://sqlite.org or http://www.berkshirehathaway.com/. Both are perfect examples of "we know exactly what we want to be and we don't need to worry about design".
But a half-baked result that pretends to be finished, suggests a lack of confidence in the software that it champions. Which is, frankly, unbecoming.
And I'm perfectly fine with that.
Neat update, old site had its charm, but w/ever.
Love to everyone in PG community (even those responsible for PgAdmin4 :)
I don't expect an open-source project with the scale and demands of Postgre to have some sort of cutting edge website. But I don't see a big improvement on usability (though I haven't spent a lot of time on the last site), the documentation is still of the old design.
The starkness is glaring, and I feel this will look very dated in the very near term. Postgre's color scheme itself doesn't help things.
I suspect the most important page is probably documentation, is that not right? And yet, there is almost no content on the main documentation page, you have to link out to the old documentation.
Fun story - I joke tweeted that their website was super old and I'd redo it for free. Someone from their team tried to get me to do it. Haha