Skip to content

feat: rework of menu management UI with overview and detail pages - #680

Open
wkonecny wants to merge 2 commits into
VirtusLab-Open-Source:masterfrom
wkonecny:feat/navigation-overview-page
Open

feat: rework of menu management UI with overview and detail pages#680
wkonecny wants to merge 2 commits into
VirtusLab-Open-Source:masterfrom
wkonecny:feat/navigation-overview-page

Conversation

@wkonecny

@wkonecny wkonecny commented Jul 7, 2026

Copy link
Copy Markdown

Ticket

N/A

Summary

This feature replaces the navigation dropdown and Manage modal with a Strapi-style overview page listing all navigations in a table. The dropdown did not show all navigation items without scrolling, which confused our users multiple times.

Note: A lot of files were moved to account for the Overview/Detail split. The QueryClientProvider was moved to the App.tsx so it could be reused across overview/detail pages.

Test Plan

The functionality was tested manually in multiple configurations. The settings page is untouched.

Note: I did not make any API changes in this PR, so no additional testing was needed on that front.

Screenshots

Overview page
Screenshot 2026-07-07 at 15 41 51

Detail page
Screenshot 2026-07-07 at 15 42 54

Wouter Konecny added 2 commits July 7, 2026 15:01
Replace the navigation dropdown and Manage modal with a CMS-style
overview page listing all navigations in a table (create, edit,
delete, cache purge), and turn the item editor into a URL-driven
detail page with a back link.

- add OverviewPage as the plugin landing route, DetailPage at /:documentId
- rename pages/HomePage to pages/DetailPage
- move shared API/permission hooks to admin/src/hooks
- remove the NavigationManager modal, reuse its form in the overview modal
- add pages.overview translations to all locales, drop obsolete manager keys
Point the overview page, form modal and detail header at the existing
popup.navigation.manage.* and form toggle keys instead of introducing a
parallel pages.overview namespace. Locale files now only add the four
genuinely new strings (subtitle, items/actions columns, empty state),
drop keys that lost their last consumer, and backfill the visibility
toggle labels missing from ca.
@CodeVoyager
CodeVoyager self-requested a review July 25, 2026 07:33
@CodeVoyager

Copy link
Copy Markdown
Contributor

Hi @wkonecny

Thank you for your contribution! There are few blockers for this PR

  • This PR assumes a new style of view as a standard. Yet there are customers of this plugin that are used to this way.
  • If we want introduce new way then we must start with new style as an option. Current is default and new one is selectable form plugins settings. Of course we can add hint or a button that will update that settings from current style, and vice versa.
  • README file should also be updated.

We appreciate your effort!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants