Assume as an example that I wanted to create a subpage for the Pages section of Dashboard for some tool or purpose. (external tool embed showing stats for group’s pages, )
Is it possible to do the following?
- Define the content of a new backend page. (i.e. /livewhale/?pages_tool)
- Add a subnav item (or main nav) for that backend page in an appropriate place.
- Limit the visibility of the page and nav items to specific groups or permissions.
…and if so, what is the best practices around this kind of development?
I am particularly interested in the possibilities of #1 and #3.
Additional Context
I’ve addressed #2 and #3 somewhat previously using a module onOutput
using str_replace
to sneak in some additional navigation items for the Registrar’s office.
For the main links of these sections, like “Course Data” under Courses, I added links to previews of widgets. That works, but the ideal would seem to be able to make a backend page which shows that widget (or similar output in an alternative approach) within the Dashboard UI, rather than linking out to a widget preview.
Specifically, I’m interested in making an additional backend page under Groups & Users where I can define a dashboard to help me better manage editors using custom fields I recently added. The exact what/why of that would be an entire separate thread, but in brief, I want any such Users resource to only be accessible in (#2/3), and ideally integrated into (#1), the Backend.