Features I wish Contentful had:
- Object Field Type: Yes, they have a JSON field type, but it’s a raw text field—not user-friendly. To make the JSON field user-friendly, you have to create a custom app. This is a pain.
- Repeater Field Type: Yes, they have a Text field type with a “List” option, but that only supports arrays of simple strings. I want an array of simple objects. Yes, they have a Reference field type, but that requires you to a) create another content type and b) create a new entry for every item in the array. Managing atomic content is a pain. Creating custom apps to work around this is a pain.
- Plus, creating a new content type counts against your usage limits. And the starting limit of 25 content types is rough—it nudges teams towards clumsy abstractions just to stay under the limit. Cost cutting is a pain.
- Field-Level References (i.e., Shortcodes): Yes, you can embed entries in rich text fields, but you can’t reference specific fields on those entries—unless you make every field a Reference, and every piece of content its own entry, which is a pain. For example, I’d like to have a content type “Product” and another type “Post” and then be able to reference any of the fields for a particular product in my post’s rich text content. Yes, I could use atomic references. Yes, I could make a custom app. Yes, I could write my own shortcode system. But again, these are pains.
It would be 🤌 so nice to have these features out-of-the-box.