Journal · PlantUML · Confluence
Articles
Practical writing on PlantUML, diagram-as-code, and Confluence Cloud — from the team behind the source-available PlantUML for Confluence.
Text in, diagram out — diffable, reviewable, regenerable. Why the workflow earns its keep for long-lived docs, and how to run it inside Confluence Cloud.
The diagram source travels to whichever server renders it. How to make that server yours: Docker, HTTPS, the CORS gotcha, and what the app stores where.
Macro shows an error, diagram won't render, app says "update required" with no update to install. What each failure means, what's recoverable, and when it's time to switch.
Both open source, both text-to-diagram — and the standard advice says Mermaid for READMEs, PlantUML for the wiki. What actually differs once the diagrams live in Confluence.
Free apps can turn paid, and free apps can be abandoned. How to tell what kind of free you're adopting — and why open source changes the answer.
The macros don't survive the migration, but the diagrams can. What breaks, what's recoverable, and a sequence that gets every diagram rendering again on the other side.