[theme-reviewers] A Question About Theme Review/Submission

[Shawn Grundy]

You might try creating it as a basic theme that supports all required core functionality, then extend the theme via a custom plugin that adds the custom post types and other custom features. Though niche themes are wonderful in terms of specific applications, the problems arise when customers (users) need or want to switch themes. It becomes difficult, (or perhaps impossible for the average end-user) to switch if the theme controls the content "too much".
For example, if your theme relies on custom post types for it's content, and somewhere down the line you stop development on the theme, the user is then forced to either (1) Use an older version of WordPress if certain functionality within the theme is no longer supported by the core, (2) Try and locate a theme that will display the content correctly (not likely), or (3) try to code the changes into a new theme/plugin themselves which, is the exact opposite of what the repository is intended for.
This is not to say that there's not a place for such themes, however, that place is not currently within the general repository. Again, if you are determined to release the theme with support for the extended functionality, my suggestion would be to implement the core requirements into the theme and have that pass as a general theme, and then create a custom plugin which will control the extended functionality. 
Best of luck!
- Shawn

> From: ryan.frankel at gmail.com
> Date: Tue, 24 May 2011 17:17:08 -0400
> To: theme-reviewers at lists.wordpress.org
> Subject: Re: [theme-reviewers] A Question About Theme Review/Submission
> 
> Otto,
>   Does this also mean if I make it pass all of the tests it would still be rejected by the Theme Review team?
> 
> -Ryan
> 
> On May 24, 2011, at 5:06 PM, Otto wrote:
> 
> > On Tue, May 24, 2011 at 2:35 PM, Ryan Frankel <ryan.frankel at gmail.com> wrote:
> >>  I am trying to submit a ticket task/management theme to the WordPress repo
> > 
> > Custom purpose-built themes cannot be submitted to the repository at
> > this time. Themes must currently support a standard blogging platform
> > or CMS type of system.
> > 
> > Heck, right now we're not even allowing child themes due to a lack of
> > core support for them (will very likely be in WP 3.3). Before allowing
> > this sort of thing into the repository, it would have to be discussed
> > and considered by the core dev team. It might be worth bringing it up
> > when the 3.3 features discussion takes place around early-mid July
> > (after 3.2 is released).
> > 
> > -Otto
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> 
> _______________________________________________
> 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/20110524/74660f5f/attachment-0001.htm>