3 ms·
Yes! If you're making a product for "pure" writers, I'm with you almost 100%. That being said, Markdown has always included the ability to insert custom HTML,
by a4isms 4y ago
Yes! If you're making a product for "pure" writers, I'm with you almost 100%.
That being said, Markdown has always included the ability to insert custom HTML, because Gruber wrote it to scratch his own itch. He didn't make Markdown to hide HTML from himself, he made it to do away with all the ceremony of angle brackets, which are a PITA to type and definitely make the result harder to read from source.
From a readability standpoint, I'd prefer:
```mermaid
stateDiagram
[*] --> start
start --> zero : 0
start --> one : 1
one --> one : 0, 1
zero --> [*]
one --> [*]
```
to:
<div class="mermaid">
stateDiagram
[*] --> start
start --> zero : 0
start --> one : 1
one --> one : 0, 1
zero --> [*]
one --> [*]
</div>
But I can deal with that. What discomforts me personally is the worry that something about the mermaid.js implementation will break in a future browser version.
Were I compiling to SVG or PNG as part of my build tooling, I would have a lot more trust that I could maintain a working toolchain in the future.
JM2C, YMMV, &c.