On Fri, Nov 7, 2008 at 11:55 PM, michelle olson <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've drafted a Documentation landing page for the site this week, with a
> link in the main left-navigation. It is just a first draft, so any and
> all comments are welcome. (Note: I replaced the Get Help link with this
> one, since Bill implemented the Get Help icon in the upper-right last week.)
>
> http://opensolaris.org/os/documentation/
>
> Let me know what you think about the sections, order, accuracy, and if
> anything is missing and general sanity checking. Where I'll need your
> help most is keeping this fresh, so as you find and read or post new
> documents, send the links to this list and we'll add them.

First, a general comment. How does this relate to the docs community
home page? I think we need to be clear how the two relate - I remember
querying whether the docs community page ought to be a docs landing
page. I'm not so much bothered what the answer is as whether we clearly
understand (and, more importantly, that visitors can clearly see) what;s
supposed to go where.

Anyway, on to the page itself:

It's almost 5 pages long; I'm worried whether people will scroll down.
Could the headings be links at the top that jump down to the right place?

Some of the categories look, well, odd. The first section mixes packaging,
databases, and education. I wouldn't put DTrace and ZFS together. So I would
change the categories. In no particular order:

ZFS
DTrace
Databases
Distributions
Virtualization
IPS (and making packages)
CIFS and Windows (which is separate from NFS etc)
Crypto
Networking
X11 (including desktops like xfce and JDS)
SMF
Storage (which would include mpxio, hadoop, QFS, FCoE)
Observability (including debugging, performance, benchmarking)

I hope you get the idea.

(I was intrigued to find JKstat alongside printing, games, and mdb. Definitely
an eclectic bunch!)

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to