[haiku-web] Re: Trac (was: Website)

Mikael Jansson (mailing lists) wrote:
I'm waiting for Marcus' reply. If he is open to testing it then nothing
speaks against setting up and customizing a sample Trac install that
everyone can test.

Okay, Marcus agreed to install it and run it side by side, so we can test it. Bugzilla will stay the official bug tracker, of course, and when we all love Trac we should switch. ;)


I think less is more. Start with the absolute minimal areas and continue from there, instead of doing too much and ending up using only half of it, making ourselves confused on the way ("Where was the build customization doc again? Support -> Help, or was it Development -> Documentation?")

I already guessed that someone would say that. :) IMHO, it's important to separate between developers and users. Let's see...

Home  (integrates blog)
  Introduction  (what is haiku, goals, why should I use it?, ...)
  Screenshots
  FAQs
  Status
  Download
  Take A Tour  ("Installation" and "Using Haiku")
Development
  Getting Started
  Projects
    Kernel
    Media
    ...
  Tutorials
  Haiku Book
  Repos Browser
  Ticket Tracker
Community
  Support Us
  Forums
  The Organization
  Administration


----------------------------------------------- | Haiku - the desktop operating system for you! | --- more productive, easier to use |---------------------------------------------- |QuickLinks: Download, Intro, Donate | Login |-------------------Home----------------------- |[Blog] | [Activity] |--R1 is out!-- | Repository: | ... | <insert-loc-graph> |--new website-- | | ... | Closed Tickets: |--why Haiku matters-- | 2006-03-21 | ... _read more_ | * x86 boot loader |--for developers-- | * mouse not working | new tutorials: ... | * port netstack | new APIs: ... | 2006-03-20 | _read more_ | * ... -----------------------------------------------

-----------------------------------------------
| Haiku - the desktop operating system for you!
|   --- more productive, easier to use
|----------------------------------------------
|QuickLinks: Download, Intro, Donate |    Login
|---------------Development--------------------
|[Getting Started]    | [Projects]
|introduction and     | how to join,
|how to contribute    | technical docs, RFCs
|----------------------------------------------
|[Tutorials]          | [Haiku Book]
|examples, intros,    | API reference,
|design patterns      | overview
|----------------------------------------------
| Other: Repos Browser, Ticket Tracker,
|        Build Factory, Repos Statistics
-----------------------------------------------

-----------------------------------------------
| Haiku - the desktop operating system for you!
|   --- more productive, easier to use
|----------------------------------------------
|QuickLinks: Download, Intro, Donate |    Login
|-----------------Community--------------------
|[Support Us]         | [Forums]
|banners, donations,  | ask questions and
|partner program      | talk to other users
|----------------------------------------------
|[The Organization]   | [Administration]
|who we are,          | commercial or special
|financial status     | contact to project lead
-----------------------------------------------

Maybe should add "Report Bug" to QuickLinks or above the list of closed tickets. What do you think in general. Is that the direction we should take? If we put the navbar at the top we should probably combine it with the QuickLinks.

Feel free to say "it's all crap", but don't forget to say *why* and please make suggestions to improve the design. ;) Thanks!

Bye,
Waldemar
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: