Drupal vs. Slack

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

Slack is great for tracking commits to new coding projects. You can take parts of code that still need to be implemented later and easily search through the history of comments if there is something that goes wrong with a code commitment. It can be difficult for people that only like Teams to adjust to a new platform if you are using both to communicate.

Incentivized

• 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

• Huddles Run smoothly without any interferences.
• Smooth individual calls quick and easy without any interruptions.
• seamless notifications across multiple devices
• The ability to easily tag a team member to urgently attend to a specific escalation.
• Slack being user friendly and able to integrate easily with other platforms and apps.
• How to easily open up different channels for different escalations and needs.
• a safe direct messaging option.

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

• Would love a better integration with GitHub. For example, notifications when your PR is updated, when review is requested, @-mention in comments, etc.
• Improved "Later" tab, for example the ability to create to-do lists or making the "Later" tab into a more powerful to-do list (annotate items with notes)
• More powerful integrations, e.g. Google Calendar could render a calendar view within Slack, rather than sending the daily schedule

Incentivized

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.

To be more transparent, I give 10 because Slack serves our collaboration needs. It provide us a good platform for team communication relaying important update within the company, it has even mobile app where you can install in your phone to monitor any updates within that team that needs your immediate attention and intervention.

Incentivized

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

My rating was 7. Its intuitive interface and user-friendly features like channels, threads, and integrations make it excellent for team communication and onboarding. However, its usability is held back by the resource-intensive desktop app and cluttered feeling in large workspaces. The mobile app's performance and unreliable notifications have also been noted as weaknesses.

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).

Yes, the app works 24/7. I don't even recall having any period that we could not use since the implementation. Even the maintenance periods are barely noticeable and our work is not impacted by it when it happens.

Incentivized

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

Slack is a soft app, we don't have many issues with it. I recall one or two people complaining about something during our usage period, but I didn't have a bad experience. When the app is slow, usually the problem is with my computer or my internet. The app works just fine.

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

Whenever I've had to troubleshoot an issue with Slack (which, to be honest, has not happened very often), their online documentation has been easy to locate, easy to understand, and effective in resolving my issue. Slack's ever-growing popularity also means that there's a large community of practice out there that can be depended upon.

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.

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

I was not part of the implementation team, but I recall being 100% happy and excited to learn and use a new tool. I'm still am to be honest.

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

I like Slack better than ClickUp, because I would spend 30-60 minutes a day updating my ClickUp tasks. The way ClickUp was used was very micromanaging. I billed by the hour, so I was willing to put in the time to alert the boss what tasks I was working on.

One of my jobs used Hive - I mostly just ran it in the background in case anyone messaged me. I did not use it often.

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

• 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

• Slack has been incredibly helpful in connecting various tech apps and ecosystems, creating a more streamlined and responsive process.
• Slack has made it significantly easier to communicate with our team members across multiple time zones, creating a more engaging environment for our all-remote team.

Incentivized