@diagrammo/dgmo 0.10.1 → 0.10.2

package/docs/guide/chart-journey-map.md

@@ -1,179 +0,0 @@
-# Journey Map
-
-```dgmo
-journey-map Coffee Shop Visit
-
-[Order]
-  Walk in | 4
-  Wait in line | 2
-  Order drink | 4
-
-[Wait]
-  Find a seat | 3
-  Wait for drink | 2
-
-[Enjoy]
-  Get drink | 5
-```
-
-## Overview
-
-Journey maps visualize a user's experience across a process or service, plotting emotional highs and lows as a continuous curve. Each step has a score (1–5, high is good) that drives the emotion landscape. Phases group related steps, annotations capture pain points, opportunities, and thoughts, and tags add cross-cutting dimensions like channel or touchpoint.
-
-Journey maps are ideal for UX research, customer experience mapping, service design, and identifying friction points.
-
-## Syntax
-
-```
-journey-map Title
-
-persona Name
-
-[Phase Name]
-  Step Name | score
-  Step Name | score Emotion
-```
-
-The first line must be `journey-map` followed by a title. Phases use bracket syntax at indent 0. Steps are indented within phases.
-
-## Persona
-
-Declares the journey's protagonist:
-
-```
-persona Tech-Savvy Shopper
-  28yo developer, price-sensitive, does extensive research
-```
-
-Name is everything after `persona `. Indented lines add description text. Only one persona per diagram.
-
-## Phases
-
-Phases group steps into logical stages:
-
-```
-[Research]
-  Compare specs | 4
-  Watch reviews | 5
-
-[Purchase]
-  Add to cart | 3
-  Complete payment | 3
-```
-
-Phases are optional — steps can appear at root level for a flat continuous flow.
-
-## Steps
-
-Steps appear indented within phases (or at indent 0 in flat mode).
-
-### Score Syntax
-
-The score goes in the pipe, separating step name from data:
-
-```
-Step Name | 4                        // bare score
-Step Name | 4 Delighted              // score + emotion label
-Step Name | 4, ch: Web               // score + tag metadata
-Step Name | 4 Delighted, ch: Web     // score + label + metadata
-Step Name | score: 4, ch: Web        // explicit score key
-Step Name                            // no pipe = scoreless step
-```
-
-- **Score scale**: 1–5 integer (high = good)
-- **Emotion label**: optional single word after the score (e.g., `Frustrated`, `Delighted`, `Neutral`)
-- **Scoreless steps**: render as cards but produce no emotion curve point
-
-## Annotations
-
-Deeper-indented lines under a step add context:
-
-```
-  Forced account creation | 1 Frustrated
-    pain: Wants guest checkout
-    opportunity: Add guest checkout option
-    thought: Why do I need an account?
-    description: User abandoned cart twice
-```
-
-| Prefix | Rendering |
-|--------|-----------|
-| `pain:` | Pain point (red accent) |
-| `opportunity:` | Improvement opportunity (green accent) |
-| `thought:` | User thought (italic) |
-| `description:` | General context text |
-
-Multiple annotations per step are allowed.
-
-## Tag Groups
-
-Tags add color-coded dimensions like channel or touchpoint:
-
-```
-tag Channel ch
-  Web(blue)
-  Mobile(purple)
-  In-Person(green)
-
-[Research]
-  Compare specs | 4, ch: Web
-  Ask friends | 4, ch: In-Person
-```
-
-Reference tag values in step pipes via the alias.
-
-## Flat Mode
-
-Steps at root level (no `[Phase]` brackets) render as a continuous horizontal strip:
-
-```dgmo
-journey-map Quick Feedback
-
-Opened app | 4
-Searched for feature | 3
-Hit error | 1 Frustrated
-  pain: No helpful error message
-Contacted support | 2
-Got resolution | 5 Relieved
-```
-
-## Directives
-
-| Directive | Effect |
-|-----------|--------|
-| `no-legend` | Hide the score legend |
-| `active-tag GroupName` | Set the active tag group for coloring |
-
-## Complete Example
-
-```dgmo
-journey-map Buying a Laptop
-
-persona Tech-Savvy Shopper
-  28yo developer, price-sensitive, does extensive research
-
-tag Channel ch
-  Web(blue)
-  Mobile(purple)
-  Email(teal)
-  In-Person(green)
-
-[Research]
-  Compare specs | 4, ch: Web
-    description: Checked 12 laptops across 4 review sites
-  Watch reviews | 5 Engaged, ch: Mobile
-  Ask friends | 4, ch: In-Person
-
-[Purchase]
-  Add to cart | 3, ch: Web
-  Forced account creation | 1 Frustrated, ch: Web
-    pain: Wants guest checkout
-    pain: Password requirements too strict
-  Complete payment | 3, ch: Web
-
-[Delivery]
-  Track package | 4, ch: Mobile
-  Unboxing | 5 Delighted, ch: In-Person
-    opportunity: Include setup guide
-    thought: Excited to try it out
-```

