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

Waldemar Kornewald <wkornew@xxxxxxx>:
>
> 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
> 
Sounds quite okay, I don't like the division between Home and 
Community, though.  Especially not if you lump together "Forums" and 
"The Organization".

Again, this doesn't matter much.. The different areas are okay for me, 
and they can be changed with a mouse click later on when there is a CMS 
in place. So I guess what you proposed is a good start.

But... I'd like to say that when the site is being built using whatever
-cms-we-end-up-using, we should start (again) with the bare minimum, 
have that on the site for a while, see how it feels like, and add one 
section per week unil we feel there's enough. I simply cannot stress 
simplicity for usability enough.

> 
> -----------------------------------------------
> | 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_ | * ...
> -----------------------------------------------
>
It's important that blog items about the site and information about 
Haiku is easily accessible on the site itself. For example, trying to 
find the Subversion repos information on haiku-os.org a couple of 
months ago was plain impossible..
 
>
> -----------------------------------------------
> | 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
> -----------------------------------------------
>
Don't like the "Other". The most important topics should fit on the 
main page directly, which shouldn't be more than 5-6 things (4, if you 
believe research on how many things a human can count subconsiously), 
and then have things under that.  Preferedly not deeper than 2 levels 
to reach any data.  Like, Download -> x86 -> Haiku-R1.zip
 
>
> -----------------------------------------------
> | 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.
>
I believe the Quicklinks should /not/ include Donate, rather have 
what's important.  I think a lot of people being attracted to Haiku are 
developers, and as such we should try to focus on them, as well as the 
already existing developers.

Exact layout should be determined by a group larger than ours. At this 
point, it's more important we try to find what should be at the site /
at all/, and what should not be there, and start working on it.  Where 
things go can be determined later, that's the beauty of a good CMS.
 
-- Mikael

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

Other related posts: