add help drop downs to primary nav

[scd]

Do we want to do this dynamically to save bandwidth?

Not urgent, but seems like a better workflow given I am now referring to articles a lot.

[lordyavin]

You mean like if hovering over the other tabs? Would be nice to access the help faster.

[brendanheywood]

+1

[brendanheywood]

If we do load this dynamically grab the whole tree in one call, not one call for each nested layer. This call can have a medium cache expires like a week.

[scd]

OK this is done in repo and is awesome. Dynamically loaded from api call

/api/config/articles

It was a little bit fiddly because I decided to make sure the the API and article's page called common code to build the article titles structure, which meant refactoring logic out of articles template.

[brendanheywood]

Awesome

I think now I'll flatten those few 3rd level pages, ie move 'bugs' up on level, 'tick types' etc up, and move gyms into it's own top level item, so from now on there is only ever 2 levels. Also thinking I'll make the left menu when inside the articles collapse all submenu items except the one you are in so it's more condensed and the same as index tab.

[brendanheywood]

Ok got this working much better now, I have completely removed the 'help nav' css and it now uses the exact same css as the main index nav and so is perfectly consistent.

In the process I've had a pretty good look through all the articles and not only do I think they need a lot of tlc, but also the structure is all over the shop as we've kept on adding stuff. In particular now that we have only 2 levels I think we need to be slightly more top heavy, ie more top levels and no more than 10 children. 'contributing' is the worst problem one. I'll put down some more thoughts in a new issue