Mermaid styling test
Not real content — this page exists to exercise every diagram type Mermaid supports so the theme can be checked against them all. Delete or draft it when the styling is settled.
Flowchart
graph TD
subgraph Ingress
A[Client] --> B{LB}
B -->|path a| C[svc-a]
B -->|path b| D[svc-b]
end
C --> E[(postgres)]
D --> E
E -.-> F[replica]
linkStyle 0 stroke-width:2px
Sequence diagram
sequenceDiagram
autonumber
participant C as Client
participant A as API
participant D as DB
C->>A: GET /things
activate A
A->>D: select *
D-->>A: rows
A-->>C: 200 OK
deactivate A
alt not found
A-->>C: 404
else found
A-->>C: 200
end
Class diagram
classDiagram
class Animal {
+String name
+int age
+makeSound() void
}
class Dog {
+String breed
+fetch() void
}
class Cat {
+bool indoor
+purr() void
}
Animal <|-- Dog
Animal <|-- Cat
Animal "1" --> "*" Food : eats
State diagram
stateDiagram-v2 [*] --> Idle Idle --> Processing : submit Processing --> Succeeded : ok Processing --> Failed : error Failed --> Idle : retry Succeeded --> [*]
Entity-Relationship diagram
erDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
PRODUCT ||--o{ LINE-ITEM : includes
ORDER {
int id PK
string status
date created_at
}
User journey
journey
title Deploying the site
section Build
Write code: 5: Me
Run tests: 3: Me
Fix build: 2: Me
section Ship
Push to main: 4: Me
Watch CI: 1: Me
Ship it: 5: Me
Gantt chart
gantt
title Release plan
dateFormat YYYY-MM-DD
section Prep
Freeze scope :a1, 2026-11-01, 3d
Cut RC :a2, after a1, 2d
section Release
Canary :b1, after a2, 2d
GA :milestone, after b1, 1d
Pie chart
pie title Where the week went "Fixing bugs" : 45 "Reading other people's bugs" : 30 "Writing new bugs" : 20 "Actually shipping" : 5
Quadrant chart
quadrantChart title Effort vs impact x-axis Low effort --> High effort y-axis Low impact --> High impact quadrant-1 Do it quadrant-2 Quick wins quadrant-3 Skip quadrant-4 Money pits Refactor: [0.2, 0.8] Rewrite: [0.9, 0.4] Document: [0.3, 0.6] Fine-tune: [0.7, 0.2]
Git graph
Merge train with a hotfix — the branch labels (main/dev/hotfix) are what matter visually:
---
config:
gitGraph:
showCommitLabel: false
rotateCommitLabel: false
commitLabelFontSize: 12
branchLabelFontSize: 12
---
gitGraph
commit
branch dev
checkout dev
commit tag: "v0.1"
commit
checkout main
merge dev tag: "v0.2"
branch hotfix
checkout hotfix
commit
checkout main
merge hotfix tag: "v0.2.1"
Mindmap
Expanded map, exercising depth:
mindmap
root((paige.bio))
Blog
NetBSD T5325 port
ollama on Docker
Mermaid styling
Design
black and white
Inter + Plex Mono
hairline rules
Infra
GitLab CI
Astro 7
RSS + sitemap
Photos
justified grid
fancybox lightbox
Timeline
---
config:
look: neo
---
timeline
title paige.bio timeline
2025-10 : New site port
2025-11 : Blog posts
: NetBSD 11 port
2026-01 : Photos
2026-11 : Bookmarks rework
: Pagination
: Privacy page
XY chart
xychart-beta title "Build times" x-axis ["Mon", "Tue", "Wed", "Thu", "Fri"] y-axis "seconds" 0 --> 30 bar [12, 14, 9, 25, 11]
Sankey diagram
Where visits to the blog come from, and where they go next — the flows make it a two-stage diagram instead of a flat ribbon list:
sankey-beta search,blog,50 hackernews,blog,25 rss,blog,15 direct,blog,10 blog,photos,28 blog,bookmarks,22 blog,about,15 blog,exit,35
Block diagram
Block diagram with real edges this time — the same delivery pipeline, top to bottom:
block-beta columns 1 git["git push"] space ci["gitlab-ci"] space build["npm run build"] space dist["dist/"] space cdn["Pages CDN"] space site["paige.bio"] git --> ci ci --> build build --> dist dist --> cdn cdn --> site
Packet diagram
packet-beta 0-15: "Source port" 16-31: "Destination port" 32-63: "Sequence number" 64-95: "Acknowledgment number" 96-127: "Data offset & flags"
Kanban board
Real work breakdown for the site itself:
kanban
Todo[Todo]
t1[Search index]
t2[Fix favicon 404s]
t3[Draft more posts]
In Progress[In Progress]
t4[Mermaid styling test]
Done[Done]
t5[Photo galleries]
t6["Pager"]
t7[Privacy page]
Architecture diagram
architecture-beta group api(ink:cloud)[API] service db(ink:database)[DB] in api service web(ink:server)[Web] in api web:R --> L:db
Treemap
Cell area is proportional to the value — breakdown of a production build’s emitted bytes (KB), so each leaf is large enough to read:
treemap-beta
"dist output (KB)"
"mermaid": 612
"icons": 318
"fonts": 204
"styles": 96
Flowchart with subgraphs and styling
graph LR Client --> Edge Edge -->|cached| CDN Edge -->|miss| Origin CDN --> Client Origin --> CDN classDef hot fill:#eee,stroke:#111 class Origin hot