Gå til hovedinnhold

Author a project visually

Goal: set up a project in Kapi Desktop: the content it governs, the voice and coordinates that govern it and, if you translate, its languages. You end with the same committable kapi.yaml recipe that kapi init writes.

For the project model itself (the recipe, the state directory, how commands find a project), see Projects and Your first project.

Outdated recording

The interface has changed since this was recorded. The workflow it demonstrates still applies, but some screens and labels differ from the current release. The clip shows an earlier layout of the project home; the app opens on the two-axis standing and where content sits. It comes from the Kapi Desktop tour, so it shows creating and managing a project within a wider walkthrough and does not follow the steps below one by one.

Steps​

  1. Create the project. Choose File > New Project (or New Project on the home screen): a name, a location and a source language. The app writes a kapi.yaml recipe and the sibling .kapi/ directory, the same layout kapi init produces. To explore a finished project first, open KapiMart under sample projects.
  2. Add content. In the Project view, add the patterns that match your source files (docs, UI strings, contracts) as named collections. The home shows each pattern beside the real files it matches and the format kapi detected for each.
  3. Bind governance. In Project Settings, choose the voice profile the project goes by (one from the project's voice store, or a starter pack), set the default point on the declared axes (a brand, and any axis you add), and declare profiles for a product that ships on several channels. The Context hub then shows what resolved: the voice at each point, and the terms and content memory the project holds.
  4. Declare languages, if you translate. Add target languages in Project Settings. The home then shows per-language coverage, and Bring up to date runs the project's default flow to the ship gates, the same loop as kapi up. A project that translates nothing is complete without this step.
  5. Commit the recipe. Commit kapi.yaml and the agent configuration so the CLI and desktop use the same project settings. .kapi/ is ignored by default. Project context lives in your workspace, and kapi context sync is how it reaches another machine or a teammate.

What the desktop adds​

The app keeps the project's shape in view: which patterns match which files, the format of each, and what governs each point. It validates the recipe as you go. The result is an ordinary kapi.yaml recipe, so kapi on the command line and in CI drives the same project.

Next​