Magnolia vs. Oracle WebCenter Content

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

If your company is large and uses other Oracle products, Oracle WebCenter Content is probably a worthwhile investment. It integrates well with other Oracle applications and has the potential to help automate some of your existing processes. If you do not use other Oracle products, I would say there are better alternatives out there that are probably more user-friendly and cost effective.

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

• It provided one single repository with a URL link to access each AP invoice.
• It gives a life cycle to each invoice where a business user can perform some additional indexing as per their needs.
• It also provides a reporting feature and a front-end for users to view invoices with ease and very helpful for auditing purpose.
• It uses the BPEL engine to customize the life cycle and also it can automate the auto entry of supplier invoices in your EBS system.
• Reduce a lot of manual efforts, manual errors and workforce.

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

• Any images in the emails sent by suppliers (supplier logos in the signature) are treated as invoices by WebCenter Content software.
• We have an invoice with 4 lines and each line has its own project manager. Ideally, each invoice line should be sent for approval to respective project managers. However, WebCenter Business Process management was sending all the lines to all project managers.
• The user experience of Oracle WebCenter Content can be drastically improved. It is not up to the mark.

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 challenges with converting to a completely new system create quite a barrier to switching to anything else. If we find another system that offers guaranteed improvements to the user interface -- as well as as a more coherent set of options for data interchanges with current and future enterprise data sources -- we would be more interested in swithing to that new product. Of course, the expense in purchasing competitor system, along with the costs of migrating all current content, along with retooling all existing workflows in place, would be carefully weighed against the benefits incurred from a switch-over.

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

It meets all required functionality requirements -- but handles none of them in an exceptional manner

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

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

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)

We were looking for an automated invoice processing solution. As we are already on Oracle ERP, it made sense for us to go for Oracle Fusion payables with Oracle WebCenter Content. We have a good relationship with Oracle and Oracle promised us priority support during the time of implementation.

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.

• When integrated with a system like Biscom, WebCenter Content makes document capture, retention, and archiving much more efficient and cost-effective.
• When integrated with a system like Siebel CRM, WebCenter Content makes communications with customers/leads more efficient.
• Leveraging the robust content authoring capabilities has helped our web clients reduce the amount of involvement required of IT services during the normal course of web content authoring and management.