Hi all,

My apologies for coming so late to the feast and my compliments to Per and Matthias for diving in and suggesting and doing super work. Now let's get to the really fun stuff and re-do the homepage and enduser download page(s).

We can't change CEE. But we *can* use the .services subdomain. This means that we can include more suitable servers that would be able to do what we want, like allow for one-click downloads.

So: Let's start. Assume a blank page (or nearly; we have to keep with the gulls :-)) And for technology, let's think Drupal. The license on this page would be the same as for all other OOo pages.


The boundaries:

* Deadline for a mockup--*before* OOoCon. This is just for a mockup we can show at OOoCon. Change is always possible.

* Basic idea: User -> www.openoffice.org -> download: *one click* download of OOo in his her or language and for her OS. www.openoffice.org thus becomes a landing page for all.

* Once the user downloads OOo, she is presented with a page listing templates, extensions, support, etc.: all that enhances her OOo environment. We need then to develop that page *plus* re-do the Support and other related pages; but the important part is to do the home and download pages.

* Homepage: My fault but it's gotten wordy again. I agree with Per's excellent analysis and would love to see him and Maarten and Christian (and Matthias, if he has time) to come up with a good design--or designs. Others of course can participate. The idea is to draft a schematic or plan that the homepage answers. This can begin immediately.

* Download page: Same group as above to draft schematics plan that the mockup addresses. Mozilla is but one example, albeit a good one. But let's see what we can do :-)

I created a wiki to start with; it's pretty empty:

http://wiki.services.openoffice.org/wiki/User_Pages_Requirements

We can start with this wiki to layout the basic requirements and schematics for the download page(s). We could also use it for the homepage, too--or start a new one. Your call.

** Decisions: Christian, Stefan, Maarten and I will decide the final design or designs to present to OOoCon.

** Implementation: Filip Molcan, a community member, has promoted a draft he called oooPortal to several OOo leads. His company could implement the design and maintain it. He would also be working with us in the design, which is to be a community effort.


Best
louis

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to