How to build a community platform in Bubble

A community platform in Bubble is built by defining clear Data Types (Users, Posts, Comments, Groups), creating Pages that display those things with Repeating Groups, and wiring everything with Workflows (like creating a post, liking something, joining a group). The core is structuring the database correctly and adding Privacy Rules so users only see what they should see. Once the data layer is right, the UI and workflows become straightforward.

Core Data Structure

These Data Types are the minimum for a functional community:

• User: name, avatar (image), list of groups (list of Group), bio (text)
• Post: author (User), content (text), images (list of image), group (Group), likes (list of User), created date (date)
• Comment: author (User), post (Post), text (text), created date (date)
• Group: title (text), description (text), members (list of User), is\_private (yes/no)

This structure lets you show feeds, comments, likes, and groups easily in Repeating Groups.

Key Pages to Build

• Feed Page: Use a Repeating Group with type Post, data source “Do a search for Posts sorted by Created Date descending”. Inside each cell, show author, content, likes, and a nested Repeating Group for comments.
• Group Page: Show information about the Group plus a filtered list of posts: “Do a search for Posts where Group = Current Page Group”. Add a Join/Leave button.
• User Profile: Show profile info and a feed of posts “Do a search for Posts where Author = Current Page User”.

Workflows That Make It Functional

• Create Post: Button → Workflow → “Create a new Post”. Set fields: Author = Current User, Content = Input’s value, Group = Current Page Group.
• Add Comment: “Create a new Comment” and tie it to “Current cell’s Post”.
• Like System: Use a custom state or a simple condition to toggle: “Make changes to Post: add Current User to Likes” or “remove Current User from Likes”.
• Join Group: “Make changes to Group: add Current User to Members”.

Privacy Rules

Go to Data → Privacy.

• Posts: Only allow viewing if the Post’s Group is private = no OR Current User is in Group’s members.
• Comments: Same rule as Posts.
• User: Allow other users to see name and avatar, but restrict email.

Optional: Notifications

You can create a Notification data type and trigger it using a Backend Workflow when someone comments or likes a post.

{
  "event": "new_comment",
  "post_id": "123",
  "author_id": "456"
}
// Send this with a webhook to external service or store in Notification type