Examples

Example 1: A Landing Page for a Feature Launch

A SaaS client is launching an AI scheduling feature and needs a page to collect early-access signups.

Step 1: Create the page. On the Web Pages page, the account manager chooses New Page. Topic: "early access to the AI scheduling feature." Page Kind: Landing page. Audience: operations managers at mid-size companies. Page Goal: sign up for the early-access beta. Both toggles stay on, and they choose Create Page.

Step 2: Read the brief. The page opens with a title, a meta description, and a slug such as ai-scheduling-early-access. Below are six sections in order: a hero, value propositions, features, a social proof section that notes real quotes must be added, an FAQ, and a call-to-action band. A short rationale explains the order.

Step 3: Fix the metadata. The title runs slightly long. The account manager clicks it, trims it, and clicks away. The HTML re-renders to match.

Step 4: Approve. They choose Approve. If Brand checking is on, the copy is checked first and the verdict shows on the page.

Step 5: Publish. They copy the HTML from the HTML Scaffold section, paste it into the client's site, and check the live page. Then they enter the address under Live URL and choose Publish. The page moves to Recently Published.

Example 2: Approving From Slack

When Slack is set up for the agent, the card appears after the brief is written.

Step 1: The card. It shows the title, meta description, slug, and the list of sections.

Step 2: Edit the brief. The slug does not match the client's URL pattern. From the more menu the manager chooses Edit brief, changes the slug, and saves. The HTML is re-rendered and the card refreshes.

Step 3: Approve. They choose Approve. The card stays active with its buttons because the page is approved but not yet published.

Step 4: Record the live address. After pasting the HTML into the site, they choose Publish on the card, confirm, and enter the live address. The card changes to a published status showing the address. The confirmation said the page would publish to the web host, but the only thing recorded is the address.

Example 3: Changing the Copy

A client does not want a comparison section.

Step 1: See the options. Section copy is shown on the page but is edited by regenerating or in the HTML, not field by field.

Step 2: Regenerate. The team chooses Regenerate Brief, which writes a new brief from the same topic, audience, and goal. The result drops the comparison section and adds a testimonials section with a note to supply real quotes. Any title or slug edits made earlier are replaced, so they redo them.

Step 3: Re-render and approve. They choose Re-Render HTML and then Approve.

Example 4: Editing After Approval

Step 1: A late change. A page has been approved. The client asks for a different meta description.

Step 2: Edit. The manager clicks the meta description, changes it, and clicks away. The HTML re-renders.

Step 3: Approve again. The page is back in Awaiting Review and its earlier brand decision is cleared. The manager approves it again before publishing.