I see. Let me just say that it's far from obvious that it's a link to the explaination of the page - it's second of a long list, of which all members are links to other parts of the same page. | [reply] |
| [reply] |
I'd call the link different ("Page Docs" sounds too much like a category like "Meditations", "Reviews",etc). For instance "Help", "Recently Active Threads Manual", "Legend". And I'd place the link elsewhere. Perhaps next to the colour bar on top, or at the bottom of the page. And I'd make sure that
the FAQ points to this help document. I'd say, just doing the latter would be enough. "Need Help??" is a clear link, and stands on its own (not part of the page navigation, nor of the site navigation), so it's quite visible.
| [reply] |
I doesn't belong in that list. I had to supersearch to find this thread to find the doc — it's not like it's hard to see, but it's very well camouflaged by being the odd one out in the middle of an otherwise uniform list of things of a completely different type.
It needs to be visually distinct.
Mockup of a proposed interface:
Viewing Nodes As of: <<<< <<< << < Now
Mode: [Root and Node|V] [Switch] | More settings | How do I use this??
Jump to Discussion | Questions | Meditations | Perl Announcements | Cool Uses For Perl | Categorized Questions | Snippets | Code Contributions
(The mode doodad is a dropdown+button here.)
That visually groups together the things that functionally belong together, and makes different things look different. The current look where a list of config options are all visible all the time and are simple links just like the long bunch of in-page anchors following them makes it hard to scan the area for units of functionality.
Makeshifts last the longest.
| [reply] |