Ankesh,
Excellent suggestions all around, thanks! I don’t think Sofat was particularly
paying much attention to the stylistic elements yet, but we might as well clean
those up next as this is nearly ready to go online.
Other comments below.
On Jul 16, 2015, at 4:00 AM, Ankesh Anand <ankeshanand1...@gmail.com> wrote:
> On Thu, Jul 16, 2015 at 8:23 AM, Christopher Sean Morrison <brl...@mac.com>
> wrote:
> Thanks Ankesh,
>
> It’s not clear to me from your screenshot what is broken, though. If it’s
> the top-level menu not working, that’s not the focus — only the documentation
> presentation (not the content itself) and the side-menu. Basically, feedback
> on the documentation framework itself and navigation constructs are what can
> help the most.
>
> Sean, I wanted to point out that the top navigation bar took an extra row of
> space on my screen.
It’s wrapping the menu because of your window size. Definitely something to
get fixed, but not related to the Docs project.
> Regarding the documentation presentation, I want to point out a few things:
>
> - The right subnav goes away on my mobile, so there is no way to navigate to
> a different documentation section if I want to.
>
> - The subnav should be sticky. If I am reading a long documentation page, I
> shouldn't have go back to the top of the page to move to a different
> documentation page.
>
> - As a rule thumb, if the sub-navigation contains important links(such as in
> our case), it should be put on the left than on the right. That's because the
> typical style of reading is from left to right, and the left side is usually
> where people expect the navigation to be. This is also validated by the
> F-shaped pattern observed for viewing content:
> http://www.nngroup.com/articles/f-shaped-pattern-reading-web-content/
I suggest putting search and navigation on the left, but keeping languages,
editing options, and other options specific to the document being viewed on the
right.
> - The word 'BRL-CAD Main Menu' is a bit confusing to me if all it does is
> encapsulate the search bar.
Agreed. It also looks like a link. Can probably just remove it altogether and
make it a field to search all documents (changing the title to “Search
Documents”)
> - [Minor] The font-size of documentation is a little big, 14px should be
> ideal for readability.
Sofat, Do those all make sense? A couple other issues I see are:
- The navigation titles should be clickable (currently only the little +- box
are clickable). Clicking the title should either expand that menu section or
display the menu (perhaps fully expanded) on the content pane.
- The +- box and article icons should be vertically centered with the word
- Some pages, the images are not displaying at the right scale, for example
http://202.164.53.122/wordpress/articles/en/build_pattern.php
- I like that the menu remembers what was expanded/collapsed, but there needs
to be some visual indication for what is actively being displayed.
- Move the edit button out of the content pane closer with the language options.
Cheers!
Sean
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel