contenir-extension / navigation

v0.3.3 2026-11-05 01:14 UTC

Requires

• php: ~8.3.0 || ~8.4.0 || ~8.5.0
• contenir/contenir-extension-api: ^0.7.4 || ^0.8 || ^0.9
• contenir/contenir-navigation: ^0.2
• php-db/phpdb: ^0.6.0
• psr/clock: ^1.0
• psr/container: ^1.1 || ^2.0
• psr/http-message: ^1.1 || ^2.0

Requires (Dev)

• contenir/contenir-qa-tools: 0.1.x-dev
• infection/infection: ^0.34.1
• nyholm/psr7: ^1.8.2
• peptolab/phpdb-migration: ^0.2
• php-db/phpdb-sqlite: ^0.3
• phpunit/phpunit: ^11.5.42

BSD-3-Clause

• menu
• navigation
• contenir
• contenir-extension

Published on Packagist.org on 2026-11-05 01:14 UTC

README

Managed site navigation for Contenir CMS. The add-on adds a Navigation section to Site Pages, where editors build the site's menus, such as its header and footer, then publish them for the site to draw. It works over contenir/contenir-navigation, which holds the menus, and the site draws them through an adapter such as contenir/contenir-navigation-mezzio.

• Menus: add, rename and delete them, each with the handle the site's templates ask for it by.
• Items: link each to a page or other record the site marks as linkable, to an address (a path, a full link, a fragment, an email address or a phone number, typed with no prefix), or to nothing, as a heading or a little text. Items nest, move up and down, and say how they are drawn: a label, an icon token or both, a new tab, extra classes, and a switch to hide them.
• Publishing: a new menu is a draft the site doesn't show until it is published once. After that, every change to it goes live as it is saved, each save recorded as a revision with who made it, and History puts any earlier revision back on the site.
• Badges mark items the site won't show as they stand: a record that is a draft, unpublished, archived or gone, or an item that is hidden.

Requirements

• Contenir CMS with the extension API 0.7.x, lending add-ons the site's database, its records (Record\RecordsInterface) and the editor signed in (Editor\CurrentEditorInterface)
• contenir/contenir-navigation, whose migrations the CMS runs against the site's database

Permissions

Every screen is guarded by the section it adds, site.navigation.menus. Viewing needs View; adding menus and items needs Add; changing, moving and restoring need Update; deleting needs Delete; and publishing a menu for the first time needs Approve. Once a menu is live, anyone who may change it changes the site's menu.

Development

composer check   # format, lint, guard, static analysis, both suites and mutation testing
composer boundary
npm ci
npm run test:coverage
npm run build    # the menu tree's script, into public/js, which is committed