Expand «Custom entry index pages» to other CP sources (Assets, Users, Users Groups) + improve discoverability

[alexanderloewe]

First: the new Custom entry index pages integration into the Main Navigation is excellent. The UX feels substantially more intentional, and it finally enables a content-first way to organise the CP for real-world projects. Kudos.

However, in daily use I’m running into two gaps:

1. The configuration is not discoverable enough.
2. The concept is limited to Entries, while other CP sources are equally “content”.

1) Discoverability: configuration feels hidden

Right now, the configuration for Custom entry index pages is not obvious from a user perspective. It’s easy to miss, which reduces adoption.

Proposal

Move (or mirror) the settings to a more predictable place, e.g.:

• Settings → Control Panel → Navigation / Index pages
• Settings → Navigation → Content Organization

If the current location must remain, even a small UX bridge would help:

• a direct link (“Configure custom index pages”)

2) Extend the concept beyond Entries

Craft has become increasingly entry-centric, and many projects model most “things” as Entries. Now that Custom entry index pages allow a content-first navigation structure, the next logical step is:

• Users are content
• User Groups are content architecture
• Assets/Volumes are content containers
• (Optional) Some Plugins are/offer “custom or extrended content”

Today, the “custom index pages” idea stops at Entries, which prevents a cohesive navigation model.

---

Proposal: Generalise “Custom entry index pages” into “Custom index pages” for CP sources

Goal

Allow the same “custom index page” grouping/placement concept to apply to:

• Entry sections (existing)
• Assets volumes / sources
• Users
• User Groups
• (Optional) Plugin CP sections

Core UX principle

Users should be able to assign any CP source to a Navigation Group / custom index page group, so the CP reflects the project’s information architecture.

---

Why this matters

Once Craft embraces content-first navigation via Custom entry index pages, users will expect that same information architecture to cover the rest of the “content surfaces” they manage daily (documents, users, groups). Otherwise the CP becomes split-brain: structured for Entries, but flat for everything else.

Happy to provide mockups or detailed UX suggestions if helpful.