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
Sysomos, now part of Meltwater
Score 8.5 out of 10
N/A
Sysomos was a social media listening and marketing solution for content discovery, planning, publishing, moderation, and analytics. Sysomos was acquired by Meltwater, and is no longer available, but the features of the former Sysomos are now part of the Meltwater platform.
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
Sysomos Expion is best suited, in my opinion, to offices where either you have only one moderator/manager OR where multiple users plan to manage a specific channel. Without live updates, it gets far too complicated for multiple users to manage the exact same workload
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.
Ad-hoc research. During planning phase of a campaign it is a helpful tool to understand the marketplace, key influencers and topics that engage a target demographic.
Post-event hashtag analysis. Rapid generation of reporting on efficacy of a campaign, key voices, topics that resonated, viral reach and more.
User interface. Friendly and accessible enough to minimize training needs and enable decentralized access, though we have found some hand-holding is still required to get the most out of the platform.
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 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.
There are two differentiating features that Sysomos MAP has that the competitor tools I have experienced (Radian6, Meltwater Buzz) did not: user-friendly Boolean queries for searches and near-real-time results. The former is important because, of course, your results are only as good as your search/campaign. With Sysomos, once you master Boolean queries (which isn't terribly difficult) you're set for creating any kind of listening report. I strongly prefer this to the "campaign creator" forms that other services provide. Second, Sysomos MAP returns results almost immediately - like a Google search. So if you get your results and see that you need to tweak your query - no big deal. Or if you have a last-minute request for a client - not an issue. Meltwater can take up to 48 hours for a search to fully populate. This is a major issue if you get your full set of results back and see that you need to adjust the query; you're looking at another two days of wait time. A long wait on results can also prove problematic in agency settings where clients or prospective clients often need results with a quick turnaround.
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.
The product is very easy to use. The platform is visual and data is easy to read. Boolean construction can sometimes be difficult, but the boolean constructor tool is helpful for boolean beginners. For more experienced boolean constructors, the boolean display at the top is very helpful in identifying where there may be holes in the construction
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.
Unfortunately, we have not had a great experience with customer support from Klear. In the sales process, they were very responsive and helpful, but when onboarded, it definitely changed. We are based in the US and our customer service rep is based in Israel, meaning our work hours barely overlap. Oftentimes we're waiting 24+ hours for a response, and when it's a time-sensitive issue (like the platform not pulling in Instagram Story data) we want it to be resolved as quickly as possible. Klear also has a chat feature for more immediate help, but we've experienced a similar situation there where it takes 12+ hours to get a response and it's usually from our customer service rep. Our rep is very nice, but also doesn't seem very knowledgeable about the platform, and usually can't provide an immediate answer to a question we ask and has to "check with her team."
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.
We've used Sprout Social & Hootsuite in the past -- and they all stack up pretty evenly. Sysomos has the same features as Sprout or Hootsuite, except their reports and analytics are a little more detailed. Hootsuite has a better social media management software and dashboard though
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.
