The control plane is the dashboard where a team turns its software changes into release notes, documentation and QA test scenarios. It reads the pull requests and tickets behind each change, asks an AI model to write drafts from them, and holds every draft until a person has checked and approved it. Only approved drafts are ever published.
The work always happens in the same order: bring changes in and generate drafts, review the drafts, then publish the approved ones. The sidebar lists the pages in that order, joined by a line from top to bottom, so it works as both the menu and a map of the process.
What each part of the sidebar does
- Product: Every page shows the work of one product at a time. A product is a piece of software the platform documents, with its own code repositories, its own ticket project and its own places to publish. Choose the product to work on here before doing anything else.
- Generate: Brings changes in from the product's repositories and ticket project, then asks the AI to draft release notes, documentation and QA scenarios from them. It is the starting point whenever a release is ready to document. Release candidate, beside it, lists every pull request and ticket in a release, so its contents can be checked before anything is drafted.
- Review: A person reads each draft beside the ticket and pull request it was written from and decides whether it is accurate. A draft can be approved, rejected with a reason, or sent back to the AI to be written again. Nothing moves on to publishing without this decision.
- Publish: Sends the approved drafts to the destinations set up for the product, such as the internal space where the team reads release notes, the help center where customers read articles, or the tool where testers pick up QA scenarios.
- Connections: The accounts the platform signs in with to read code and tickets and to publish, and whether each one is working.
- Config: Each product's settings: its repositories, its ticket project and where each kind of draft is published.
Generate, Review and Publish each show a small count of what is waiting there: changes that have no draft yet, drafts that still need a decision, and approved drafts ready to send. A check mark means nothing is waiting at that step.
Viewing and signing in
Anyone with the link to the control plane can open every page and see the drafts, their status and what has been published. Making a change (generating, approving, rejecting, publishing or editing settings) requires signing in from the sidebar with an account on the platform's list of administrators. The platform records who approved or rejected each draft, so every decision can be traced back to a person.
Knowing what to do next
The bottom of each page names the next step and how much is waiting there, for example how many drafts still need review. Following those prompts from page to page walks through a whole release from start to finish.
When a product is not ready to run
A product that is missing something it needs shows a box on the Generate, Review and Publish pages. The box lists what is missing and what to do about it.
- [Product name] is not set up yet: Appears when nothing can run, because no GitHub repository is chosen or every output is switched off. The box replaces the rest of the page. For example: "No GitHub repository is chosen. Choose its repositories under Where changes come from."
- [Product name] needs attention: Appears when a connection is missing or failing. The box sits above the normal page, so drafts can still be reviewed underneath it. For example: "The GitHub connection is failing its check. Open it on the Connections page and check it."
1. Click Open Config in the box to open the settings of the product chosen in the sidebar, or Open Connections when a connection is failing
A product that is fully set up shows no box, and its pages appear as usual.