Plugin Contributor
pglewis
(@pglewis)
Rather than try to give a run-down on the entire feature set, I can boil it down to this:
* If you’ve used custom post types before, you probably would have been better off with Pods.
* If you’re considering using custom post types on a project, you’re probably better off with Pods.
* If you’re scratching your head over how to store and retrieve various related data and tie it all seamlessly into your theme and admin back-end… you see where I’m going.
I use it to allow clients to manage home page slide content: slide image, title, maybe a content paragraph, and anything else project specific. I’ve used it for product catalogs (both physical and software products) with product, category, ingredients, testimonials, success stories, etc. Very easy to pull product-specific testimonials to be displayed on a product detail page.
For basic stuff I don’t even have to break into using helpers. It’s nice to know they’re there when I have a specific problem to solve, but 99.9% of the time I use Pods I’m doing productive programming not fiddling with the UI or configuration. It does its job well, you can set things up quickly, and get back to getting work done.
this page is generated from pods
each item has been input via a form which is then generated on the page pods generated
as details of each item change yearly doing so in html took days but in pods takes a couple of hours
