Contentful Platform

I really enjoy using Contentful due to: - the platform's core performance - it works well for our needs and setup; - thoughtful updates and functionalities; for example, the new pattern where one can navigate e.g. from a component a few levels back in a section just by clicking on the desired window - it's more visual now; - intuitive navigation & UI - the collaboration aspect - it's nice seeing who was the last user to update a model, to track the progression of its use

They respond quickly and they regularly check in on feedback while delivering a feature for you. It feels like they take our input seriously which is really nice. The meetings and working sessions that we have had with the Contentful team were always very efficient and fruitful. Additionally, our content editors like to work with Contentful as they think the UI is quite user friendly and straight forward. It's also quite easy to create new content types and using custom apps gives you a lot of flexibility too.

The product is very flexible, it has been able to handle our peak traffic times without issue, update statuses are clear if something is published or in draft mode, you can schedule an update for a later time which has been great for timed announcements. Overall it has been relatively easy to learn how to use and quickly become productive.

- missing duplicate functionality: since one cannot duplicate content models, the needed model needs to be rebuilt from scratch, which feels unnecessary and time consuming; in design & code, one can easily reuse base structures for a more efficient workflow - when creating a new updated, component (component v1 VS component V2)- the work that goes into the migration becomes very tedious: e.g. if a component which previously consisted of text-only is then updated to let's say text & image, content managers have to manually copy-paste all the text and basically build from scratch instead of having a smarter or smoother solution; I'd imagine some automation could create partial migrations or aid in the process; - lack of adding folders in the workspace - we're currently relying on naming the right entities to figure out the different clusters building e.g. a page; sure, we have the filtering tool & we can see how each building block is used, as well as on what pages, but it can sometimes be easier and quicker to have a visual distinction too;

It can take a long time for them to deliver a new feature to the market. Integration possibilities are quite limited, especially if in your architecture it doesn't make sense to import everything to Contentful. There are very limited options in template configurations for dynamic pages such as product details pages.

It doesn't support search for the frontend without third-party integration. I don't know if this is a limitation of Contentful or how we built it, but I wish we could use the same space to trigger a deploy to stage then prod separately, currently any publishing in Contentful goes to all environments so there isn't really a way to test it after we went live.