<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build Process on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/build-process/</link><description>Recent content in Build Process on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 02 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/build-process/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 8: Building the Core Pipeline: Routing and Output Generation</title><link>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-08-core-pipeline-routing/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-08-core-pipeline-routing/</guid><description>&lt;h2 id="chapter-8-building-the-core-pipeline-routing-and-output-generation"&gt;Chapter 8: Building the Core Pipeline: Routing and Output Generation&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 8! In the previous chapters, we laid the groundwork for our Rust-based Static Site Generator (SSG). We&amp;rsquo;ve learned how to parse content, extract frontmatter, convert Markdown to HTML, and render that HTML using a templating engine like Tera. We even introduced the concept of component support within Markdown, preparing our system for dynamic interactions. Now, it&amp;rsquo;s time to connect these pieces and bring our SSG to life by defining how content maps to URLs and generating the final static HTML files.&lt;/p&gt;</description></item><item><title>Chapter 14: Search Indexing with Pagefind Integration</title><link>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-14-search-indexing/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-14-search-indexing/</guid><description>&lt;h2 id="chapter-14-search-indexing-with-pagefind-integration"&gt;Chapter 14: Search Indexing with Pagefind Integration&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! In this installment, we&amp;rsquo;ll elevate the usability of our static site generator by implementing powerful, client-side search capabilities. While our SSG is excellent for generating static content, a modern website often requires a way for users to quickly find specific information. We&amp;rsquo;ll integrate Pagefind, a fast and efficient search library designed specifically for static sites, to provide an intuitive search experience without needing a backend server.&lt;/p&gt;</description></item><item><title>Chapter 14: Deployment and CI/CD for React Applications</title><link>https://ai-blog.noorshomelab.dev/react-production-guide-2026/deployment-cicd-react/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-production-guide-2026/deployment-cicd-react/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! So far, we&amp;rsquo;ve built robust, performant, and secure React applications. But what good is a fantastic application if no one can use it reliably? This chapter is all about getting your React app out into the world and keeping it running smoothly.&lt;/p&gt;
&lt;p&gt;Here, we&amp;rsquo;ll dive deep into &lt;strong&gt;Deployment&lt;/strong&gt; and &lt;strong&gt;Continuous Integration/Continuous Delivery (CI/CD)&lt;/strong&gt;. You&amp;rsquo;ll learn how to automate the process of building, testing, and releasing your React application, ensuring every change you make is delivered to your users quickly and safely. We&amp;rsquo;ll explore why these practices are non-negotiable for modern software development, the common pitfalls to avoid, and how to implement them step-by-step using industry-standard tools.&lt;/p&gt;</description></item><item><title>Project: Simplified CI/CD with Docker</title><link>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-14-project-simplified-cicd/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-14-project-simplified-cicd/</guid><description>&lt;h2 id="introduction-automating-your-workflow-with-docker-and-cicd"&gt;Introduction: Automating Your Workflow with Docker and CI/CD&lt;/h2&gt;
&lt;p&gt;Welcome back, future Docker master! In our journey so far, you&amp;rsquo;ve learned to containerize applications, manage multiple services with Compose, and understand the power of isolated environments. Now, it&amp;rsquo;s time to put those skills to work on a concept that truly revolutionizes software development: &lt;strong&gt;Continuous Integration/Continuous Delivery (CI/CD)&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;CI/CD is all about automating the process of building, testing, and deploying your code. It helps catch bugs earlier, ensures consistent quality, and speeds up your development cycle. While full-fledged CI/CD systems like GitHub Actions or GitLab CI can be complex, this chapter will introduce you to the core principles by building a &lt;em&gt;simplified&lt;/em&gt; CI pipeline right on your local machine, powered entirely by Docker. You&amp;rsquo;ll see how Docker&amp;rsquo;s consistent environments are a perfect fit for ensuring your code builds and tests the same way, every time.&lt;/p&gt;</description></item><item><title>Chapter 4: Building Custom Docker Images with Dockerfiles</title><link>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-4-building-custom-docker-images-with-dockerfiles/</link><pubDate>Sun, 23 Nov 2025 22:00:12 +0530</pubDate><guid>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-4-building-custom-docker-images-with-dockerfiles/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the previous chapters, we learned how to run containers from existing Docker images. While readily available images from Docker Hub or private registries are incredibly useful, real-world applications often require specific configurations, custom code, or unique dependencies that aren&amp;rsquo;t met by generic images. This is where building your own custom Docker images becomes essential.&lt;/p&gt;
&lt;p&gt;Custom Docker images allow you to package your application and its entire environment into a portable, reproducible unit. The blueprint for creating these images is a &lt;code&gt;Dockerfile&lt;/code&gt;. A Dockerfile is a simple text file that contains a series of instructions that Docker Engine reads to build an image automatically. By mastering Dockerfiles, you gain precise control over your application&amp;rsquo;s deployment environment, ensuring consistency from development to production.&lt;/p&gt;</description></item></channel></rss>