Skip to main content

Documentation

RIFT is a git-native CMS for teams that write their own HTML and need every publish to be traceable. These docs cover the full authoring-to-publishing loop. They are written in RIFT and published by RIFT — the commit that shipped this page is in the site's public git history.

Start here

Guides

First steps

Getting Started

From first login to your first published page: create a site, add a folder, write a page, push it to staging.

Read →
Mental model

Core Concepts

Sites, folders, content items, workflow states, and why the CMS and your published site can never take each other down.

Read →
Authoring

Writing Content & References

Raw HTML authoring, linking pages with cms:item references, and placing design-system components with parameters.

Read →
Design

Design Systems

Tokens, components, versioning, the package format, and the AI generator's create and update modes.

Read →
Shipping

Publishing & Git

Deploy keys, staging and production branches, publish scopes, and hosting on Vercel, Netlify, or Cloudflare Pages.

Read →
Safety

Version History & Workflow

Every save is a version. Compare any two, review AI proposals as diffs, and roll back with confidence.

Read →
Onboarding

Site Migration

The Crawl, Classify, Parameterize, Migrate pipeline that moves an existing site into RIFT with a human gate at every step.

Read →
Integrate

API Reference

The versioned REST API behind every edit, publish, and migration — with dry-run mode and full audit logging.

Read →
Answers

FAQ

The honest answers: what RIFT deliberately does not do, and whether it fits your team.

Read →

Want a guided walkthrough? We're onboarding a small number of design partners.

Request Access