Hi Angela In order to give an answer I would like to ask you some quick questions:
- Is your organization going to maintain the CMS by yourself or is the web agency going to maintain it or a combination? - Do you have internal human resources which are familiar with Java? - Is the CMS going to be standalone or being integrated with third party systems, like for example your association management system? - Is continuous integration/delivery/deployment also a requirement? To have some transparency I should mention that I am neither associated with Magnolia, nor DotCMS nor Drupal, but with Yanel, which is also a Java/XML based CMS, but I think the above questions are rather important if you want to do a long term investment. I have some experience with Drupal 7 and Magnolia though. Thanks Michael Am 09.04.15 um 21:59 schrieb Angela Miller (via Magnolia Forums): > Hoping you can offer your honest opinion on Magnolia as your CMS. We are a > 100 employee not-for-profit, but happen to have a java back end for our > association management system. We are going through a website redesign > discovery project and analyzing CMS options. Our agency is promoting Drupal, > but since we have a java back end we are also exploring Magnolia and DotCMS. > Can you offer your insight into pros and cons of Magnolia? Why did you choose > Magnolia? Have you worked with others... or have some solid reasons why they > werent the riht choice for you? > > Appreciate your feedback. This is a big investment for us and want to make > sure we love (or at least really like) the system we marry. :) > ---------------------------------------------------------------- Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
