npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lucidcms/plugin-pages

v0.2.0

Published

The official Pages plugin for Lucid

Downloads

70

Readme

@lucidcms/plugin-pages

The official Pages plugin for Lucid

This plugin adds support for hierarchical documents and slugs to Lucid. When enabled on a collection, it will register three new fields to the collection: fullSlug, slug and parentPage. These fields are used to construct the fullSlug which is computed whenever a document is edited and is the combination of all of a document's parentPage slugs and the slug of the document itself. It achieves this by registering a handful of 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.

Installation

npm install @lucidcms/plugin-pages

Setup

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

import LucidPages from "@lucidcms/plugin-pages";

export default lucid.config({
  // ...other config
  plugins: [
    LucidPages({
      collections: [
        {
          collectionKey: "page",
          useTranslations: true,
          displayFullSlug: true,
        },
      ],
    }),
  ],
});

Configuration

This plugin provides a few configuration options to control how it behaves. Aside from the collectionKey, all of these options are optional and have default values.

collections: Array<{
  collectionKey: string;
  useTranslations?: boolean;
  displayFullSlug?: boolean;
}

collectionKey

The collectionKey is the key of the collection that you wish to enable the plugin on.

useTranslations (false by default)

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.config.ts file.

displayFullSlug (false by default)

If set to true, the plugin will make the fullSlug field visible in the documents page builder along with making it filterable and listable in the document listing. This is mostly intended for testing and development purposes, though there is no reason it can't be used in production. Please note, however, that the fullSlug field is always calculated, meaning it is not possible to edit this via the document page builder and even if this option is set to true, the field will be disabled.