Curata vs. Drupal vs. Strapi

I liked Curata, but it depends on the use case of how it will be used as to how effective it is for someone. If you are trying to curate content it works great. Had I not been so put off by the issue mentioned earlier I would have given more effort to learn the CMS, so I am not sure how effective it really is.

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

1. If a headless CMS is needed. 2. Need the cms UI to be clean. 3. There is a need for customization options in the UI and API as well. 4. Expertise in javascript and need cms with node js backend. 5. Want auth APIs pre-made. 6. Easy to customize the backend as well. 7. The user interface can be fully customizable.

Incentivized

• Curata is great at curating in content that is relevant to our audience. It is easy to add many different sources to the feed from all around the web and we've really seen Curata "learn" what we see as the most relevant.
• The microsite we got as part of our Curata subscription is really fantastic. It's very customizable and we've been able to really craft it to suit our needs. There are so many different options available and our Curata rep has been really great with helping us cater each piece to our vision while making helpful suggestions along the way in terms of best practices. Plus, the word processor for publishing blog posts is so easy to use and I've had no issues with it so far unlike many other CMS platforms I've worked with. The Curata microsite is actually going to be replacing our current blog very soon - we love it that much!
• I've had a great experience with customer service from Curata. Our rep is responsive and helpful and really good about not just answering our concerns but also providing feedback on our processes and giving advice for how we can improve.
• Search capabilities within the curated content feed are fabulous. This is one area where I found other solutions to be lacking when we were going through the sales process, but Curata really succeeds here. It's extremely easy to find exactly what you're looking for in your content feed.

• 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

• Free and open source.
• CMS UI is nice and clean.
• Customization options.
• Regular updates and bug fixes.
• Easy to find and understand docs.
• Blogs available to learn more.
• Plugin eco system.

Incentivized

• more subscription plans as not all people need all features.

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

• Tutorial videos.
• Use typescript for it's backend.
• Detailed explanation of commands available.
• More clear docs for releasing.

Incentivized

For all of the features we loved when we signed on like the microsite and search capabilities and also their customer service, we will very likely renew with Curata. We also really like the evolution we have seen of the solution, just recently a new integration with Marketo (also a vendor of ours) was announced which will be very beneficial to us in optimizing our email newsletters

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.

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

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

The main difference that made me choose Curata over Percolate is that it is not complex. Curata is easier to set up, to use, and to manage. It does not involve any complicated configuration to get the content and data you need. Curata technical support is amazing, to say the least. I am not an expert in the technical stuff, but I feel assured their team can help me out when I have an issue

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

• I would say neutral for us, but more so because of how we were using it and it being a stop-gap fix for us.

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

• Easy to setup.
• Customize the ui.
• Increased productivity.
• Get prebuilt auth apis.
• Customize the backend and add new apis.

Incentivized