Magnolia vs. Salesforce Experience Cloud

Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.

For well-suited, this product is great for your external clientele groups that you would not necessarily want to have a high user fee rate for. So basically general public or a group that will be authorized to come in and just do a few things here and there, but you don't necessarily want them access to all of your systems and your data points for groups that it would not be a great use for. I'd say probably your high level internal staff, they're going to be using a lot of the backend functionality automations, evaluating data, managing data, and doing custom inputs. That's just not what's intended for.

Incentivized

• Speed of development - time to delivery from zero to MVP was excellent
• Ease of use - the authoring experience is very easy to build and train
• PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.

• Complete integration with the Salesforce ecosystem. Data displayed in your Community portal reflects records from a Sales Cloud organization
• Highly customizable. A Community Cloud portal can be totally customized both visually and with different funcionalities with little to no coding skills required

Incentivized

• The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
• The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
• Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
• Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.

Incentivized

• The documentation for implementing Experience Cloud can be a bit confusing as their rebranding hasn't made it's way into all articles, resulting in different terminology being used to refer to the same thing
• Some things are not as intuitive regarding their customizability, so there's a bit of a learning curve (i.e. Lightning apps can't be used to customize layouts in Experience Cloud)

Incentivized

We have invested a lot of time and energy into tailoring a solution that works for the company.

We think the new features in v6.2 will help us get to the next level

We also don't have the resources to rebuild a website platform from scratch even if we wanted to

Incentivized

We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.

Incentivized

Usability is pretty streamlined, especially if you're familiar with other Salesforce products, but even if not, take it from me, as I just entered the technological space about two years ago, that this product is pretty simple to learn. You don't have to jump in with your head underwater. Small wins and learnings along the way are what foster long-term understandings and enable your evolution alongside the product. I definitely recommend Salesforce Trailhead along with it

Incentivized

I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.

It's delivered on our original requirements and we've found ways to grow its usage. We continue to build on our original success and we can report our data out to leadership to show a true return on investment which is great for growing support and expanding uses for the system.

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

We have weekly calls with our Salesforce reps. They bring new ideas to the table and help with taxonomy builds. They have also answered many questions and connected us to the right people for us to grow our knowledge and utilization of the platform. They are a good partner overall in comparison.

Incentivized

I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.

Incentivized

Salesforce Experience Cloud was selected due to its tight integration with our existing Salesforce CRM platform. Customization of the portal was much, much simpler compared to Sharepoint - especially with role-based security parameters that are ultimately inherited based on attributes within the Salesforce CRM platform. Salesforce Experience Cloud was a natural fit for this customer-facing purpose.

Incentivized

• Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
• The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
• The templates makes the whole process easy

Incentivized

• Improved online admission application completion rates from mid-60%s to mid-80%s.
• Positive user experience from start-to-finish to leverage one data system for all prospective student data
• Fewer data integrations transforming and loading sensitive student data by leveraging Salesforce Community Cloud to access already existing data

Incentivized