:murb: [maarten brouwers] wrote:
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

Yes, these are first important steps and I really appreciate and enjoy the efforts of the website team, excellant work,

[...]

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...

yes, these are different target audiences,

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?

developers are quite good in writing structured code or dumping their brain on a wiki page but most of them will fail to write readable documentation if there is not already a structure is given. I think it would help to have technical writers available which are able to provide a useful structure so that consumers will find what they need and developers find the location where they can dump their brain into.

g.,


Maarten

Martin


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

Reply via email to