When you develop for WordPress, you start to pick up on things most blog owners don’t. That little nag in your theme, that plugin that is missing the one thing you were looking for in the first place. So on and so forth. So, you begin to look into the code. You see the change is relatively small, so you make it. But you know in the back of your head you shouldn’t have, because you know once your little plugin or theme gets updated, U R Screwed. So, you either redesign the goddamn wheel and make your own when there are plenty of good ones out there already or you make a baby, or child for that matter.
I severely hacked up my last theme, 1 to make it my own, but with the release of 3.0, I knew it would only be a matter of time before they released an update. StudioPress made it, so I knew they kept up their stuff.
So with a fresh start came a fresh theme and chance to do it right this time. I had already found crap I didn’t like in twenty ten, 2 so I started my usual opening of the editor and my hacking away and I was like, STOP child! Or more appropriately STOP, child! As in use a child theme. That way you aren’t pinned into the usual trap. So I did. Now I have my very own child theme based upon Twenty Ten. It is a pretty good theme after all, besides the little quirk here and there. 3
So I made my changes and I was good to go. But what is a theme without the screenshot inside? So I added mine, and now I am done.
Until next time.
I have to say I brought back the true meaning of lol when I read this post. I like how you put at twist of a child theme. I didn’t know where you were going with it at first. Nice tip though. I’m going to make a post about child themes on my blog next… don’t worry I’ll link to you for props.