Implement megamenu highlight, using a body class (either hard-coded or generated by the CMS) match against the class on each link. Addresses #644.
Merge branch 'develop' into 644-megamenu-highlighting
Use reverse_id rather than the slug attribute on body class. (#644)
Hard-code appropriate body class into storybase_user list and detail templates. (Projects, Organizations, etc.) (#644)
Add proper class to my account megamenu. (#644)
Convert tabs to spaces in megamenu template. No other changes.
Better method for right-aligned My Account menu in megamenu. Add in commented-out News & Updates menu. Tighten up margins in megamenu to allow for more stuff in there. (#642)
Update megamenu content to match current content outline in google doc. I hope. (Needs review.) (#642)
Convert tabs to spaces in megamenu.less. No other changes.
Tweaking and slightly more sanity to megamenu styling. (#642)
Content updates and style tweaks to megamenu. (#642)
Add subtle shadow to megamenu legends. (#642)
Merge branch '642-megamenu-content' of https://github.com/patternleaf/atlas into patternleaf-642-megamenu-content
Added classes to highlight "News" item in megamenu

Assumes top-level page of the "News" section has an id of ``news``.

Closes #644
Wire in links for "News & Updates" section

Assumes pages with these ids exist:

* story-raisings
* workshops
* updates

Closes #642
Dynamically generate sub-page lists in megamenu

I also had to alter the call to ``reverse`` in
``NewsItem.get_absolute_url`` and attach the news item apphook to pages
*IN EVERY LANGUAGE* in order for the URL reversal to work correctly for
the news item detail pages in the menu.

Addresses #664
Move megamenu templates to the menu subdirectory

Addresses #664
A more dynamic, DRY megamenu template

These commits try to clean up the megamenu templates to avoid repeated
markup and hard-coded URLs.

I made the ``menu/megamenu.html`` template be included using the
``show_menu`` template tag instead of ``include``.  This allows the URLs
for the menu items to be generated from the back-end instead of
hard-coded in the templates.  This also lets us rely on the menu system
to tell us if the menu item is active instead of matching megamenu and
body classes (though I left in the wiring for the body classes).

I added a ``STORYBASE_MEGAMENU_ITEMS`` setting to specify which items
are in the megamenu and a template filter, ``megamenuitems``, to reduce
the ``children`` list passed to the template by ``show_menu`` to just
the desired items.

I broke each megamenu item's additional content into separate templates
that all inherit from ``menu/megamenu_extra_base.html``. See the comment at the
top of the ``menu/megamenu.html`` template for how this is wired up. By
default, these templates show the sub-pages and the top-level page's
teaser attribute.

I made the ``CMS_MENU_TITLE_OVERWRITE`` ``True`` by default in the
``settings`` module, allowing admins to specify a different title for
pages when they're displayed in the menu.

Closes #664