Skip to content
commitpress Open CMS

What you can do

The tools to manage structured content.

Build the content model your website needs, manage its entries and assets, and use the resulting files in your application.

Content management

Built around your content model.

  1. Schemas and reusable blocks

    Define fields, groups, repeatable content and reusable blocks in the browser. Schemas are committed as JSON.

  2. Pages, collections and globals

    Manage individual pages, sets of entries and content shared across your website.

  3. Assets

    Upload and organize the images and files used by your content.

  4. Website preview

    Connect a running instance of your website as a preview target. Live updates depend on the preview integration in that website.

  5. Branches and history

    Work on repository branches and follow the commits behind content changes.

  6. Site publishing

    When configured, review pending commits and request a site release from the CMS. Content drafts stay separate from site releases.

For developers

Read the files. Build your website.

CommitPress manages the content. Your application decides how to render it. The Node.js SDK reads local repository files and can generate TypeScript types from your schemas.

Explore the Node.js SDK
src/content.ts
import { query } from '@commitpress/sdk-node';

const page = await query(
  'content/pages/index',
  process.cwd(),
);

// Your saved homepage content.
const content = page.content;

Use the SDK in server code or at build time. Connect your own website for preview.

Integration

Your website, your setup.

Where is my content stored?

Your content and schemas are JSON files in the configured content directory of your GitHub repository. Assets live in that directory too.

Does saving content publish my site?

Saving content commits it to your active branch. A site release is a separate operation and depends on your publishing configuration. Draft content stays separate from the site release.

Do I need a particular framework?

The Node.js SDK reads local files and does not require a frontend framework. Your application is responsible for rendering the content and providing a preview target.

Start with your repository

Give your content a place to work.

Connect a GitHub repository, define your first schema and start editing in CommitPress.

Cookie settings

commitpress sets no advertising or analytics cookies, and no third party sets any through this site. What is stored is listed below.

Strictly necessary — always on
  • Keeping you signed in, and the token that stops another site submitting forms as you
  • The project and branch you are working on, and a short-lived cache of its configuration
  • One-off status messages, deleted the moment they are shown
  • This choice
Accept all