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
Squarespace
Score 8.4 out of 10
N/A
Squarespace is a CMS platform that allows users to create a DIY blog, eCommerce store, and/or portfolio (visual art or music). Some Squarespace website and shop templates are industry or use case-specific, such as menu builders for restaurant sites.
$25
per month
WooCommerce
Score 8.4 out of 10
N/A
WooCommerce is an eCommerce plugin for WordPress, developed by WooThemes (recently acquired by Automattic). Like WordPress, it is designed to be an extendable, adaptable, open-sourced platform. WooCommerce allows merchants to sell physical products, downloadables, or services.
$0
Pricing
Drupal
Squarespace
WooCommerce
Editions & Modules
No answers on this topic
Basic
$25
per month
Core
$36
per month
Plus
$56
per month
Advanced
$139
per month
Woo Enterprise
Contact Sales
Offerings
Pricing Offerings
Drupal
Squarespace
WooCommerce
Free Trial
No
Yes
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
28% to 36% discount available for annual pricing.
WooCommerce is a free and open-source plugin for WordPress. Merchants can host their WooCommerce store on any private hosting service, or with Automattic directly via WordPress.com. Some added features or services from the WooCommerce Official Marketplace may have one time or subscription pricing.
I've used Squarespace and WordPress for other businesses, and Drupal was honestly selected due to cost. It does a good job of scaling across our organization - and many units have benefited from having a space to provide content. Squarespace is more modern, and WordPress may …
I inherited Drupal from a developer who made the website for our nonprofit many years ago. It was increasingly obvious that it wasn't a fit for our organization, which has multiple staff and volunteers who need to edit or update the website but don't have coding experience. Wix …
Drupal excels at allowing seasoned programmers to really get creative with marketing initiatives in terms of working with a theme and the core code. That being said, it is definitely much more challenging for average developers and front-end builders to use, especially at …
Drupal is certainly a more complex animal, comparatively. But its power lies in its flexibility, extensibility, and stability. And the API is fantastic. There's really nothing else like it.
Between these products, as a developer I would most likely go with Drupal unless I had a very specific reason to go with something else. To put it simply, Drupal is capable of anything that these other products can do. It may take a little longer to configure it in some cases, …
Drupal is highly customizable unlike WordPress and Joomla. It may take a longer time to set up but it works well for the needs of the organizations it is set up for.
Again, Squarespace is the best option for small businesses seeking an e-commerce solution. If you need more robust features, look to Drupal or WordPress, depending on site size. Weebly or Wix are solid options for basic sites, but I personally have had significant issues with …
WordPress is much more flexible and offers a much broader and deeper range of capabilities that Squarespace. However, setting up a WordPress site can be quite time consuming in comparison, and you must commit to spending time regularly - at least once a month - to updating …
SquareSpace is infinitely easier to use than any CMS I've used before. It's more reliable and saves a lot of time. I wouldn't recommend SquareSpace for large e-commerce sites or big government sites, but for small business, it's ideal.
WooCommerce and Shopify both permit essentially limitless customization. However, WooCommerce runs on PHP, a commonly used development language with a thriving community, whereas Shopify uses Liquid, a relatively obscure programming language, in its backend. I'm not I would …
We love the functionality of Wordpress itself, so that's why we ended up using WooCommerce to do checkout instead of going over to the Shopify platform. Wordpress allows us to do so much more with the backend code and customization of our website. We were not impressed with the …
WooCommerce is cheaper than the other solutions I evaluated. It is a more complicated platform but because of that it is much more flexible. In the end it was an easy choice to go with WooCommerce because we already were using WordPress for our website and it made sense to …
Since WooCommerce has merged with WordPress, the integration has become even more seamless than ever before. The fact that the database space has been reduced because of the integration, has lightened the load on servers. The additional overhaul of variations has also taken a …
I haven't used anything else, so I cannot comment too much on this. I use PayPal for single items instead of implementing WooCommerce, so I guess that's easy, but not great for non-developers (i.e. the client) to update. WooCommerce is a simple, very intuitive content …
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.
Squarespace is one of the best solutions out there for building a website or web experience that looks good, has great functionality and is cost-effective, even for smaller businesses. Although most people in marketing will find most of the elements intuitive, if the creator is struggling with any of the functionality, there are many, many support options and other users who can offer assistance.
WooCommerce is best suited to customers whose website is built on the WordPress platform, and whose development team has a good understanding of plug-in implementation. If your website is not built on WordPress, but on Laravel or React (or any other non WordPress technology), then WooCommerce is not for you. WooCommerce is also great for customers who just need a simple online shopping experience. If your needs involve more complex or immersive features such as timed discounts, pick up locations, delivery reminders, or post shopping feedback surveys, know that you will need to purchase additional add-ons to make to get these features using WooCommerce set up on WordPress.
Stupid simple to use. I know very creative people who cannot code and this is probably the easiest ever platform for them!
Pretty website templates and great functionality with showing off portfolios.
They've already figured out what are the problems that non-coding people have when creating websites and they've figured out a simple solution for all of it.
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.
Despite very rare glitches, more connected to an excessive number of plugins, that affect the speed of the site, we are extremely satisfied with the platform, the ability to import and export products, even though we just export them, as we have our proprietary system for updating inventories. We love the ease of upgrading, enhancing, innovating, and the freedom we have to do whatever we want, which is a plus, when you consider Shopify can take down your whole store as they please, if they think you aren't abiding to their TOS or their ever changing set of rules.
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.
It's simple to use for someone who is really good with computers as well as those who are not. I've been using my personal squarespace for years and have also helped clients build a starting page which they are later able to manage theirselves.
It is built on the Wordpress platform, so there are some quirks compared to a dedicated e-commerce product, but it is very intuitive and easy to use, especially for anyone with Wordpress experience. There are numerous great support articles and learning resources available. Significant customization can be achieved with plugins vs other eCommerce platforms, which may require more custom code and have fewer plugin options.
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.
Help is available directly from the back end and uses full sentence searching to find answers to questions others may have asked before. With a ton of articles and support questions documents, it is very likely that your question has been answered. If not each page has the ability to open a direct email to support. Each case has a number and can be followed. Responses are often quick and have links and directions clearly stated
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.
Squarespace was quicker to set up and more accessible to manipulate the theme, pictures, and content. The page layouts are more versatile and fluid. With WordPress, more time-consuming efforts go into making a template work the way you want it to (because of the lack of the drag-and-drop grids that Squarespace has).
We were pretty sure we wanted a WordPress site so that we had more control over the site itself, having been burned by third-party vendor sites before. The fact that WooCommerce integrates so well with WordPress was a big selling point for us. Magento would have been too heavy of a lift for our small dev team and we didn't want to rely on Shopify or BigCommerce (though all of those products could have their merits for other projects or clients).
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.
The cost is reasonably decent. My client says they spent about $20 a month or $240 a year. I asked her if she could add Google AdSense to her blog one day, and they believe they can. They said a custom site would cost them $3000-10,000 depending on who does it. And I agreed, but I found the website they created was on the lower end of that range.