Ecosystem

Plugins

Plugins extend CELLAS capabilities while Runtime, Engine, and Conformance stay stable. Start from the official plugin template; study reference plugins in the monorepo for the contract.

Plugin SDK docs Create a plugin project

What plugins are

A plugin packages a capability—validation, transformation, rendering, analysis—behind a manifest and loadable entrypoint. CELLAS loads plugins under the same deterministic rules as the rest of the stack.

Why the model exists

Documentation systems need domain-specific behavior without forking the platform. Plugins keep core packages focused while teams ship reusable capabilities.

When to use plugins

You need a capability not covered by the reference set
You want to share an internal tool as a versioned package
You are learning the author contract with a certifiable starter

How to start

pnpm create cellas my-plugin --template plugin --yes
cd my-plugin
pnpm install
pnpm exec cellas verify
pnpm exec cellas certify

Reference plugins (monorepo)

The CELLAS repository ships reference plugins used for conformance and examples. They are the source of truth for packaging and behavior—not a marketplace UI.

Browse plugins/ in the public repository
Follow docs/developer/plugin-author-guide.md for authoring rules
Keep fixtures certifiable when you change behavior

Catalog note

This page describes the plugin model. A searchable public catalog UI is not part of Public Beta; discoverability today is through docs, starters, and the GitHub repository.