Clickability (discontinued) vs. Magnolia

As a true content management system it is great for site and content creation. It does need some help when it comes to adding functionality for using modern code systems that require server side scripting. For a marketing or public company site, it is an ideal CMS. For a SAAS type site, there could be many road blocks.

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.

• Easy to get going for a business that has tons of content they need to manage.
• Clickability offers development and design services so you don't really even need IT.
• No need to worry about server uptime, storage, bandwidth, etc you have all the reports at your fingers for what you are using.
• Simple template and content design system, easy to expand and add.
• Powerful CMS and settings with a design and programming guide provided.
• AkAMAI and Limelight CDN's can be used for powerful and fast loading in many regions.
• Debugging tools to see how long specific templates and content load is exceptional. One can narrow down that this specific template ran X number of times and took this look and had to be stopped at X number of time due to exceeding set limits.
• Having a built in Dev, Staging, Production environments for testing makes seeing new features and how they will integrate into your site seamless.

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

• Choosing ad size/placement should be easier than it is. Now, I have to re-create the whole thing.
• When you "save" anything a pop-up comes up that is redundant.
• Ad list only shows a limited number. It's not until you click on one and cancel it out, then you can see all the listings. A bit tedious and redundant.

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

As mentioned in the last questions we are going to use a competitor brand next year. I think the issues are trying to find and fix problems from the previous programer. The steep learning curve and lack of mobile and social sharing capabilities. Things that I like are the strength of the programing which comes with a trade off. The ease for those who don't know markup to make updates to the website. Clickability isn't the easiest and can be difficult to find the content that you are interested in. We will not be using it next year.

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

My experience with Clickability has been mostly positive but there are a few areas for improvement. It's generally easy to learn and use on a daily basis. I can move fast and do my job with speed with needed. But there is some clunky functionality with targeting and page building. My rating would be higher if some improvements were made.

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

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.

I found that some agents were better then others, usually you have an account representative and that I would consider level 1 support. To get really complex answers you need to talk with an engineer.

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

Overall, it was pretty seemless to switch the sites over.

Many of other content management systems similar to WordPress need custom installation. The server costs and upgrades quickly add up. Clickability while expensive, eliminated the overhead of managing all the dependency needs for a CMS. Clickability also works with its clients to understand the business needs and proposes the solutions accordingly. They have a good support team.

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

• I know a big positive is the fact that it is always-on. We are the leading news corporation for our state, and in many markets, nationwide. We pride ourselves on our strong ethics in the community and thus need to exude reliability to maintain the trust of these communities. Having a website fail periodically erodes that reliable perception.
• It has allowed different areas of the company to approach our team and work in a cohesive manner.

• 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