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 |
Ease of use and how FAS it is operationally.
Nothing currently. I would say it was just too expensive for a self employed artist.
Having fluid and consistent content that matches all platforms so it looks polished and like I know what I’m doing.
Interface is easy, it's very flexible so you can customise it fully to best meet your requirements. Its also great at being able to create a whole range of content templates. Real-time editing is great when there are multiple users working on the same piece of content.
The image/file area is quite clunky. If you're not a developer it can be quite difficult to customise. Because it's a headless CMS its also difficult to see how the content will be displayed in live.
Managing website data, web content and storing image/document files for publishing online.
Contentful helped us bridge the gap between developers and our marketing team ( the content developers). Our car pool app, PoolY, has recently seen major success and increase in the number of active users recently so Contentful's pay as you go payment plan has been very profitable for us when we wanted to scale up. We saved so much time and money because we didn't have to write code and create our own data servers for our website. Contentful's API readily integrated with our website and apps' code and we were up and running in a matter of months.
it takes a long time for the changes we make in the backend to show up on our live website. This makes the maintenance period painfully long and creates long periods of time when users cannot access our website.
We use Contentful to deploy backend updates and maintenance while hiding the code form our content providers and marketing team. Contentful also helps us with storing our data and content in a secure manner.
The possibility to have multiple spaces, and the potential to handle multiple languages
The default contentful long text editor is very limited, it forces us too integrated some application like tinyMCE which is paid
As we have many brands, Contentful lets us have a solid backend code, so we don't have to re-code each time we want to sort out a new brand; we can handle it on Contentful, much faster and less time consiming
Quick to get going, user-friendly UI, flexible content model.
Less ideal for more serious or mid-sized startups, or plans seem tailored to a different type of business. Hard limit of 25 users is ridiculous as only option is to upgrade to enterprise which is way beyond our needs. CDN price is baked into the price, so not only are you overpaying if you want to use your own CDN, there's also no real built-in support for using your own asset library and/or CDN.
Quick and flexible CMS to easily collaborate on content.
The self-service is easily understandable and also the Schema definition. Setting it up for a small team is quick and easy, and the APIs, especially the Media APIs are very powerful.
The limitations. The 48 content types are limited across all plans except enterprise. This is a hard limiter to modular design and requires thinking ahead and designing components in a generic way for them to work. The generic approach might impact the content editors' experience negatively.
Multichannel Content Management. Since it is headless and we can access everything by API (Rest and GraphQL) we can access the data in the form we want (GraphQL) and reuse it across different channels (app and web).
I like the layers that give an easy overview of the different page sections. I like how you can use assets in more than one place.
It can be a bit tricky with sizing and specs. Also, I wish there was more variation with the placement of content and assets.
An good way to build web pages that all look consistent and on brand.
What I like best about Contentful is that the UX is clean, and most aspects of Contentful are easy to learn and use.
What I dislike about Contentful is that due to the high volume of users, it can be slower at times, and it can also be challenging to customize certain things.
The problems I am solving with Contentful are work-related, and the benefits are great.
UI is intuitive and easy to use. My view is a great addition. Publish history and Versions are superb. The editor is good. Information architecture is cool so as content models.
Reusable components and their related functions suck. No way to conditionalize text for different versions. Single sourcing (write once, publish anywhere) is not so great. UI is a little laggy at times. Image editing needs improvement.
Content publishing Content structure In-product help Support site docs Migration of content from Confluence
The performance of it is nice and quick and our devs like the simplicity of building out modules
As an author on the marketing side, I find the nested content structures difficult to navigate
We were on wordpress before and this is MUCH better in terms of speed and performance
API automation is helpful to connect it with our apps
Frequent partial outages could cause serious problems
Content management
Very easy to navigate and use. The interface is built to guide users step-by-step in regards to utilizing media.
It would be better to include multiple asset uploading instead of uploading them one by one in individual entries. It takes some time to create collateral of imagery. It would also be better if archiving an asset took the link offline altogether, or redirect to a not available image. We have issues where customers have a link saved and we are unable to remove that asset from the internet.
International distribution of marketing collateral. Sharing amongst our wider team to work more agile together.
Definitely seems like a more developer-friendly tool, and integrates well into our deployment workflow. The modular approach to content is an interesting one, and for certain types of websites it would be a killer feature.
From the editor's perspective, Contentful is maybe a bit TOO developer-friendly, as it lacks a lot of the basic features that I look for in a CMS. While it may be highly configurable, it puts the onus on me to repeatedly ask our development team to add or change things at a platform level, rather than giving me the ability to do so myself. Instead of empowering my team to do more without the intervention of the dev team, it's simply changed the nature of our requests to them.
We didn't have any CMS in place before, so having one now has made posting and editing content easier for us. The biggest benefit is that the learning curve for Contentful is pretty low, so it's pretty easy for us to onboard new members of the team.
The level of customization -- like being able to add helpful hints to tell people what kind of data goes in each field.
Using Contentful requires a different mindset and it takes some time to understand how all the pieces fit together. It's possible that some of my frustration comes from my company's instance of it -- I haven't used it in any other jobs. Many tasks feel like they should take way less effort, it's hard to get things to look nice, and it's easy to accidentally make errors. It feels like way too much clicking to achieve simple tasks. I find search less helpful than I'd like.
Being able to update the website, add new pages, and edit pages.
I like that it looks nice and modern. That's about it. Good UI. Horrible UX.
Everything else. We use both Wordpress and Contentful, but I wish I could move everything back to wordpress. You never know when things will update and when an update is pushed through it could take HOURS. Additionally, it's so complicated on the back end that only our developers are allowed to approve changes making it a NIGHTMARE to use when someone is on vacation, or out of office and you have time sensitive projects.
Nothing, I guess our site looks marginally better?