Enonic Recenzje i szczegóły produktu

I was first introduced to Enonic XP7 when I was still attending Uni. The solution was easy to get into, as the stack uses languages and technology most are already familiar with. Now, after having used XP for some years, I am still satisfied, and the product keeps on getting better. There's always something new and exciting getting released for their product, and I can't wait what the future of this product will be. The staff at Enonic are easy to get in touch with, either on their forum or their Slack, and the community helps each other out with issues and problem solving. I have briefly used similar CMS solutions, like Optimizely (formerly Episerver). They ship out a robust product, which is too grand from the start. XP on the other hand, takes less than a day to learn and begin developing in, without any unnecessary overhang.

As with everything, XP is not perfect. The company and product have existed for years, yet some areas it's not as polished as one would expect it to be. I do miss having more restrictions on parts - how many are allowed on a page, or in which area you're allowed to place some, but not others. Also, there's a lack of configurability for the WYSIWYG-editor. I have found areas where I'd love to add custom fonts or styling to text, yet not being able to add new, just alter the existing ones. One solution of course would be inserting macros, but that's not the perfect solution to possibly inexperienced editors.

XP's tasks have helped me out a lot in a project, where it's scheduled to run daily and retrieve data from an external source. After having done so, it generates content based off of the data, and doesn't overwrite existing, yet updating the changes flawlessly.

An editor-friendly editor, quick access to all content on site with elastic search, flexible solution.

It annoys me a LOT that the browser spellcheck still does not work in titles.

We use Enonic as the publishing platform for an online news site with ads.

The layer structure fits our international company structure well and fuels collaboration between content departments. On the developer side I find that we have solutions to almost all of our wants and needs and it's well integrated with our visual profile. I like the overall flexibility; from working with tags for our content, tasks between content editors, the site and search function are super fast, moving and sharing content. As a content editor the platform works great.

The layer structure makes all the pages from the parent page visible on the "child" pages. I know that they're working on a fix for this in a release coming soon. I also miss Digital Assets Management, even though our developers have developed a similar function through the layer function which works almost just as well.

Our SEO work and ranking have significantly improved after we migrated to Enonic XP. The benefits with the layer function have been several as our communication team across countries collaborate closely and Enonic XP is just the right tool for us to share and collaborate on content and structure.

The total control you have of the metadata for your project. The structures give reusable data/fragments that are easy to implement for both developer and maintainer.

It would be best if you were a skilled javascript developer to start maintaining a project. It requires more of you as a developer, and it can be confusing that the server-side javascript doesn't support npm packages.

We are making a homepage for a political party. The reuse of fragments and data is the most significant benefit of Enonic. Accessible tools and wizards to start a new project.

It´s easy to get the hang of Enonic XP. As a content editor, you get a sense of endless possibilities. You can use templates or build pages by drag-and-drop. Together with a good developer, you can make almost anything. In addition, there are several useful apps on Enonic market. We use Enonic XP for our relatively small web platform and look forward to scaling up in the future. I like: - Issues management - Image handling - Version comparison Also, the team at Enonic is fast to respond, polite, and always very thorough. You get in contact with them and the rest of the community through Slack and the user forum.

- Some of the apps on Enonic market is quite simple.

We have recently moved our web platform into Enonic XP. Benefits: - Building pages is fast - Low-level content creators can use the site with ease - Up-to-date technology (headless) gives us many possibilities

I've been using Enonic for close to a year now. From what I've experienced, I've seen a lot of capabilities. Everything that I needed to implement I have found a clean way to do, and when not natively, you can implement a Java extension to do what is required. It's an excellent and versatile development experience. One really nice thing 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. 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 relatively fast.

- The docummentation is well written, but IMHO I believe that there is space to improve it with more examples; - The community is not huge since It's not a wide known technology yet; - There isn't a lot of apps in the Enonic market;

In the last company that I worked on, the team was using Enonic as the primary platform for development, building complex web apps using server-side javascript (or typescript). There's also room to do many cool things using modern front-end frameworks such as Vue and React, for example.

Enonic is versatile, robust and user-friendly. I love the hybrid approach, combining both headless and traditional editorial functionality. We use it for multiple sites at Gjensidige, and have successfully integrated it with our design system.

I would have liked an even bigger community, so please Wadyider trying it out.

We use it as a key part of our web platform for both internal and customer-facing digital services in four different countries. Works great on-prem and in the cloud, and both for developers, digital editors and content designers.

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.

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

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.

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.

- 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.