Your blog, docs and FAQs, written in the console, read over the API.
Posts, help articles, FAQ groups, testimonials and reusable text blocks are written in the console by whoever owns the words, not in your repo. Your site reads them through a token-authenticated REST API at build time or from your server, so the token never reaches a browser.
Your app is an organization in BuildBase. Your users sign in and work inside workspaces - one per team or customer.
You set up
In the console and the SDK
- Your blog, docs, FAQs and testimonials, written in the console
- Who on your team writes and publishes
- One fetch from your site to show them
You get
For you and your team
- Words you change without a deploy
- Drafts that stay private until published
- SEO title and description for every post
Words that change without a deploy
Marketing and support edit in the console, and your site picks up the change the next time it fetches.
Five Kinds of Content
Blog posts, docs, FAQs, testimonials and reusable text blocks, all written in the console.
Organized in Folders
Posts live in folders and are fetched by the same path a reader sees in the address bar.
Drafts Until Published
A post stays a draft until you publish it, and its address is locked after that so links never break.
SEO for Every Post
Each post has its own search title, description, keywords, tags and authors.
Reusable Text Blocks
A refund policy or a pricing footnote kept in one place and fetched by name, so the wording changes without a deploy.
FAQs in Groups
Group questions, order them, and reuse a question in more than one group.
Read a post by the path a visitor uses
There is no React hook for content, because the org API token has to stay on your server or in your build. Call the REST API from any language, or use the client in @buildbase/sdk/server, which keeps copies so reads are fast.
const API = 'https://api.console.buildbase.app/api';
// Server-side or at build time only - the token must not reach the browser.
export async function getPost(path: string) {
const url = new URL(`${API}/blogs/path`);
url.searchParams.set('path', path); // e.g. 'engineering/why-we-moved-off-cron'
const res = await fetch(url, {
headers: { Authorization: process.env.BUILDBASE_TOKEN ?? '' },
});
if (!res.ok) return null;
return res.json();
}const API = 'https://api.console.buildbase.app/api';
export async function getBlock(slug: string) {
const res = await fetch(`${API}/rich-content/slug/${slug}`, {
headers: { Authorization: process.env.BUILDBASE_TOKEN ?? '' },
});
if (!res.ok) return null;
return res.json(); // { title, slug, content, ... }
}Fast content without building the plumbing
Read your posts and pages from your backend with @buildbase/sdk/server. It keeps copies so pages load fast, refreshes them when you publish, and keeps serving if BuildBase is down. It runs on Node, Bun, Deno, Cloudflare Workers and other edge platforms.
Fast by default
Every read keeps a copy, in memory, Redis or Workers KV. When the copy may be out of date, the client only asks whether it changed, and an unchanged post costs one tiny reply. Identical reads at the same moment share one request.
Up when we are not
If BuildBase can't be reached, your site serves the last good copy. The client refuses to run in a browser, so your secret token never ends up in one.
Fresh the moment you publish
When you publish, a webhook tells your server what changed, and only those saved copies are cleared. One adapter covers Express, Fastify and NestJS, and Next.js gets cache tags.
Static sites too
One command copies every published post, doc, FAQ, testimonial, block and collection into a JSON file during your build. A static site then never calls BuildBase while people browse it.
Rebuild from the console
Save a deploy hook (the link that tells your host to rebuild) for Vercel, Netlify, Cloudflare Pages or Render. A banner offers a deploy when posts change, and Vercel reports back whether the build worked.
Reads that stay in budget
A "has this changed?" check that finds nothing new never counts against your plan's content reads. So a site that keeps copies and refreshes when you publish uses almost none of them, however much traffic it gets.
import { createServerClient } from '@buildbase/sdk/server';
export const content = createServerClient({
serverUrl: process.env.BUILDBASE_SERVER_URL!,
apiToken: process.env.BUILDBASE_API_TOKEN!, // read-only content role
});
const post = await content.blogs.byPath('guides/getting-started');
const refund = await content.richContent.get('refund-policy');
const questions = await content.faqs.questions('help-center');# In CI: published content to one JSON file, token never leaves CI
npx @buildbase/sdk content pull --out src/content/buildbase.jsonRead more in the docs
Setup guides and reference for Content Management.
Overview
Blog posts, docs, FAQs, testimonials, and reusable rich-content blocks.
Blogs and docs
Resolve a post by its folder path, preview drafts, and manage tags and authors.
Delivering content
Read content from your server with copies kept for speed, refresh them when you publish, or pull everything in at build time.
Deploy hooks
Rebuild a static site on Vercel, Netlify, Cloudflare Pages or Render from the console.
Assets
Upload images, store them public or private, and read back their URLs and dimensions.
Admin API
Authenticate with an org API token and call the REST API behind the console modules.
Frequently Asked Questions
What people ask about Content.
Do my users see this?
Readers of your site see what you publish. The editor is for your team only.
Is there an SDK hook for content?
Not a React hook. Reading content needs your organization's API token, and that token has to stay on your server. There, the server client in @buildbase/sdk/server reads every content type, keeps a cached copy, and refreshes it when a content webhook says something changed. For a static site, npx @buildbase/sdk content pull writes your content to a file at build time. Other languages use the REST API.
Can I read content straight from the browser?
No. Every read needs your API token, and the token must stay on your server.
Can I schedule posts or publish in several languages?
No. Posts are published by hand, one language per post.
Move your blog out of the repo
Write the first post in the console, create an API token, and fetch it by path from your build. Your site renders it the same way it renders everything else.