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

[Lionel POINTET]

I agree with you and think it's a good idea to have some kind of
conventions with these types of CMS, and that makes me think of BuddyPress,
which is exactly what you say: an standard implementation of a community
management and social networking CMS.
It's extendable so that there are many BuddyPress plugins (so plugins of a
plugin) and many "BuddyPress ready" themes too!
You might achieve your goal in doing the same thing: developing one
reference plugin which gives the convention. The other way is taking an
already existing and widely adopted plugin as the base of the your
convention.
I'm aware it's not that simple (BuddyPress is supported by Automattic) and
you could achieve it in just writing standards :).

2012/8/4 onlyunusedname <onlyunusedname at gmail.com>

> Exactly.  I think it could be a really powerful convenience if plugins knew
> to expect certain common metadata to be stored in a certain fashion.  Kind
> of analogous-ish  to the way the larger web uses microformats.
>
> And it would seem to me that if you made the spec for each common CMS item
> maximally complicated and taxonomy overloaded, then the extra data would be
> there for developers who wanted it and could be gracefully ignored by
> developers who didn't.  Similar to Post Formats.
>
> And its worth noting, that while post formats were a nice benefit for
> developers, think of what a much, much bigger benefit they were to
> non-developers.  Then think of the benefit to non-developers who could know
> that if their restaurant plugin or theme was "WordPress Community
> Restaurant Standard"-compatible that they could use any other theme or
> plugin that also was and it would just work.  And their legacy data would
> always persist.
>
> And there is the benefit of having the community standardize these sorts of
> implementations for the sake of novice developers.
>
>
>
>
> On Sat, Aug 4, 2012 at 10:24 AM, Otto <otto at ottodestruct.com> wrote:
>
> > On Sat, Aug 4, 2012 at 6:17 AM,  <photofantaisie at gmail.com> wrote:
> > > However, what are we really talking about here? Off the top of my head,
> > the
> > > main areas where one would like to see consistency are in naming
> > > conventions, eg post_type 'restaurant', rather than 'restaurants', for
> > > example, so that template naming is predictable, and rewrite rules. So,
> > one
> > > convention could be that, like 'post' and 'page', the CPT registered
> name
> > > must be singular. But once you get beyond this, I'm not sure much can
> be
> > > standardised. For example, I would not support a convention that says
> > that
> > > 'restaurant' must be non-hierarchical. In my use case, I may need
> > > 'restaurant' to be hierarchical. (Note: I hope I'm not misunderstanding
> > the
> > > kind of conventions that people are thinking about.)
> >
> > Think about metadata and the formats therein. A restaurant may have
> > odd opening and closing hours, and storing that data in a sane format
> > that was the same across plugins/themes might be useful.
> >
> > -Otto
> > _______________________________________________
> > 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
>