Kontent.ai Reviews: 4.3/5 — Solid Choice

Modern administration environment. Pleasant and modern appearance of the final web presentation.

Very complexity of translations of texts. Something is in the form. Something in the Kentico cloud. Something in the settings. Something right on the page. For me, as a beginner, crazy confusion.

Currently, I only deal with translations that have been in status "In Progress" for a long time.

That you can easily adapt your website even though you know nothing of CMS systems.

Sometimes it's not really clear what the structure of your website looks like in Kentico.

Easier to use website with adaptible screens and functions.

The malleability of the platform to make live changes as needed quickly.

There are a lot of little things to remember for functionality that takes some time to get used to if you're not the main user.

Marketing to target audiences and Kentico has allowed a lot of flexibility for us to make changes as new data comes.

easily way to upload contents. dashboard user friendly.

too many click for creating a new version of the content to perform the changes

our website in now cooler and more user friendly. the navigation is at a very high level.

Possibility to add individual help texts directly near the fields Huge range of templates for different content elements Use a content element on different pages

Having to type in an internal name for every content element Not able to publish a whole page with one click like in other CMSs Not able to crop an image directly in Kentico Cloud

Local marketing departments are able to maintain the local website themselves. That saves a lot of time compared to a centralized maintenance and avoides errors or missunderstandings.

I like the fact that the design of Kontent by Kentico is so clear and easy to navigate.

I dislike the pages within pages that need their own name. Sometime I lose the pages I am working on.

Kontent by Kentico is way quicker, and modern than what I am used to. It offers many more possibilities.

What I like about Kentico Kontent is that non-tech people can add content and change taxonomies pretty easily if the developer implemented everything correctly. The content editor is pretty nice as well and other than that it has a nice and intuitive UI.

What I dislike about Kentico Kontent is probably the API. It's pretty much useless without an API to connect to, and that's expected, but the API is horrid. It's super slow. We tried using their SDK, and the SDK experience is a nightmare. Super unintuitive and very bloated. To anyone trying to use their content on Kentico Kontent, just skip the SDK. Build some wrapper yourself.

We are storing user documentation on Kentico, also some blog posts that get compiled down to static content. The best benefit is that our product owners can edit stuff by themselves and it gets automatically propagated to the users.

Easy to manage multiple contributors' content.

Sometimes the rigid publishing process can be more time consuming than we'd like, but it also helps prevent mistakes.

Content managements across multiple sites, with multiple contributors.

The UI Is getting better, good features are developer. Centralization of content for multiple platforms

The API and developer experience is not that polished as the UI and editor experience. The Caching on the API side could be implemented in a better way. Currently the first request to the API is very slow due to cache being implemented in an first access manner.

Centralized content management. The benefits are that we don't have to host our own CMS and develop backend solutions.

Nice UI Flexibility with organizing data

Spotty performance API lacks some functionalities

Sharing content between different sites. Having one centralized place to keep business data. Save costs when translating content.

the support is awesome, but 70% the support doesn't know the technical solution in Gatsby for example. so I always find the solution in communities or other places than the support. but they answer very fast and try to help as much as possible.

In a world with more than 90+ headless CMS + solutions like WordPress/ Wix/ webflow, more. I didn't saw something unique in Konten. - Wordpress have a better navigation and menu system. I spend weeks on implementing a menu with only three layers, it's harder to create a menu or a sidebar in Kontent. - no repeatable widgets, in WordPress ACF, they have a repeatable field, and you don't have it, for example, if I want to create a list widget, when the user needs to click + to add a list item, or a carousel, in which the user adds a new slide in the CMS it's easier to use ACF + Wordpress.

im giving the user the option to edit the text in a CMS with workflows which is nice

ability to automate a large amount of website production through use of templates etc

too many menus and layers of interface, can be difficult for newcomers

giving customers control over their content

Headless cms technology and performance in it

Lack of features like search and controls that can easily be found in a standard cms

Introducing new cms technology. Benefit is we can use any front end to retrieve data

kentico cloud is new revolution for web dev tool. and I like the most of kentico. it is user friendly .

the only thing that i dont like about kentico. unable to create folder Inside content . if user has more than 200 content . it is hard to categorize

Dev web site . faster pace than normal web dev process. and easy to make changes.

Good support for preview environments and easy page building

No custom widgets using UI extension or release management.

A scalable and extensible CMS with versioning and release management support.