FreeNew
simple-navigation
No summary provided by the publisher yet.
Install
msc install --appId=simple-navigationWhat this extension does
Simple Navigation API
A module for managing simple navigation with GraphQL support.
Abstract
The simple-navigation module provides functionality for handling navigation menus in applications. It integrates with GraphQL APIs, offering features for menu management and navigation.
What it does
This module enables your application to:
- Manage navigation menus through GraphQL
- Handle menu items and structure
- Provide navigation data for frontend
Key Features
- GraphQL Integration: Provides queries for navigation data
- Data Storage: Persists menu and navigation information
- Menu Management: Supports hierarchical menu structures
Where the parts live
models/Navigation.ts— the menus;src/controller— sitemap and robots; GraphQL queries. The settingROBOTS_DISALLOW_ALL(settings/) turnsrobots.txtintoDisallow: /for every robot.src/adminizer/NavigationApp.ts+ui/NavigationManager.jsx→assets/adminizer/NavigationManager.js— the admin page/admin/navigation-manager(rightnavigation-manager), built bynpm run build:adminizer.src/mobile/NavigationMobileApp.ts+mobile/navigation.js→assets/mobile/navigation.js— the same editor in the mobile admin app, as one JS file the server hands the phone (theapp-mobile-apihook of restoapp, registered onmobile-api:ready), built bynpm run build:mobile.
Changelog
1.9.0 (2026-11-19)
- The setting
ROBOTS_DISALLOW_ALL(settings/robots_disallow_all.json, off by default): on,robots.txtisUser-agent: *andDisallow: /, without the sitemap - for a test or preview server that must stay out of search. Read on every request, no restart. robots.txthas no blank line between the rules: a blank line ends the group, and a robot could drop theDisallowlines after it.
1.8.2 (2026-11-10)
sitemap.xmlhas the pages of the sections of the menu (/menu/<section>, every section whose dishes are in it) and the switched-on text pages of base-pages (/static/<slug>, where that module is installed) - before, only those a menu of the site linked to. A dish a menu links to goes in once.
1.8.1 (2026-11-04)
sitemap.xml: the address of a dish is/menu/<section>/<dish>, without a query; an address goes in once, and only the pages of the site do - no outer links and no#of the menus.
1.8.0 (2026-11-04)
- The module's screen in the mobile admin app: «Навигация», the editor of the site's menus on the phone - add a menu and delete it, rename it, add an item, change its label, its link (the site's pages offered) and its icon, switch it off, drag it into place, delete it. The same menus and the same right as the admin page,
navigation-manager. - The app's code is one JS file the module ships: the source is
mobile/navigation.js, the bundle the mobile API hands the phone isassets/mobile/navigation.js, in the repository next to the admin page's one; after a change of the sourcenpm run build:mobile(esbuild,mobile/package.json). - The server part is
src/mobile/NavigationMobileApp.ts(the app, its methods and their schemas) andsrc/mobile/menus.ts(theNavigationrows): registered onmobile-api:readyof theapp-mobile-apihook of restoapp, the way the admin page is enabled onadminizer:loaded. A server without the mobile API loads the module as before.
1.7.1 (2026-10-28)
- The hook's
adminizer:loadedhandler catches: a failure of the module's admin part is logged and does not stop the panel (Adminizer emits the event inside its start; base-pages 1.5.0 left the HP server's panel unmounted that way).
1.7.0 (2026-10-28)
- The admin panel part is an Adminizer app (
src/adminizer/NavigationApp, enabled onadminizer:loaded): the page "Navigation" in "Marketing" (/admin/navigation-manager, rightnavigation-manager) - the menus on the left, the items of the chosen one on the right: switch, label, link with the site's pages offered (sections of the menu, static pages, stocks), icon, the order by dragging; a menu is added and deleted there. The switch writes bothactiveandvisible; the other keys of an item are kept. - The page's source is
ui/NavigationManager.jsx, the bundle the panel imports -assets/adminizer/NavigationManager.js, in the repository: after a change of the sourcenpm run build:adminizer(esbuild,ui/package.json). - The model's table in the admin panel is gone (
src/lib/bindAdminpanelconfig.ts): its items were raw JSON. - The editor's Save, Undo changes and Delete stay at the top while the form scrolls; the questions (unsaved changes, deleting, the link of the text) are the panel's dialog (
window.UIComponents.Dialog,ui/ask.jsx), not the browser's confirm and prompt.
1.6.5 (2026-10-27)
- MCP: menu items with link, active, visible - as the storefronts and the sitemap read them; config/bootstrap.js rebuilt from bootstrap.ts.
1.6.4 (2026-10-22)
- The build is plain
tsc: browserify and gulp are removed. - Admin panel config in the current sails-adminpanel field format (
{ visible: false },{ title },tooltipinstead ofdescription).
1.3 Add sitemap.xml
Release history
21 releases| Version | Channel | Status |
|---|---|---|
| 1.9.0 | staging | Latest on staging |
| 1.8.2 | staging | Archived |
| 1.8.1 | staging | Archived |
| 1.8.0 | staging | Archived |
| 1.7.1 | staging | Archived |
| 1.7.0 | staging | Archived |
| 1.6.5 | staging | Archived |
| 1.6.4 | staging | Archived |
| 1.6.3 | staging | Archived |
| 1.6.2 | staging | Archived |
| 1.6.1 | main | Latest stable |
| 1.6.0 | main | Archived |
| 1.5.0 | staging | Archived |
| 1.4.2 | main | Archived |
| 1.4.1 | main | Archived |
| 1.4.0 | main | Archived |
| 1.3.5 | main | Archived |
| 1.3.4 | main | Archived |
| 1.3.3 | main | Archived |
| 1.3.2 | main | Archived |
| 1.3.1 | main | Archived |
Support
Issues with the extension itself go to the publisher. Anything about the registry goes to us.