Thomas Kräftner

It already is on the list of ideas: https://github.com/justintadlock/content-type-standards/issues/13 So what we need now is a concrete proposal.

Okay as I'll probably need this soon let's kick this off with a first draft. I have not used CPT prefixes here as discussed in #29. # Post Types -...

I am not sure if I got your idea. So you say we shouldn't duplicate properties by creating a media response object but let the media response just be a...

@benhuson Underscore of course. Was a typo -> fixed

Concerning the "many" issue - I haven't thought about that to be honest as I am coming more from the direction of staff and less of a generic person. And...

Sounds like a nice idea. Two more ideas that come to my mind when reading this: - Have these migrations as [WP-CLI](http://wp-cli.org/) commands - Some further help with migration if...

This is relevant for this issue: https://github.com/justintadlock/content-type-standards/issues/5

I'd like to strongly oppose the idea of just dumping the instructions as one huge blob of text in the `post_content`. This is _the_ chance to enforce some more structure...

@GaryJones Well that could work...but it is very fragile and only caters to the very basic use case of splitting steps, but not really to anything further like adding metadata...

@justintadlock I see your point about the 80%. I'm just proposing to at least define a standard for how to store instructions in a way that makes it easy and...