Put My Understanding of Pods in Perspective
-
Hi, this is not really a support question. But I really want to understand what Pods does to help me as a site builder in relationship with other tools I’m already using. Thus, I could decide giving up cobbling a couple tools together and switching to Pods or keep the status quo.
Thus, I’d like to ask: does Pods replace the need to use both CPT UI and ACF? So, when Pods speaks of “fields” in its definition, as in “Create and edit custom post types, taxonomy, fields”, does it mean custom fields which you can choose where to display on a post or page?
Please help clarify. Thanks.
-
ACF allows you to create fields and add them to existing post types or other custom post types that are already registered. They have more ‘fields’ than we do, but we handle quite a few of them. ACF doesn’t do Custom Post Type or Taxonomy Registration. CPTUI ONLY does Post Type and Taxonomy registration. Nothing else. No field management. You have to use ACF in your scenario to add custom fields to those items.
Pods (as our plugin description states) is about helping you organize and manage your content in one place. We create Custom Post Types and Taxonomies and add custom meta to those and connect them with powerful relationship fields. We also extend existing WordPress objects (very easily) to allow you to add fields to them or connect them to other post types, etc. with Relationships. We also can extend post types and taxonomies created by other plugins.
Your best way of seeing how it works for you as a Site Builder is, honestly, to just install it and check it out. It’s free.
We don’t have all the metabox management of ACF, but it’s coming in Pods 2.8. We’ve also added a very powerful interface for managing ‘connected’ content our new Flexible Relationships in our Pods 2.7 currently in beta but slated for production in July.
If you have any other specific questions, please feel free to jump onto our Slack Chat at https://pods.io/chat/
Looks like the forum just killed one of my replies. Well, that’s not helpful.
ACF is about adding fields (a number of amazing fields) to posts, pages or custom post types or taxonomy. But it doesn’t handle creating any of those.
CPTUI is about creating Custom Post Types or Taxonomies. But it doesn’t handle fields at all.
Pods is about being a one-stop shop for managing your custom content needs. We handle creating Custom Post Types and Taxonomies and adding fields to those objects. We can also extend existing WordPress objects (Posts, Pages, Users, Media, Comments, Categories or Tags) or Post Types or Taxonomies created by any other plugin in order to add fields to them.
We also add the power of Relationships to all of the above situations to easily connect your content with one to many, many to one or many to many relationships that can also be defined bidirectionally to automatically update the connections. Our Pods 2.7 Beta (which should be rolling out in July) adds a new powerful interface for managing these relationships in a much cleaner way for your end users.
We don’t have the sexy metabox and flexible groups of ACF Pro, but we’re adding Group Fields and Management with Pods 2.8 which is our next focus after 2.7 launches.
Honestly, if you want to know if it fits into your workflow, play around with it locally and see how it goes. Use it on one of your next projects and see if it works for you. We’re free and we have free support so the only thing you’re out of pocket is time. Most people who’ve used our plugin swear by it.
You are always free to come ask us questions on our Slack Chat at https://pods.io/chat/
- The topic ‘Put My Understanding of Pods in Perspective’ is closed to new replies.
