[theme-reviewers] Theme Development Checklist: Theme Standard?

Joseph Scott joseph at automattic.com
Fri Jun 25 23:07:22 UTC 2010

I tend to agree with Edward's comments on this.  Providing good
examples of how to do things is definitely worth while, but balanced
with the realization that we want people to have some creative
freedoms.  We still get people who make minor alterations to existing
themes and then try to upload them as their own.

On Fri, Jun 25, 2010 at 1:17 PM,  <chip at chipbennett.net> wrote:
> Would it be useful/helpful/feasible to develop a "Theme Standard" (perhaps
> similar to the "Readme Standard" that exists for plugin developers)? I
> could see the following:
> 1) index.php
> A simple "index.php" that incorporates all of the code/structure
> requirements from the TDC. (Perhaps other files could be split out - such
> as header.php or loop.php - but it might be easiest just to have all code
> in a single PHP file.)
> This file could then incorporate all of the required hooks, functions,
> template tags, etc.
> 2) functions.php
> A sample "functions.php" file that incorporates the necessary functions,
> such as widget and menu support.
> 3) style.css
> A style.css that demonstrates the proper header information, as well as
> all of the base element/ID/class declarations that need to be styled.

Joseph Scott
joseph at josephscott.org

More information about the theme-reviewers mailing list