package/docs/guide/chart-kanban.md

@@ -1,158 +0,0 @@
-# Kanban Board
-
-```dgmo
-kanban Plunder Sprint 7
-
-tag Priority
-  Urgent(red)
-  High(orange)
-  Low(green) default
-
-tag Crew alias c
-  Blackbeard(red)
-  Anne Bonny(purple)
-  Calico Jack(teal)
-
-[Awaiting Orders](red)
-  Recruit gunners at Tortuga | priority: High, c: Calico Jack
-  Chart new trade route | priority: Urgent, c: Anne Bonny
-    Scout the Windward Passage
-    Avoid Royal Navy patrols
-  Resupply rum and powder | priority: Low, c: Calico Jack
-
-[Underway](orange) | wip: 2
-  Forge letters of marque | priority: High, c: Anne Bonny
-  Raid merchant convoy | priority: Urgent, c: Blackbeard
-    Three ships spotted off Nassau
-
-[Done](green)
-  Bribe the harbour master | priority: High, c: Anne Bonny
-  Repair hull damage | priority: Low, c: Blackbeard
-```
-
-## Overview
-
-Kanban boards visualize work items as cards organized into columns. Columns typically represent workflow stages (To Do, In Progress, Done). Cards can carry tags for color-coded categorization and freeform detail text.
-
-**Drag-and-drop:** In the app, drag cards between columns or reorder within a column. The editor text updates automatically.
-
-## Syntax
-
-```
-kanban Board Title
-
-[Column Name]
-Card Title
-Card Title | key: Value, key: Value
-  Freeform detail text
-  Another detail line
-```
-
-## Settings
-
-| Key     | Description      | Default |
-| ------- | ---------------- | ------- |
-| `chart` | Must be `kanban` | —       |
-| `title` | Board title      | None    |
-
-## Columns
-
-Columns are defined with `[Column Name]` syntax. All cards between one column header and the next belong to that column.
-
-Kanban columns model a workflow pipeline. Cards move left to right as work progresses. Each column should answer "what stage is this work in?" If something isn't a stage — like acceptance criteria, decision gates, or definitions of done — model it as a tag on cards rather than a separate column.
-
-```
-[To Do]
-[In Progress]
-[Done]
-```
-
-### WIP Limits
-
-Add `| wip: N` after a column header to set a work-in-progress limit. A warning appears when the limit is exceeded:
-
-```
-[In Progress] | wip: 3
-```
-
-## Cards
-
-Each non-indented line within a column creates a card. Cards can have tags and detail lines.
-
-### Tags
-
-Tags follow the card title, separated by `|`. Multiple tags are comma-separated:
-
-```
-Build login | priority: High, assignee: Alice
-```
-
-### Detail Lines
-
-Indented lines under a card are freeform detail text:
-
-```
-Build login | priority: High
-  OAuth + email/password support
-  Needs design review first
-```
-
-### Card Colors
-
-Add a color suffix to a card title:
-
-```
-Urgent fix(red)
-```
-
-## Tag Groups
-
-Tag groups define categories with color-coded values. They appear before columns and use the `tag` directive:
-
-```
-tag Priority
-  High(red)
-  Medium(yellow)
-  Low(green) default
-
-tag Assignee alias a
-  Alice(blue)
-  Bob(purple)
-```
-
-- `default` marks the fallback value for cards without an explicit tag
-- `alias` provides a short name for the tag (e.g., `a` instead of `assignee`)
-- Colors are shown as dots on each card
-
-## Complete Example
-
-```dgmo
-kanban Product Roadmap
-
-tag Status
-  Blocked(red)
-  Active(green) default
-
-tag Team alias t
-  Frontend(blue)
-  Backend(purple)
-  Design(yellow)
-
-[Backlog]
-Dark mode support | t: Frontend
-API rate limiting | t: Backend
-  Research token bucket vs sliding window
-
-[In Progress] | wip: 3
-User dashboard | t: Frontend, status: Active
-  Charts and metrics overview
-Auth refactor | t: Backend, status: Active
-
-[Review]
-Payment integration | t: Backend, status: Blocked
-  Waiting on Stripe webhook setup
-
-[Done]
-Onboarding flow | t: Design
-Landing page | t: Frontend
-```

