Custom post types are e-commerce products, books, real estate
properties and many other things, but the last thing they are, are
posts. So why do we continue to use the default posts interface to manage all this awesome additional information we’re storing?
Data.
I was wondering about this issue a while back, as we (Theme Force)
use custom post types to store information for a number of the features
we maintain (after all, it’s a darn powerful feature of WordPress). Our
features are all relatively simple concepts (food, event, slides,
etc.), but we were making it far too hard to use. This, simply because
we had visually ridiculed information that already had context,
to plain old data bound by post_id’s, thus leaving it up to the user to
find their way around a table that doesn’t differ much from the SQL one... < more at www.noeltock.com/web-design/wordpress/custom-post-types-are-not-posts/ >
Nenhum comentário:
Postar um comentário