Entry Types: Usage Limits & Level Restrictions

[Steve-JG]

Thank you in advance for reading & considering :)

Feature Request -

It would be great if we could apply Usage & Level restrictions to entry types which would be specified on the Section (since Entry types can be added to any Section at will).

Reasoning -

This request is based on my preference to create websites primarily using structures - vs a combo of singles (for index pages) and 'disconnected' channels/structures.

I feel the benefits to heavily going down the structure route are as follows -

• It reduces the overall number of sidebar items in the Entries area
  (as exampled below with my 'About' area - I'd need 3 different tabs)

• It allows you to more closely mirror the frontend sitemap/structure, improving the users' ability to navigate the CMS and find the content to edit.

• The URL structure is more dynamic with the use of /{parent.uri/{slug}/ - where as with a channel that has a parent single, you need to explicitly set the parent slug? (which can cause issues if you allow the user to modify the single URL on the entry)

---

Usage Scenarios

Below is a mockup of 3 separate site areas, which I feel is considerably cleaner to interpret & navigate, than if I had created a series of singles & additional sidebar tabs in the Entries area.

1) INSIGHTS & EVENTS

A section which houses all blog posts & events. Naturally, the 'Insights & Events' Index page should only exist once, and only be created at the top level.

Applying both a Usage Limit(1) and a Level Restriction(1), would prevent the user from:

• Creating an additional 'Index' page
• Accidentally moving the Index page to the 2nd level = to live within the Insights/Events
• Accidentally moving the Insight/Event posts to the top level, to sit outside of the rest.

2) SERVICES

Similarly to I/E above, the 'Services' index page would only exist once, and at the top level, the 'Service Type's at 2, and the individual 'Service' at 3.

3) ABOUT US

This section is a bit different, as the 'Meet the Team' index page sits at level 2, as a child & sibling of 'General' content pages.

In this particular scenario, it would be cool if I could somehow assign the 'Team Profile' Entry type to only ever be allowed created as a child of 'Meet the Team' - as it isn't something that should exist anywhere else.

---

Comparatively, it just feels strange/a bit wrong if I were to create e.g. the Insights & Events index page as a 'single', to by-default live with all the other singles in which it has no relation to.

I could 'mostly' mimic what I'm after by 'Customizing Sources' - but I feel my suggestion with structures would still be cleaner.