Kontent.ai Reviews & Product Details

The ease of use is the biggest advantage.

Sometimes it is hard to get used to some aspects.

We have managed to create a local version of global company website.

I liked how easy it was to pick up and learn. Everything is laid out well.

grabbing links from the assets to post on the website is a little cumbersome due to the fact you have to extract only a piece of the url link when you click the asset.

Providing a quicker turnaround the the clients for website revisions and articles for the website.

We like interface, SDKs, multilingual support, an option to use different technologies. Kentico also listens to our feedback on the features and improvements that we need. We are confident that the product will grow and we will deliver our promises to a client.

On some projects, we required more complex role management.

Kentico Cloud centralises all content for our clients and we are free to distribute it to different sources like multilingual sites and apps.

Support requests are answered very quickly and the team are always eager to help. Even when asking silly questions they answer patiently and comprehensively. The platform itself is very robust and easy to use. I especially like the modern interface and intuitive layout.

I found it difficult to create content models around our complicated product catalogue. I don't feel that this is a failing of Kentico but more of this kind of system as a whole.

Our current CMS is outdated, slow, and hard to use. We wanted a more modern solution that allowed us to reuse content across channels.

The smooth interface for the editor and easiness to get started, be it for the content editor or for the developer. The support has been very quick to solve the very few hiccups we encountered with the platform. In terms of performance, we only had an issue once, delaying the publishing process, which has been fixed by the product team. As the CMS is SaaS base, you can benefit from the latest features released by Kentico. You do not have to bother about terrible upgrades. This is a good fit when you need to create digital solutions integrated within a complex ecosystem of systems and information sources, and you need a central system to manage all your (extra) content which can then be easily reused.

The fact the features are not up to par with the current Kentico CMS on premise offering. But we can see on their public roadmap they are going there, the products evolves quickly, and Kentico listen to their customers. In comparison with other major enterprise headless CMS solutions, they lack, at the writing time, a few things (but in their roadmap pipe) to make the full development process around the CMS devops ready (handle schema change at once, automate schema change by code, multiple publishing target) .

We used it mainly to experience the headless CMS capabilities of Kentico Cloud. We ended up creating a bunch of website for a couple of start up companies within our group based on the same web platform, and templates. We could deploy a new website in a matter of minutes. The main benefit was speed, and of implementation, and ease of management. We did not have to bother about infrastructure anymore.

What I like about Kentico is that you learn how to operate it very quickly.

We sometimes experience glitches and bugs as the software is still being developed.

We take care of our whole website and publishing with Kentico.

Simple and clear application design. There is no need to manage CMS onside (like Liferay portal administration and maintenance) Great technical support.

Missing deletion log, missing tracking changes in Content types, missing possibility to recover deleted Content Items and missing possibility to recover the previous state of Content Types

Content Management: 1. System content (like main system screens in mobile application) 2. Campaign (Marketing) Content like banners, news, ...

Kontent.ai is a fast and efficient cloud-based CMS that offers an easy separation between content and code for website development. It allows content makers to use a simple and friendly online interface to edit website content. The codebase of the website can be version-controlled easily and relies on API calls for content. This also enables a choice of development platforms and languages. We are now migrating all our websites to it, and the feedback from our content editors has been extremely positive also.

More flexibility around environments would be an improvement. And the contributor field is a bit annoying because it causes email notifications, does not automatically set to the most recent editors, nor unset from them after items are published. There are a few other features we don't really use as well, like "Tasks".

The business problems being addressed through use of Kontent.ai are many, and include: - Website speed - Ease of version control - Build/deployment speed - Ease of content updating by more than just developers - Technology independence (can write websites in any language) All of these aspects have been improved vastly across the websites we have migrated to Kontent.ai.

Kontent.ai is an easy-to-use platform. In that same ilk, it has made my life easier. I appreciate my job more, and I could speak highly of Kontent and recommend it others without hesitation.

There are many different things that could possibly be improved upon. That is most definitely a case-by-case situation. Kontnent does it best to prevent and meet issues head on.

The business has made back their money spent. Kontent has allowed for us to build our application in peace and without regret. The headless CMS is proving to be a life/stress saver.

I have enjoyed working with the Kentico Kontent UI and find it very intuitive to edit and administer content types

It would be great to have more flexibility with the workflow, rather than having one size fits all

It means that content can be updated quickly across the website without having to rely on a developer. It also ensures uniformity and consistency

The UI is pretty good. We can easily have people review it. Previously we had CMS on Jekyll, but we had to follow the PR approval process to update. Now it's just tagging people with new versions.

The learning curve with UI is different at first. But once you get used to it, it gets easier. Documentation could use some videos or gifs to make things better.

Moving the previous static page from Jekyll helped save our time moving from Github to Kentico. We had to wait for a long time to get our PRs approved. Also, assigning people got more relevant in Kentico.

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.

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.

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.

Kentico Kontent is a straightforward platform that makes it easy for content editors to create, edit and collaborate on different types of content. At the same time, the platform is easy to set-up from a technical standpoint, with easy to configure content models and a wide-array of of SDKs to help you handle data fetching, data migration, backups, ect... This is on top of the amazing Kentico support team, who are always available to answer any questions you might have.

Some of the initial hurdles we struggled with when implementing our new website Kentico Kontent had to do with migrating sections of the old site that were very dependant on the tree-hierarchy model we were used to seeing in more traditional CMS. At the time, the platform wasn't well set-up to accomodate this requirement given that it fully embraced the Headless flat-hierarchy approach to content structure ( i.e it was hard for content editors to visualise the whole sitemap and see how pages could be nested below one another). Since then, the platform has made significant improvements in terms of bridging the gap between the Headless CMS and more traditional CMS with features like WebSpotlight.

After having had the experience of being hamstrung by a custom platform with limited support, we wanted the flexibility to choose best-of-breed micro-services and not be locked into an all-in-one CMS. Kentico Kontent gives us the scope to expand content beyond the web and leverage new technology as it emerges. It also provides us with an ideal platform to manage a wide range of content meant for different channels, with great editing and collaboration features.

Kontent has a very easy to use interface for building complex data structures. It's easy to use for developers; it's easy to use for business users. I like the fact that there are a pre-defined datatypes available to use, while still having the ability to create custom data elements. The delivery API is very fast and is easy to implement.

I don't like the fact that for rich text content, the only format available is HTML. I would prefer if there was a flag that would allow me to request that content as Markdown (or something like that). It also feels like the JSON response from the delivery endpoint is also larger than needed.

We were trying to decouple the content that was being created from the display of this content. Kentico Kontent allows us to define all of our data / pages in one location and then allow the web developer to display this as desired on-screen. Content editors can change the content at any point without worrying about code; developers can write web applications against a well defined API and not worry about the content.

How quickly you can set up a website with a full fledged CMS.

Lack of asset organization. Also more security features for assets behind login as well as audit history for assets. More options for what to include in development API by status.

Let marketing control easy website updates.

I enjoy how simple the user interface is and how quickly the support team responds to queries.

The fact that you cannot get the asset urls directly and that long names cannot be seen on the minimized linked items.

Dynamic layouts have been solved ( with easy to using models )

- headless approach - training of content managers is really fast during good usability - simple admin menu and permission management - usability!!!! the best thing

- hard to say that from a PM and user perspective, because for your projects it was always perfect and perfect configurable. only thing i found: "filter content" in section content, cant be reduced or minimized to the left. its always visible and i really dont use it in all my projects.

implementation of a white label WebApp and copying it several times => centralized cms content of all projects in different languages etc.