Clickability vs Magnolia

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

Read full review

• The usability of Magnolia is appreciated, a content editor easily learns how to manage the content in two hours only.
• Magnolia is open, flexible and extendible and it is possible to modify or improve the standards features. Using Java API, REST, SOAP, CMIS, XML, etc. makes it possible to integrate other software or legacy data.
• Magnolia as a modular architecture, a module has its lifecycle, configuration, version handing and dependency: this is a good approach for package content and functionality.
• Magnolia is written in Java, the platform of choice for enterprise IT systems. It is scalable, stable and secure, and Magnolia separates the staging from public environment.

Read full review

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

Read full review

• Give users specification details and or tips for module items and fields (ie. explain what the fields would do to the front end-user)
• Batch upload drag and drop for assets/images
• [The] simpler way to find out the URL of a page without publishing for both EN/FR users
• No way to revert to past versions of a page that hasn't been published live
• A way to copy a specific module on a page with all the fields and settings completed and paste it to a different page

Read full review

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

Read full review

• Has provided our organization with an easy-to-use CMS. Even inexperienced web page builders can create content.
• Has allowed us to create a bilingual website that reaches a large audience while meeting language requirements.
• Common templates have allowed us to create a cohesive website.

Read full review