Frontend for the Admin Portal. This web interface is used by Community Admins (cadmins) to administer community-specific portals and by Super Admins to administer the entire MassEnergize web platform.
You can find all context related to this PR in the tickets I've linked.
Here are the features introduced:
[X] There is now a new page dedicated to editing menu items. You get there through the "community profile page" of each community, and click "Configure Navigation"
[X] You can add as many items to the navigation list as you want, and each of them can have children, infinitely š
[X] You can remove any child
[X] You can edit any menu item
[X] You can reset menu (Removes all custom modifications)
[X] Any menu item can either point to a page internally, or externally
[X] You can change community logo, and provide an external link users will be taken to when they click on the logo
Summary / Highlights
You can find all context related to this PR in the tickets I've linked. Here are the features introduced:
[X] There is now a new page dedicated to editing menu items. You get there through the "community profile page" of each community, and click "Configure Navigation"
[X] You can add as many items to the navigation list as you want, and each of them can have children, infinitely š
[X] You can remove any child
[X] You can edit any menu item
[X] You can reset menu (Removes all custom modifications)
[X] Any menu item can either point to a page internally, or externally
[X] You can change community logo, and provide an external link users will be taken to when they click on the logo
DEMO
https://github.com/massenergize/frontend-admin/assets/26961591/e6950041-111c-4485-a338-74fb618159dd
https://github.com/massenergize/frontend-admin/assets/26961591/e98788d7-9d24-4765-ac98-86c8135b4549
Details (Give details about what this PR accomplishes, include any screenshots etc.)
Testing Steps (Provide details on how your changes can be tested)
Requirements
Transparency (Project board)
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch or to a feature branch, not themain
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)Other information: Any otherthing we need to know