[theme-reviewers] Theme starter code.

Edward Caissie edward.caissie at gmail.com
Fri Aug 19 12:22:54 UTC 2011

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.

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.
If the client says they want something to look like "x" theme then obviously
start with "x" theme (if possible) and build.

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.

Just some thoughts ...


On Fri, Aug 19, 2011 at 4:35 AM, Tony Crockford <tonyc at boldfish.co.uk>wrote:

> Is there a favourite starting point for theme developers?
> 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?
> e.g. like Justin's Hybrid Core
> before I commit to using it, I wondered if there were any others I should
> look at?
> or do most use their own home-grown starters?
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20110819/4edb66ed/attachment.htm>

More information about the theme-reviewers mailing list