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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pinelab/vendure-plugin-simple-cms

v0.1.0

Published

Vendure plugin for simple CMS content management

Downloads

13

Readme

Vendure Simple CMS Plugin

The goal of this plugin is to provide simple content management within Vendure. It is not intended as a page builder or drag-and-drop editor, but instead allows you to define structured content types such as a Hero title, image and text block, Blog posts, or other simple content entities. It can be seen as a kind of mini, simplified version of Directus.

Configuration of content types is similar to how custom fields are defined in Vendure itself: you specify which fields are available for each type of content (e.g., string, number, boolean, relation, or struct fields), and can indicate which fields are translatable.

This keeps things flexible and familiar for Vendure developers, focused on structured content rather than complex layouts or design tools.

Features:

  • Pre-defined content types
  • Translatable fields
  • Relation, struct and primitive fields
  • Content entries
  • Content entry translations

Getting Started

Install the plugin along with your own content types:

import { Asset, Product } from '@vendure/core';
import { SimpleCmsPlugin } from '@pinelab/vendure-plugin-simple-cms';

SimpleCmsPlugin.init({
  contentTypes: {
    // A single Hero block, edited as one entry
    hero: {
      displayName: 'Hero',
      allowMultiple: false,
      fields: [
        { name: 'title', type: 'string', isTranslatable: true },
        {
          name: 'subtitle',
          type: 'string',
          isTranslatable: true,
          nullable: true,
        },
        {
          name: 'image',
          type: 'relation',
          entity: Asset,
          graphQLType: 'Asset',
        },
      ],
    },

    // Multiple blog posts, with translatable body and a featured product
    blogPost: {
      displayName: 'Blog post',
      allowMultiple: true,
      fields: [
        { name: 'title', type: 'string', isTranslatable: true },
        { name: 'slug', type: 'string', isTranslatable: false },
        { name: 'body', type: 'text', isTranslatable: true },
        {
          name: 'publishedAt',
          type: 'date',
          isTranslatable: false,
          nullable: true,
        },
        {
          name: 'featured',
          type: 'boolean',
          isTranslatable: false,
          nullable: true,
        },
        {
          name: 'featuredProduct',
          type: 'relation',
          entity: Product,
          graphQLType: 'Product',
          nullable: true,
        },
        // Nested struct: list of CTA links
        {
          name: 'cta',
          type: 'struct',
          isTranslatable: true,
          fields: [
            { name: 'label', type: 'string', isTranslatable: true },
            { name: 'url', type: 'string', isTranslatable: false },
          ],
        },
      ],
    },
  },
});

Field types reference:

  • string, text, int, float, boolean, date — primitives
  • relation — references another Vendure entity (Asset, Product, ProductVariant, …)
  • struct — nested object containing primitive sub-fields

Set isTranslatable: true on any primitive or struct field to store a value per language. Set allowMultiple: false to enforce a single entry per channel (singletons like a Hero or Footer).

TODO

  • Relation saving and fetching: Saving seems to work, but on refresh no relation is shown