Re: New site - final(?) list of problems - Mailing list pgsql-www
From | Robert Treat |
---|---|
Subject | Re: New site - final(?) list of problems |
Date | |
Msg-id | 1103215592.5774.53.camel@camel Whole thread Raw |
In response to | Re: New site - final(?) list of problems ("Dave Page" <dpage@vale-housing.co.uk>) |
Responses |
Re: New site - final(?) list of problems
|
List | pgsql-www |
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