A friend of mind attended Wordcamp B-Ham and taped (that’s old school lingo for podcasted) a panel discussion about Pods and Flutter as two competing options for making WordPress a CMS.
Admittedly, I’m biased. You can read my review of WordPress Pods CMS here. But here’s my two cents anyway:
- If all you’re looking for is a way to add a new content type, and it’s ok that that content type is mostly based on the “post” format, then flutter will probably get you there. Flutter basically customizes the user interface for entering custom fields. Theoretically you could even get rid of all the default fields and use all custom fields instead.
- But if you need to create all new content types and need to have complete control over the end-user experience then pods is a much better choice. Pods is especially powerful when creating directories where you need to cross reference fields. For instance, you want to create a list of events where the end user can click on the speaker’s name and see all other events with that speaker. Trying to do this with flutter would be a nightmare. But with pods, you create a pod table for events and one for speakers, set up a template, and your done. Well, it’s not quite that easy … but it’s close.
The advantage of pods is that it’s robust and dynamic. Flutter is essentially just an advanced hacked. Pods is a true extension. But the disadvantage of pods is that, at least for now, it is still a tool for developers who know their html and at least a little bit of PHP. A novice user is going to find Pods maddening!