ExpressionEngine vs. Magnolia

For someone with a limited budget, it's hard to recommend ExpressionEngine simply because of the cost of the license and any add-ons just to get up and running. As a developer, the budget needs to be a certain amount before I can even consider ExpressionEngine - no matter how appropriate it is for the site. Besides that, I recommend ExpressionEngine for those who have a lot of content, have a need for a certain level of flexibility, or who have special feature requests. There are a number of ExpressionEngine add-on developers who are willing to help build (for a fee) custom add-ons to fulfill that need.

Incentivized

If you need a business CMS that brings along a good amount of features and also give you the chance to develop features on your own, Magnolia would be a good choice. Even if you have not the fitting infrastructure around, Magnolia provides you different ways like SAAS oder PAAS. If you have to review your code our have any problems the team behind will helps in a short time. Without using the connectors it is not so easy to connect special functionalities like Marketing tools or optimization tools. The DAM is very slow if you have an huge amount of documents and pictures to store for your website - you have to add an external DAM.

Incentivized

• ExpressionEngine has no preconceived ideas about how your content should look or what code is generated.
• A robust template engine makes integrating designs and content a breeze.
• The control panel can be customized to control what content managers have access to.

Incentivized

• Use of YAML to define content models with code.
• Versatility of defining actions for custom handlers.
• Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.

Incentivized

• Can be too cumbersome for smaller projects, takes time to pair down the built in functionality so our clients have to sift through unused features
• Large queries take significant processing power, recommended use of a cache module to store this data and speed up page load
• Backend can be overwhelming for clients, lots of things to manage in the control panel
• No way to repeat custom page fields or groups of fields, meaning page layout must be pretty established and not customizable from the control panel

Incentivized

• As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time.
• Having a history of modifications not only at the page level but also at the Content Apps level would be very useful.

Incentivized

I'm satisfied with the way that my site runs on EE. My primary concern is that support is now a profit center for EE's publisher and so they've consequently gutted their community support boards. However, a good EE community is developing at StackExchange. At this stage, I don't think that EE is a good choice for an individual site owner. WordPress or SquareSpace would be a better choice unless you have a budget for support.

Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.

ExpressionEngine is very powerful and flexible. With this flexibility comes a bit of a learning curve. There are some great online resources for getting up to speed with EE, but the control panel can be a bit daunting. A lot of EE's installation process involves settings, configurations and flipping of switches. It is tedious, but well worth it as you ultimately have a very robust, secure and scalable CMS. Also, as of version 2.9.2, the control panel isn't responsive natively. You'll want to have a big enough screen to see the full control panel UI. Personally, I think the control panel would benefit from a major overhaul. It would be nice to see the colors and UI controls "modernized" and be able to more effectively customize the layout. Yes, some of this is built-in, and there are third-party add-ons to help, but maybe we'll see more refinement in future versions.

There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.

Incentivized

Never experienced an issue like this with it

Incentivized

The admin section would slow to a crawl the larger the tag section grew. There were many areas where better pagination would've helped improve performance. Nothing complicated, which made the lag so frustrating

Incentivized

It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.

Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.

Incentivized

I have personally never found any complications when trying to receive support from EllisLab in regards to ExpressionEngine when using the support plans they offer. I have always been responded to promptly and received satisfactory help with whatever my needs were in an extremely timely manner. This makes rating the support offered an easy job for me

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

After installing the system a few times, you can see a pattern of things that have to be done to work the way you want them (settings, paths, etc.). By knowing what you want, you can put together some scripts that prepare the file system for installation, adjust post installation configuration settings, and install initial templates.

ExpressionEngine outweighs most all of its competitors by being so flexible. If you can imagine it, then you can build it with EE (ExpressionEngine). Most competitors lock you in with certain ways to build your website or use only their tools; ExpresionEngine gives you the freedom to build how you would like and decide how you want your site to run and operate. The ease of use for clients to go in and edit their content is great, and I am able to control the way they edit that content to make it the easiest for them. The feature set and plugins for EE are great, and I am able to provide top service for my clients by using EE.

Incentivized

Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)

Maybe it's scale-able from the content user perspective, but it was very limited from the programmers perspective. So many custom hacks were necessary that it reached a point it would be impossible to upgrade to a newer version

Incentivized

• Being able to be recognized as a leader within the ExpressionEngine development community has led to us being sought out by those customers seeking expert guidance.
• We tend to specialize in using ExpressionEngine for our customers, so it has been easier to ramp new resources up on our development process, as well as be able to seek out independent experts to use as sub contractors or freelancers.
• As we have been using ExpressionEngine almost exclusively for a number of years, we have built a reusable repository of proprietary code that makes our development process much more efficient and decreases the effort required for our projects.

Incentivized

• We have placed web content management in the hands of the organisation than retained it within the technology team.
• We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
• The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.