A bunch of ideas allowing developers to defer decisions in, and reduce coupling of, an application's technology stack through the provision of design patterns.
An administrator should be able to create a menu item that serves as an entry point to pages, extensions, and individual entities within an extension. So, for example, I should be able to create a menu item for each of the following:
The 'About us' page;
The blog engine root (needed to get page title / metadata, etc..)
/blog/my-post-title (in the event that the user wants an entry point inside a menu.
I should not have to create a menu item for the following:
Unpublished pages (publishing a page should also create a menu item if the user so chooses to do so);
Blog non-root pages
The menu item needs to store the following data:
Menu Item title (the title displayed inside in the menu)
Browser title (what the <title> attribute will display, in part or in whole)
Metadata
Custom Slug
A reference to the entity or extension
When I create entities, I should have the option of instantly creating menu items from them (give a dropdown for a parent?)
An administrator should be able to create a menu item that serves as an entry point to pages, extensions, and individual entities within an extension. So, for example, I should be able to create a menu item for each of the following:
I should not have to create a menu item for the following:
The menu item needs to store the following data:
<title>
attribute will display, in part or in whole)When I create entities, I should have the option of instantly creating menu items from them (give a dropdown for a parent?)
Comments welcome and needed.