[wp-hackers] Community conventions for custom post types?

[Beau Lebens]

I haven't heard of something like this around CPTs or Taxonomies, but
I know there is, for example, this one around custom fields for Geo:
http://codex.wordpress.org/Geodata


On Fri, Aug 3, 2012 at 7:45 PM, onlyunusedname <onlyunusedname at gmail.com> wrote:
> I mean, I take Lionel's point that a lot of the premium themes are "doing
> it wrong" which kind of reduces my suggestion to: Let's all do it wrong in
> the same way.
>
> But often (this week in particular) I catch myself wishing for just this
> sort of consensus.
>
>
>
> On Fri, Aug 3, 2012 at 7:27 PM, onlyunusedname <onlyunusedname at gmail.com>wrote:
>
>> I think all I really meant, Ade, was to extend the concept of Post Formats
>> to common  Custom Post Types and Custom Taxonomies that I routinely see
>> others implementing for CMSs.  Maybe it's not really necessary.
>>
>> Once upon a time (pre-3.1) if you wanted to do targeted styling for an
>> "aside-like" post  and I wanted to do targeted styling for an "aside-like"
>> post we would both probably implement that in a very similar but not
>> interoperable way.  Which would probably be relatively easy to resolve.
>>  But now we can just know that we are both just using the aside post format.
>>
>> Today, if I get two restaurant clients with two restaurant "Premium"
>> themes, they very frequently will have two different sets of very, very
>> similar but not interoperable custom post types and/or taxonomies and/or
>> meta.  I just thought it would be nice if I could say that my
>> restaurant-related theme or plugin was "Portable Menu Taxonomy Spec
>> vX.X-compatible" (or what have you) it could add up to a big time save.
>>
>> I mean, if everyone building a restaurant CMS (or art gallery CMS or
>> whatever common CMS implementation) knew where to go for the consensus spec
>> and there were snippets for everyone to register everything in the same
>> manner...  (And if you had a solution that was very uncommon, well this
>> wouldn't pertain to you.)  Or would that just create more hassle than it
>> eliminated?
>>
>> On Fri, Aug 3, 2012 at 6:41 PM, Ade Walker <photofantaisie at gmail.com>wrote:
>>
>>> 2012/8/3 onlyunusedname <onlyunusedname at gmail.com>
>>>
>>> > For example, if developer A implements a custom post type with custom
>>> > taxonomies for menu items on a restaurant CMS, it would be great if
>>> > developer B could take for granted the conventions developer A was
>>> using.
>>> >
>>>
>>> Hi,
>>>
>>> I'm curious too. Can you give an example or two of the kind of conventions
>>> you are thinking of?
>>>
>>> Thanks.
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>>
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers