Lucid CMS - Pages Plugin

The official Pages plugin for Lucid

The Lucid CMS Pages plugin adds support for hierarchical documents and slugs to your collections. It's ideal if you're creating content for a website and want to manage pages through collections and documents.

When enabled on a collection, it registers three new fields: fullSlug, slug and parentPage. These fields are used to construct the fullSlug, which is computed whenever a document is edited. The fullSlug is the combination of all the parent slugs and their slugs.

The plugin achieves this by registering hooks that fire at different points in the document lifecycle. Depending on the hook, either its fullSlug is updated via its ancestors, or all of its descendants' fullSlugs are updated.

The intended use case for this plugin is to enable easy document fetching for front-end applications, whereby you can use the URL location to filter a document via the fullSlug. Using the content endpoints that might look something like this:

/api/v1/content/document/COLLECTION_KEY/published?filter[_fullSlug]=about

Installation

npm install @lucidcms/plugin-pages

Setup

To use the Pages plugin, you need to add it to your Lucid CMS config file. You will need to provide it with the necessary configuration options, such as a list of collections to enable the plugin on.

import { configureLucid } from "@lucidcms/core";
import { node } from "@lucidcms/runtime-node";
import { pagesPlugin } from "@lucidcms/plugin-pages";
import { sqlite } from "@lucidcms/db-sqlite";

export default configureLucid({
	runtime: node,
	db: sqlite,
	config: () => ({
		plugins: [
			pagesPlugin({
				collections: [{
					key: "page",
					localized: true,
					prefix: {
						en: "en",
						fr: "fr",
					},
					ui: {
						fullSlug: true,
					},
				}],
			}),
		],
	}),
});

Configuration

This plugin offers several configuration options to control its behavior. Aside from key, all of these options are optional and have default values.

| Property | Type | Default | Description | |----------|------|---------|-------------| | key | string | - | The key of the collection that you wish to enable the plugin on | | localized | boolean | false | If set to true, the plugin will enable translations for the slug and fullSlug fields | | prefix | string \| Record<string, string> | - | Optional prefix prepended to the start of the computed fullSlug for the collection | | ui.fullSlug | boolean | false | Shows the computed fullSlug field in the document builder and listing | | ui.tab | string | - | Places the plugin fields in an existing matching tab | | ui.widths | Partial<Record<"fullSlug" \| "slug" \| "parentPage", FieldWidth>> | - | Overrides the admin grid width of individual plugin fields | | unique | boolean \| { fields?: string[] } | true | Controls route uniqueness validation for computed fullSlug values |

localized

If set to true, the plugin will enable translations for the slug and fullSlug fields. This means that in the documents page builder, the slug and fullSlug fields will require translations for each locale that you have registered in your Lucid CMS config file.

UI

Set ui.fullSlug to true to show the computed fullSlug in the document builder and listing. The field remains disabled because its value is always calculated by the plugin.

Set ui.tab to an existing tab key to place all three plugin fields in that tab, regardless of its position. When the tab does not exist, the option is ignored and the fields retain their normal positional placement.

Fields use Lucid's 12-column admin grid. When fullSlug is visible, it and slug each use half a row and parentPage uses a full row. Otherwise, all fields use a full row. Override individual values through ui.widths using 12, 8, 6, 4, or 3.

prefix

If set, the plugin prepends the given prefix to the start of the computed fullSlug. This does not change the stored slug value itself. You can provide either a single string for all locales, or a locale map when translations are enabled.

unique

By default, each computed fullSlug must be unique within the same collection, version type, and locale. This checks the computed route rather than the raw slug value.

Set unique: false to disable this route uniqueness validation for a collection.

Use unique: { fields: ["fieldKey"] } to include selected top-level field values in the uniqueness check. Supported field types are text, textarea, select, number, datetime, relation, media, and user.