[openbeos] Re: the new website

"Waldemar Kornewald" <wkornew@xxxxxxx> wrote:
> On 8/25/06, Jonas Sundström <jonas@xxxxxxxxxxx> wrote:
> > 1. Pure users
> >  - task oriented people?
> >  - applications, lifestyle, entertainment,
> >  - peripherals, not just the computer
> >    printers, scanners, removable storage, voip gear, ...
> > 2. Corporate/education
> > 3. Web developers
> > 4. App developers - classic "third party" developers
> > 5. Haiku developers - we, the people!
> > 6. Distro makers
> > (7. Offspring/consulting, like what Wasabi is to NetBSD)
> 
> Could you please make a suggestions of what you imagined for the
> navigation? That would save me some time. Thanks.

Yeah, that's the hard part. I'm sure there are many possible ways to 
organize the website and have it work, but this idea is to have 
distinct website areas, and entry points for these categories of 
people. Some information split up, some shared, some adapted to each 
group. 

(A Haiku developer, an application developer and a web developer may 
not want the same downloads, or the same wiki articles or documentation 
or blog entries. The pure user category of people, new-comers perhaps, 
may not find a statuspage based on Trac tickets meaningful. Etc.)

The categories could be the first level of tabs in a two-level bar of 
tabs, like the one Apple uses, or some other hiearchial form. The 
target groups don't have to be named explicitly though, and it's hard 
anyway, coming up with good labels. 'Users' and 'developers' are blunt 
words, but maybe these descriptive labels could work: "Using Haiku", 
"Making Software", "Making Haiku", "Selling Haiku", ... 

"Using Haiku"
(primarily for users and new-comers)
- Haiku as product
- why it's so great using Haiku and Haiku applications
- supported hardware
- where to get software
- user-oriented downloads
- available services (.Haiku ;)
- mailing-lists specific to users, for support, discussion,
  low-traffic info and security advisories
- links to news sites, user groups, ...

"Making software"
(primarily for 3'rd party developers of 
applications meant to run on Haiku,
- Haiku as platform
- the BeBook and Be's developer articles would fit here
- developer workshops, begeistert, etc.
- relevant documentation, books
- general developer downloads

"Making websites"  (big if!)
(web developers, if this is a category we even want 
to target, or consider lost to either unix or windows.
We don't have anything native like ASP, PHP or WebObjects.
Logically they are "users", but there's a big overlap.)

"Making Haiku"
(the Haiku developers,
- Haiku as project
- team and developer presentation
- source code repository, webinterface
- bug tracker
- development-specific mailinglist
- documentation that pertains to internals:
  knowledgebase, standards, device drivers, ...
- specific Haiku development downloads

"Selling Haiku"
(distromakers and resellers)
- legal info?
- contact into

The seventh category I don't know what to call.
- legal info?
- contact into

Oh, I missed the corporate/edu group..
How about "Haiku Enterprise",,, :-)
- overview of the available tools, supported dataformats,
communication protocols, interoperability, hardware, etc.
- overview of networked management and backup.
 (some day in the future)

Below these headings, everything relevant to the group
would be presented from that point of view.

Every area could have an interactive part in addition to
the static content, a wiki perhaps, and each blog post 
would only display in the appropriate part of the website.
But the main thing is to organize the static content in an
easy to grasp, user-oriented way.

Just a few ideas. 

/Jonas.

Other related posts: