David just put up a great post on Devlounge about making your themes client friendly
. What this encompasses is making sure the theme can be moved around across domains, the title of the blog can be altered and basically avoiding hard coding details which the client may want to later change.
It’s also a great read if you’re producing themes for sale/free release as you need to be extra vigilant in catering for a mass of possible usage scenarios.
Making themes Portable
/future-proof is a topic I’ve been promoting quite a bit lately. Our motto has always been to leave the client with total control, we don’t want to lock you into retainers and other such nasties so empowering you to make small changes like this yourself without a steep learning curve is what we’re all about.
David’s running a series of posts on this topic, today’s just focuses on Wordpresses header.php file. Looking forward to the rest.
lidagazeteler
Vikas Gupta
perde
anada
Victor
I don’t know if it was making it more portable, or just making it into what a theme should be. All of the themes I have ever used are just this “out of the box” function able. I’d rather write about “about this author” tutorials like I do for guest posts.
Comment by
hellyeahdude.com — 11/12/07 @ 5:40 am
— It’s definitely best practice for themes which are being released for public consumption, but I’ve known a lot of people that stick to hard coding elements of a theme that should be dynamic options under Wordpress, such as the name of the blog, it’s URL etc when they’re producing the themes on commission.
Comment by
Chris Garrett — 11/12/07 @ 12:56 pm