How to build a CMS in Bubble

A simple CMS in Bubble is built by creating a data type for your content (like “Post”), building admin pages where you can create/edit/delete items, and showing that content on your public pages using Repeating Groups. You control who can manage content with Privacy Rules and optional admin-only pages. Bubble becomes your content manager: the database stores entries, and your admin UI lets you update them without touching page design.

Core Structure

You need a data type (database table) that represents the content you will manage. For a basic blog-style CMS, create a Post data type with fields like Title (text), Body (rich text), Image (image), Slug (text), and Status (text — e.g., Published/Draft).

• Create it in Data → Data types.
• Use rich text editor inputs for long content.
• Make Slug unique so each Post has a pretty URL.

Admin Editor Pages

Create a page like admin\_post and set the page type to Post. Add Inputs for Title, Body, ImageUploader, etc. Add two main workflows: “Create a new Post” and “Make changes to current page Post”.

• To edit: navigate to this page and send a Post as Data to page.
• To create: navigate without data and show a “Create Post” button that runs Create a new thing → Post.

// Example workflow action for saving edits
Make changes to thing → Thing: Current page Post
Field Title = Input Title's value
Field Body = RichTextInput's value
Field Image = ImageUploader's value

Admin List Page

Add a page with a Repeating Group (RG) showing all Posts. Each cell can have “Edit” and “Delete” buttons. “Edit” navigates to the editor and sends the cell’s Post as data.

• RG Data source: Do a search for Posts → Sort by Created Date descending.
• “Delete” runs workflow: Delete a thing → Current cell Post.

Public Display

Make a public page called post, set type to Post, and lay out text elements bound to dynamic data (Current page Post’s Title, Body, Image). When clicking a post on the public listing, navigate to this page and send the Post as data.

Privacy Rules

Go to Privacy tab → Post. Add a rule for logged-in admins (e.g., User’s role is admin). Allow “Create, modify, delete” only for admins. The default rule should prevent unapproved users from editing.

• Public users should have “Find in searches” and “View fields” allowed only for fields you want public.

Optional Extras

You can add things like autosave using Auto-binding, scheduling drafts with Backend Workflows, or generating SEO-friendly URLs using the Slug field and a “Go to page” action with ?slug= parameters.