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

Edward Caissie edward.caissie at gmail.com
Wed May 25 00:45:56 UTC 2011

Along Justin's idea ...

I would consider something akin to:

   - Design and submit an appropriately made theme that meets all of the
   current WPTRT guidelines
   - Develop and submit a plugin that handles all of the functionality

... and for the coup de grace: The correctly designed theme properly meeting
all of the requirements for acceptance into the Extend repository
"transforms" into your current "application" once your specific plugin is
installed and activated.

It would simply require appropriate conditionals be added to the Theme
checking for the existence of your plugin that will be doing all of the
heavy lifting. This is already a method some current themes do for other
more common plugins but I see no reason you could not use the extensibility
of WordPress and your design / development creativity to create a "theme as
application" model to then carry forward with ultimately leading to the
potential for many different designs (read: themes) to manage the
functionality of the "custom" plugin but still behave and conform to current
WPTRT guidelines.

Just some thoughts ...


PS: Just so you know, I would expect this to be the best documented Theme
ever to cross the paths of the WPTRT reviewers, too. EAC

On Wed, May 25, 2011 at 8:26 PM, Justin Tadlock <justin at justintadlock.com>wrote:

> Somewhat on topic:  I am currently developing a bug tracking plugin that
> can be used with any theme.  The great thing is that you can have users
> install this plugin and only have to worry about styles and templates.
>  Plus, you won't be tied down to a single theme.  You can make multiple
> themes that all support this plugin with minimal effort.
> If you want to bounce any ideas around or throw your code into the mix,
> shoot me an email.
> On 5/24/2011 7:02 PM, Otto wrote:
>> On Tue, May 24, 2011 at 5:24 PM, Ryan Frankel<ryan.frankel at gmail.com>
>>  wrote:
>>> I agree.  We had an internal debate on which way to go with this and it
>>> was decided that since we were including styling it would be a theme.  What
>>> we saw with a lot of plugins is that while they give you the functionality
>>> you still have to do all the styling yourself (see any calendar plugin).  We
>>> wanted to create something that required absolutely no end-user interaction
>>> or coding so the theme was born.
>>> It is even more of a grey area then I realized though.
>> I would consider separating theme from functionality here. Sure, a
>> theme can do anything a plugin can, but limiting themes to a stylistic
>> model, where only functionality that affects the display of things is
>> included, makes the most sense. While I get that's it's hard to
>> separate the two in this case, perhaps making a sort of generic
>> "ticket" plugin and generalizing the concept might be useful.
>> No reason you can't make both a theme and a plugin which work
>> together. This also gives you the side benefit of being able to create
>> many different themes for the same basic ticket system.
>> -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/f6535196/attachment.htm>

More information about the theme-reviewers mailing list