Enonic Reviews & Product Details

The now proven transformation from a traditional CMS with many limitations, to a now fully flexible build-anything platform that runs well in the cloud. We are now moving from on-premise servers to hosting in the cloud with very little effort.

The support community, mostly on Slack, is excellent. If anything, I would love to see an improvement in tutorials and code examples that could inspire us to take more advantage of the platform.

We run several web sites on Enonic, many with fairly heavy traffic. It just works, in six years we have created fewer than six support tickets.

Enonic is easy to set up, administrate, and easy to learn for new content editors. It has a lot of flexibility and is fast to update.

It is still not possible to schedule already published content for changes. It would be great to be able to hide certain functionality, especially for content editors with few and very specific tasks.

Compared to other CMS platforms Enonic XP is faster to learn for content editors, and our developers also use a lot less time to develop on and update the platform.

The architecture is nice. I like that most of the necessities are wrapped in the installation. Everything from webserver to login. The ability to use ecmascript in the backend is nice.

The upgrade process could be better. It should not be necessary to have two entire clusters of servers to upgrade a CMS to a new version. Also, it should be easier to upgrade one site at a time.

Have built a nice set of sites. Providing editors with the tools needed to create and manage sites across Europe.

Adding new functionality to a site is quick and easy. XP makes for a flexible content tool, and allows us to build solid websites with a high level of self-reliance in our editorial staff. It integrates well with existing ecosystems. Having close ties with the developers and a short feedback loop is very valuable to us.

Using modern javascript tooling is possible but sometimes clumsy. We have React components working, and we use Typescript, Webpack, Babel, etc, but there is some overhead to the build pipeline. Build times are very fast out of the box, but after adding all the necessary layers needed to get these features working, we see increased wait times.

We use Enonic XP to import data and display new and updated content automatically. We use Content Studio to allow many users to edit and work with their content directly and in a faster way than before.

I like the UX which anyone with a tad of prior experience from blog systems and wordpress-like systems will reckognize. Important for an organization like ours that it is offered in Norwegian. That helps our editors a lot.

I would like for it to scale traffic peaks on the servers better. Also it could be better at differentiating user levels, restrictions and access. We have a multi layered organization and need to use a different system to manage user access and authentication. I would urge Enonic to find solutions to hide or disable read only content from the cms. I understand that this may be an option in some content project, but has not been installed/developed on our site.

Enonic offers our organization a tool for a nationwide organization with a lot of non-professional users. This seems to flow well after som time online. Enonic is the CMS for our most important com-channel to our customers and the outside world in general.

- Very agile platform based on javascript that's easy for developers to use. - You're up and running with a server in a few minutes and it's just works. Migrating and exporting data is easy too. - Lots of plugins / Apps on the markedplace to solve common usecases like GA/GTM, SEO ++ - Forum and slack-channel for communcating directly with Enonic staff and other users and enterprise support option - Cloud based subscription - Open source and free

- Upgrading to new major versions requires a lot of work and testing and the more applications and sites you have the longer each major upgrade takes. - The backend implementation of how data is stored not optimal resulting in an ever growing folder of files and folders that are not in use. - None (or few) out of the box sites to use. You have to setup/develop everyting from scratch. - Content Studio feels like it's made by developes for developers and can be hard to use in some cases

One platform for all our cms needs and a more streamlined development processes.

- Easy to use across the team (from developers to content creators) - Easy for developers to develop content with javascript/typescript - Powerful built-in APIs offers a variety of great functionality - Lots of great plugin options on the marketplace - Excellent and fast support

- Long build times while developing - Small community - Breaking changes not always specified in release notes

We use it as part of our web platform that contains editorial content

Users can manage their own content for their website.

No standard way to implement certain things, little example code or explenation from libraries which are not standard

Custom webpage administered by non technical people