Subtitle: Or why I seem to spend more time messing with my own site than any of my RW themes....
Since I hit the web in 2005, the site has been forever changing. The site changes look fairly frequently (something that is stupid, given that until fairly recently there was never a sizeable update of content occurring frequently). And as ever, there is something brewing for the new year (check it out
here). But that's not the point. People don't really care about a re-design. Until it's done. So instead of talking about the new design, I'm going to go off on an alternative path. A path on designing for RapidWeaver along with why I use RapidWeaver (I get all manner of emails about that). Enjoy!
Websites1. Stating the obvious - I am a web snob. I look at a site, and will dismiss it very happily if it contains: Firefox-based browsers not displaying CSS (WTF?!), Use of Java, Windows Media Player content, music that plays when you visit the site, popup adds and more. Some of those things are common things that everyone gets pissed off about. But some things, like CSS not showing in Gecko browsers, are just
guaranteed to make me disregard a site, no matter how great it may be in (sigh) Internet Explorer or Safari.
Browser ChoiceFollowing on from my previous point, I'm going to talk about browsers. Safari is the default browser on Mac OS X. It's a great browser, really it is - it's damn fast, and seems less cluttered than others. I also love the Apple + 1, +2 for easy bookmark bar navigation (I'm very much a keyboard shortcut person).
But, and this is pretty much the only thing that stops me using Safari full time, GMail does not have all the full functions when in Safari. No web-chat (GTalk/Jabber from within the browser - something that has been really handy at certain points). But other than that, I love Safari - especially as in GMail (something I use for literally every message I send, regardless of the address) I can use the Apple + Left Arrow command to
actually get to the start of the line when replying to messages. Camino doesn't do too well with that sadly.
Camino is currently my browser of choice. Firefox power, Mac style. Enough said.
So why am I making a big point over the fact that CSS not showing in Gecko browsers by talking about browsers? Well, a year or so back, it wasn't acceptable to say 'Just use Firefox if you want transparent PNGs to appear properly', in this day and age (with Firefox's market share growing) it's not acceptable to say 'Just use anything other than a Gecko browser'. People respect sites that just *work* on their chosen browser (and that's why my own site is being changed so that it works in everything!). Period.
Why I Use RapidWeaver1. I like software that exports to a FTP server (not a server-side app) as it allows easier media integration. It also means that moving my site is pretty much simply a case of re-publishing to a new location. OK, things like the Base URL need to change, but that's a 2 second job.
2. RapidWeaver is just so simple yet powerful. Plus, the 3rd party plugins rock.
3. It's developed by an English company. Go RealMac!
4. It allows me to do as little or as much code as I care to. Sometimes I love writing my own code. Sometimes, I choose to leave things such as RSS generation to RapidWeaver (its sorts out the content and permalinks etc).
Designing for RapidWeaverOnce you know how RW's theme workflow goes (css classes, plist bits and pieces), it's really easy to get going with your own themes. Compared with Sandvox, or iWeb *sigh*, it's simply far easier to work with. Sandvox requires lots of HTML files, whereas I find RW's theme structure to be far more compact.
Truth be told, RapidWeaver users are very very diverse, and have a huge amount of creative genius. That means, they're always pushing the limits of what they do with themes. That makes a theme developers job really complex - especially with some of the awesome (previously mentioned) 3rd party plugins available. When I design my own site, I only ever code the stuff I know I'm going to need (blog and styled text) as that encompasses all the page content I'll ever have (apart from the Frappr map) - even the Rapidflickr stuff is taken care of. I never use movie galleries, and photoalbums are already done, so I leave most of the theme empty (come to think about it, it would be easier for me to remove the extraneous portions of code to reduce the CSS files download time, but that's something I'm hesitant to do).
Why do I mention 'my site vs everyone elses'? In short, I've been converting all the had-coded pieces of the current theme I'm using into a sellable RW theme. People have asked for it, but I use so much handcoding at the moment that it wasn't working with all of RWs functions - only those that I use on a day in, day out basis. The logo at the top? Handcoded. The box at the bottom, that too. What about other things, such as lightbox? That too is handcoded. It's not done through an addition to the plist, it was hardcoded into the index.html template. As I tinkered about with the current theme, I simply piled on mode code wherever I wanted it, failing to realise that if I'd done it through RapidWeaver, it wouldn't be biting me in the ass now. So where am I at this point in time? Well, I'm putting all my energies into music right now (this blog post has taken about a week to write) so don't expect it before new year. I'm in need of a break, and a new laptop. I can't code on an iBook that has keys falling off and the Apple and S buttons worn off!