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
Trello
Score 8.4 out of 10
N/A
Trello from Atlassian is a project management tool based on a Kanban framework. Trello is ideal for task-management in a to-do list format. It supports sharing boards and cards across users or teams. The product offers a free version, and paid versions add greater automation, collaboration, and administrative control.
$6
per month per user
Pricing
Drupal
Trello
Editions & Modules
No answers on this topic
Standard
$6
per month per user
Premium
$12.50
per month per user
Enterprise
$17.50
per month per user
Free
Forever Free
Offerings
Pricing Offerings
Drupal
Trello
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
A discount is offered for annual billing and for larger numbers of users.
In my mind, Drupal and WordPress are the top open source CMSes, and I rarely recommend not going with an open source CMS. WordPress can be great, especially for single developers, but I find that the code structure and extensibility of Drupal makes it superior for many use …
Front-End Web Developer, Office of Mediated Education
Chose Drupal
WordPress would be the best alternative to Drupal that I've seen, but in my experience, Drupal is better at complex websites that need a lot of customization. WordPress would be much better suited for a blog than Drupal.
I only briefly looked at Joomla, and I wasn't impressed.
I used JIRA, Basecamp and Redmine. JIRA is for big/huge projects, very technical ones. Redmine is fine and used by another team. It needs more rules for a good Agile use and you can do what you want (more than with Trello, too much). And the visual interface is not as useful as …
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.
For teams or individuals with lots of individual tasks/details to track, Trello is perfect! It basically removes the need for a paper checklist. For those that need an overall project management tool that requires less tasks and more overarching goals, collaboration amongst various teams, and gantt charts I would suggest monday.com
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.
I am very likely to renew Trello, because it doesn't cost anything to do so. I am also very likely to use Trello's upgraded features in the future because a lot of my team's data is stored on there and they have already gotten used to the platform. Trello is very easy for new team members to pick up, making the onboarding and usability very streamlined.
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.
Trello is incredibly intuitive, both on desktop and mobile right away. It is also full of helpful features that make it even easier to use, and is flexible enough to suit almost any organizational need. Onboarding for the software is thorough, but concise, and the service is frequently updated with even more QOL improvements.
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.
I haven't reached out to their support very often and their support is very limited anyway for the free users. They do have tons of great articles and videos in their Help Center and constantly send emails with updates and add-ons to the product. The fact that I've barely ever had to contact their support team means that they've developed a great product.
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%
For our small business, getting a few of us started well on Trello was the key, I think. As long as a couple of us were really comfortable with the interface, we could lead others and help them with any questions. From now on, anyone who works with us just naturally uses Trello for information sharing - it's just part of what we do.
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.
Trello is more simple and not as "robust" as the other tools, but it's easier to use and manage and understand and ACTUALLY get stuff done with. It's simplicity is part of the beauty of using it. You don't need a million options that nobody uses, you just need to get stuff done.
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.
Trello keeps me organized, focused, and on track. I could filter the Trello board to only see my issues and understand what I needed to work on and when.
Trello helped our team implement an agile structure. It's a very simple kanban method of viewing all of your team's tasks and statuses. You can completely customize the columns to your team's specific workflow and create tags relevant to your work.
Trello helps reduce unnecessary communications between teams. When I want to request translations, I simply create a card on the localization Trello board -- no need to directly message anyone on the team, and I can watch the status of the card change from "in progress" to "in review" to "translated," all without having to directly ask for updates.
