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 365 Business Premium
Score 8.9 out of 10
N/A
An integrated solution, designed for small or medium-sized businesses, bringing together the productivity of Microsoft Office with advanced security capabilities to help
safeguard data from external threats and help protect against data leaks.
With Microsoft 365 Business Premium, users can empower employees to be productive
anywhere on any device. Get more done with AI built into the Office apps. Work
better together with a hub for teamwork bringing your tools and people together
in one place.…
Drupal is similar to WordPress when discussing content management and WYSIWYG capabilities. That is where the similarities end from a functional standpoint. WordPress is a top contender for blog sites, whereas Drupal is for sellable content, i.e. products and services. Both …
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.
Microsoft 365 Business Premium is well suited to any size organization and is a must-have for business purposes. It is a vital component for the majority of work software needs, as the Microsoft 365 Business Premium package has apps to handle needs that I didn't know we had. It is a great way to provide the required software programs to teams, especially those that work remotely due to the great sharing capabilities built into it. Furthermore, the nonprofit program provided our small nonprofit with vital components for our remote work, while allowing us to keep our donated funds going directly to our mission.
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.
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.
The basic apps are straightforward and easy to use, especially since they have been around so long. I'm referring to the basic apps like Outlook, Excel, Word, PowerPoint, OneNote, etc. Other features such as Microsoft Teams and Sharepoint Sites, Sharepoint Lists, Sharepoint Groups, etc. all require a higher level of knowledge to both implement and use properly
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.
In the last 5 years, Microsoft has come a long way. The performance of the products has become more and more user-friendly and it seems that the feedback provided by the user community is being listened to and worked on. The processes are very fast and seamless. There are negligible errors and doesn't slow the systems down.
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.
As mentioned elsewhere in the review, Microsoft has historically paid attention to community feedback and issues, but timeliness can improve, and so can the addressing of long-standing issues about which many users have said "I have this issue too!" but no official solution exists. For issues that do have a solution, however, the solution is usually not difficult to find, and the explanation of features on Microsoft's website can mitigate many problems.
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 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.
Before migrating to Microsoft 365 Business Premium, we possessed an in-house exchange server. Therefore, it was difficult for us to look at alternatives to Microsoft for a solution – we did look at the Google Suite of products, but the transition for us seemed less cumbersome to stay with Microsoft from a staff and administrative perspective. While the G Suite does offer us many outstanding products and services, we also didn’t feel that Gmail is up-to-par as a corporate solution the way Exchange/Outlook/OWA are – this alone was also a driving force for our end-users, as there was minimal transition for them to move from an on-premise solution to an off-premise solution. The additional features of SharePoint, Teams, Project, and so many other applications within Microsoft 365 also helped us make a strong case to stay with Microsoft and expand what we were using. The end-user and mobile protections of InTune have also put us at ease when issuing laptops and mobile phones to an almost fully-remote end-user base.
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.
We can now keep work going from anywhere. It doesn't matter if we are on a job site or sitting in the office or working from home for a day or two we don't have to miss a beat.
It has unified how we store information so that everything isn't stored on individual computers
