Kontent.ai Avis et détails du produit

User interface is good. Available features covered all of our use cases. They also seem to be actively working on even more features and are impressively responsive to feedback.

There's not a whole lot I dislike about Kontent. The JavaScript SDKs I've been using are alright and are improving consistently. Perhaps more security features for asset management would be nice.

Headless CMS, so we solved the problem of being able to manage the content of our website easily, without having to change the code. We can also manage content and languages for multiple regions.

Kentico Kontent is a great headless CMS tool that is easy to use for our business clients. Our development team can help our business create their content structure and model so that all they have to do is go in and enter their content, review, and publish when they are ready. Very quick and easy to learn, even for the not so tech-savvy users.

There are still some limitations in Kentico Kontent. One that has bothered our business clients is the ability to add images in line with text (like in a newspaper article).

We are able to give the power to our business clients to be in full control of their content and when they want it to be published. This allows our team to focus more on improving the solution and the website features.

I enjoy how seamless and overall User Experience design of this CMS. It is easy to follow and has consistent functionality. In comparison to other competitors, it has better technical support and overall layout.

I don't particularly appreciate how the URL slugs do not generate properly, and some features do update in real-time in the environment. I would like to see more tips within Kontent to engage the user.

We are bridging the gap between non-technical audiences and using a CMS for content creation. It is beneficial because we can improve their user experience with their feedback, and Kentico makes changes easy to implement.

I love the spotlight concept, allowing you to view pending changes real-time as if it was on the website.

I dislike that you can currently not create environments via the public api. However, I do know this is now a work in progress.

We are decoupling content from the website code, allowing new content without continuous development & following a change procedure.

I like the visual aspects of the software and how I can find things by looking at the website page and then choosing to edit things from there. In competitor's software, that isn't always and option.

I don't love that I have to go in to tiny image websites and reduce the size of the file, perhaps in the future this could be automated by Kontnet when users upload images.

We are solving the problem of allowing the marketing team to make edits on their own vs. developers, therefore allowing the marketing team to be more productive and be able to make changes quicker.

It makes for great workflows and collaboration.

Not a lot to dislike - they've been consistently improving the product.

We've reduced complexities tenfold, making migraines a lot less frequent across several product teams.

Ease of use for content editors, in-page editing of page content, great APIs, and customization of the CMS. Great consulting team and support from the sales team during product selection.

Subscription level pricing and metrics have changed at short notice. This means that pricing comparissons have to be re-checked before purchase to save unexpected surprises.

Deployment of a single enterprise content management system across multiple brands and businesses which permits content sharing and granular permissions management.

Web Spotlight is inspired - it means content editors can focus on understanding and editing the content without needing to worry about understanding the complexity of the content modelling.

Content modeling is completely free, you can build the content model any way you like. This is wonderful, but sometimes too much choice is paralyzing. It would be nice to have a better tool for moving content types and changes to content types between projects (and environments within a project).

We're moving content from an outdated self-hosted CMS to an evergreen cloud headless CMS, we're getting benefits from the performance and the simplicity of creating new environments for development.

The user interface is very user-friendly and self-explanatory. Many features (notes, comments, tasks, etc.) simplify collaborative writing. The documentation is very detailed and helpful.

Kontent is still a young headless CMS. Currently, e.g. the taxonomy handling with multilingual websites is still suboptimal. Presumably, the feature will follow shortly.

The flexibility that Kontent brings with it through the headless approach allows it to react quickly to new marketing needs.

I love the support, the API output. THe user experience

There is no way to force default values for instance. Content item fields could have more options.

Currently working for a client migrating their platform to Kentico.