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
Content has no SDK hook, so you call the REST API from your server or your build, with an org API token.
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, ... }
}Read 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.
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?
No. Your site reads content over the REST API with an org API token, from your server or at build time.
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.