For the none of you that frequent this blog, I’m sure you’ve noticed the change to the design.  For some reason, Wordpress themes felt so foreign to me.  But I wasn’t feeling the one I had before.  So I decided to take a crack at building a theme that incorporated the look of qrisper.  Wasn’t too bad…just had to navigate through all of the Wordpress PHP.      Actually learned a couple of things about managing browser discrepancies by looking at how theme developers dealt with them.

Which brings me to IE7.  At some point, qrisper got totally broken on IE7.  Ended up using the * hack in my CSS files, which now won’t validate.  To that I say fuggem.  Rules are meant to be broken.

The development theme for the past week was spring cleaning.  I consolidated a number of pages, modularized my CSS (as much as I could), cleaned up and moved all my js files to the footer and tidied up all of my control/view files after the redesign.  qrisper just feels lighter to me now, although there wasn’t any noticeable improvement in performance.

A couple of new/updated pages:

• created a personalized 404 page…heard it’s a good thing to have
• redid the splash page screenshots after the layout redesign…but need to redo them yet again
• added Disqus comments to all answer pages.  I had comments in the pre-alpha version of qrisper but took them out because of poor site.  Still kinda slow but the ability to sign in via Facebook Connect was irresistable.  Too bad that ain’t working…can’t figure out what I’m doing wrong
• Tweaked my existing autocomplete functionality…basically made it look nicer.  Only thing missing now is to add keyboard navigation functionality.

Next up on my list is security and validation.  I’m already using sanitize classes to filter out all user input but I want to add additional layers of security.  Also want to incorporate jquery into the validation process so that users have a clear sense of what’s going on.