On Mon 28 Apr 2008 at 12:36PM, Michelle Olson wrote:
> Hi all,
> 
> Thanks again for your detailed feedback, I've updated the landing pages 
> with a lot of additional links this weekend and tried to incorporate all 
> of your changes. Please have a look and let me know how you think it is 
> coming, and if the content I've added make sense. If there are errors, 
> omissions, broken links, any help you can provide is much appreciated!
> http://opensolaris.org/os/project/website/splash3/

Michelle, overall, I think these pages seem very helpful.  My only
strong comment is that the right hand column is not functioning properly
as a column-- I think that having each of the callout boxes be a
different width is visually jarring.  I would recommend ensuring that
the righthand area is reserved in all of these three pages cases as true
column.

Some nits:

I would recommend that in links prefaced with the >> character,
that the >> not be part of the link itself.  In other words:

Instead of:
   <a href="blah"> &raquo; some link to content</a>
   &raquo; <a href="blah>some link to content</a>

Perhaps "New-to-Solaris" should be "New-to-OpenSolaris"?

Some of the callout boxes seem a little overly self explanatory.  For
example, if the heading is "Quick Source Browser Links" (already wordy)
do we really need "Use these links to browse the components" in the
callout box?  I would replace both with just (perhaps) "Source Code
Bookmarks" in the title of the callout box.  Ditto for the rest of
the callout boxes.

Random ideas:

I like the "link lists", for example: "Communities that Code Core
Technologies."  Brainstorming for a second: One thing which might add
visual interest would be grouping this into more of a "cloud" shape:

            Nevada   ZFS   Zones   DTrace
      Service Management Fault Management  Security
         Performance Networking Branded Zones 
           Device Drivers  X Window System  

Just a thought.

        -dp

-- 
Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp

Reply via email to