Enonic

Pros: I've been using Enonic for almost a year now. From what I've experienced I've seen a lot of capabilities. Everything that I needed to implement I've found a clean way to do, and when not natively, you can just implement a Java extension to do what is needed. It's a really solid and versatile development experience.

One thing that has been really nice is that the support through Discuss forum and Slack works very well, and you talk directly to the skilled and friendly people who are developing the features. I've never been stuck for more than 2 days in something "out of the box" that I had to implement because of them.

The last thing that is worth mentioning is that the learning curve is not high. The idea of development is a bit unique, but once you understand it through the documentation, you can become productive with Enonic really fast.

Cons: It is not a wide known technology yet. For some developers, this might be a bad thing because they'll be investing time in something that they, at the current moment, are probably not going to be working with in other companies.

Overall: My experience with Enonic has been great, and I'd like to keep using it in future projects. The only thing that concerns me a bit is that it's not a wide known technology yet... but I'm sure that they are growing and working on it too.

Pros: - Good balance between being powerful and easy to use
- A very "full featured" CMS
- I can develop in TypeScript (or JavaScript) with the npm ecosystem backend too, but use Java in cases where library support is better in Java
- I feel I have to good palette of tools to create good experiences for my content creators in Content Studio

Cons: - Developers can experience a bit long build times (if you are using the webkit starter).
- The community isn't very large.

Overall: I'm a web developer, and Enonic XP is my CMS of choice for most of my web projects. I think XP enables me to create very robust web pages and web applications.

I think it's a fun platform to work on!

Pros: Enonic is easy to learn for users, developers and operators.
It is a modern, light, modular CMS with a lot of features and flexibility.
Integrating React-components for the frontend is easy. Server-side-rendering is part of the solution and implemented by setting a parameter. enonic does not need a separate database and elasticsearch is used for indexing the content.
Other powerful features are:
- query, filter and aggregate data
- define properties on site , component and content -level with xml-files and generate forms for users
- define layouts
- page composition
- image-handling (it is possible to process images in real time, e.g. resize an image)
- APIs for everything
- Multi-Site Handling
- enhance features through apps from app-store
- exporting and importing content
- and a lot more

Cons: There are currently no integrations with eCommerce-Solutions.
For React the Integration with UI-Frameworks like Material-UI or Chakra-UI (or any other frameworks based on Styled Systems) is currently not possible. For SSR nashorn, which is deprecated is used. Migration to GralVM is on the Roadmap.

Overall: We have experience with different CMS (or nower DXP)-Solutions since 2004. We operate websites with different market-leading solutions. We will migrate all of them to Enonic. As we do not have a shop, Enonic fits best for our use cases. It is flexible, feature-rich and user friendly. Although it is open-source, the support is very good. There are no limitations in the community-version as with other vendors.