CoreMedia vs. Drupal vs. Live Center - Live Reporting

I think this CMS is best suited as an enterprise level system. For small, or simple sites, there are better options, but for large high-traffic sites, this is a great CMS.

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

As we have to show the highlights of our blogs in the main page of our website. We choose Live Center as here it is very easy to embed those blogs in the home page. Also, this embeding thing was done by content creator so we don't have to reach to developer always.

Incentivized

• Allows many staff members to contribute content to various portions of our website, and allows our Electronic-Communications staff to delegate tasks to these various staff (diffusing the work-load).
• CoreMedia allows for easy creation of different types of content (like teasers, articles, download objects, links, etc). Permission levels can be set, so only certain staff can upload content such as photos, videos, or audio files.
• The CoreMedia workflow process is easy to understand and follow. Once a staff member has submitted content for publishing to the web, they can then see who it's been assigned to for review, and at what time. You're able to leave detailed notes and stay abreast of where the workflow is at any given time.

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Early learning within the company was slow.
• We elected a customized version of CoreMedia - which in the end may not have been the best decision.

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

• The flow of comments could be improved.
• The ability to turn off auto updates on a live blog doesn't exist.
• Could add more reporting functionality.

Incentivized

CoreMedia continues to refine and deliver new features. They also explore new technologies and trends, like social media integration. The platform is solid and growing. We are also slightly locked into using CoreMedia. Migrating such a large amount of content to another system would likely not be feasible or prudent.

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Set aside more time than you think you need to migrate content. That is the hard part. Implementing the technology is easy.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

While CoreMedia has a better workflow, django CMS has a much easier user interface, wysiwyg editor, and is superior on every other level. Django CMS is easier to teach and support, easier to manage and develop, and provides much more flexibility in the development and design areas.

Incentivized

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Increased employee proficiency compared to nothing at all. I really don't have anything else to compare it to though.
• Reports from Core do not help/.

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs