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
Ecwid by Lightspeed
Score 10.0 out of 10
N/A
Ecwid allows customers the ability to create an online store to any webpage or social media profile. Boasting hundreds of thousands of merchants in 175 countries as users, Ecwid aims to provide everything needed to reach customers wherever they are: in-person, through a website, Instagram, Facebook, Amazon, or Google Shopping. In addition, Ecwid’s point-of-sale integrations, email marketing integrations, and dedicated mobile app allow sellers to manage marketing merchandising, and sales - any…
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
Ecwid is absolutely perfect for any business that is looking to start out with online sales and mobile point-of-sale. Many times, business owners may have limited experience in setting up a website or point-of-sale. Having to spend on this expertise with a limited budget can be frustrating. Ecwid allows you to have great results even if you are a novice.
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.
Clarity - there has been very little confusion and need to reach out to Customer Support for help
Consistency - no big, crazy updates or changes have been made to the format of Ecwid during my time using it, so I know when I log in to preform my business tasks I can always locate what I need and accomplish what is at hand easily
Simplicity - everything is so clear and straightforward. It's like e-commerce for dummies.
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.
The value given by Ecwid is unmatched. When combined with the ease of use of the product, it is a no-brainer to continue to use the product. The only thing that could cause us to switch is if some feature we needed which is not available which is unlikely based on the feature list we reviewed when making the decision to go with them.
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.
I gave a 9 instead of a 10 only because I haven't figured out a function or two. I believe it has less to do with Ecwid's overall usability and more to do with my own understanding and skill level, but regardless, it may also have something to do with the limits of Ecwid's functions.
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.
I have always received the support I need in a timely manner. I enjoy receiving emails every week on trending business topics and new suggestions. They often serve as a reminder for me to include new e-commerce tools into our strategy. And I've always had great experiences with reaching out to the support team with specific questions.
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.
We sell a product that requires certain controls to sell and most of the companies we researched had specific policies preventing us from selling on their platform. We aren't selling anything dangerous, they are parts of ammunition (the shell casings) and not entire ammunition rounds. Most other vendors restrict the sales of firearms and ammunition, but even when just selling a part used to create ammunition, we were still restricted. I'm not really sure why they restrict sales of products like ours from different vendors. Ecwid had no such restrictions and were happy to confirm that for us.
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.
