<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Learning Platform on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/learning-platform/</link><description>Recent content in Learning Platform 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/learning-platform/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 20: Real-World Example: Crafting a Learning Platform with Chapters</title><link>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-20-learning-platform-example/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-20-learning-platform-example/</guid><description>&lt;h2 id="chapter-20-real-world-example-crafting-a-learning-platform-with-chapters"&gt;Chapter 20: Real-World Example: Crafting a Learning Platform with Chapters&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 20! In this chapter, we&amp;rsquo;ll apply the robust static site generator (SSG) we&amp;rsquo;ve been building to a practical, real-world scenario: creating a structured learning platform with courses, modules, and individual chapters. This example will highlight our SSG&amp;rsquo;s capabilities in handling hierarchical content, dynamic navigation generation, and flexible templating, demonstrating how it can power complex content architectures.&lt;/p&gt;
&lt;p&gt;The core challenge of a learning platform is organizing content into a logical, navigable structure. We&amp;rsquo;ll leverage our existing content processing pipeline, frontmatter parsing, and Tera templating to define courses, modules, and chapters, automatically generating sequential navigation (previous/next lessons) and a course-specific sidebar table of contents. This chapter will solidify your understanding of how to model and render complex content relationships within a static site context.&lt;/p&gt;</description></item></channel></rss>