Unclaimed: Are are working at Contentful ?
Contentful unifies content via a central hub and helps structure it for use across various digital channels. It also easily integrates with numerous other tools through open APIs. Contentful lets users bring their content anywhere using our APIs, and completely tailor their content structure while using your preferred programming languages and frameworks.
| Capabilities |
|
|---|---|
| Segment |
|
| Deployment | Cloud / SaaS / Web-Based, Mobile Android, Mobile iPhone |
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
| Training | Documentation |
| Languages | English |
It is simple and flat. It was easy to adapt. Most of our developers enjoy using Contentful, easy-to-build or find already-built Apps (widgets; you guys chose a confusing name).
I do not have something in particular that I dislike. Maybe taking the flat structure a level too high. I would like to have folders at least for the assets. It would make organizing easier when used from other places over the Assets API. When using your cloud UI, it works great, but its quite a nightmare when we have to use that in our applications directly.
Very simple, but powerful tool. Makes it easier to integrate in our current setup. Especially for assets its a game changer. Now our products are in sync so we only need to use one set of assets.
The level of customization we got with it. Also, it's not simple, but all the team got to understand, and Marketing is now free to create content fast.
The nested approach of components is what was more complext to explain to the team. And it has sometimes created problems, especially during the first weeks.
Enabling all teams create and modify our webpage, without needing any dev work.
What I love most about Contentful is how quickly you can prototype a solution and get it production ready.
Contentful has a lot of nooks and crannies that need attention and polish. As you get more advanced with the platform and your custom integrations, you will find blockers and sharp edges to things I believe their product managers need to recognize and prioritize.
Operating content platforms at enterprise scale, Contentful has solved our constant waste of resources building custom CMS solutions in our various micro services. Uniting many atomic, independent teams on one content platform is no easy task, but the approachability and flexibility of Contentful has drastically reduced the fatigue for both our engineering teams and our content editing teams.
the software itself is very functional and user friendly. both customer support and documentation (learning materials etc.) are top notch.
it is missing some basic functionality such as superscripts in text editor there are no tools available to help editors collaborate on a given text itself (such as change tracking)
Contentful is allowing us to structure our data in a way that allows us to service complex business requirements for our front-end digital solution
I love the authoring experience in Contentful; it's very flexible for composing structured content. It's easy to teach the platform when content types follow best practices, and learning it is effortless.
I think that they need to address competitors more directly. Maybe the devs don't love it like before?
They are continually improving the UI and Releases Workflows.
Contentful has unlocked ultimate flexibility for our website, enabling us to fully showcase our products and brand story for our customers.
The cache refresh delay can make things slow for updates.
Combining a Headless set up with Contentful has allowed us to think beyond standard Shopify theme limitations and speeds.
Their API and user interface is intuitive and easy to use. Both developers and business users at my company can use their software without requiring much help from our internal IT team. We built and awesome Reactjs site backed by a Contentful CMS system.
I wish it was easier to change back to a previous version of certain content. This feature would really allow for easier mistake handling when changes needed to be made quickly.
We use Contentful as the headless CMS backend for my company's primary website. This allows us to create a custom frontend without being restricted to plugins or other bespoke frontend liimitations. Like Wordpress, but much more flexible and customizable and developer friendly because you don't have to learn PHP.
Simple but powerful CMS that empowers our marketing team to load fast, dynamic content across our digital presence.
There isn't much to dislike. Clean UI for users who prefer it, great API for devs.
Enabling content teams to dynamically switch up content across our digital presence without engineering time.
The overall user-friendliness is my favorite contentful feature. When I first began using the application, I required very little walk-through during training and find it extremely easy to train new hires.
I wish updates were reflected sooner. I know it doesn't actually take long. Still, when our company requests report updates, we typically hold an affiliated email until updates are reflected. This scenario is typically an issue when updating pdf attachments. (And really only an issue because we're pestered by team members who do not use contentful as they believe we have not made the requested updates until reflected on their end.) There are two additional hangups I've encountered: 1. When uploading a large photo asset that I want to resize within Contentful they often time out/glitch using the resize feature and I will resize outside of contentful, then re-upload. This is a minor issue. 2. Strikethroughs are inconsistently displayed, sometimes correctly and sometimes showing the <s></s> html.
The best thing contentful solved was the ability to stop using an extremely outdated WordPress. We were legitimately counting down the days until we made the switch!
UI it's really beautiful and the experience is pleasant to the users. Also, it helps the productivity of the teams in general. From a dev perspective (my role) helps a lot, cause we don't need to be careful of the content in code, so we just leave the responsibility to the content authors and this improves development time.
Sometimes the UI doesn't load changes in real-time so we need to reload the page to see the changes. If we make changes in nested content types, no button allows us to publish all the changes at the same time and we must accept each one individually (sometimes it is a bit annoying, although it is not a big problem)
It allows managing the content of the page without the need to make changes in code. This allows speeding up content management processes, and allows the team to make changes in production without the need to make changes in production and deploy them in different environments before seeing the final changes in production.