Hi Martin, Currently we are about to launch a new redesign of the main page, adressing primarily the needs of the first and third group you are mentioning. A preview is available at
http://test.openoffice.org/ (It will be launched, if everything goes according to plan, somewhere after 20:00 CET) This is imho a first step towards simplifying the website. Basic steps, central points. E.g. to replace support.openoffice.org the following page is proposed (but not yet finalized): http://test.openoffice.org/help In general a more central coordination of the website's content is not a bad thing. Especially when it concerns pages that are browsed to and from. If these pages are maintained independently from each other, structure lacks. For the help page I've tried to start an effort on the wiki to produce content for new pages... http://wiki.services.openoffice.org/wiki/Website/Content/help while not very popular (not many people tried/dared editing), it does allow for cooperatively finetuning wording if needed. Whoever commits the final content to the collabnet infrastructure doesn't really matter then. Maybe other projects could start experimenting with this more often as well. Note that the wiki page linked to above is not intended to be yet another entry point, but simply a place where a new collabnet page is being developed. Why the wiki? Lower entry, and its easier to collaborate between different projects. The website project could serve as a general coordinator, and assist with converting to proper HTML, advice on design elements etc. Anyhow... more on topic... the first page users of our website wanting to contribute something to OOo will probably get to is the participate page. Even the developer section of this page is seems quite complex already... (too many things one can do from there) > * development.openoffice.org > * http://contributing.openoffice.org/programming.html > * http://wiki.services.openoffice.org/wiki/Main_Page#Getting_started_with_OOo_development > 2. Target Audience: Developer > > most important topic for them > > 1. Where to start / How to build -> Should be described when downloading source. > 2. Developer documentation a. Writing Macro's b. Writing Extensions c. Writing external programs interfacing with OOo (can one phrase this shorter) d. Contributing to the main code (shorter phrase?) e. ...? > 3. How to participate (I guess this is a more general topic, not dev specific... tell 'm about issuezilla, mailinglists etc.) I must admit that we have been neglecting the developer/contributors lately... (aside from some new icons) What bothers me is that the division between extender (e.g. developer of macros/python scripts etc) and developer of code that is supposed to go into the OOo product is rather vague... But it is hard for me to tell what is really needed here, since I'm not the audience for the developer pages (I'm not a programmer), nor do I know many people who are interested in building OOo. I don't know what type of page a developer would like to see. And maybe there are even more sub-audiences. At the moment my time is limited, but as a first start, maybe some developers could try for themselves to draft a new wiki page, that is intended to become the dev central? g., Maarten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
