Navigation
Navigation lets editors own primary, footer, sidebar, and campaign menus per site and language.
What Navigation helps you do
Active Capell Membership access covers the curated Released catalogue and lets the account opt into Beta extensions after reviewing their risk.
Workflow screenshots
6 capturesNavigation lets editors own primary, footer, sidebar, and campaign menus per site and language.
Link pages or custom URLs, nest dropdowns, and render menus in the theme with one tag.
Active states, publish windows, and site cloning keep menus aligned with published Capell content.
Use it when site structure should be editor-managed and reliable across languages or sites.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Navigation adds when enabled.
- Navigation
- Menus
- Page Url References
- Drag Drop
- Frontend Cache
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/navigation -
02
Register the extension
php artisan capell:extension:enable navigation -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Navigation
Switch the evaluation lens to see how different roles should assess this package before installing it.
The menu follows the page tree on its own — what to verify
Add, rename and reorder child pages beneath an auto-expanding menu item. Navigation should mirror each change without direct menu editing.
Read more Show less
Acceptance evidence: Because a Page item pulls in its children automatically, adding or moving a page under it updates the menu with no hand-editing, and the active highlight follows along on its own. Site owners grow and rearrange the site without entries drifting to the wrong place.
Boundary of fit: On a small site whose menu is basically fixed, site owners would rarely feel the benefit. A static menu is perfectly adequate when the structure is stable and site owners are not reshaping it as things grow.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
