For Developers

Official SDKs for the stacks you already ship

RuleCMS publishes widgets once. Embed them with a first-class React SDK — or with official Angular, Vue, Svelte, Flutter, and React Native packages that render the default component set. A script tag works on any HTML page. Same environments, same tokens, same customer journey.

Getting started guide →

Pick your framework

Each card opens a full integration guide. Packages and public sample labs live on those pages — never a private SDK repository.

First-class

React

@rulecms/widget-react

The deepest RuleCMS integration: custom component libraries, design systems, SSR, React Server Components, and live Development drafts.

React developer guide

Angular

@rulecms/widget-angular

Official Angular SDK with the default RuleCMS component set. Same composer, environments, and tokens as every other stack.

Angular developer guide

Vue

@rulecms/widget-vue

Official Vue 3 SDK with the default RuleCMS component set. Compose once, publish, and embed in Vue or Nuxt.

Vue developer guide

Svelte

@rulecms/widget-svelte

Official Svelte 5 SDK with the default RuleCMS component set. Publish from the composer and drop the widget into a Svelte app.

Svelte developer guide

HTML

@rulecms/widget-custom-element

Framework-agnostic custom element. Load one script from RuleCMS and drop <rulecms-widget> into WordPress, PHP, static HTML, or any other host.

HTML developer guide

Flutter

rulecms_widget

Official Flutter SDK on pub.dev. Deliver the same published widgets into iOS and Android with the default RuleCMS cards.

Flutter developer guide

React Native

@rulecms/widget-react-native

Official React Native SDK on npm. Same published content and default cards, rendered with native views.

React Native developer guide

What every stack shares

Buy RuleCMS for the product. Choose the SDK for the host app.

Direct JSON editing

Drop from the visual composer to raw JSON on any widget. Marketers stay in the canvas; developers work in the format they prefer.

Environment-scoped API tokens

Three environments per project — Development, Staging, Production — each with its own tokens so a lab never talks to production.

Default RuleCMS components

Every official SDK renders the shipped card set: text, images, video, icons, buttons, dividers, embeds, lists, and accordions.

The same customer journey

Compose, preview per device, publish to staging, promote to production, and embed. The stack you ship does not change that path.

Three integration paths

Headless fetch via the content API

The universal path when you are not using an official SDK.

fetch-widget.jsJS
// Fetch published widget content via the headless APIconst widget = await fetchPublishedWidget({  publishedKey: "your-widget-key",  token: "your-environment-token",});// Returns published JSON ready to render in any framework

React is first-class when you want to register a custom component library or a design system in the composer. Other official SDKs ship the default RuleCMS cards and still cover the full publish-and-embed journey. If you need a language we have not packaged yet, the headless API is enough.

Explore RuleCMS

Dive deeper into what makes RuleCMS different.

Start building with RuleCMS

Provision three environments and API tokens in one sign-up step.