Joomla! vs. Magnolia

It seems with the release of Joomla! 4 that the weak areas have all been covered. Its always been good for the mid-level small to large business, the blogging was WP, and the large-scale enterprise was probably bespoke. But the new interface is so simple it seems pointless using WP when Joomla! is as easy and can then grow as big as you like. The Workflows feature which allows you to set up work pipelines easily is going to be a boom to any larger enterprise sites. Couples with the new API which I got to see at one of their user groups, is amazing. They were creating articles on one site then another site was taking the feed directly for just certain categories. Really blows your mind what you could do with that and the new workflows.

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

• We use Joomla to build our websites and web applications because of its incredible intuitiveness and tools to make everything more manageable.
• Its working environment is quite comfortable for my development team, and its web design resources significantly speed up our work when carrying out web development projects.
• It allows you to use blocks to create and visually manage websites and divide them into different categories without programming knowledge.

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

• Updating was never as seamless/easy as it seems to be with Wordpress. Obviously we accounted for this with our own workflow/methods, but I remember whenever we did WordPress updates it always seemed a breeze compared to the time/energy involved with a Joomla update/upgrade.
• For a while (I think this has changed some) Joomla left itself open to attacks when administrators were not as well versed as they should be. There were developer additions that did security checks/audits for you, but the CMS was the subject of a lot of attacks when left in the hands of our clients for a long time (who had changed permissions to make editing easier/convenient). Ideally the CMS would have been more restrictive on some of these things to prevent easy abuse. Obviously this is more the fault of the misinformed/human then the CMS, but it could have been more dummy-proof.
• No native versioning. There are some community extensions that add this functionality, but they pale in comparison to the versioning plugins of other CMS's (WordPress specifically). Again this was some time ago and in our experience, it could have changed by now.

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 gave it a rating of 10 because I just love how Joomla! works, how it is set up and how it handles many users. Also it is very fast, and there is no overload on the MySQL database or servers ever.

Incentivized

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.

The user experience and interface are good, but sometimes it is down. Delayed in the loading speed. Workflows can be simplified, and understanding templates needs much time. It is user-friendly and with multi-language support. Users can be added to the groups, which is easier. User controls can also be created based on role-based permission.

Incentivized

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

Today's Modern Joomla performs very well and is robust and durable. The pages load faster than they ever did in the past and Modern Joomla's integration into other software or systems has become seamless. Modern Joomla sites will last long and will stay running forever.

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

Between the core Joomla developers who are excellent at answering questions and providing support, you have a whole community of developers who work with Joomla and are happy to help fellow developers out answering questions and supporting the Joomla project. Out of the many communities I am involved in for open-source software, Joomla's community is by far the best.

Incentivized

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

It is good if you know Joomla! if not it can get a bit confusing

Make sure that PHP.ini is set to at least 60 ms for computer priority, 60MB for maximum downloads and 128MB for uploads. This is the minimum. It is best to run Joomla on a business host if you are using a shared hosting environment so that there are fewer accounts on the server. Make sure you have access to the root on CPanel. Be sure to point the DNS to the host and set up all zones prior to implementation and run your new version in a sub-domain hidden from the live version until you are ready to cut over.

Joomla is a very stable and secure CMS platform that ranks about in the middle of the pack with the other 'modern day' CMS systems out there. It's not as complex and frustrating as Magento, but it's also not as easy or robust to work on as WordPress. Thankfully when we do utilize it, there's still an online community our we can bounce issues and ideas off of.

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)

• Deploying Joomla! for clients has helped them discover the benefits of using Open Source software while helping them appreciate our expertise.
• Because the Joomla! community is smaller than the WP community, we are able to reach a wide range of clients looking for experts in the software, boosting our bottom line.
• Occasionally a client will find Joomla! too complicated and wish to move to a proprietary DIY CMS, which we do not support, so we have lost clients looking for that level of flexibility.

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.