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
Microsoft Yammer
Score 6.9 out of 10
N/A
Yammer is used for private communication within organizations or between organizational members and pre-designated groups, making it an example of enterprise social software. It originally launched as an enterprise microblogging service and now has applications on several different operating systems and devices. The company was acquired by Microsoft in 2012.
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
Yammer is great when you have a company culture that encourages friendly collaboration and communication. It can be a great supplement (but certainly not a substitute) for bonding and sharing ideas and thoughts. Certain channels can be really successful, too, like a channel where people can post dog pictures or something fun like that!
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.
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.
Although the social enterprise network works very well, there is room for some slight improvement - such as the ability to attract users. By being part of the Microsoft Office Suite, it is offered as an "add-on" and many overlook it and see it as unnecessary at first. It would be smart for Microsoft to sell it as its own product so it could gather more popularity as a "social network".
Giving an option to filter results could be better as well as giving an option to turn off the "recent activity" bar on the home page.
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.
Microsoft is dedicated to continual improvement on Yammer. They realize the value that Yammer brings to the table with their clients. In the short time that we have had Yammer implemented, we are just now beginning to see the strong impact it has on becoming more effective and efficient around collaboration.
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.
Overall easy to use and intuitive, although limited in the possibility to personalize layout and look & feel of a site. Some functionalities are not easy to use, like document editing, but some others are quick and effective (posts and tagging above all). Performance and responsiveness of the Yammer site is typically acceptable, in my experience.
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.
We have never had to use the support for Yammer. The tool works well and we have not come across any bugs. User Interface is simple and easy to use, similar to other forum type products, thereby removing the need for any extensive training. Team members are invited in and immediately are able to start using the tool.
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.
Our team briefly used Salesforce.com's Chatter product before switching over to Yammer in 2012. While Chatter is essentially the same product as Yammer, it left much to be desired. Chatter's design was (and remains) clunky and difficult to navigate. Yammer is a simple, easy-to-use product that offers similar functionality as Salesforce's Chatter.
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.
My company is pleased with the positive impact Yammer has created departmentally and on an individual basis with work flow efficiency.
Adversely, most old and new employees are more familiar with SharePoint, causing the company to pay for training for all current and incoming employees.
As Yammer becomes more widely used, the need for training may diminish, which is where we will see our return on investment, as the product clearly provides a more effective form of file sharing and communication between employees and their department.
