Skip to content

contributing: drop the no-Mermaid prohibition - #26

Merged
TaprootFreak merged 2 commits into
developfrom
docs/contributing-allow-mermaid
Jun 6, 2026
Merged

contributing: drop the no-Mermaid prohibition#26
TaprootFreak merged 2 commits into
developfrom
docs/contributing-allow-mermaid

Conversation

@TaprootFreak

@TaprootFreak TaprootFreak commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Why

The ### Diagrams section in CONTRIBUTING.md prescribed diagram style and was repeatedly ignored in practice:

A contributing guide is not the place to dictate diagram form. Devs pick what renders the point best.

What changes

The entire ### Diagrams subsection is removed (10 lines).

The bans on external images and external tooling were de-facto carried by the project anyway (everything in docs/ is markdown + Docusaurus); no need to re-state them as diagram-style rules.

Verification

Single-section removal, no code touched, no build artefacts affected.

The Diagrams section banned Mermaid outright. In practice this was
ignored — architecture.md has shipped with a Mermaid flowchart since
the deployment-diagram PR, and the implementation-readiness pass had to
back-convert two useful lifecycle/data-flow diagrams to ASCII solely to
comply with the rule on paper. The constraint produced no benefit and
forced uglier diagrams.

Allow both ASCII and Mermaid; keep the ban on external images and
external tooling (no PNGs, no draw.io, no Lucid).
User feedback: the prescriptive diagram-style rule has no business
being in a contributing guide. Devs choose what renders the point
best. Section dropped.
@TaprootFreak
TaprootFreak marked this pull request as ready for review June 6, 2026 12:20
@TaprootFreak
TaprootFreak merged commit 5bf4631 into develop Jun 6, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant