Clickability (discontinued) vs. Magnolia

I think Clickability does a good job of organizing all the elements in a webpage. You clearly can choose what and where you need to be, via tabs. Some functions are redundant and cumbersome. Like switching an ad placement. We have a, b, c positions and it should be easier to move them around. Currently, it is not. You have to re-create the entire ad, with a different position. Not efficient.

Incentivized

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

• The ease of search for items by ID makes finding something quick and easy.
• The system moves very fast, which enables us to respond to breaking news and get content up on the site quickly.
• Making copies or opening read-only versions of stories are great so that one person can read while another person produces.

• 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

• 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

• 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

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.

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.

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.

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'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

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.

I have mainly worked with open source content management systems like Wordpress, Drupal and Joomla!. Clickability is far more customizable and elegant to code things yourself. The main downfall of Clickabliity is the lack of community developed modules and plugins. If there were developers creating these of wide spread use, Clickability would be a must have for any business.

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)

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

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