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
Stripe Payments
Score 9.0 out of 10
N/A
Stripe is a payment gateway software solution which supports a range of payment related needs such as subscription management and recurrent billing via Stripe Billing, integration with third party payment services via the Stripe Connect API, assistance starting an Internet business which accepts payements via Stripe Atlas, fraud prevention via Stripe Radar, and payment analytics via Stripe Sigma. Additional features and modules include Stripe Issuing, which allows users to create,…
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.
Stripe is much easier to set up and use, has a simpler UI, and lower transaction fees. A no-brainer when it comes to taking credit card payments online.
Paypal is much better due mainly to the server hardly ever having outages, just as easy if not easier to install and customers are used to the brand and trust it more than others. Square is very similar to Stripe but obviously integrates with its own system so has very few …
They are very similar. PayPal charges you monthly to have the ability to set up monthly payments. I had a problem with PayPal earlier this year where it would let me set up a recurring payment but then would not let me charge my customer the following month. It's actually a …
Stripe and Paypal are both excellent options for accepting payments. Paypal is a little more widely accepted for international payments, but domestically within the US we see that most of our customers use the Stripe module for payment processing over Paypal. Both are equally …
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.
We had a client who wanted a QR to use in their marketing, which enabled their clients to donate to us. It was so useful to be able to set it up, and we can track the views and donations received using this code. Another client with issues with our website wanted to set up a monthly subscription, so I sent her a payment link, which worked brilliantly. For clients that want to make one-time donations, it also lets the client choose the amount. The only scenario where we haven't been able to help is when clients want to change the card associated with the payment - whilst we understand it is for security/gdpr, it means they have to cancel and set up something new, which poses the danger that we may lose them as a customer.
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.
Stripe is the leader in the industry when it comes to any type of industry. All that is needed is a plan and then implementing that plan either with a developer, or through the help of Stripe's customer service team to assist in getting you setup. The ease of use time it takes to get up and running is second to none
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.
Stripe offers a very easy-to-navigate platform with many different functions. From linking it to our website and accounting platform to tracking our payments, being able to issue a refund quickly if required, and setting up QR codes and payment links for subscriptions or one-time donations, it really covers so many aspects that we need and use on a weekly and monthly basis.
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
Stripe's support is nearly perfect – great attention to detail, fast response times, and a willingness to really dig into issues and get to the bottom of them. In the five years we've been using Stripe, the only negative thing I can say about their customer support is that it seems like there has been a slight shift to less technical front-line support agents, which means it's more likely your issue will have to be escalated before you get more information. This, however, has happened as Stripe rolled out more real-time support features like call and chat, and that really isn't workable if you're escalating everything right off the bat. It's absolutely an acceptable trade-off.
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).
Stripe is easier to use and offers better support and rates. My favorite part with Stripe is probably their ready-to-use plug-in that's offered for me. We have multiple eCommerce stores and we rely on our payment process going smoothly. The plug-in from Stripe is free, constantly updated, secure, and very easy to implement.
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.
It makes getting money from your clients really easy
It gives your clients the guarantee that their payment information is totally secure and confidentially used and kept
It is very easy to integrate with online assets of the company
In a couple of occasions, some companies have wanted me to use Stripe for them to pay me, and I have had a couple of hiccups. This was more related to the way that these companies set up the Stripe integration of my account to their platform. In both cases, the integration has not been possible and to this date, I still do not know why with exactitude.
As I said before, the commissions kept by Stripe could be lower, and shared with the CC companies, rather than having us clients pay for all of o it.