REVOLUTIONS STARTED • UPRISINGS QUELLED • GOVERNMENTS RUN • TIGERS TAMED

The problems with Jquery & WordPress as a CMS

I’m a big fan of increasing productivity by having computers do work for me. With the release of the website for InBloom version 2.0, I decided to use WordPress as a CMS (content management system) so I wouldn’t have to fire up Dreamworks to make a correction or an update.

So far, it’s been working quite nicely aside from some minor Remix theme gripes, but as I grow the base of users and set the objects in place for even greater growth I’m using pre-built components more and more. I’m also seeing that a number of components are slightly overlapping in functionality. Thus, code for my Support request form, for a tabbed download page, and for the email newsletter submission form are all downloading a separate version of Jquery for each homepage request. Theme and plugin authors need to do more to make sure that they link to Jquery through the WordPress core or from Google code. Frankly, it’s irresponsible if they do otherwise.

Posted in: Blogging, General, Programming, Wordpress ♦ Tuesday, September 8th, 2009, 10:01 pm ♦ 2 Comments

2 Responses to “The problems with Jquery & WordPress as a CMS”

  1. Posted by: Adam Dempsey
    September 9th, 2009 at 2:21 am

    It’s actually easier for the Plugin authors to use the build in WordPress version rather than include their own, you just need to do like:

    wp_enqueue_script(“jquery”);

  2. Posted by: Da Management
    September 9th, 2009 at 8:15 am

    I agree and I’ve used that wonderful line many times – I wasn’t expecting to do it on behalf of plugin authors though!

    Btw, any luck with finding a Moo Plug developer for Mac?

About SWL

Welcome to SWL's blogging playground where I keep tabs on all manner of design, blogging software, FileMaker news, Apple lore and just about anything else. Design, Code, Business, FileMaker, Simplicity, and more.