mrjonwhite

• A significant simplification (e.g., with some built-in, ready-to-go GUI/front-end elements) of the functions.php protocol for creating, and CPT-associating, Custom Fields meta boxes, of various types. Right now it’s so easy, and so lean, to hand-register Custom Post Types and Custom Taxonomies. The third piece of that WordPress-as-CMS trinity — meta keys/values — are still too prohibitively verbose & cumbersome to write, practically, without the help of a Plugin (like Verve or MagicFields). At the end of the day, no one’s using CPTs without also the need to throw at least one (or twenty) custom fields at it, too. Custom Taxes can only cover so much.
• An oldie but a goodie: The out-of-the-box ability to assign arbitrary one-to-many Post (of any Post Type) relationships. The table infrastructure is so close, and the stopgap Plugins that fake it now are so thin. It’s the one missing piece that makes WP-to-clients evangelism so….tricky.
• Not a request, but a comment: You guys are the best. Thank you for keeping this rolling so intentionally.

I’d like to “third” this suggestion. Just to give the problem some validity, this would solve the (seemingly perpetual) problem of “one-off” components in site design: Homepage billboards, rotating elements, and the like. Semantically, these really should be WP Pages, not WP Custom Post Types, since they don’t “clone” or “grow.” There’s only one of each, and the ultimate goal is to tack custom meta properties to each one of these, individually.

The plugin “Simple Fields” can pull this off, but, having tried both, I’m still more attracted to Verve Meta Boxes. Not only does VMB innately support (and retain) crisp, short, meaningful WP Meta Keys, but (more importantly) it supports meta types that SF doesn’t, like Date, that are pretty critical.

So, as soon as this is possible — hooking a unique Verve Box to a single WP Page — then it’ll be a sealed, done deal.