English

Deutsch

English

Deutsch

Appearance

Workspace Board ​

Part of the Designer guide. Previous: Overview · Next: Context Map.

The board is the entry point into the Designer. A workspace is technically a directory (repository) with a .jardis/ manifest; it holds one or more domains. From here you navigate into every detail surface.

bash
jardis ui

The Designer opens in the browser on 127.0.0.1.

The workspace board with domain, subdomains, bounded contexts, aggregates, rules and processes

The Structure ​

At the very top sits the domain as a chip header: the real business domain (e.g. "Energy Industry"). Every chip is a domain; the active chip carries the actions Context Map, Edit and a kebab menu (rename / delete).

Below that you work through a finder made of Miller columns, from left to right, every selection opens the next column:

  1. Subdomains — the business-level breakdown of the domain (e.g. "MeterDevice").
  2. Bounded Contexts — the closed model units per subdomain.
  3. Three parallel columns for the selected bounded context: Aggregates, Rules, Processes.

Domain vs. Subdomain

"Domain" is the top-level business domain in the chip header. "Subdomain" is what earlier versions of this surface called "Domain". On disk this is reflected as .jardis/{Domain}/{Subdomain}/{BC}/….

Context Map and Steckbrief are not columns of their own but call-out buttons: the Context Map on the domain tile, the Steckbrief on the BC tile. They lead to their own dedicated pages (Context Map, Bounded Context Editor).

  • Clicking an aggregate or process tile opens the respective canvas in the working frame (Aggregate Designer, Process Designer).
  • ⌘K opens the command palette for project-wide direct jumps.
  • Draft marker: if an aggregate carries an open draft, it shows on its finder tile, a hint that a build is blocked until the draft has been resolved (see Aggregate Designer).

When the window gets narrower, the finder collapses into two bands instead of scrolling horizontally: band 1 strategic (Subdomain · BC), band 2 tactical (Aggregate · Rules · Process).

Creating & Switching Workspaces ​

A workspace comes into being when Jardis registers the .jardis/ manifest in the repository. If the manifest is missing or the repo isn't registered, the Designer shows a banner with the matching repair step.

You drive the same flow headless via the MCP server, there, one workspace is one process (jardis mcp against a project root).