Experience has been great. Technical documentation is good, and the example projects in various languages has been helpful.

Flexibility of content taxonomy, ease of implementation, speed of Delivery API, excellent tech support.

It is up to the client to determine how best to structure their content's taxonomy. There is a lot of flexibility in Kentico's Admin Portal, so some "best practices" and recommendations from Kentico would be helpful.

Our experience with Kontent to date has been outstanding. The platform allows us to deliver content-rich experiences for our clients across multiple channels quickly and efficiently, which is a win for all parties. The platform features continue to grow and excellent communication and support makes adoption fast and seamless.

Kontent's API-first approach means we can quickly and seamlessly integrate with modern tech stacks and front-end frameworks (including React, Vue, Angular, etc.). The Delivery API, Management API, Webhooks and Custom elements provide versatility and scalability to meet the needs of ourselves and our clients.

Some upfront knowledge is required to get the best out of the platform, especially when considering content modelling. As Kontent is a headless CMS, one of the objectives should be to utilise content in the most efficient fashion. To do so requires understanding of content models and taxonomies, and once understood, it's very easy to execute. It should be noted that this isn't a negative about the platform, as this comment applies to all headless CMSs.

good

pretty straight forward from a user perspective, very flexible and adaptable

Requires loads of dev time to make basic changes and implement features that would be out of the box in other instances.

I am really looking forward to the next months in which I work on the integration of Kontent!

The GraphQL and REST APIs work effortlessly with the modern software stack. The Kontent team managed to create a simple but powerful user interface with a flat learning curve. And that can be proven by the coherent e-learning experience. It is made from people for people

The rich text editor could use a straddle functionality for tables. Referring to text passages is an important choice users would like to know exists. The integration of assets or linked items and components with list views seems not to be tolerable - could you improve upon indentation - better a clear relation between text and other elements - like making all elements able to be inline?

Ease of integration with modern tech stacks, ability to use latest front-end frameworks such as React, Vue, Angular, etc. Easy integration with a variety of back-ends using their SDK - we have used the Javascript SDK to integrate into Node.js projects very effortlessly. The API is feature rich, for example: - you may set it to preview mode, to set up your staging & testing environments to preview draft content items - fine grain control which content workflow steps trigger webhooks to your server - use webhooks to easily integrate with services such as Elastic Cloud, Azure, translation services such as Google Translate / Amazon Translate

Kentico Kontent has improved dramatically over the past 12 months, it was already a very competitive headless CMS before, now after all of the recent updates I am confident to say that it is the best product on the market and is my default selection for greenfield projects.

I like the Web Spotlight feature, the JavaScript SDK, the Management API, and the Migration Tool to add items via code rather than the UI.

Some features like the Taxonomy seem very basic and also the APIs don't cover all of the things we do in the UI, so we can't approach Kontent as do everything via code approach.

Well, I started journey with them when they were a Kentico Cloud, and now with a stronger brand, Kentico Kontent is going better and better.

Architecture API oriented, ready to support Headless solutions right away. The way they design content authoring approach, with versions, content repository, and other makes Kentico Kontet a perfect solution for business content-oriented projects.

Everything that was strange to me before, they fixed or changed very quickly, so nothing at the moment :)

- Best support I have ever had, super competitive team, instant replies - Feedback is very welcomed. All the suggestions are noted, and reviewed by Kontent Team - Software Developers love this product. Its easy to use and has great SDK. Content models are abstract by itself, so you are not limited to anything. You can create your own blocks and use them the way you want. - Speeds up the product development and delivery - Image transformation API takes care of fitting the images to any screen resolution. - Ability to create custom form elements - Very elastic about workflow definition and has good granulation of access rights management. - Attractive free plan, comparing to other Headless Cloud CMS

- (As for 29.11.2019), I'm missing a mechanism for grouping content in directories so we can functionally separate top level content (for applications views/pages) from less crucial content. Because of that, developers often have to teach the end user where to start and how to use prepared models

Great support from the Kentico Kontent team is encouraging the team to put the platform as a genuine alternative to the traditional CMS route.

• The Kontent platform has now evolved into a production-ready system • There's strong support from Kentico sales department • Good technical support from Kentico development team including sample code available for multiple frontend frameworks • The Kontent team are ready to adapt and evolve products to client/agency needs • There's Great integration possibilities g • Good customisation is now possible of the CMS editor • Competitive pricing model with the other contenders in the marketplace

• The platform needs agencies/developers to re-train or employ additional frontend developers to deliver public site if they committed to the Kentico EMS platform for their business, essentially either are a cost to an agency • Deprecation of features in the past has left a nervousness over the platform (e.g. Draft CMS Import module, personalization engine) • The product is focussed at clients who have a specific project fit and knowledge of technology

One of recurring problems that we are solving is making sure we create a future-proof solution. Previously we had to go through (painful) upgrade procedures, to keep the WCMS supported and secure. Content as a Service solves this problem and allows us to focus on .

My favorite feature is the Content Management API. This API is very flexible, intuitive and easy to use. I have used the Content Management API to migrate thousands of content items from a traditional WCMS to Kentico Kontent. This included optimization of HTML and enabling support for Omnichannel publishing.

Some areas of the Content Management API are not finalized (yet). This sometimes requires workarounds to get the job done. It would be nice if we could speed up the improvement of the product within these areas.

Service and support are top tier

it is inexpensive for such full featured headless CMS

I wish I started using it sooner as it is a joy to setup

We moved our website from a legacy CMS to Kentico Kontent, and have other sites we'll move over next year. Kontent allows us more flexibility in running multiple sites, and running our main site in multiple languages. Compared to our old system, it's *much* faster and easier to use. Our site performs better/faster, and we're able to shift to a more open-source model of development and integration. We're excited about the opportunities it will open up to us in the future as we more fully redevelop our sites and begin to leverage it for other digital properties. Their sales and customer support teams have been highly responsive to our issues and are overall a pleasure to work with. The one drawback: Kentico the company seems to be running in multiple directions at once, and some dev issues we encountered with their plugins took longer than they should have to resolve due to developers on their side being on vacation or dedicated/specialized in other areas. Once we got linked up with the dev that specialized in our plugin/issues, it's been a productive a mutually beneficial working relationship. However, the degree to which their skill sets seem to be siloed is concerning.

Easy to use, flexible, a good value, good team behind the product

Currently, Kentico resources are spread thin

My overall experience with Kentico has been amazing over the years and much less stressful than other DXPs

What I like the most about Kentico is Ease of use and support it provides.

Kentico can do better in providing more clarity on licensing options

Customer support, SDKs, Ease of use for devs and customers, Assets (integrated image transformations and web optimizations)

In really complex scenarios admin UI is starting to be a little confusing. Admin UI is available only in the English language, which is sometimes a problem for our Czech clients.