> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duckpost.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Public page

> Configure and share your DuckPost public updates page.

<p align="center">
  <img className="rounded-lg" src="https://mintcdn.com/duckpost/aAhMZODiV5dM3w5v/brand/public_page.webp?fit=max&auto=format&n=aAhMZODiV5dM3w5v&q=85&s=4577c48195ad883fcb34752abe5580a7" alt="DuckPost public page" width="720" data-path="brand/public_page.webp" />
</p>

DuckPost gives every organization a hosted public changelog page for customer-facing updates. You manage its URL from [**Integration**](https://duckpost.app/integration), and customers read it under a path like:

```text theme={null}
https://duckpost.app/updates/<organization-slug>
```

## What the public page is for

* Share a permanent updates page with customers
* Publish product updates, improvements, and fixes in one timeline
* Let customers open a full detail page for each release
* Collect email and Slack subscribers from the same surface
* Gather lightweight reaction feedback on published releases

## What customers see

The public page shows:

* Your organization name in the page header
* A timeline of published releases
* Release tags, summaries, content, and optional images
* A **Read update** link that opens the full release permalink
* A **Subscribe** flow for email and Slack
* Feedback reactions on each published release

## Public URLs

DuckPost uses two public URL patterns:

* Changelog home: `https://duckpost.app/updates/<organization-slug>`
* Release detail page: `https://duckpost.app/updates/<organization-slug>/<release-slug>`

Only published releases appear on the public page.

## Slug rules

Owners can change the organization slug from [**Integration**](https://duckpost.app/integration).

* Use lowercase letters, numbers, and hyphens
* Choose a stable slug before you share it widely
* Changing the slug changes the public URL
* Old public links stop working after the slug changes

## How subscriptions work on the public page

Customers can subscribe directly from the public page:

* **Email** subscriptions use a confirmation email
* **Slack** subscriptions use an **Add to Slack** flow

After a release goes live, DuckPost can notify those subscribers if the release has notifications enabled.

## Feedback and engagement

Each public release can collect one simple reaction per visitor:

* 👍 Good feedback
* 😐 Neutral feedback
* 👎 Bad feedback

That feedback rolls back into your release engagement data in [**Releases**](https://duckpost.app/releases).

## Recommended public page flow

<Steps>
  <Step title="Set your public slug">
    Open [duckpost.app/integration](https://duckpost.app/integration) and choose a stable public changelog URL.
  </Step>

  <Step title="Publish your first release">
    Drafts stay private. Publish at least one release before you share the page.
  </Step>

  <Step title="Open the public page">
    Visit `duckpost.app/updates/<your-slug>` and confirm the branding, content, and release order look right.
  </Step>

  <Step title="Invite customers to subscribe">
    Share the public page as your main changelog archive and subscription surface.
  </Step>
</Steps>

## Related pages

<CardGroup cols={2}>
  <Card title="Integration overview" icon="code" href="/integrations/overview">
    Start with the full integration setup and available options.
  </Card>

  <Card title="Widget" icon="code" href="/integrations/widget">
    Embed the widget and show releases inside your product.
  </Card>

  <Card title="Subscribers" icon="square-terminal" href="/audience/subscribers">
    Understand email and Slack subscription delivery.
  </Card>
</CardGroup>