package/docs/guide/chart-line.md

@@ -1,79 +0,0 @@
-# Line Chart
-
-```dgmo
-line Ship Speed Over Voyage
-series Knots
-x-label Day
-y-label Speed
-
-era Day 1 -> Day 3 Rough Seas (red)
-era Day 3 -> Day 7 Fair Winds (blue)
-
-Day 1 8
-Day 2 10
-Day 3 7
-Day 4 12
-Day 5 9
-Day 6 11
-Day 7 6
-```
-
-## Syntax
-
-```
-line Chart Title
-series Series Name
-x-label X Axis Label
-y-label Y Axis Label
-
-Label value
-```
-
-## Era Bands
-
-Annotate named time periods with a shaded background band and label:
-
-```dgmo
-line U.S. Strategic Petroleum Reserve
-y-label Million Barrels
-
-era '77 -> '81 Carter (blue)
-era '81 -> '89 Reagan (red)
-era '89 -> '93 Bush (red)
-
-'77 7
-'78 67
-'79 91
-'80 108
-'81 230
-'82 294
-'83 379
-```
-
-Era syntax: `era <start> -> <end> Label (color)`
-
-- `start` and `end` must exactly match data point labels
-- Color is optional; omit for the palette default
-- Named colors: `red`, `blue`, `green`, `orange`, `purple`, `teal`, etc.
-- Multiple eras can overlap — both render without error
-
-## Metadata Keys
-
-| Key       | Description                               | Required |
-| --------- | ----------------------------------------- | -------- |
-| `chart`   | Must be `line`                            | Yes      |
-| `title`   | Chart title displayed above the chart     | No       |
-| `series`  | Name of the data series (shown in legend) | No       |
-| `x-label` | Label for the X axis                      | No       |
-| `y-label` | Label for the Y axis                      | No       |
-| `color`   | Override the line color                   | No       |
-
-## Data Format
-
-Each data line follows the pattern `Label value`:
-
-```
-Day 1 8
-Day 2 10
-Day 3 7
-```

package/docs/guide/chart-mindmap.md

@@ -1,198 +0,0 @@
-# Mind Map
-
-```dgmo
-mindmap Product Strategy
-
-Research
-  User Interviews
-    Surveys | description: Quarterly NPS survey
-    Focus Groups
-  Competitor Analysis
-    Feature Matrix
-    Pricing Review
-Development
-  MVP Features
-    Auth System
-      description: Handle login, signup, OAuth flows
-    Dashboard
-  Nice-to-haves | collapsed: true
-    Dark Mode
-    Export PDF
-Go-to-Market
-  Launch Plan
-    Blog Post
-    Demo Video | description: 2-min product walkthrough
-```
-
-## Overview
-
-Mind maps visualize hierarchical information radiating from a central concept. Each branch represents a subtopic, with deeper nesting for finer detail. Mind maps are useful for brainstorming, project planning, knowledge organization, and breaking down complex topics.
-
-**Interactive features:** Click nodes to navigate to their source line. Collapse and expand subtrees by clicking nodes with children. Toggle tag group coloring and depth-based coloring via the legend controls.
-
-## Syntax
-
-```
-mindmap Title
-
-Node
-  Child Node
-    Grandchild
-  Another Child
-```
-
-The first line declares the chart type. The title becomes the root node. Indentation establishes the parent-child hierarchy.
-
-## Nodes
-
-Every non-blank, non-directive line is a node. Nesting is set by indentation:
-
-```
-mindmap Root
-  Level 1a
-    Level 2a
-    Level 2b
-  Level 1b
-```
-
-### Node Colors
-
-Add a color suffix in parentheses:
-
-```
-Important Topic(red)
-  Sub-topic(blue)
-```
-
-### Descriptions
-
-Nodes can have descriptions shown as secondary text. Two forms:
-
-```
-// Pipe form (single line)
-Surveys | description: Quarterly NPS survey
-
-// Indented form (before children)
-Auth System
-  description: Handle login, signup, and OAuth flows
-  Login Page
-```
-
-### Collapse Default
-
-Set a node's default collapsed state with pipe metadata:
-
-```
-Nice-to-haves | collapsed: true
-  Dark Mode
-  Export PDF
-```
-
-Collapsed nodes show a drill-bar indicating hidden children. Click to expand.
-
-## Multi-Root
-
-Omit the title to create multiple independent root trees:
-
-```
-mindmap
-
-Q1 Goals
-  Ship MVP
-  Hire designers
-Q2 Goals
-  Launch marketing
-  Expand team
-```
-
-The diagram title is inferred from the first root's label.
-
-## Pipe Metadata
-
-Attach metadata after `|` with comma-separated `key: value` pairs:
-
-```
-Node | priority: High, status: Done
-```
-
-Tag values, descriptions, and `collapsed` are all set via pipe metadata.
-
-## Tag Groups
-
-Tag groups define color-coded categories. They appear before content and follow the standard tag syntax:
-
-```
-mindmap Root
-
-tag Priority p
-  High(red)
-  Medium(yellow)
-  Low(green)
-
-  Task A | p: High
-  Task B | p: Low
-```
-
-- The alias (`p`) provides a shorthand for metadata keys
-- The active tag group colors nodes by their tag value
-- Click a tag group name in the legend to activate or deactivate it
-
-## Options
-
-| Option | Effect |
-|--------|--------|
-| `active-tag GroupName` | Set the default active tag group |
-| `no-descriptions` | Hide description text on all nodes |
-
-Options are placed on their own line before content:
-
-```
-mindmap Root
-
-tag Priority p
-  High(red)
-  Low(green)
-
-active-tag Priority
-no-descriptions
-
-  Task A | p: High
-```
-
-## Complete Example
-
-```dgmo
-mindmap Product Strategy(blue)
-
-tag Priority p
-  High(red)
-  Medium(yellow)
-  Low(green)
-
-tag Department d
-  Engineering(blue)
-  Design(purple)
-  Marketing(orange)
-
-active-tag Priority
-
-Research | d: Marketing
-  User Interviews | p: High
-    Surveys | description: Quarterly NPS survey
-    Focus Groups
-  Competitor Analysis | d: Engineering
-    Feature Matrix
-    Pricing Review
-Development | p: High, d: Engineering
-  MVP Features
-    Auth System
-      description: Handle login, signup, OAuth flows
-    Dashboard
-  Nice-to-haves | p: Low, collapsed: true
-    Dark Mode
-    Export PDF
-Go-to-Market | d: Marketing
-  Launch Plan
-    Blog Post
-    Demo Video | description: 2-min product walkthrough
-```

