draw.io vs. Drupal

draw.io can be more suitable for technical documentation for architectures, flow diagrams/charts, and conceptual images of an application infrastructure. However, this tool is not made for business intelligence work nor for dashboarding to monitor the technical components. From the administrative standpoint, this is not well suited for agile ceremony structures like retrospective boards or planning or even quarterly planning boards. The strength of draw.io lies strongly in being a lightweight diagramming tool.

Incentivized

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

• Draw.io offers a lot of shapes and customizability of how the diagrams are laid out. We've been able to create a lot of different things with it, and have barely scratched the surface of the sorts of things that we could do.
• Draw.io is fairly intuitive in the way that you draw shapes and connect shapes together, I was able to figure it out without a tutorial.
• Draw.io is fast and performant for me compared with some of the alternatives.

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

• When very elaborate diagrams are needed, it lacks the amount of tools and customization needed
• Since this is an online tool, it can freeze and that causes you to lose that work up to that point
• Performance can lag with very complex diagrams

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

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.

The UI is intuitive. It allows a new user to start diagramming almost instantly. Manipulating elements, linking them together, etc. are all easy to do. Draw.io nevertheless a broad variety of diagram templates to help get started and also of shapes to use in diagrams. Some situations can make it a bit tricky to use, such as when having multiple shapes on top of each other (e.g. shapes placed within swimlanes) but that's a minor issue.

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

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.

Incentivized

The support for draw.io is pretty decent, considering it is a free website. I had a question one time when I was trying to do something, so I sent an email to their support email and got a response fairly quickly with an answer to my question. They also have some excellent support tools on their support website for helping you get more familiar with their program, and I found that very helpful.

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

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

draw.io is open-source and free for many uses, which means minimal upfront cost and good value.It works in the browser, also has a desktop version (so you can use offline) which helps teams that may not always be online or want local backups. Useful when you want a diagram tool that “just works” without huge ecosystem lock-in.For organisations that value control, less vendor-dependency, this is a plus.

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

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

• draw.io has surely impacted our organization positively by saving some crucial time.
• It has not really impacted much monetarily to be honest.
• The ROI we got from draw.io is that it has made complex things clear for everyone in our organization.

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