Can WordPress replace server-side frameworks (like Django and Ruby on Rails)?

WordPress can handle a lot of the processes on it’s own and has a strong foundation. So what’s the benefit of using these frameworks? Sites like Pinterest are built on the Python framework Django, but you can technically achieve the same results with WordPress templates using Javascript and CSS3. So again, lets discuss the differences and benefits of using a server-side framework in that particular case?


Essentially, you can achieve the same functionality with frontend code like Javascript and CSS3. But, while you gain convenience with that method you lose the speed and ability to scale. In general it’s harder to maintain on the frontend.

While WordPress is flexible it runs a lot slower on a larger scale. Because of it’s foundation you get a pretty flexible runtime modification of behavior, which can open up a can of worms on your system. Simply put, it can start all sorts of extraneous processes that clutter your server and the browser.

Once you open the door to changing WordPress to do more than it’s intended (as a CMS) you start running against the way the code was originally designed to run. Working outside of those bounds can add tons and tons of extra code what would not normally be needed.

That being said, some frontend changes work great when they are designed using the WordPress framework. I’d say try it and see how it goes. Some times, if it’s simple enough, it can work perfectly and there’s not much need to scale, for instance. However, if you need this frontend build that scales while maintaining WordPress’s efficiency, you will probably run into road blocks, which you could avoid using serverside frameworks.

Share →

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>