<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Erzan Engineering Docs Blog</title>
        <link>https://erzan.docs/blog</link>
        <description>Erzan Engineering Docs Blog</description>
        <lastBuildDate>Tue, 24 Mar 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[Slowly transitioning to Portfolio CMS starting from Blog/Dev Log]]></title>
            <link>https://erzan.docs/blog/transition</link>
            <guid>https://erzan.docs/blog/transition</guid>
            <pubDate>Tue, 24 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[This will be on the next minor update for the next v1.5.0 it will include blog content management since I will be slowly transitioning to CMS type portfolio, so all of my development, new content, features and future updates will be manage easily here. I will be using Supabase and Drizzle orm for database management. This is where I will personally manage my Portfolio as I planned to reduce my static page usage since I have Github API already for my projects fetch data queries.]]></description>
            <content:encoded><![CDATA[<p>This will be on the next minor update for the next v1.5.0 it will include blog content management since I will be slowly transitioning to CMS type portfolio, so all of my development, new content, features and future updates will be manage easily here. I will be using Supabase and Drizzle orm for database management. This is where I will personally manage my Portfolio as I planned to reduce my static page usage since I have Github API already for my projects fetch data queries.</p>]]></content:encoded>
            <category>supabase</category>
            <category>Content Management system</category>
            <category>Drizzle</category>
            <category>DevOps Architecture</category>
        </item>
        <item>
            <title><![CDATA[Converting Product Inventory System into Monorepo]]></title>
            <link>https://erzan.docs/blog/convert</link>
            <guid>https://erzan.docs/blog/convert</guid>
            <pubDate>Mon, 23 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[This blog post is about converting my currently existing development with backend and frontend into a monorepo approach, next.]]></description>
            <content:encoded><![CDATA[<p>This blog post is about converting my currently existing development with backend and frontend into a monorepo approach, next.</p>]]></content:encoded>
            <category>Monorepo</category>
            <category>Fullstack</category>
            <category>NestJS</category>
            <category>NextJS</category>
        </item>
        <item>
            <title><![CDATA[The First Deployment]]></title>
            <link>https://erzan.docs/blog/first-blog</link>
            <guid>https://erzan.docs/blog/first-blog</guid>
            <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[This is a blog post about my journey from planning, building, pre releases and first mature and stable release with vercel deployment on version 1.0.0.]]></description>
            <content:encoded><![CDATA[<p>This is a blog post about my journey from planning, building, pre releases and first mature and stable release with vercel deployment on version 1.0.0.</p>
<p>After the following release at March 22, 2026 I have already new things and ideas in mind to add and implement. With this momentum I will be continuing to improved my public facing personal portfolio platform. Yes I noticed that there are bugs and errors and it will be patched soon as I already issued them at my GitHub Repository.</p>
<p>The journey was really fun and the excitement and trill when day the release came even though I have to still polished many things up, but I managed and that is the most fulfiiling part and rewarding seeing what you have been working on bring to life. I always planned and wanted to build my own professional looking public facing portfolio but never started or started but got hit by something that cannot be fixed asap lol. But this year I mustered my courage and desciplined to really push and have something I can deploy to the web.</p>
<p>It was not easy but I was determined I stayed consistent when its hard when I just want to relax and spend my day doing not productive things. I can feel my momentum already on finishing this project from my backend development now at work currently with NestJS and I want myself to be expose to NextJS so I can really feel whats going on on the other side like to become a certified or should I say I can really consider myself as Fullstack Dev.</p>
<p>So the day came and I don't know what was into me that day, where I was planning things up what is my approach and what do I need to get started and yes the side of me where says I want to develop this with the scalabality in mind in the future lol, it was so funny for me because this kind of trait is new to me as a developer because back then I don't really give much attention to scalability with my projects as long as it gets things done and it is finished then proceed to another.</p>
<p>I am really thankful to my current work where I am now, they teach me a lot I learned a lot of things with the people I am sorrounded with in work. I adopt to what they are doing, what they are thinking and how things should be done yes my start was a bit slow but it was progressive day by day as time pass by all the experiences, failures, success, small wins, big wins, project proposals, project discussions, and meaningful conversations with my fellow devs and manager especially my Sr. who had been with me no progress to slow progress and stuck to snowballing and no momentum to in the zone and the growth mindset where I can relate myself too since the things they are interested are also what I am passionate about. I will always be grateful and thankful to this people. They are the best.</p>
<p>So now it has been released and deployed these are the things I have in my add a fully utilize blog at personal portfolio blog here in documentation maybe deprecated soon, personal chatbot assistant, make this into a Portfolio CMS and separate the dev tools platform deployment, add schedule a call or meeting, update and improve ui/ux, integrate to supabase to reduce static datas usage, add demos to projects with deployments, and to utilize my personal docs as my demo ground and also other documentations for my projects.</p>
<p>For now these are my plans. Thank you for your time reading. Have a nice day, God bless!</p>]]></content:encoded>
            <category>First Deployment</category>
            <category>Documentation</category>
            <category>Vercel</category>
            <category>Versioning</category>
        </item>
        <item>
            <title><![CDATA[MDX Blog Post]]></title>
            <link>https://erzan.docs/blog/mdx-blog-post</link>
            <guid>https://erzan.docs/blog/mdx-blog-post</guid>
            <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Blog posts support Docusaurus Markdown features, such as MDX.]]></description>
            <content:encoded><![CDATA[<p>Blog posts support <a href="https://docusaurus.io/docs/markdown-features" target="_blank" rel="noopener noreferrer" class="">Docusaurus Markdown features</a>, such as <a href="https://mdxjs.com/" target="_blank" rel="noopener noreferrer" class="">MDX</a>.</p>
<div class="theme-admonition theme-admonition-tip admonition_IZjC alert alert--success"><div class="admonitionHeading_uVvU"><span class="admonitionIcon_HiR3"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>tip</div><div class="admonitionContent_bl22"><p>Use the power of React to create interactive blog posts.</p></div></div>
<!-- -->
<p>For example, use JSX to create an interactive button:</p>
<div class="language-js codeBlockContainer_ZGJx theme-code-block" style="--prism-color:#F8F8F2;--prism-background-color:#282A36"><div class="codeBlockContent_kX1v"><pre tabindex="0" class="prism-code language-js codeBlock_TAPP thin-scrollbar" style="color:#F8F8F2;background-color:#282A36"><code class="codeBlockLines_AdAo"><span class="token-line" style="color:#F8F8F2"><span class="token operator">&lt;</span><span class="token plain">button onClick</span><span class="token operator">=</span><span class="token punctuation" style="color:rgb(248, 248, 242)">{</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token plain"> </span><span class="token arrow operator">=&gt;</span><span class="token plain"> </span><span class="token function" style="color:rgb(80, 250, 123)">alert</span><span class="token punctuation" style="color:rgb(248, 248, 242)">(</span><span class="token string" style="color:rgb(255, 121, 198)">'button clicked!'</span><span class="token punctuation" style="color:rgb(248, 248, 242)">)</span><span class="token punctuation" style="color:rgb(248, 248, 242)">}</span><span class="token operator">&gt;</span><span class="token maybe-class-name">Click</span><span class="token plain"> me</span><span class="token operator">!</span><span class="token operator">&lt;</span><span class="token operator">/</span><span class="token plain">button</span><span class="token operator">&gt;</span><br></span></code></pre></div></div>
<button>Click me!</button>]]></content:encoded>
            <category>Docusaurus</category>
        </item>
        <item>
            <title><![CDATA[Welcome]]></title>
            <link>https://erzan.docs/blog/welcome</link>
            <guid>https://erzan.docs/blog/welcome</guid>
            <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Docusaurus blogging features are powered by the blog plugin.]]></description>
            <content:encoded><![CDATA[<p><a href="https://docusaurus.io/docs/blog" target="_blank" rel="noopener noreferrer" class="">Docusaurus blogging features</a> are powered by the <a href="https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog" target="_blank" rel="noopener noreferrer" class="">blog plugin</a>.</p>
<p>Here are a few tips you might find useful.</p>
<p>Simply add Markdown files (or folders) to the <code>blog</code> directory.</p>
<p>Regular blog authors can be added to <code>authors.yml</code>.</p>
<p>The blog post date can be extracted from filenames, such as:</p>
<ul>
<li class=""><code>2019-05-30-welcome.md</code></li>
<li class=""><code>2019-05-30-welcome/index.md</code></li>
</ul>
<p>A blog post folder can be convenient to co-locate blog post images:</p>
<p><img decoding="async" loading="lazy" alt="Docusaurus Plushie" src="https://erzan.docs/assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg" width="1500" height="500" class="img__Ss2"></p>
<p>The blog supports tags as well!</p>
<p><strong>And if you don't want a blog</strong>: just delete this directory, and use <code>blog: false</code> in your Docusaurus config.</p>]]></content:encoded>
            <category>Facebook</category>
            <category>Hello</category>
            <category>Docusaurus</category>
        </item>
    </channel>
</rss>