Não reclamado: estamos trabalhando em Kontent.ai ?
O Kontent.ai é um software CMS headless mais conhecido por ser uma plataforma de conteúdo modular que permite que desenvolvedores e profissionais de marketing planejem, criem e forneçam experiências com ótima aparência em vários canais. Ele foi desenvolvido para suportar perfeitamente a dinâmica de trabalho das equipes, facilitando a produção fácil de conteúdo, a reutilização modular de conteúdo, a colaboração em tempo real e as aprovações.
( 1 )
| Capacidades |
|
|---|---|
| Segmento |
|
| desenvolvimento | Nuvem / SaaS / Baseado na Web |
| Suporte | 24 horas por dia, 7 dias por semana (representante ao vivo), bate-papo, e-mail/Help Desk, perguntas frequentes/fórum, base de conhecimento, suporte por telefone |
| Formação | Documentação |
| Idiomas | Inglês |
Comparar Kontent.ai com outras ferramentas populares na mesma categoria.
The simple, clean and straight forward user interface.
Functionalities are too basic especially for enterprise usage, eg. lacking of audit trails, CD for content type and taxonomy, debugging logs of API etc.
The concept of ability to segregate content from delivery channels so content efforts can actually be expedited and not dependent on the tech.
The Headless API, content management flow, and ease of use. I like the way it allowed me to manage the content we would be utilizing for the solutions that we build.
Not a whole lot that I dislike. I felt like the product was fairly robust and easy to use. I would recommend this to clients that we work with.
We were exploring CMS's with Headless APIs for a solution.
Versatility and ease of use are the most important advantages of Kentico Cloud. It is very important for us to have a platform that users from different countries can use easily and also localize content. Users can input content and collaborate easily and manage the content from anywehere. You can set up pages easily. For example, It is a complete all-in-one solution that can help your business. Setting engaging content for customers can be created easily.
The platform is easy but it could take some improvements. Also, you need to adapt to the platform philosophy that makes you input all the content first before creating any page/event. For example when creating an event you should provide everything regarding the event from images to short and long description and headlines, speakers, agenda etc. Which some times it is not easy to do...
Due to the cloud technology a team can work simultaneously on a project from anywhere. The platform can be used from users from different countries that need to collaborate fast.
We selected headless CMS, because in terms of the steps to get started with designing the content types and content population, it was certainly quicker as a starting point. We did not have to install traditional CMS somewhere or get too deep into page types and their setup. Kentico Cloud enabled the content population to start day-one of the project. There is a wide range of SDKs available for all major platforms.
The solution is still maturing and the content authoring experience could be improved.
Enabled the rapid development of a dynamic Vue.js website, with the ability to scale further as required,
The best thing about Kentico Cloud is how simple their front-end is to use as well as how well-documented their API is.
With their constant improvement of their product, some things become outdated - such as taxonomies. This can become a headache if you are planning to use their API in your own system.
We are storing all our marketing website data in Kentico. The ability to have embedded content types has been a wonderful way to have complex data in our site and still store it in Kentico.
Manage All Your Content in the Cloud Deliver Content to Any Website or Mobile Application Provide a Personalized Experience Kentico Cloud—the Solution to Digital Agency Problems Great for large scale, client-updated sites
Slow to load Bulky to install Naming conventions are not consistent with industry terminology (doctype, for example) Can't directly import .net code in all cases, sometimes forced to use Kentico solutions which take more time to implement than just writing code to a code behind.
Automated content sharing - Most of the content sharing that we do (site-wide) is set up through a manual process. The ability (or knowledge on how to do this) in an automated fashion would be ideal, and is something that we've been researching since launching our Kentico-powered site.
Support is 24 hours. Live online which is great
It’s a little expensive which i my opinion
Easy and user friendly
The flexibility and possibilities. You can do so much with the product if you have the imagination. The ability to create granular content templates ensures consistency and helps writers focus on the research and words. Re-use of modular components supports single sourcing. Support is excellent and responsive.
We're wondering about scalability. The UI becomes cluttered very quickly when you have a number of pages that each have related resources. Filtering goes some of the way to helping with that but it doesn't show you anything that's mis-tagged. We're looking at using separate projects for different subject matter but how would we pull them together? Taxonomies for nested site maps rapidly become very cumbersome .
We're still in PoC, but we're seeing the way Kentico Cloud can help us to train our writers to produce more consistent content. The ability to single source and have other areas use that content in their workflows would help with information accuracy and consequently, brand trust.
I think the content modelling and editing interface is great. I am able to craft my content models very quickly and the interface is snappy. The exposed features such as "discussions" and "workflows" are very good.
I can't seem to find a way to programatically create webhook notifications for content model updates. This would be veery useful for IaC setups
- Content management - Static websites - Mobile app content - Small site administration
Some of the best things about Kentico Cloud is its ease of use, collection of connectors and boilerplates and its support level.
There's nothing major to dislike. Sure, there are some annoyances in the content editing flow and managing media items - but they are usually added to the read map pretty quickly so dont last for long!
Structured data separated from the design is key for a lot of customers. They can rest in the knowledge that their content editors can do their job without worrying about breaking brand or causing functional issues on the site. The speed doesn't go a miss either!