Enonic is a leading digital experience platform that helps businesses create and manage their digital presence efficiently. It combines powerful tools for content management, commerce, and data management in one platform with core features that include an intuitive content editor, headless commerce, and robust data management capabilities. By using Enonic, businesses can streamline their digital operations, save time and resources, and create seamless and personalized digital experiences for their customers.
Capabilities |
|
---|---|
Segment |
|
Deployment | Cloud / SaaS / Web-Based, On-Premise Linux, On-Premise Windows |
Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
Training | Documentation |
Languages | English |
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.
- 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
My favourite part of Enonic XP is the flexibility the platform provides and the helpful community on discuss.enonic.com and their Slack community. Enonic XP can be used for both small, medium and large websites, in both a traditional monilithic way and pure headless, or even a hybrid. This makes the platform perfect for us, at it allows ut to build user-focused experiences without being forced by the platform to do things in a particular way. Our developers love being able to choose wether to code in pure JavaScript or TypeScript or even use frameworks such as Vue or React. The content editors also enjoy the freedom and flexibility of Content Studio, allowing them to either use templates when building content, or engaging their creativity and make a completely different page optimized for a particular use-case.
The documentation could be better and include more complex examples. It would also be nice if there were more apps on market.enonic.com. Even though Elasticsearch is great, the version bundled with Enonic is not the newest, and we would love to have more access to the index.
We use Enonic XP hosted in Enonic Cloud to help our customers serve their users and customers great online experiences. Ranging from corporate information sites, through webshops to intranets, Enonic XP can do it all.
I like the user interface, it is easy to learn and easy to use for me as a web editor.
I'm not sure if I have any specific down sides, but sometimes it can take a while for Enonic to develop features we ask for thru our partner. But they listen and take our suggestions into account.
We use Enonic XP as our CMS and are very satisfied with the product. Our partner Bouvet handles everything so we don't really contact Enonic that often, but we do attend some webinars and have yearly meetings.
Lots of possibilities. Dynamic. Good user interface
We experience sometimes that errors appear, and that it can be hard to see where to adress it - whether it is Enonic or the developer.
We have more control over the content and what to put on the index page e.g. It's more flexible and gives us more possibilities.
The Enonic platform makes it easy for developers to write custom code that suits our customers.
The documentation can be better written and documented.
Content Studio is the content management interface the Enonic platform features. It is both editors friendly and provides advanced tools for developing.
Efficient and easy to publish, nice lay out
No downsides, and I do not miss anything
Efficient and straightforward internal communication channel
The possibility to work in the same CMS for more than one member of same team when you have several sites to administrate. Makes the job faster and easier.
Nothing special, would like to have help for several languages - but I know this will come in the next version.
We have one website with 4 different languages and 3 other different sites that my team is responsible for. All of us can login at the same time and see and do updates in one place. Saves a lot of time and frustration we used to have with our old CMS, logging in and out and not being able to see what changes we did, which we need to do at the other sites.
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.
- 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.
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