> For the complete documentation index, see [llms.txt](https://docs.ucollect.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ucollect.me/tutorials/ready-to-start/are-you-a-community-builder/post-creation/how-to-create-a-public-post.md).

# How to create a Public Post

A Public Post is a post that is not associated with any memberships, allowing users to view it and access the content without the need to make a purchase. Follow these steps:

1. **Click on your profile picture** in the top right corner of the page.
2. Go to "**My Board**."
3. Just under your banner, locate "**Type Something**" and click on it to open the Creating Post interface.
4. On the top right, **slide from "Protected" to "Public."**
5. Add your Post Title.
6. Include a description for your post.
7. Add a cover image to make your post visually appealing.
8. Once you've filled in the details, click "**Next**."
9. **Select the type of utility** you want to share with your community:
   * Photo
   * External Video
   * Secret Code
   * Calendly Link
   * File
   * URL
10. Add Claim options to enhance engagement.
11. **Click "Publish Content"** to share your Public Post with the community.

{% embed url="<https://youtu.be/mBVLsfC_0SQ>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ucollect.me/tutorials/ready-to-start/are-you-a-community-builder/post-creation/how-to-create-a-public-post.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.