The admin dashboard will be a large production piece apart of the itinerary manager. Admins should be able to modify or update various parts of the itineraryManager from the website such as data endpoints used for mongoose.
Depending on the notifier, some such as Discord and Slack apps support embed systems for content visibility. The dashboard should include tools like these to rebuild how the embed looks 'on-the-fly' as opposed to reworking the entire codebase.
Ideally this is entirely managed by a sidebar the directs the user through sub-routes
For example: If the user starts at /admin/dashboard and wants to modify the discord bot embed, Then they should click the "discord" icon under the "bots" section in the sidebar which redirects them to /admin/dashboard/bots/discord from which they can select the embed builder and be taken to /admin/dashboard/bots/discord/embeds
The number of routes in the dashboard is not static and may change depending on which direction the project goes
In general a skeleton should be designed with base implementation:
Header
static to the root-most layout and span across all subpages; should only be imported once and can be used across every child route. Can include the navigation information for the page or sub-routes that can be access within the page.
Sidebar
static to the root-most layout and spans across all subpages; should be used primarily for navigation across other routes
Content display
The primary area on the page where content will be displayed.
The admin dashboard will be a large production piece apart of the itinerary manager. Admins should be able to modify or update various parts of the itineraryManager from the website such as data endpoints used for mongoose.
Depending on the notifier, some such as Discord and Slack apps support embed systems for content visibility. The dashboard should include tools like these to rebuild how the embed looks 'on-the-fly' as opposed to reworking the entire codebase.
Ideally this is entirely managed by a sidebar the directs the user through sub-routes
For example: If the user starts at /admin/dashboard and wants to modify the discord bot embed, Then they should click the "discord" icon under the "bots" section in the sidebar which redirects them to /admin/dashboard/bots/discord from which they can select the embed builder and be taken to
/admin/dashboard/bots/discord/embedsThe number of routes in the dashboard is not static and may change depending on which direction the project goes
In general a skeleton should be designed with base implementation:
Header
Sidebar
Content display