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.5 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.
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 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.
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
We've found Squarespace perfect for quick, well-designed websites that you can literally design and launch in a day. However, if you want to get more complex with your website, including custom backend integrations or code, Squarespace presents a bit more of a challenge when it comes to what they will allow you to modify on their platform (especially using third-party integration apps).
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
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.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
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.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
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.
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 is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Overall, as a designer, it makes perfect sense for small to large businesses to use a site such as SquareSpace. Costs are relatively reasonable with the ability to go in and do custom code.
The issue is certain aspects of it, depending on the plan, you can't do. So, if you want to do API to the site, you need to use the top-tier program to do so. Even at custom code, you won't have access to the API section.
As well, like all templates and themes, everybody is using the same style too.
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.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
The key positive impact on my overall business objectives is how simple Squarespace sites are to implement new information. Whenever our services change, we can quickly update pages or even change how the website flows, in a very short window of time. This allows me to get back to more urgent work sooner.
Our Squarespace site for Club Swim Show helped present our web series to potential partners; Club Swim Show went on to partner with a popular swimming magazine and reach a larger audience through that magazine's hosting thanks to the professional design of our original website.
Squarespace does not bring in customers to my storefront, which is fine for me, since I sell things infrequently and it is not my main business, but might work against someone who is expecting a Shopify or Etsy level connection with buyer markets.
