Thread: New site - final(?) list of problems
Morning, Those of you monitoring the www committers list will have nnoticed a huge flurry of commits form Omar at the beginning of the week as he updated the site to it's new design and added a bunch of new/external content. Many thanks to Omar for that :-) Anyway, I haven't seen any commits in the last couple of days so I assume he's more or less finished (Omar; can you confirm where you think we're at please?). The following are the issues with the site that I've found, barring a couple that I've fixed already: - PostgreSQL 8.0 is not out yet but is featured on the front page - No privacy policy, yet links to one - View this page in... links for unused languages - Doc page - Says under review?? - About page is empty - 'Latest News' shows all news - should only be active stuff. Need archive page. - 'Upcoming Events' shows all events - should only be active stuff. Need archive page. - 'Upcoming Events' order is wrong - some missing dates? - Hosting solutions - TODO (lift from Techdocs?) - Press enquiries on Contact page - TODO As you can see, the majority of those are relatively minor content issues. If we want to go live for 8.0, I think we should do it at least a week before release if possible, so, any volunteers to pick up items on there please? Is there anything I've missed? The master site can be viewed at http://wwwmaster.postgresql.org/ and a mirror at http://wwwdevel.postgresql.org/ - checking both is important to ensure the static site generation is working as it should. Let's make the final push and get this out the door!! :-) Regards, Dave.
Dave, > - PostgreSQL 8.0 is not out yet but is featured on the front page Hmmm. Can we hide this? > - No privacy policy, yet links to one We should drop this. Since when do we have a Privacy Policy? > - View this page in... links for unused languages > - Doc page - Says under review?? > - About page is empty I'll fill in the Press Faq, and possibly the general About as well (one paragraph, yes?) Will probably need someone to mark it up for me, though. > - Hosting solutions - TODO (lift from Techdocs?) Yes, do. Can fix it later. Also, we should lift the consultants list as well. Do we have a place for them? > - Press enquiries on Contact page - TODO Are we thinking about a webform here, or the international list of regional contacts? I'll have the latter ready in a few days. -- Josh Berkus Aglio Database Solutions San Francisco
> -----Original Message----- > From: Josh Berkus [mailto:josh@agliodbs.com] > Sent: 16 December 2004 08:53 > To: Dave Page > Cc: PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > Dave, > > > - PostgreSQL 8.0 is not out yet but is featured on the front page > > Hmmm. Can we hide this? I was thinking we could replace it with 'Coming soon, PostgreSQL 8.0'. > > - No privacy policy, yet links to one > > We should drop this. Since when do we have a Privacy Policy? We don't. Perhaps we should though? Or we can drop it - I don't care much either way. > > - View this page in... links for unused languages > > - Doc page - Says under review?? > > - About page is empty > > I'll fill in the Press Faq, and possibly the general About as > well (one > paragraph, yes?) Will probably need someone to mark it up > for me, though. OK, I'm sure one of us could cope with that. > > - Hosting solutions - TODO (lift from Techdocs?) > > Yes, do. Can fix it later. Also, we should lift the > consultants list as > well. Do we have a place for them? Not yet (I don't think). > > - Press enquiries on Contact page - TODO > > Are we thinking about a webform here, or the international > list of regional > contacts? I'll have the latter ready in a few days. Contacts would seem good to me. Regards, Dave.
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Dave Page > Sent: 16 December 2004 08:57 > To: Josh Berkus > Cc: PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > > > - No privacy policy, yet links to one > > > > We should drop this. Since when do we have a Privacy Policy? > > We don't. Perhaps we should though? Or we can drop it - I don't care > much either way. Ack, what the heck - removed for now. > > Yes, do. Can fix it later. Also, we should lift the > > consultants list as > > well. Do we have a place for them? > > Not yet (I don't think). Yes there is - it's 'Professional Services' Regards, Dave.
Dave Page wrote: <snip> >>>- PostgreSQL 8.0 is not out yet but is featured on the front page >> >>Hmmm. Can we hide this? > > I was thinking we could replace it with 'Coming soon, PostgreSQL 8.0'. Sounds like a good idea. :) >>>- No privacy policy, yet links to one >> >>We should drop this. Since when do we have a Privacy Policy? > > We don't. Perhaps we should though? Or we can drop it - I don't care > much either way. There's a "Privacy Policy" on the Techdocs site's registration page: http://techdocs.postgresql.org/accounts/register.php Is it suitable to cut-n-paste into a generic one we can use? Regards and best wishes, Justin Clift -- "One who sees the invisible can do the impossible." + Frank Gaines
Hi, > Anyway, I haven't seen any commits in the last couple of days so I > assume he's more or less finished (Omar; can you confirm where you think > we're at please?). The following are the issues with the site that I've > found, barring a couple that I've fixed already: I was very busy with a pure CSS implementation, which I've just committed. > - PostgreSQL 8.0 is not out yet but is featured on the front page I thought the point of the new site was to go live with the release of 8.0. No reason to put it up before that, is there? > - No privacy policy, yet links to one Well, I was waiting for it to magically write itself. :) > - View this page in... links for unused languages Gone with new commit. Actually, the whole language thing needs to be rethought. A language should only be added to the list if the vast majority of the site has been translated. We should follow what Mozilla Europe does for their site. http://www.mozilla-europe.org . A much better system, really. > - Doc page - Says under review?? Just means that it was written at 4am in a hurry, and probably needs to be reworded. > - About page is empty Not anymore. > - 'Latest News' shows all news - should only be active stuff. Need > archive page. > - 'Upcoming Events' shows all events - should only be active stuff. Need > archive page. > - 'Upcoming Events' order is wrong - some missing dates? The previous method doesn't make any sense. Say you wanted to link to the news section from another page (like we do in about)--not only the front page. With the previous method, there would be no way to see the 'active' news on that secondary page. It makes no sense for things to disappear from the secondary page. The purpose of the front page is to show (at maximum) 3 latest news and event items [any news item that is accepted, and any event that is accepted and has a start date > today, limit 3.) The upcoming events stuff will work properly when the events have dates assigned. I've gone through all the events and added dates and locations to every single one, but I'll need to modify update.sql. > - Hosting solutions - TODO (lift from Techdocs?) Going to add this and professional solutions to the admin section. > - Press enquiries on Contact page - TODO Was pending CSS stuff. Now done, so Emily's going to help Josh with markup and so forth. > As you can see, the majority of those are relatively minor content > issues. If we want to go live for 8.0, I think we should do it at least > a week before release if possible, so, any volunteers to pick up items > on there please? Is there anything I've missed? support/professional.html:<p>TODO</p> support/hosting.html:<p>TODO</p> docs/faq.html:<p>TODO - to be integrated with <a href="/docs/faq/postgresql">PostgreSQL FAQ</a> through multi-language support.</p> about/contact.html:<p>TODO</p> about/press.html:<p>TODO</p> about/history.html:<p>TODO</p> :) > The master site can be viewed at http://wwwmaster.postgresql.org/ and a > mirror at http://wwwdevel.postgresql.org/ - checking both is important > to ensure the static site generation is working as it should. > > Let's make the final push and get this out the door!! :-) Getting excited there, Dave? :) > Regards, Dave. Best Regards, Omar and Emily
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Omar Kilani > Sent: 16 December 2004 09:59 > To: PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > Hi, > > > Anyway, I haven't seen any commits in the last couple of days so I > > assume he's more or less finished (Omar; can you confirm > where you think > > we're at please?). The following are the issues with the > site that I've > > found, barring a couple that I've fixed already: > > I was very busy with a pure CSS implementation, which I've > just committed. :-) > > - PostgreSQL 8.0 is not out yet but is featured on the front page > > I thought the point of the new site was to go live with the > release of > 8.0. No reason to put it up before that, is there? Testing. We don't want to find a major problem the day we release and get slashdotted. > > - No privacy policy, yet links to one > > Well, I was waiting for it to magically write itself. :) <grin> - I'll review the techdoc one per Justin's suggestion - anyone object to using that assuming it's roughly suitable? > > - View this page in... links for unused languages > > Gone with new commit. Actually, the whole language thing needs to be > rethought. A language should only be added to the list if the vast > majority of the site has been translated. We should follow > what Mozilla > Europe does for their site. http://www.mozilla-europe.org . A much > better system, really. Yes - we use about 90% in pgAdmin before we list a language as official. Still, before we can use any languages we need a way to update the pot file... > The previous method doesn't make any sense. Say you wanted to link to > the news section from another page (like we do in about)--not > only the > front page. With the previous method, there would be no way > to see the > 'active' news on that secondary page. It makes no sense for > things to > disappear from the secondary page. The purpose of the front > page is to > show (at maximum) 3 latest news and event items [any news > item that is > accepted, and any event that is accepted and has a start date > > today, > limit 3.) > > The upcoming events stuff will work properly when the events > have dates > assigned. I've gone through all the events and added dates > and locations > to every single one, but I'll need to modify update.sql. If you're limiting stuff on the front page then I think you need 2 secondary pages - one for the active-only stuff, and one archive page listing everything (possible not the currently active stuff). Or is that what you are saying (my brain is mush right now - I'm in the middle of a software licence audit). > > Let's make the final push and get this out the door!! :-) > > Getting excited there, Dave? :) Just trying to chivvy up some enthusiasm from everyone. It would be nice to get this job done and move on... Regards, Dave
> > > - PostgreSQL 8.0 is not out yet but is featured on the front page > > > > Hmmm. Can we hide this? > > I was thinking we could replace it with 'Coming soon, PostgreSQL 8.0'. If you do this, make sure it looks very different from the "out now" image and text. So it's clear something major has changed when the release is actually out. If you just change the text, casual surfers won't notice right away, which we'd want :-) //Magnus
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Omar Kilani > Sent: 16 December 2004 09:59 > To: PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > I was very busy with a pure CSS implementation, which I've > just committed. Ack - that broke my Firefox fix (http://gborg.postgresql.org/pipermail/pgweb-commits/2004-December/00038 5.html). I quickly found it very annoying that when Firefox fits a page on the screen, it removes the vertical scrollbar, thus altering the center position of the page. The net result is that as you browse the site jumping between long and short pages, the layout jumps horizontally a few pixels which is *really* off-putting. I realise it's probably not pure CSS, but unless there's another way I think this should definitely be put back. Regards, Dave
Dave, > Ack - that broke my Firefox fix It's not a good fix since it clips x-overflow. There's really no way around it except writing more content. :) https://bugzilla.mozilla.org/show_bug.cgi?id=72540 Is a very lengthy bug. And... vertical scroll is unsightly when there's no actual content to be scrolled. CSS can't be done to do an inactive scrollbar in Mozilla. Best thing to do is leave it, really. > Regards, Dave Omar
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Omar Kilani > Sent: 16 December 2004 12:20 > To: PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > Dave, > > > Ack - that broke my Firefox fix > > It's not a good fix since it clips x-overflow. I'm not entirely sure what you mean - the horizontal scrollbar won't display when it should, leaving content slighly clipped? > There's really no way > around it except writing more content. :) > > https://bugzilla.mozilla.org/show_bug.cgi?id=72540 > > Is a very lengthy bug. And... vertical scroll is unsightly > when there's > no actual content to be scrolled. CSS can't be done to do an inactive > scrollbar in Mozilla. Best thing to do is leave it, really. I'd rather see the content left justified if there's no other way. I found it instantly annoying and off-putting. Regards, Dave.
> -----Original Message----- > From: Justin Clift [mailto:justin@postgresql.org] > Sent: 16 December 2004 09:32 > To: Dave Page > Cc: Josh Berkus; PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > There's a "Privacy Policy" on the Techdocs site's registration page: > > http://techdocs.postgresql.org/accounts/register.php > > Is it suitable to cut-n-paste into a generic one we can use? Looks good to me - added. Regards, Dave
Hiyas, Looking at wwwdevel, there's a link to "Tech Docs" on the front page (in the middle) linking to: http://wwwdevel.postgresql.org/docs/techdocs Not sure if that's right or not, but it gives a 404 when clicking on. Regards and best wishes, Justin Clift -- "One who sees the invisible can do the impossible." + Frank Gaines
> -----Original Message----- > From: Justin Clift [mailto:justin@postgresql.org] > Sent: 16 December 2004 15:48 > To: Dave Page > Cc: Josh Berkus; PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > Hiyas, > > Looking at wwwdevel, there's a link to "Tech Docs" on the > front page (in > the middle) linking to: > > http://wwwdevel.postgresql.org/docs/techdocs > > Not sure if that's right or not, but it gives a 404 when clicking on. Ack, missed that one, got the other. Thanks Justin, fixed in CVS now. Regards Dave
On Thu, 2004-12-16 at 06:06, Dave Page wrote:
> > -----Original Message-----
> > From: pgsql-www-owner@postgresql.org
> > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Omar Kilani
> > The previous method doesn't make any sense. Say you wanted to link to
> > the news section from another page (like we do in about)--not
> > only the
> > front page. With the previous method, there would be no way
> > to see the
> > 'active' news on that secondary page. It makes no sense for
> > things to
> > disappear from the secondary page. The purpose of the front
> > page is to
> > show (at maximum) 3 latest news and event items [any news
> > item that is
> > accepted, and any event that is accepted and has a start date
> > > today,
> > limit 3.)
> >
> > The upcoming events stuff will work properly when the events
> > have dates
> > assigned. I've gone through all the events and added dates
> > and locations
> > to every single one, but I'll need to modify update.sql.
>
> If you're limiting stuff on the front page then I think you need 2
> secondary pages - one for the active-only stuff, and one archive page
> listing everything (possible not the currently active stuff). Or is that
> what you are saying (my brain is mush right now - I'm in the middle of a
> software licence audit).
>
The issue comes from the fact that, in the old method, all of the
active/latest news was always displayed on the front page, and the
secondary page was all archive info. This makes the new design somewhat
limiting since we only get 3 entries... for example, one thing we can
accomplish with the current setup is that we can keep a note about the
most recent version of postgresql around, even months after a release,
right on the main page for folks who need that information. With only 3
entries we're not going to be able to do that. Another thing we can do
now is that we can let content sit for a while even when more content
comes out... for example we can leave up news about pgadmin releases for
a good month no matter how many stories come and go... in the new scheme
we are going to lose that ability. Thinking about that I think Dave's
scheme makes some sense... front page is last 3 entries by date --> more
link takes you to the list of active news items, with summaries -->
which has a link to "all news" which shows the archive page. This isn't
quite as good as what we have now, but I think it is workable.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Omar,
> Was pending CSS stuff. Now done, so Emily's going to help Josh with
> markup and so forth.
Which brings up a couple of points:
1) Emily, you haven't replied to my E-mail from Monday. Did you not get it?
2) When the Press Pages are done, we're going to need a place to stick them.
We'll have them in 11-14 languages, yet the web site isn't available in that
many languages yet.
So, where do we stick them?
Last year, we just stuck them in as static HTML files with links from a News
item and the Advocacy page. Do we have to do something different this year?
If so, what?
--
Josh Berkus
Aglio Database Solutions
San Francisco
Robert, > for example, one thing we can > accomplish with the current setup is that we can keep a note about the > most recent version of postgresql around, even months after a release, > right on the main page for folks who need that information. With only 3 > entries we're not going to be able to do that. Another thing we can do > now is that we can let content sit for a while even when more content > comes out... for example we can leave up news about pgadmin releases for > a good month no matter how many stories come and go... If we have this ability, we've certainly never used it. -- Josh Berkus Aglio Database Solutions San Francisco
On Thu, 2004-12-16 at 12:58, Josh Berkus wrote:
> Robert,
>
> > for example, one thing we can
> > accomplish with the current setup is that we can keep a note about the
> > most recent version of postgresql around, even months after a release,
> > right on the main page for folks who need that information. With only 3
> > entries we're not going to be able to do that. Another thing we can do
> > now is that we can let content sit for a while even when more content
> > comes out... for example we can leave up news about pgadmin releases for
> > a good month no matter how many stories come and go...
>
> If we have this ability, we've certainly never used it.
>
?? Certainly we do. Look at the main page right now, the pgadminIII
release is still listed on the front page, even though its the 4th item
on the list. There is also an announcement about the 7.x series as well
as the beta release.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
> -----Original Message----- > From: Robert Treat [mailto:xzilla@users.sourceforge.net] > Sent: 16 December 2004 19:47 > To: Josh Berkus > Cc: Dave Page; Omar Kilani; PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] New site - final(?) list of problems > > ?? Certainly we do. Look at the main page right now, the pgadminIII > release is still listed on the front page, even though its > the 4th item > on the list. There is also an announcement about the 7.x > series as well > as the beta release. Yes - I try to review the list of news items regularly. My general policy is to remove anything older than a month, however PostgreSQL releases and closely related project releases (read, pgAdmin, phpPgAdmin, psqlODBC, Slony etc.) may get a little longer (particularly PostgreSQL releases of which there is almost always one there). Regards,Dave.
Robert, > > > right on the main page for folks who need that information. With only > > > 3 entries we're not going to be able to do that. Another thing we can > > > do now is that we can let content sit for a while even when more > > > content comes out... This also points out something a couple of people (including me) mentioned some months ago: we really need to split "news" and "events" into 4 sections: Project News Other News PG Events Training ... which will deal with the expiration issue. However, I think we should wait until after launch to make further changes. -- Josh Berkus Aglio Database Solutions San Francisco