FreeNew
base-pages
No summary provided by the publisher yet.
Install
msc install --appId=base-pagesWhat this extension does
Pages API
A module for managing pages with GraphQL support.
Abstract
The base-pages module provides functionality for handling pages in modern applications. It integrates with GraphQL APIs, offering mutations and queries for page management.
What it does
This module enables your application to:
- Manage pages through GraphQL mutations and queries
- Handle page content and metadata
- Provide real-time updates via subscriptions
Key Features
- GraphQL Integration: Provides mutations and queries for page data
- Data Storage: Persists page information in the database
- Event System: Supports subscriptions for real-time page updates
Changelog
1.7.0 (2026-11-10)
- The page "Pages" has what a page says to the search engines and to a preview of its link (SEO): the title, the description and the keywords, under the text. They are kept in the page's
customData.seo({ title, description, keywords }, the rest ofcustomDatais left as it is); a storefront reads them from the querypage. An empty field is the storefront's own: the title of the page, the description of the site, no keywords. - The MCP tools
page-createandpage-updatenamecustomDatain their schema.
1.6.1 (2026-11-08)
- The text editor of the page "Pages" has the blocks the storefront styles (layout2, the keys
text-*of the layout): "Subheading" (h3), "Note" (blockquote, a framed block) and "Divider" (<hr>, a line between parts of the text).
1.6.0 (2026-11-01)
- The page "Pages" switches a page on and off (
enable): the switch of each row is saved at once (POST /admin/pages-manager/pages/:id/enable, as the banners' of base-promotions), the one of the form - with Save; a new page is switched on unless switched off in the form. A switched-off page answers "not found" on the storefronts, an open one is told by the subscriptionpage; a link to it in the site's menus stays until it is taken off in the navigation.
1.5.1 (2026-10-28)
- Built with TypeScript 5 (was ^3.1.6): 3.x knows no
target: ES2022, compiled the admin app to ES5, and an ES5 class cannot extend Adminizer'sAbstractAdminizerApp-new PagesApp()threw inadminizer:loadedand the whole admin panel stayed unmounted (1.5.0 on the HP server, /admin - 404). - The hook's
adminizer:loadedhandler catches: a failure of the module's admin part is logged and does not stop the panel.
1.5.0 (2026-10-28)
- The admin panel part is an Adminizer app (
src/adminizer/PagesApp, enabled onadminizer:loaded): the page "Pages" in "Marketing" (/admin/pages-manager, rightpages-manager) - the list of pages with Edit and Delete, a page's title (its heading on the site), address (/static/<slug>; empty - made from the title) and text in a rich text editor: paragraphs, headings (h2, the one level the storefronts style), bold, italic, underline, lists, links, tables. A page is added (switched on) and deleted there; it is not switched off: it would stay a link of the site's menus answering "not found" - a link is taken off in the navigation. - The page's source is
ui/PagesManager.jsx(Tiptap: semantic HTML, the tables of the pages kept), the bundle the panel imports -assets/adminizer/PagesManager.js, in the repository: after a change of the sourcenpm run build:adminizer. - The model's table in the admin panel is gone (
src/lib/bindAdminpanelconfig.ts), and with it the hook'safterHook, which only bound it.
base-pages
- 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.4.3 (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). - The hook waits under its own name
base-pages(wasbase-vacancy).
Release history
14 releases| Version | Channel | Status |
|---|---|---|
| 1.7.0 | staging | Latest on staging |
| 1.6.1 | staging | Archived |
| 1.6.0 | staging | Archived |
| 1.5.1 | staging | Archived |
| 1.5.0 | staging | Archived |
| 1.4.3 | staging | Archived |
| 1.4.2 | staging | Archived |
| 1.4.1 | main | Latest stable |
| 1.4.0 | main | Archived |
| 1.3.0 | staging | Archived |
| 1.2.1 | main | Archived |
| 1.2.0 | main | Archived |
| 1.1.3 | main | Archived |
| 1.1.2 | main | Archived |
Support
Issues with the extension itself go to the publisher. Anything about the registry goes to us.