Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature: Navigation #4535
The Navigation UI provides a simple user interface for creating a list of links to output in your theme. The interface allows for the clickable text and url for each link to be entered. Each item can be reordered using drag and drop, edited, removed and new items can be added to the end of the list. In the theme API, we get a new
Should we wrap with
Should we put the ARIA role into the UL? Like
@JohnONolan Two questions:
Should the default 'Home' item only be present in the UI by default (and stored after pressing save) or should it be stored by default and output by the
Should the navigation helper definitely always output absolute URLS? (Note: I moved that part of the spec to #4541)
referenced this issue
Jan 15, 2015
#4539 is already closed, but this will be harder to change later. So here is my 2c:
Hi there, just thought I'd share my view on post, pages & navigation structures from working with different content management systems for over ten years.
A lot of other platforms make the visual distinction between navigation and the actual content like you're proposing here. One downside with it is that it cripples the publishing flow somewhat since most of the time you're first "writing content", and the "attching it" to a structure. In other words you're transforming a simple task into a two-step process.
Also, for the person writing the content, the only point of separating the navigation structure from the pages is if it's possible to create several navigation structures and publish the same page in several of them at the same time.
A simpler way to present this to the user would maybe be to create a new view called Pages/Site/Whatever where the navigation structure is shown. Here users can create "pages" of different kinds, for example:
When the user creates a new entry the new post is created together with the navigation item in a single transaction, making it seemless for the user and turning it into a single step. If this kind of view was created, then maybe it would also be logical to filter out posts with
In other words, the same underlying structure could be used, it's just presented in a different way.
Btw, I really love the project!