What do you like best?
We're using Kentico to handle content and more. To preserve data from business logic in the current system that has no other space. In case of change in technical requirements it is very easy to expand / update the existing structure. And teaching end-users (editors) what is to be done there is also very easy.
What do you dislike?
Some features are still needed to maintain data integrity in business-level projects, where data validation is necessary to automate. It includes unique verification rules, additional field constraints options, etc. What also amazed us is that the measured traffic includes access to property.
Recommendations to others considering the product:
Kentico has an opportunity from around the world if a small sizing with status labels is needed. But it is a correct choice if you have a lot of information that was seen as our business. Although not widely used, the device is still very likely and it is supported by a number of things.
What problems are you solving with the product? What benefits have you realized?
You can begin very quickly. Kentico Kontent has a simple user experience and a distinct gui. I obtain fast and useful responses every time I contacted technical support. And the reliability and availability of APIs have never been problematic. The key questions are answered in the documents and many design tools and SDKs are available to ensure a smooth development process.