New: Introduce Menus as Pages

[oliverfoster]

fixes #365

With config.json:_isPageMenu = true, menus may have articles, blocks and components, menus are rendered as pages. Use ComponentMenuView and ComponentMenuModel as the basis for menu components, which will inherit the children and therefore completion from the nearest contentobject and render the contentobject's children by default.

New

• Added ComponentMenuView to render child views by default
• Added ComponentMenuModel to inherit the children and therefore completion, from its immediate contentobject ancestor
• Added config.json:_isPageMenu to register PageView for course and menu _type.
• Restricted AdaptView so that a default page doesn't render child contentobject types
• Updated getAllDescendantModels to take a filter argument as part of an options object

Testing

• Install https://github.com/cgkineo/adapt-contrib-menuBox
• Remove default menu
• Add config.json:_isPageMenu = true
• Add course.json:_pageLevelProgress._showAtCourseLevel = true
• Add an article with a _parentId = "course", along with a block and a component, which should have _component = "menuBox"
• Add any other articles, blocks and components to the course page

Or use the following zip, extract and run npm install then build as usual:
test.zip

Todo

• Bring to AATv1 - allow menus to be edited as pages when _isPageMenu = true, default to _isPageMenu when no menu is selected @taylortom
• Remove page header for a banner component Page header plugin - new component? adapt_framework#2703

[StuartNicholls]

I have actually started work on a page header / hero plug-in, will add some layouts we've mapped out on the issue #2703

[kirsty-hames]

This works great thanks @oliverfoster. I have some queries/issues if you could take a look please...

1. When _isPageMenu = true, the PLP drawer only displays contentObject items, none of the standard components show as items. Is this expected? For page views, both contentObjects and components display as items in the drawer.

2. When using the menuBox component as a sub menu, you get a duplicate PLP entry: a child item of course and a child item of the parent contentObject (See screenshot: Page test topic is displaying as a course child in the PLP but this should only be available via Question components topic).

[oliverfoster]

This works great thanks @oliverfoster. I have some queries/issues if you could take a look please...

1. When _isPageMenu = true, the PLP drawer only displays contentObject items, none of the standard components show as items. Is this expected? For page views, both contentObjects and components display as items in the drawer.
2. [...]

Verified, need to tweak plp to get it to work properly.

[oliverfoster]

Aria-levels are off by one for components and group sub items.

[oliverfoster]

The confusing part about this is that the children of the Page Menu don't run in render order.

Ideally:

Parent Name	Child name
Page Menu	Article 1
	SubPage 1
	Article 2
	SubPage 2
	Article 3
	SubPage 3

Whereas because articles live in article.json and pages live in contentObjects.json and the Page Menu can live in course.json, we have the children of the Page Menu children split over two separate files and their order isn't reflective of the render order.

course.json	contentObject.json	articles.json
Page Menu	SubPage 1	Article 1
	SubPage 2	Article 2
	SubPage 3	Article 3

Currently:

Parent Name	Child name	Block	Component	Content Object
Page Menu	Article 1	Block 1	Component 1	n/a
	Article 2	Block 2	Component 2	Sub Page 1
	Article 2	Block 2	Component 2	Sub Page 2
	Article 2	Block 2	Component 2	Sub Page 3
	Article 3	Block 3	Component 3	n/a