Manage content in one place and send it to your website or app.

This website is the CMS control panel for your team. Use it to create pages, blogs, media, and integrations, then connect your frontend to the public API so visitors always see published content.

Open Dashboard How It Works

Quick Start

1. Sign in to the dashboard.

2. Create a project.

3. Add pages, blogs, and media.

4. Publish the content.

5. Connect your website to the public API.

Tip: keep private keys on the server and use webhooks to refresh the frontend when content changes.

How It Works

Step 1

Open the website

Visit the Buildstack CMS website to see the public landing page and learn what the platform does.

Step 2

Go to the dashboard

Step 3

Publish content

Once a page or blog is published, the public API can serve it to your website or mobile app.

Step 4

Connect your app

Use the public API for reading content and webhooks for refreshing your frontend or syncing data.

What You Can Manage

Projects

A project groups pages, blogs, and media for one website or product.

Pages

Pages are the main website screens, like home, about, pricing, or contact.

Blogs

Blogs are articles, announcements, updates, and long-form content.

Media

Media stores images, files, and other assets used in your content.

Integrations

Integrations let you create API keys and webhooks for trusted backend connections.

Public API

Your website or mobile app reads published content from the CMS through public API routes.

For Content Editors

Open the dashboard, choose a project, and add the content you want to publish. The public site will read the published content automatically.

For Developers

Use public API routes in your frontend and webhooks in your backend. Private keys should stay server-side only.

FAQ

Who is this CMS for?

It is for teams who want one place to manage website content and send it to a frontend, mobile app, or internal tool.

How do I make content visible?

Create or edit a page or blog post, mark it as published, and then use the public API from your website.

Where should API keys live?

Private keys should stay on the server only. The browser should never hold write keys or webhook secrets.

What do webhooks do?

Webhooks tell your backend when content changes so you can refresh the frontend, update caches, or sync other systems.