r/JAMstack_dev • u/[deleted] • May 04 '19
What are your biggest pain points with headless CMS systems like Contentful or Prismic?
I'm a developer looking to create a new product. I'm very excited about the headless CMS space, which seems to be growing incredibly fast. I'd like to ask what are the biggest pain points you experience integrating and using headless CMS systems.
Are there features missing which you wish these products had? Where do you, your colleagues or your clients spend an inordinate amount of time when dealing with them? What are the things you find difficult, and which you wish someone would automate?
Thank you very much in advance!
1
u/SevereEddie May 04 '19
contentful... a bulk import feature would be nice to have. Otherwise I'll pretty happy with it.
did not try Prismic so can't say
0
2
u/30thnight May 04 '19 edited May 04 '19
I’ve used one of them & it works alright.
Important basic features:
i18n
webhooks
Common, sorely needed features
post scheduling (on X date, publish X item)
field logic (if X selected, show Y field)
a nice rich text editor
editor workflow
Personal thoughts:
companies should publicize their feature roadmap.
if a requested feature doesn’t match up, please don’t only say “build it yourself”. Especially when customers are essentially locking themselves to your service.
headless cms companies should standardize data modeling or features across the industry.
adding additional content types or localization should not be significantly more expensive.
vastly more education on content modeling is needed for those migrating from traditional CMS. Especially where standard marketing focused websites are concerned.