<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Mermaid.js on cbugk&#39;s blog</title>
    <link>https://blog.cbugk.com/tags/mermaid.js/</link>
    <description>Recent content in Mermaid.js on cbugk&#39;s blog</description>
    <generator>Hugo -- 0.140.2</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Apr 2024 01:17:02 +0300</lastBuildDate>
    <atom:link href="https://blog.cbugk.com/tags/mermaid.js/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mermaid Diagram</title>
      <link>https://blog.cbugk.com/post/mermaid-diagram/</link>
      <pubDate>Thu, 18 Apr 2024 01:17:02 +0300</pubDate>
      <guid>https://blog.cbugk.com/post/mermaid-diagram/</guid>
      <description>&lt;p&gt;I am late to the party! But hey, each to their own&amp;hellip;&lt;/p&gt;
&lt;p&gt;My archaic plan of getting fluent in plantUML has failed, &lt;a href=&#34;https://mermaid.js.org&#34;&gt;mermaid.js.org&lt;/a&gt; should do.
To be honest, if I had known early on that &lt;a href=&#34;https://diagrams.net&#34;&gt;diagrams.net&lt;/a&gt; had plantUML insertion capability,
then I might have stuck to it. I also came across &lt;a href=&#34;https://d2lang.com/&#34;&gt;D2&lt;/a&gt;, but I do not need server-side
image generation just yet. Until then mermaid&amp;rsquo;s ubiquity wins.&lt;/p&gt;
&lt;p&gt;So an example is placed below to ensure mermaid integration on my blog blocks Gitlab Pages pipeline.
Henceforth, my wacky ASCII diagrams are no more [*].&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
