Update On CMS Switch

I’m still chugging away at finishing up my custom custom content management system. Here’s a quick summary of what will happen to Nusuni Dot Com when I start the transfer:

  • The site may go down for a few hours - possibly a day - during the switch. I am working on my local server to help minimize any problems, but as any developer knows it is possible for a script to work perfectly on server A and completely crap out on server B. I will keep WordPress installed for a few days after the switch just in case something goes wrong.
  • The interface of the site, on your end at least, shouldn’t change at all. Certain things like comment subscription via e-mail may not be available for a few days/weeks after the switch ( I need to remember to add it in!).
  • Until I do a complete optimization of the CMS, it may not run as fast as WordPress. Hopefully in the following weeks/months I can go through and speed up critical parts of it.
  • Graphical smilies will no longer work. I’m still trying to figure out how I want to go about adding in smilies… if you know of a service that has free smilies please let me know!

The switch will hopefully be happening within a month. Remember, I’m writing the darn thing from scratch - be patient.

If you are wondering, I am dumping WordPress for a few reasons: speed, security, and expandability (is that even a word?). WordPress is very limited in what it can and cannot do - so I decided to write a custom content management system to fit my needs. It will let me do a whole lot more with this site than I could do before without installing 700 different plugins.

Please subscribe, or else I will cry. Do you really want to make a programmer cry?

4 Comments

  1. XIII Says:

    Quite a tall order. Good luck with everything, I hope the transition goes smoothly.

  2. Jeremy Steele Says:

    Thanks, so far it’s coming along pretty nicely. Some things go quickly, but other things take a while.

    For instance, the admin toolbar that appears at the top of every page took 2 days to build - but it has a nice fade in-out effect for the menus and even works perfectly on every browser I threw at it including IE 5.5.

    Still debating whether or not to release it as open source. On the one hand it can provide great feature and security benefits, but on the other hand it could very easily turn into a bloaty mess with mismatched coding styles and would take up more my time to manage it. Hmm…

  3. XIII Says:

    Or you could release it and wait and see if someone else will work on it? Or start a community around it?
    Either way, I’ve got to hand it to you, to build something like that from scratch to match and top WP’s feature set must have taken a mad amount of coding hours. Respect.

  4. Jeremy Steele Says:

    What I’ll probably do is install it on this site for now, try to make the features get somewhat closer to WP, optimize it a bit, then release it sometime in late spring or early summer.

    One of the main reasons it has taken so long is I’ve completely redone the base architecture so many times, especially with modules. Probably once it is up and running on here that’ll help relieve a bit of stress and let me really get down in the code and design a more efficient core for it.

    There’s still quite a few things like pingbacks/trackbacks and RSD (for writing via client blogging software like Echo) that I have hardly any clue how to do, so it’ll be interesting to see if I can write up secure implementations in a short period of time.

Leave a Reply

Note: By submitting your comment you agree to this blog's comment policy.

If you want a little icon next to your name - sign up for one at Gravatar.