Publish Use Case Pages to Your Website

Describe a workflow in Slack. Zero writes the full use case page, translates it into four languages, and opens a PR to your website repo.

Zero connects:

What Zero delivers

Publish Use Case Pages to Your Website — sample output from Zero — screenshot 1

What the problem is

Your team just shipped a new workflow that customers love. Marketing wants to add it to the use cases gallery on the website, but that means writing the page copy, structuring the scenario, prompt variants, and step-by-step breakdown, translating everything into German, Japanese, and Spanish, adding the right metadata to the codebase, and opening a clean PR. By the time someone finds a spare hour, three more use cases are waiting. You paste the workflow into Slack, tag Zero, and a production-ready PR appears in minutes with the full page in all four locales, matching the site's design system.

How Zero fixes it

Step 1: Connect your tools

GitHub

Required

GitHub - Zero creates a branch, commits the data and locale files, and opens a pull request on your website repository. Write access to the repo is required.

Connect

Slack

Required

Slack - Zero receives the workflow description and posts back with the PR link and a summary of what was added. This is how you trigger the whole flow.

Connect

Step 2: Ask Zero

@Zero add this to our use cases page: [paste a link or description of the workflow]. Target audience is marketing teams. Include Slack and GitHub as integrations.

try it

Zero analyzes the workflow you shared

Zero reads the link, thread, or description you dropped into Slack. It identifies the persona, the problem being solved, the tools involved, and the key steps. If anything is ambiguous, it asks a clarifying question before proceeding.

Zero writes the full page in four languages

Zero drafts every field the page needs: title, description, scenario, prompt variants, Slack preview, step-by-step breakdown, next actions, integration notes, and tips. Then it translates all of that naturally into German, Japanese, and Spanish, adapting idioms rather than translating word-for-word.

Zero opens a PR with all changes

Zero commits the new use case entry to the data file and all four locale message files, adds any screenshot you provided, and opens a pull request on your website repo. The PR triggers CI and a deploy preview so you can see the live page before merging.

Step 3: Take it further

Review and refine the copy

Check the deploy preview and ask Zero to adjust the tone, add details, or swap out a prompt variant.

@Zero in the PR you just opened, change the scenario to focus more on the time-saving angle and less on the translation step.

try it

Batch multiple use cases

Queue up several workflows and have Zero add them all in one session.

@Zero here are three more workflows we want on the use cases page: [1] ... [2] ... [3] ...

try it

Keep the gallery fresh on a schedule

Set a recurring reminder to review shipped workflows and turn the best ones into pages.

@Zero every Friday, check the #shipped channel for new workflows and suggest which ones should become use case pages.

try it

Tips for better results

●The richer the context you give Zero, the better the page. Paste a thread with real examples, screenshots, or even a short video description rather than a one-liner.

●Review the deploy preview before merging. Zero gets the structure right every time, but your team knows the voice best. A quick copy pass makes the page feel native to your brand.

●Pair this with the content performance report use case so you can track which pages drive the most signups and double down on those workflow categories.