[wp-hackers] post format types

Otto otto at ottodestruct.com
Thu Jan 6 20:06:07 UTC 2011

On Thu, Jan 6, 2011 at 1:56 PM, Brian Layman <wp-hackers at thecodecave.com> wrote:
> You've got an incorrect assumption here:
> You are thinking of this only from the perspective of general use themes.

General use themes is the only place it matters. A custom theme
designed for a custom site and a custom client can just use a custom
taxonomy quite easily.

You talk about "hacking it into sites", but using a custom taxonomy is
not a "hack" as I see it. Nor is creating a custom meta box to put on
the edit posts page. These are features that are and have been
available to developers for a long time.

Postmeta (aka Custom Fields) is another way to do it, although I think
a custom meta box with a radio selector in it is a better UI. The
Custom Fields UI is a catch-all for custom postmeta, but there's
nothing preventing a developer from just doing an add_meta_box and
adding whatever better UI they prefer.

> The clients that pay me to develop a theme from scratch or to convert an
> existing site don't care that their theme isn't going to work with a
> competitor's site. Nor do they care that 2010 will remove that behavior.
>  They have unique functionality that expresses their creativity and their
> own business vision.  Custom post formats just seem to make sense.

No, Custom Post Formats *don't* make sense on custom sites at all.
That's not what they do. That's not what they're for. That's not how
they work. A custom site design is *custom*. You don't need
interoperability, and interoperability is the only reason for putting
Post Formats into the core at all.


More information about the wp-hackers mailing list