package/docs/guide/chart-multi-line.md

@@ -1,84 +0,0 @@
-# Multi-Line Chart
-
-```dgmo
-line Monthly Captures by Fleet
-series Blackbeard(red), Roberts(blue), Vane(green)
-x-label Month
-//y-label Captures
-
-era Jan -> Mar Atlantic Season
-era Mar -> Jun Caribbean Season (teal)
-
-Jan 3 5 2
-Feb 4 3 4
-Mar 2 7 3
-Apr 6 4 1
-May 5 6 5
-Jun 3 8 2
-```
-
-## Syntax
-
-```
-line Chart Title
-series Series1(color), Series2(color), Series3(color)
-x-label X Axis Label
-
-Label value1 value2 value3
-```
-
-## Metadata Keys
-
-| Key       | Description                                                      | Required |
-| --------- | ---------------------------------------------------------------- | -------- |
-| `chart`   | Must be `line` (or `multi-line` as an alias)                     | Yes      |
-| `title`   | Chart title displayed above the chart                            | No       |
-| `series`  | Comma-separated series names with optional colors in parentheses | Yes      |
-| `x-label` | Label for the X axis                                             | No       |
-| `y-label` | Label for the Y axis                                             | No       |
-
-## Data Format
-
-Each data line provides space-separated values matching the series order:
-
-```
-Jan 3 5 2
-Feb 4 3 4
-```
-
-The number of values per line must match the number of series names.
-
-## Era Bands
-
-Annotate named time periods with a shaded background band and label:
-
-```dgmo
-line Monthly Captures by Fleet
-series Blackbeard(red), Roberts(blue)
-x-label Month
-
-era Jan -> Mar Q1 (green)
-era Apr -> Jun Q2 (orange)
-
-Jan 3 5
-Feb 4 3
-Mar 2 7
-Apr 6 4
-May 5 6
-Jun 3 8
-```
-
-Era syntax: `era <start> -> <end> Label (color)`
-
-- `start` and `end` must exactly match data point labels
-- Color is optional; omit for the palette default
-- Era bands render on the first series only
-
-## Series Colors
-
-Colors can be specified in parentheses after each series name using named colors:
-
-```
-series Gold(yellow), Silver(gray), Bronze(orange)
-series Fleet A(red), Fleet B(blue)
-```