View Issue Details

IDProjectCategoryView StatusLast Update
1366Composrcorepublic2013-12-30 23:56
ReporterChris Graham Assigned ToChris Graham  
PrioritynormalSeverityfeature 
Status resolvedResolutionfixed 
Summary1366: Adaptive menu mode
DescriptionBy default, vastly simplify site structure set up. Make it so the default menu is auto-managed from the site-tree, only showing stuff where there actually is content.

i.e No link to downloads until you have a download.

Another advantage of this is that if the default menu is a drop-down, we essentially "de-obscure" all Composr features, as some are not currently linked in by default.

If you go in to edit the automatic site-tree based menu, it tells you it is auto-managed, but has a button to clone it to a manually managed menu.

We can rip out all the default menu item placement from Composr module install code knowing that the adaptive menu will do it for us initially. It would be good for Composr to be smart though, when you add the first piece of content, it asks you whether to add the content type to your manually managed menu (if you've set it up for manual management).
TagsNo tags attached.
Attach Tags
Time estimation (hours)4
Sponsorship open

Sponsor

Date Added Member Amount Sponsored

Relationships

related to 142 ResolvedChris Graham Merged sitemap API 
related to 16 ResolvedChris Graham Fully support menu stitching 
related to 1367 ClosedChris Graham Adaptive block mode 

Activities

Chris Graham

2013-12-30 23:56

administrator   ~1949

This is mostly done.

It's not fully adaptive, because I decided that's inefficient/confusing. If you installed downloads, you want it on the menu -- because you will be considering your whole nav, plus want to see where things will go.

In some cases it is adaptive to content, e.g. for invoices and subscription management, which are minority features that should stay buried for most users on the site.

In all cases it is adaptive to what you have installed, given it is generated from the Sitemap.

It'll still be the case that unwanted features should not be installed, there are many usability and performance reasons for this as a key to our approach.

The ability to clone an automanaged menu to a managed one was implemented.

Issue History

Date Modified Username Field Change