<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>WASM on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/wasm/</link><description>Recent content in WASM on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/wasm/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 7: Implementing Partial Hydration for Interactive Components</title><link>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-07-partial-hydration/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-07-partial-hydration/</guid><description>&lt;h2 id="chapter-7-implementing-partial-hydration-for-interactive-components"&gt;Chapter 7: Implementing Partial Hydration for Interactive Components&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 7! In the previous chapters, we built a robust foundation for our Static Site Generator (SSG), capable of parsing Markdown, extracting front matter, and rendering static HTML using Tera templates, including custom components. While this provides excellent performance for static content, many modern web applications require interactivity. This is where &lt;strong&gt;partial hydration&lt;/strong&gt; comes into play.&lt;/p&gt;
&lt;p&gt;In this chapter, we will extend our SSG to support interactive components that are initially rendered as static HTML on the server and then &amp;ldquo;hydrated&amp;rdquo; on the client-side with JavaScript and WebAssembly (WASM) to become interactive. This approach, often called &amp;ldquo;Island Architecture&amp;rdquo; (popularized by frameworks like Astro), offers the best of both worlds: fast initial page loads for static content and dynamic interactivity where needed, without shipping heavy JavaScript bundles for the entire page. We will use the &lt;a href="https://yew.rs/"&gt;Yew framework&lt;/a&gt; for our client-side WebAssembly components, leveraging Rust&amp;rsquo;s power end-to-end.&lt;/p&gt;</description></item><item><title>Chapter 14: Monitoring, Maintenance &amp;amp; Future Extensibility</title><link>https://ai-blog.noorshomelab.dev/mermaid-lint-guide/chapter-14-monitoring-maintenance-extensibility/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mermaid-lint-guide/chapter-14-monitoring-maintenance-extensibility/</guid><description>&lt;h2 id="chapter-14-monitoring-maintenance--future-extensibility"&gt;Chapter 14: Monitoring, Maintenance &amp;amp; Future Extensibility&lt;/h2&gt;
&lt;p&gt;Welcome to the final chapter of our journey building a production-grade Mermaid analyzer and fixer. Throughout this guide, we&amp;rsquo;ve focused on correctness, performance, and best practices. Now, as we approach deployment, it&amp;rsquo;s crucial to consider the long-term aspects: how to keep our tool reliable, performant, and adaptable to future needs.&lt;/p&gt;
&lt;p&gt;In this chapter, we will delve into critical topics such as monitoring the tool&amp;rsquo;s performance, establishing robust maintenance strategies, and exploring avenues for future extensibility. We&amp;rsquo;ll integrate structured logging, set up performance benchmarks, design a conceptual plugin system, discuss WebAssembly (WASM) compilation, and demonstrate CI/CD integration. By the end of this chapter, you will have a comprehensive understanding of how to ensure the &lt;code&gt;mermaid-tool&lt;/code&gt; remains a valuable asset for years to come, with a clear path for its evolution.&lt;/p&gt;</description></item></channel></rss>