Boards, tags and diagrams
A set is the archive; a board is the surface people actually mark up. These are the commands that turn one into the other and keep the result findable.
Turn a set into a board
vitrinka board create --title "Checkout — pass 3"| Flag | What it does |
|---|---|
--title / --btitle | Board title. |
--slug | Board slug. Defaults to the set key. |
--journey | Build a branching journey tree instead of a flat flow board. |
--actor | X-Board-Actor attribution. Defaults to the stored operator. |
--root | Capture root. Default .vitrinka/screenshots. |
Find a board
list filters by the three axes a board is filed under — project, subgroup and tag — plus its type.
vitrinka board list --project myapp --type journeys
vitrinka board view checkout-pass-3| Flag | What it does |
|---|---|
--project | Only boards owned by this project. |
--subgroup | Only boards in this sidebar subgroup. |
--type | Only boards of this type — brainstorm, docs, journeys… |
--tags | Comma-separated. Prefix one with - to exclude it. |
--match | How to combine tags: all (default) or any. |
--archived | Include archived boards. |
Put things on a board
upload puts arbitrary files on as cards. import-chat publishes a chat transcript — an eve run or NDJSON — as a chat card.
vitrinka board upload ./report.html ./notes.md
vitrinka board import-chat run.ndjsonTags
The third axis beside project and subgroup.
vitrinka tag add checkout-pass-3 regression payments
vitrinka tag list
vitrinka tag remove checkout-pass-3 regressionDiagrams
import parses a file you already maintain into a diagram; schema introspects a live Postgres locally and pushes what it finds.
vitrinka diagram import docker-compose.yml
vitrinka diagram schema