> On Apr 18, 2018, at 6:40 PM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote: > >> On 04/18/2018 03:07 PM, Peter Geoghegan wrote: >> On Wed, Apr 18, 2018 at 3:03 PM, Adrian Klaver >> <adrian.klaver@xxxxxxxxxxx> wrote: >>> I would contact the Webmaster but Contact goes to a big image of an elephant >>> head. That is also where Downloads, Support and Donate lands. Might have >>> been a good idea to roll out a demo site for testing first. Will reserve >>> judgment on the site design until it is functioning. >> I really don't think it's practical to give everyone a veto on a >> website design. It took years to launch this website redesign. >> Honestly, I was beginning to think that it would never happen. >> Anyway, I did notice something myself, which is that the git logo >> links to https://git.postgresql.org/gitweb/, which has many >> non-very-important git repos. Instead, it should point to the main >> PostgreSQL repository's gitweb page, which is at >> https://git.postgresql.org/gitweb/?p=postgresql.git. > > And to get to the mailing list archives(arguably one of the most important links) you have to: We designed the website with 3 user profiles: - New to PostgreSQL - Users - Hackers These are 3 very different experiences. It’s hard to find a balance for all of these different needs. When we analyzed the traffic we opted to make various trade offs based on what the most accessed pages. We did note that the people who need to access the mailing list archives know how to get there. The nice thing about a website is that it is easy to iterate over and we can rapidly add things in should they be necessary. > Click on Community, click on Mailing Lists on the left sidebar, then scroll to the bottom of page to find the search box. > > I am one of the No votes in the survey. I’m sorry to hear that. However based on our data we opted to focus optimizing the experience for getting people using PostgreSQL in their apps to the right places. If you have constructive feedback on how we can improve in other areas I’m happy to listen. As someone who does answer webmaster@xxxxxxxxxxxxxx feel free to reach out. Jonathan
