Unclaimed: Are are working at Enonic ?
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.
( 1 )
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 |
Compare Enonic with other popular tools in the same category.
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
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.
Integrate Web-Applications based on React into our homepages and build dynamic webpages
It is a very open system and has a lot of relevant logic within. For our editors it is easy to understand and to work with. I also like the fact that it is PWA compatatible
The market place for add on could contain some more add ons.
We have built a media platform for all clubs in the top two divisions in soccer in Norway. All clubs have their own identity and share all concepts when it comes to design, modules and integrations. It is a system that is easy to scale as well as reuse for several different clubs.
- 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
- Developers can experience a bit long build times (if you are using the WebKit starter). - The community isn't very large.
As a developer, I make both web pages and web applications with Enonic XP. I think I can work very effectively to create robust and enjoyable applications for my customers.
Enonic allocates an extended range pf digital experience tools that makes it easy to create and design websites.
Domain registration at Enonic is a bit expensive compared to Namesilo, but I point it via nameservers and DNS.
It makes it straightforward to manage website contents. Website design and development.
XP is very powerful and yet flexible. It is really fast, it scales. It's also a breeze to setup locally. That it is built and documented to be molded into your liking is something that helps us adopt it across a broad team of developers with different preferences. It's JavaScript core makes it just a matter of reading about the APIs to understand how things work. You can use the CMS for rendering, go hybrid (my preference), or all headless. The docs are solid and gets you up and running, the community is there to help. Enonic as a company feels more than willing to implement feature requests and bug fixes, its always been a very fast and pleasant communication with the core team. The core developers are active in the community, you get first-hand insights and advice. Frequent releases with each having a rather big impact for both editors and developers. A small but feature-full ecosystem, you'll find stuff on the market for most things you'll need. The Page Editor is nice, you edit parts of your page with drag-and-drop and editors love it. For developers the way you built apps feels solid, each file and folder has a meaning and you need to config next to nothing as long as you learn the structure. Enonic CLI is a great addition for developers.
As all big platforms there's an overwhelming amount to understand and know about the platform to use it best. Feels like people tend to start using it in an odd way, making them gain less from the full potential. Docs can sometimes be too brief in some areas, or contain small errors that are hard to detect for the untrained eye. Getting expert developer help for longer times on the platform is very difficult. The Html-editor feels outdated where even Wordpress has been a smooth editing experience for many years, Content Studio's editor have very limited features in comparison. The Nashorn engine will be removed soon, it's been a pain point that everyone works around anyway. Also some long-missing features: you still can't do custom input types, custom html styles/classes in the editor, control where uploaded media goes, image handling is sub-optimal, can't schedule publishing of modified content, co-edit content.
We run multiple custom facing websites, also intranet. Usually a lot of React apps running in the middle using Enonic to stitch everything together. We run everything in Azure using Kubernetes.
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.
adoption of languages - fragments and having access our DAM directly in Enonic
Nothing to dislike so far. We are happy using Enonic XP
Sharing content between country-sites, easy publishing
Efficient and easy to publish, nice lay out
No downsides, and I do not miss anything
Efficient and straightforward internal communication channel
I like the flexibility of the Enonic. You can choose from several approaches how to use the system. We, for example, take advantage of the Headless CMS, where our client part is created in Angular. The definitions of the content structures are entirely in our hands and can describe both simple and very complex data. I like the market which Enonic offers, where are many useful plugins and projects prepared for downloading. I also like the Guillotine query editor which is provided by Enonic and where you can tune your GraphQL queries. One of the real benefits is the Enonic support, which is always very fast and helpful.
We would appreciate setting the specific access rules to specific editors in Content Studio. Some people are responsible for a part of the content, but we cannot give them access only to the data they need to edit. Sometimes the Enonic documentation is out of date
We were creating a new Intranet system for our company, and we were looking for a modern opensource CMS with WYSIWYG editors. Enonic provided us with everything we required.
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.