Обсуждение: portal code changes
Alexey,
I'm planning to shuffle some of the content around in the new portal and
rename the menu items accordingly... the new menu would look like:
Home (the home page w/ news, events)
About PostgreSQL (general overview, case studies, advocacy, newbies
Using PostgreSQL (users lounge, gui tools, bug reporting )
Contributing to PostgreSQL (mainly developer.postgresql.org stuff)
Download (overview download page, ftp links, etc.)
Support (support overview page, lists, etc.)
Documentation (docs, faqs)
I'm thinking none of this should conflict with anything your working on, LMK
if you see any problems with it.
Oh, I was also thinking now might be a good time to split events into
events/training, how feasible do you feel that would be?
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
> Alexey, > > I'm planning to shuffle some of the content around in the new > portal and > rename the menu items accordingly... the new menu would look like: > > Home (the home page w/ news, events) > About PostgreSQL (general overview, case studies, advocacy, newbies And I just got Alexey to change that one *from* about to overview :-) None of this stuff is really "about", IMHO. The stuff that's under about is like "who are the team" and "development model" and things like that. But that's me :-) Just had to say it. //Magnus
Hi, Robert Treat wrote: > I'm planning to shuffle some of the content around in the new portal and > rename the menu items accordingly... the new menu would look like: > > Home (the home page w/ news, events) > About PostgreSQL (general overview, case studies, advocacy, newbies > Using PostgreSQL (users lounge, gui tools, bug reporting ) > Contributing to PostgreSQL (mainly developer.postgresql.org stuff) > Download (overview download page, ftp links, etc.) > Support (support overview page, lists, etc.) > Documentation (docs, faqs) > > I'm thinking none of this should conflict with anything your working on, LMK > if you see any problems with it. Well, as Magnus already pointed out, I just renamed "About" to "Overview". I don't see the point of splitting it into "About" and "Using" --- we don't yet have enough content to justify any splits. Some of the stuff should probably end in the "documentation" section alongside the official docs, though. > Oh, I was also thinking now might be a good time to split events into > events/training, how feasible do you feel that would be? ::shrugs:: You tell me what do you mean by "splitting", I tell you how feasible this is...
On Wednesday 20 October 2004 15:53, Alexey Borzov wrote:
> Hi,
>
> Robert Treat wrote:
> > I'm planning to shuffle some of the content around in the new portal and
> > rename the menu items accordingly... the new menu would look like:
> >
> > Home (the home page w/ news, events)
> > About PostgreSQL (general overview, case studies, advocacy, newbies
> > Using PostgreSQL (users lounge, gui tools, bug reporting )
> > Contributing to PostgreSQL (mainly developer.postgresql.org stuff)
> > Download (overview download page, ftp links, etc.)
> > Support (support overview page, lists, etc.)
> > Documentation (docs, faqs)
> >
> > I'm thinking none of this should conflict with anything your working on,
> > LMK if you see any problems with it.
>
> Well, as Magnus already pointed out, I just renamed "About" to "Overview".
> I don't see the point of splitting it into "About" and "Using" --- we don't
> yet have enough content to justify any splits. Some of the stuff should
> probably end in the "documentation" section alongside the official docs,
> though.
The difference in the two sections is that one is to keep advocacy oriented
material... stuff the someone who is trying to determine if postgresql is
good for them would need to know. The other section is aimed more at people
who use postgresql everyday, or need to explore deeper into the different
options they have with postgresql. I think there will probably be some
overlap between the two sections, but I also think we have enough content for
a split if we pull in information from advocacy and techdocs, something we've
been talking about doing for some time.
>
> > Oh, I was also thinking now might be a good time to split events into
> > events/training, how feasible do you feel that would be?
> >
> ::shrugs::
>
> You tell me what do you mean by "splitting", I tell you how feasible this
> is...
I mean listing "regular" events seperate from "training" events, sort of like
we have news seperate from events now.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Hi, Robert Treat wrote: >>Well, as Magnus already pointed out, I just renamed "About" to "Overview". >>I don't see the point of splitting it into "About" and "Using" --- we don't >>yet have enough content to justify any splits. Some of the stuff should >>probably end in the "documentation" section alongside the official docs, >>though. > > The difference in the two sections is that one is to keep advocacy oriented > material... stuff the someone who is trying to determine if postgresql is > good for them would need to know. The other section is aimed more at people > who use postgresql everyday, or need to explore deeper into the different > options they have with postgresql. Hey, *you* know anout the difference between "advocacy-oriented" and "user-oriented" content. But will the website users know it? That's the question you need to answer first. If there is no difference for them then there is no need to split. >>You tell me what do you mean by "splitting", I tell you how feasible this >>is... > > I mean listing "regular" events seperate from "training" events, sort of like > we have news seperate from events now. OK, I could understand *that*. ;) But *how* do you think they should be split: in display, in submit form, in admin interface, etc.?
On Thursday 21 October 2004 02:08, Alexey Borzov wrote:
> Robert Treat wrote:
> >
> > I mean listing "regular" events seperate from "training" events, sort of
> > like we have news seperate from events now.
>
> OK, I could understand *that*. ;)
>
> But *how* do you think they should be split: in display, in submit form, in
> admin interface, etc.?
Well, I guess the first step is allowing people to designate things
differently in the submit form, and then showing that difference in the admin
screen. After that we can haggle over how to split the display :-)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Hi, Robert Treat wrote: >>>I mean listing "regular" events seperate from "training" events, sort of >>>like we have news seperate from events now. >> >>OK, I could understand *that*. ;) >> >>But *how* do you think they should be split: in display, in submit form, in >>admin interface, etc.? > > Well, I guess the first step is allowing people to designate things > differently in the submit form, and then showing that difference in the admin > screen. After that we can haggle over how to split the display :-) OK, so you would like to add a flag to database showing whether the event is "training" or "generic", all other fields would be the same. You'd like to add a switch to submit form and event editing form in admin interface. You don't yet know how it'll look like on website and don't volunteer to update the design for this. Correct?
On Thursday 21 October 2004 09:12, Alexey Borzov wrote:
> Robert Treat wrote:
> >>>I mean listing "regular" events seperate from "training" events, sort of
> >>>like we have news seperate from events now.
> >>
> >>OK, I could understand *that*. ;)
> >>
> >>But *how* do you think they should be split: in display, in submit form,
> >> in admin interface, etc.?
> >
> > Well, I guess the first step is allowing people to designate things
> > differently in the submit form, and then showing that difference in the
> > admin screen. After that we can haggle over how to split the display :-)
>
> OK, so you would like to add a flag to database showing whether the
> event is "training" or "generic", all other fields would be the same.
> You'd like to add a switch to submit form and event editing form in
> admin interface.
yep.
> You don't yet know how it'll look like on website and
> don't volunteer to update the design for this.
>
Well, the easiest thing to do is to just create three separate sections on the
main page... one for news, then one for the "general" events, then one for
the training courses. Each could then carry it's own rss feed too. The idea
is that sometimes our community events get lost in the sea of training
courses, so separating the two should help to distinguish them.
Of course I am open to suggestions if people have an alternative idea they'd
like to implement, but barring a radical change the bits for the database
will need to be done regardless. As I see it we can leave a TODO item for
implementing the interface changes, if you or no one else picks it up I'll
get to it eventually.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL