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

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's AbstractAdminizerApp - new PagesApp() threw in adminizer:loaded and the whole admin panel stayed unmounted (1.5.0 on the HP server, /admin - 404).
• The hook's adminizer:loaded handler 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 on adminizer:loaded): the page "Pages" in "Marketing" (/admin/pages-manager, right pages-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 source npm run build:adminizer.
• The model's table in the admin panel is gone (src/lib/bindAdminpanelconfig.ts), and with it the hook's afterHook, 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 }, tooltip instead of description).
• The hook waits under its own name base-pages (was base-vacancy).