Documentation

ContentBind renders your components inside your application. The integration is a fetch and a render; everything else here is about what authors can then do without you.

tsx

import { fetchOneEntry, isContentBindError } from '@contentbind/sdk'
import { Content } from '@contentbind/sdk/react'

export default async function Page({ params }) {
  const { slug } = await params
  const entry = await fetchOneEntry({
    model: 'page',
    publicKey: process.env.NEXT_PUBLIC_CONTENTBIND_KEY,
    urlPath: '/' + (slug ?? []).join('/'),
  })
  if (isContentBindError(entry)) return null

  return (
    <Content
      model="page"
      content={entry}
      publicKey={process.env.NEXT_PUBLIC_CONTENTBIND_KEY}
    />
  )
}

Getting started

QuickstartFrom an empty project to an editable page in about ten minutes.How it worksWhat the editor does, and why the canvas is your own site.

Building

Custom componentsRegistering your own components and declaring their inputs.Preview and draftsSeeing unpublished content, and sharing it with people outside.CLIScaffolding an integration and diagnosing a broken one.

Shipping

PublishingEnvironments, versions, approvals and scheduling.ExperimentsRunning A/B tests with the flag tool you already use.PersonalizationSaying something different to a campaign, an audience, or one arm of an experiment.

Reference

Delivery APIThe HTTP surface behind the SDK.Security modelKeys, isolation, and what the bridge will and will not do.

Working with an assistant? Every page has a “Copy for an LLM” button, and the whole site is available as llms.txt and llms-full.txt.