Founded in 1997 with a vision to create the first truly open content management system, Magnolia is presented as a fast way to launch digital experiences. With a mission to help clients move fast and stay flexible and boasting users among brands like Atlassian and The New York Times, Magnolia DXP supports industries ranging from automotive to telecommunications, offering enterprise features and headless agility to help them stay ahead. From humble beginnings in Basel, Magnolia's…
N/A
Salesforce CMS
Score 8.2 out of 10
N/A
Salesforce Marketing Cloud Personalization (formerly Salesforce CMS) is a hybrid CMS allowing users to author content once and deliver it anywhere, in or out of Salesforce. Users create content, define content access, and define channels so they can share content and limit access to appropriate contributors. For an experience built with Salesforce, users can choose from two of the company's “what-you-see-is-what-you-get” (WYSIWYG) tools: Experience Builder and Commerce Page Designer. If the user…
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.
Salesforce CMS is well suited for anything sales. If you need information on an account, want to touch your old accounts, need to get a better idea of ownership by vertical, or want to estimate revenue from your pipeline, it is very A-OK. We use Salesforce to open, close, and study prospects to later convert them into closed deals. There is a section for notes to detail about each and every account. You can add contacts in, complete with their title, email, cell phones, and other additional info, and since our program is sync'ed up with Outreach.io you can make an immediate call from the Salesforce page. It's a must if you are growing your company and want to stay organized within multiple departments.
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.
Easy to use, just like Salesforce's other products. Many users can sit down and figure it out in no time, and with a little training become power users.
Fast and secure - Salesforce is a leader in the cloud world so you get consistently fast results and security that is top notch in the industry.
Accessible from anywhere - if you use cloud CMS already this is a no-brainer, but for those that do in-house CMS still, this is a major difference. Mobile access from anywhere on the planet without a VPN is something you just can't do without the cloud.
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.
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.
It's super awkward if you aren't familiar with it. I have several years' experience in both my organization's salesforce as well as others and there are still things that trip me up. I think Salesforce can get to a point where it's TOO bloated with all this information, all these integrations, what-have-you, that it can be difficult to find what you need in a timely manner or it creates a hiccup in workflows that you then have to work around. On the other hand, once these issues are identified, there is the possibility to manipulate Salesforce into creating automated workarounds. So, at least it allows for that. I think it's an issue of having so many options for bolt-ons that you start to lose perspective and functionality. You tend to lose focus on usability for users.
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.
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
I'm not sure - we have hired a person/team that are Salesforce Admin so when I have a question or need support I go in-house. But, I know Salesforce has incredible L+D and trainings available for free to help users develop in their skillsets.
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.
Salesforce has a wide variety of services and its user interface was easy to understand and use. Our teams [thought] Salesforce to be better. When we were comparing the features as per our Marketing and Branding teams needs and uses, Salesforce came out on the top.
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.
