<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Content Management on The Coders Blog</title><link>https://thecodersblog.com/tag/content-management/</link><description>Recent content in Content Management on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:07:48 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/content-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Websites With Many Little HTML Pages: A Practical Approach</title><link>https://thecodersblog.com/building-websites-with-many-small-html-pages-2026/</link><pubDate>Wed, 06 May 2026 22:07:48 +0000</pubDate><guid>https://thecodersblog.com/building-websites-with-many-small-html-pages-2026/</guid><description>&lt;p&gt;Tired of the JavaScript-heavy complexity that plagues modern web development, turning simple content sites into performance nightmares? It&amp;rsquo;s time we revisited a fundamental truth: the web was built on HTML pages.&lt;/p&gt;
&lt;h2 id="the-core-problem-over-reliance-on-javascript-for-basic-interactions"&gt;The Core Problem: Over-Reliance on JavaScript for Basic Interactions&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;ve become so accustomed to Single-Page Applications (SPAs) and their intricate client-side routing that we often overlook a simpler, more robust approach. For many content-driven websites – blogs, documentation sites, e-commerce catalogs – the need for full-blown JavaScript frameworks to manage navigation, accordions, or even modal pop-ups is overkill. This over-reliance leads to:&lt;/p&gt;</description></item></channel></rss>