Turn the warning block into callouts with four kinds (#62) #63
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba!63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/62-callouts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #62
Summary
The Editor.js warning block becomes a Callout: an optional title and a message, in one of four kinds. The kind is chosen in the block's settings. Editor and reader show the kind's icon, border and tint.
--warning--danger--info(new)--success(new)GLOSSARY (Callout), ADR-0005, CHANGELOG (Unreleased) and the German catalogue are updated.
Evidence
After: the new e2e test
a callout's kind shows while editing, also in dark mode, and when readswitches a callout to error in dark mode, asserts the icon reaches ≥ 3:1 contrast on the tint, saves, and finds the error callout with its icon in the read view (8/8 repeated runs green).warningreads as a warning callout; a missing/unknown kind reads as note.Merge Danger
Door: one-way, for content
Once a description or step with a warning is saved after deploy, it is stored as a
calloutblock. Rolling back to a build without this change would drop those blocks from rendering and from the editor (unknown blocks are discarded by the parser), and the next save would delete them.Blast Radius: rich-text
All rich text (guide/category descriptions, step content) renders through the changed parser; the search text is unchanged. Not verified by eye: the other three kinds in light/dark mode (colours only checked via tokens).
🤖 Generated with Claude Code