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

[onlyunusedname]

Thanks, Otto.  I think maybe I will try to collect some thoughts and see if
they appeal to anyone else.


Thanks also, Lionel.

I was originally given to believe that you should never do with custom
taxonomies what you could just as well do with native taxonomies.  I
believed (and still sort of believe) that your WordPress data degrades more
gracefully if it is all just posts and pages and categories and tags and
post formats.

The problem I was having with this ideal is that while it is intuitive to a
WP developer brain to think of every sort of content as either a post or a
page, it was much less intuitive to my clients.  And I started to worry
that I was sacrificing an elegant CMS user experience on the altar of best
practices.  More and more I catch myself straying the other direction,
making a garbled mess of the WP database towards the end of a beautiful,
easy, CMS user experience for users who simply prefer this to the
intangible benefit of interoperability.

It seems like lots of developers are doing this.  Some very cleverly.  But
no two identically.  I feel like if we could make a collaborative
repository of these sorts of innovations, we could sort of make common
cause between developers who love WordPress for its amazing flexibility and
developers who love WordPress for its interoperability.




On Fri, Aug 3, 2012 at 12:59 PM, Otto <otto at ottodestruct.com> wrote:

> There is no set of conventions that I'm aware of, but a community
> document that details several conventions is a very good idea and
> would allow for interoperability. Why not start one, see if you can
> get somebody else interested.
>
> -Otto
>
>
> On Fri, Aug 3, 2012 at 11:38 AM, onlyunusedname
> <onlyunusedname at gmail.com> wrote:
> > One of the most compelling reasons for me to develop small to midsize
> CMSs
> > on WordPress is that WordPress has really emerged as the lingua franca of
> > this market segment.  When an existing WordPress user comes to me wanting
> > enhancements, upgrades, or redesigns (which happens increasingly) I
> *love*
> > how much I just magically know about their existing codebase without
> having
> > to do a bunch of discovery.
> >
> > I was wondering if, towards this end, there had been any sort of
> community
> > effort to standardize custom post type and/or custom taxonomy
> nomenclature
> > for common CMS implementations?
> >
> > 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.
> > And both developer A and developer B could make interchangeable
> restaurant
> > themes that worked perfectly right out of the box on each other's
> > restaurant sites.
> >
> > Does there already exist somewhere a sort of community consensus around
> the
> > implementation of common custom post types that would encourage ease of
> > interoperability?  If so, I'd like to be following it.  If not, does it
> > seem like a potentially useful thing to others?
> >
> > Just curious.
> > _______________________________________________
> > 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
>