<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Muhammad Saim Faisal on Medium]]></title>
        <description><![CDATA[Stories by Muhammad Saim Faisal on Medium]]></description>
        <link>https://medium.com/@saimdeveloper25?source=rss-ae1a6509ef5d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*P7WKssj_TK-jl9Rr55zP8w.png</url>
            <title>Stories by Muhammad Saim Faisal on Medium</title>
            <link>https://medium.com/@saimdeveloper25?source=rss-ae1a6509ef5d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:08:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saimdeveloper25/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Reason Why CMS Builders Are a Nightmare (Also a Headache)]]></title>
            <link>https://medium.com/@saimdeveloper25/the-reason-why-cms-builders-are-a-nightmare-also-a-headache-c3bc8f9a9ca5?source=rss-ae1a6509ef5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3bc8f9a9ca5</guid>
            <category><![CDATA[website-development]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Muhammad Saim Faisal]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 16:50:02 GMT</pubDate>
            <atom:updated>2025-09-01T16:50:02.958Z</atom:updated>
            <content:encoded><![CDATA[<p><em>(Note: I’ve been through the fire so here’s what I learned)</em></p><figure><img alt="header image" src="https://cdn-images-1.medium.com/max/1024/1*ZXQ2sxdIlbI9BEu2jg8gyQ.png" /></figure><p>For a long period of time, I have been working on <a href="https://wordpress.com/">WordPress </a>(a CMS for building websites). When I started it was all fun, learning new ways and building complex structures. It was all good so far. But one morning…. I asked myself:</p><blockquote>Why not build a website on WordPress and sell it online?</blockquote><p>It sounds pretty good. Right? Then listen,</p><blockquote>It was a horrible idea.</blockquote><h3>Step 1: How It All Started</h3><p>I was very hyped. Choosing typography, colors, designing, developing all good stuff. But, that was just the start of a huge <em>pain.</em> While designing, the structure I built was pathetic. Sure, it looked great, but building it was a nightmare. For a single animated section, I had to install a bloated, trash loaded plugin just to make it work.</p><p>Well, after the design was completed, it was finally time to actually develop my first site on WordPress. I installed Elementor (Yeah I installed another page builder inside WordPress to develop the site). Working on it was quite simple, you drag the object, place it, change it and you are good to go. But, my design was already bloated to the extent that I installed another plugin just to enhance the overall functionality of my page builder.</p><blockquote>In total I installed over 20 plugins.</blockquote><h3>Step 2: Jumping off the cliff</h3><p>I thought building a template site would not take long. Max a week or 10 days.</p><blockquote>It took a whole worthless month.</blockquote><p>After waking up night after night and working on it, I finally reached the end. I literally built a single page template website for the first time. But unfortunately, it was only me who thought that it was the end. Actually, I was only half way through. I forgot responsiveness settings. Also forgot to check the site speed.</p><h3>Step 3: The Crash</h3><p>At that moment, I knew that I completely messed up. Responsiveness settings again took a hell of a lot of time. At least I was hoping a good site score. Guess what?</p><blockquote>I got a worthless score below 50 on Google.</blockquote><p>At this point, I knew that no one is going to buy this garbage on which I spent painful sleepless 30 days.</p><p>As if that wasn’t enough, the free hosting I was working on expired just three days after finishing the website and with it, I lost even the memory of my pain.</p><h3>Is CMS Really That Bad?</h3><p>Actually, no. CMS is not that bad if you know at least the basics of coding like:</p><p><strong><em>HTML</em></strong><br><strong><em>CSS</em></strong></p><p>Which I was unaware of at the time. I only knew a bit of HTML, but with just that, it’s like a closed door without a key.</p><p>So, if you know the basics of coding you can actually build complex structures without bloating your website with plugins. Here’s an example:</p><blockquote>My updated <a href="http://ecommerce.wprojectcreations.com/">Portfolio</a>, built on WordPress again, but this time much more optimized.</blockquote><h3>Conclusion</h3><p>I went through CMS hell so you don’t have to. That bloated trash website broke me but also taught me a lot. So, here’s my advice to everyone who’s reading this.</p><p>CMS is a nightmare if you walk blindly and a weapon for those who use it wisely.</p><p>A big thanks to everyone who made it this far.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3bc8f9a9ca5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>