In my case a lot depends on the what the customer wants or needs more than anything else ... or my mood for my own works.<br><br>If I am developing a theme for a client then their budget may constrain the development time, so if necessary I find a GPL-compatible (looking at my own first) theme and build off of one of those.<br>
If the client says they want something to look like "x" theme then obviously start with "x" theme (if possible) and build.<br><br>If I am making a "new" theme, I prefer to work from a very basic (read: blank screen) template structure and build up from there. No reason to have a lot of extra functionality that may never be incorporated into the theme included in the code. The idea is to keep it simple and easily transferable, making sure to document well so another developer can carry forward if the need arises.<br>
<br>Just some thoughts ...<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Fri, Aug 19, 2011 at 4:35 AM, Tony Crockford <span dir="ltr"><<a href="mailto:tonyc@boldfish.co.uk">tonyc@boldfish.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Is there a favourite starting point for theme developers?<br>
<br>
I don't mean making child themes from a theme framework as such, more something like a theme library that you start with and develop from?<br>
<br>
e.g. like Justin's Hybrid Core<br>
<br>
before I commit to using it, I wondered if there were any others I should look at?<br>
<br>
or do most use their own home-grown starters?<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote></div><br>