Quick start
Content reaches a workspace through a connector, and every route meets in the same place: the same voice profile, the same vocabulary, the same content memory, the same review queue. Pick the route that matches where your source lives.
| Your source lives in | Start here | Anything to install? |
|---|---|---|
| A content platform, a design tool, or documents | From your content | No |
| A repository, and nobody wants a pipeline | From a repository | No |
| A repository a developer works in every day | From a checkout | The kapi CLI |
From your content
You write and publish content; you want it on brand, and in more languages. Nothing to install — open app.bowrain.cloud (or your own server) and sign in. A personal workspace is created on first login.
- Create a project and bring content in. Upload files directly in the web app — the editor works on the formats you already publish — or connect the systems your content lives in (WordPress, HubSpot, Figma) so source flows in and published results flow back. See Getting started on the server and Connectors.
- Establish the brand context. Run a brand scan over content you already trust — it drafts a voice profile and term candidates for you to review and adopt. Vocabulary and content memory grow in the workspace from there.
- Draft and check. In the editor, AI drafts against the workspace's voice profile, vocabulary, and memory; checks flag what drifts.
- Review and publish. Step through the Review surface, approve what's right — corrections feed the learning loop — then export, or publish back through the connector.
The end-to-end path for this route is Publish on brand.
From a repository
Your source files live in a GitHub or GitLab repository, and you would rather not add a pipeline to it. Connect the repository server-side: a push webhook triggers a run, and the results arrive as one open pull/merge request that every later delivery updates in place.
Nothing is installed and nothing is checked out — the server holds the credentials and does the work. With a GitHub App registered for your server, installing the app on a repository and binding it to a project is the only per-repository step.
See the GitHub / GitLab connector for setup, and The Bowrain GitHub App for the walkthrough.
From a checkout
A developer edits the source files every day and wants the results in the working tree they already have open. This is the kapi connector — the kapi CLI with the bowrain plugin installed:
brew install neokapi/tap/bowrain-cli
Connect the repository to a workspace, then catch it up:
kapi init # write kapi.yaml + .kapi/, sign in, connect to a workspace
kapi up # catch every language up — runs on the server
kapi status # per-language coverage, server standing, and venue
kapi up pushes what drifted, runs on the server with the organization's keys
and shared memory, streams progress into the terminal, and pulls the results
down. What a machine cannot decide parks into the team's
review queue.
The full command set, flows, and the CI contract are in the CLI section; Installation covers the other platforms.
Next steps
- Connectors — every route into a workspace, side by side
- Keeping content caught up — what a run does and who starts it
- Publish on brand — the content route, end to end
- The loop in CI — pipelines and the ship gate
- Walkthrough — the developer route on video