[theme-reviewers] Theme Vs Plugin Territory

[Greg Priday]

This guideline isn't limiting at all. If some functionality is in the
plugin domain, that just means you need to move it out of your theme
into a plugin. You can fully support your plugin in your theme...
just make sure you gracefully degrade if it isn't installed.

This is a great starting point to handling plugin dependancies -
http://ottopress.com/2012/themeplugin-dependencies/

On Sat, Mar 2, 2013 at 2:51 AM, Stephen Cui <scui2005 at gmail.com> wrote:
> The reason I ask is because Plugin has its limitation to display "user
> content".  Because of the limitation, I think it should be flexible on
> certain gray area. Anyway, I am stick with post meta until policy changes.
>
> Stephen
>
>
> On Fri, Mar 1, 2013 at 6:26 PM, Chip Bennett <chip at chipbennett.net> wrote:
>>
>> Custom Taxonomy would fall under the same criterion, as "creation or
>> definition of user content".
>>
>>
>> On Fri, Mar 1, 2013 at 6:35 PM, Stephen Cui <scui2005 at gmail.com> wrote:
>>>
>>> Is Custom Taxonomy allowed in theme?
>>>
>>> Regards
>>>
>>> Stephen Cui
>>>
>>>
>>> On Fri, Mar 1, 2013 at 4:40 PM, Josh Pollock <jpollock412 at gmail.com>
>>> wrote:
>>>>
>>>> Chip-
>>>>
>>>> I feel like this requirement limits the ability of themes to enable
>>>> WordPress to work as a CMS for specific purposes. For instance I am working
>>>> on a custom theme for a book review site that uses a CPT called books for
>>>> reviews, and the regular posts for blog/news posts. I know I could have used
>>>> custom post meta, but having two totally separate options (post and books)
>>>> in the menus made the system super-easy for the not incredibly tech-savvy
>>>> content editor on this project.
>>>>
>>>> I think a generic version of this theme or something similar could be
>>>> very helpful to people wanting to do a book review site. You could make a
>>>> similar case for recipe blogs or other similar situations. These types of
>>>> themes exist all over the place, but are pretty much excluded from the theme
>>>> repository due to the user lockin. It seems to me that with some simple
>>>> standards that these types of themes could be included in the repository
>>>> without creating user lockin. Why not provide a way for users to have these
>>>> types of very specific CMS themes with the high code standards and
>>>> guaranteed GPL2 license that the theme repository provides?
>>>>
>>>> Thanks,
>>>> Josh
>>>>
>>>>
>>>> On Fri, Mar 1, 2013 at 1:59 PM, Chip Bennett <chip at chipbennett.net>
>>>> wrote:
>>>>>
>>>>> Custom Post Types are, by definition and design, intended for
>>>>> "generation or definition of user content", and as such are explicitly
>>>>> Plugin territory, as per the Guidelines.
>>>>>
>>>>> If a user creates content using a Theme-registered CPT, then when that
>>>>> user switches Themes, that content disappears. (It's there in the database,
>>>>> but no longer exposed to the user, either in the WordPress admin, or in the
>>>>> site front end; to them, that content is simply gone.) Thus, CPTs represent
>>>>> a form of Theme "lock-in" and are not allowed.
>>>>>
>>>>> Special-case Themes that use CPTs can be considered on a case-by-case
>>>>> basis.
>>>>>
>>>>>
>>>>> On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <sun_ravi90 at yahoo.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I am a bit of confused on theme vs plugin territory. Recently my theme
>>>>>> was rejected because of the use of CPT in my theme the reason was that it's
>>>>>> plugin territory. I know that CPT is better suited to plugin but I didn't
>>>>>> know that it was a required case. I have seen themes on WordPress repository
>>>>>> that have registered multiple CPT and being approved. I am not saying that
>>>>>> some X theme was approved, why not Y theme is approved for same case. My
>>>>>> question is,It is strictly prohibited to use CPT inside theme. Is it a
>>>>>> required case or is it a recommended case. If using CPT is completely
>>>>>> prohibited then I think writing it down on Theme review guidelines will
>>>>>> clear out the confusion. Though Prensentation Vs Functionality might cover
>>>>>> this but those words are some what vague.
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>
>>
>> _______________________________________________
>> 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
>



--
I make free WordPress themes
http://siteorigin.com
http://facebook.com/SiteOrigin
http://twitter.com/SiteOrigin