Magnolia vs. PrestaShop

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

I really wouldn't recommend PrestaShop to every person or business. This service has very good features to be able to create an online store and allow customers to add products to their cart instantly, it allows to make electronic payments quickly and the money reaches the company's wallet instantly, without However, it has many disadvantages, PrestaShop does not have a technical service to help implement the software on the website, so if you are thinking of using PrestaShop, you must first have a good team of web developers who are capable of integrating PrestaShop with the Wordpress site without any problem, in addition, PrestaShop takes up a lot of space in the Hosting service, each product that you add to the PrestaShop catalog occupies much more Hosting space and this causes the catalog to take longer to load when the client comes to visualize it. To use PrestaShop I recommend a very powerful Hosting that is able to withstand the high consumption it has.

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

• Quite easy to use compared to other open-source e-commerce software.
• Has lots of free plugins to help you set up a great basic shop.
• You can easily create your own unique site.
• Lots of payment option plugins and you can use them to sell globally.

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

• Since it starts as ready to go platform it's difficult to protect your store from being copied by someone else
• Without a developer, you depend on Prestashop's modules marketplace that lacks free extensions
• Since it isn't an enterprise level platform the use of Prestashop is strictly related to the size of your business

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.

Considering the problems we had and still have, 0.

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

The lack of performance and the unstable system make it very hard to use it for a serious e-commerce application.

100s of implementation and so far no major security breaches.

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

Some caching and optimization is definitely needed. However, it is not as bloated as other CMSs with lots of plugins needed.

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

Since we use PrestaShop OpenSource there is only community support. What we found is that many other users fight with the same problems and there seems no solution or input from the PrestaShop developers' side.

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)

As compared to other open-source systems, PrestaShop has the most elegant backend interface. Most of your standard eCommerce features come default: 1. Invoice and Delivery documents in PDF, 2. Promotion and discount mechanism, 3. SEO functionalities, 4. Quick access, 5. Statistics, 6. Categorization, Brands, Attributes, Features/Filters, sorting, pagination, list or grid view. The next best thing is the stability of versions. Currently, at only ver1.7, this is the only open-source CMS that doesn't require the constant nightmare of updating and breaking the site. The open-source community is still offering modules for ver1.5, 1.6 and 1.7. If you need modules to enhance the features, it is also a one-time cost since the versions are so stable. The experiences with 3rd party module developers are very good so far. Most modules are from EUR49-100.

This is the best example of "If it's not broken, don't fix it!".

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

• If you don't have open source developers on staff it will be costly.
• The out-of-the box solution is not really a solution. Be prepared to hunt down modules to do standard things you'll want to do.
• The interface is unlike the e-commerce usual. There will be a learning curve and don't count on online documentation.

Incentivized