Search by

Managed site navigation for Contenir CMS: the Navigation section of Site Pages, where editors build, publish and restore the site's menus, over contenir/contenir-navigation.

Package info

github.com/contenir-extension/navigation

Type:contenir-extension

pkg:composer/contenir-extension/navigation

Statistics

Installs: 7

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

dev-main / 0.1.x-dev 2026-10-24 11:05 UTC

This package is auto-updated.

Last update: 2026-10-24 11:05:28 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.
  • Drafts and publishing: every change goes into the menu's draft, which shows how many changes it holds. Publishing makes the draft live as a revision, recording who published it and an optional note. Changes can be discarded, and History restores any earlier revision into the draft.
  • 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, discarding and restoring need Update; deleting needs Delete; and publishing needs Approve, so a role can work on a menu's draft without making it live.

Development

composer check   # format, lint, guard, static analysis, both suites and mutation testing
composer boundary