Compfeed
Contributions

From Playground to Manifest

Turn the work in Playground into the component's documentation, then review and finish it.

The Manifest is the component's documentation. Compfeed drafts it from the contribution you already made, and then you review and finish it. Drafting is the cheap part; the review is what makes it trustworthy.

Before you begin

  • A contribution with notes and completed checks in Playground. See Work in Playground.
  • The Admin or Editor role on the team.

Generate the Manifest

Switch to the Manifest

Open the component and choose MANIFEST.

Generate the draft

Choose Ready to Generate Documentation.

Compfeed drafts the page from the contribution: the notes you wrote, the checks you completed, and the images in the contribution.

Read it and fix it

Work through the draft and correct it. When the stored copy is current, the Manifest shows Document is up to date.

The draft is a starting point, not a finished page. Compfeed does not check whether it is accurate, and nothing records which parts a person reviewed. Read every line before you treat it as documentation.

Add images

A Manifest takes two kinds of image. Single image adds one picture. Do & Don't adds a pair, for showing a correct and an incorrect use side by side.

Give every image a caption that says what it shows, so the Manifest still makes sense to somebody skimming it.

Work on it with other people

The Manifest is collaborative in the same way Playground is. The header shows Connected when your changes are being saved, and Connecting when they are not yet.

Review a suggestion from an AI tool

If your organization has MCP turned on, a coding agent can suggest a change to a Manifest rather than editing it. A suggestion waits in the Manifest until a person decides.

Choose Accept to take the change, or Reject change to discard it.

Only an Admin or Editor of the component's team can suggest a change, and only one suggestion is held at a time: a new one replaces any suggestion still waiting.

Expected result

The Button has a Manifest that a person has read, with the reasoning behind the loading state and any images that make the usage clear. Anyone on the team can open the component and read it. An AI coding tool connected over MCP can read it too.

If something doesn't work

  • The Manifest says it cannot be found: the component has no Manifest document yet. Generate one.
  • The draft is missing most of the contribution: there were few notes in Playground to draft from. Add them and generate again.
  • Anything else: see Troubleshooting.

What's next

Set up the widget

On this page