-
Notifications
You must be signed in to change notification settings - Fork 681
Description
Created by: Neal Stammers (neal@netgorilla.co.uk) on 2015/03/10 18:02:16 +0000
Votes at time of UserVoice import: 5
This would allow for creating a fixed structure of 'single' pages.
For example if you had a parent 'about us' page with the following child pages: staff, policies, etc.
Currently the URI has to be hard-coded:
about/staff
about/policies
Which is fine until you need to update the URI for the parent. You would then need to go through each child page and update the URI.
We've tried using structures, but this falls down when you want to use custom templates/fields for lots of individual pages (a staff page is very different from a policies page). You end up with lots of 'Entry types' available, but you probably wouldn't want a user re-using 'staff' or 'policies' template. Hence why a 'single' is perfect.
Having a hierarchy also makes it much easier to render breadcrumbs and side menu's of pages with the same parent.
I'm guessing it would also make it easier to find the single to edit if it's in a tree view