Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Meltwater
Score 7.0 out of 10
N/A
Meltwater Media Intelligence platform is a set of public relations software tools for media monitoring, social media monitoring, and collecting brand insights. The four areas of functionality are Monitor, Analyze, Distribute, and Engage. (Note that this product combines features from the vendor Meltwater's former Buzz, Press, and News products.)
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Meltwater is well-suited for agencies that have an engagement team who is looking to service a variety of client needs such as social media reporting, public relations outreach, and community management. If you're looking to have a platform serve just one need, you can still use Meltwater but will get more bang for your buck if you are needing a variety of tools.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
Media research - you can search for relevant publications and journalists to add to your media list.
Earned media coverage - you can search for coverage of your brand and find news stories that also include data that may be useful (how many people did the story reach for example).
Building media lists - if you have no current existing list, you can build and export one in Excel for example.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
The dashboards are not user-friendly, customizable (color, font size, etc.), or worthy of presenting to a client. All of the insights from a dashboard get pulled from the platform and placed into a more client-friendly presentation.
Paywalls for certain publications connected to who-knows-what. DowJones racket limits media monitoring capabilities and results in manual searches for a growing number of publications.
TVeyes, the broadcast monitoring arm of the media monitoring capabilities, just needs TLC and to become more client-facing. Currently, the links produced to share clips look sketchy, and they have a relatively short shelf life.
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.
Meltwater works well for our organization and has allowed us to meet our internal goals. We are always open to new products and services that may be able to provide similar or better features; however, our experience has been that many of Meltwater's competitors are not up to the task.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
Once you get some basic training it's pretty easy to use. I would like to see training manuals, or instructional videos to help me explore features I'm not currently using.
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.
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.
Our account rep at Meltwater went dark for a long time. Then, a couple of weeks ago, our new account manager reached out to set up a meeting. Apparently, they had a big shakeup in the company, and there were some personnel changes. Our new account rep was great in discussing the platform's capabilities that were available to us and even offered to schedule a follow-up meeting with his technical team to introduce our new social media team members to the platform and how it could help them with their jobs.
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.
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%
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
I was looking for a full-service option. I did some research. What really sold me was the presentation. They offered products that were helpful, and I wasn’t even aware of them. It is more expensive than the other products that are out there, but you get more. The other companies are good, but Meltwater Media Intelligence is more full service.
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.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
As a PR firm, we rely on the media databases that [Meltwater Media Intelligence Platform] supplies to deliver the media exposure that they expect from us.
We utilize their tracking of media hits for our overall reporting to our clients.
Both of these are advantageous in helping us to not only keep our existing clients happy but also to gain new clients (and, in turn - revenue), as well.
