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
Volusion
Score 4.9 out of 10
N/A
Volusion is a cloud-based ecommerce solution from the company of the same name in Austin, TX. It features an intuitive dashboard, built-in marketing and promos, SEO, templates, and tools to customize look and appearance.
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
Volusion is a good company if you're starting out. The problem is that, if you want more complexity out of the program, you're kind of stuck. Also the regular time out errors and slow downs can be very frustrating. Packages that miss overnight deadlines because your system stops working can cost you customers. In today's highly competitive market, that's just something that's hard to put up with. If you have a lower volume of business you might be able to work around these issues.
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.
Templates are pre-built for a good end user experience. I've gone through the process of building custom sites as well as tweaking both free and paid templates that Volusion's design team provides.
Their support team didn't use to be as helpful, but in recent years have answered nearly all questions I've had. Their support section within the database provides detailed walkthrus as well.
Order processing is easy once you've been trained on the system. We got to a point where nearly the entire process was automated from initial purchase through shipping.
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.
API calls use the previous call as a reference, even if you weren't the one we made the previous call. Can lead to data gaps, so you often have to set a manual date range to look back to make sure you aren't missing any data.
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.
When you spend so much time with a product like this and not only have you witnessed its growth, but you almost feel like you are next those that make the decisions of building features a certain way, you can't help but want to stay and be a part of their continued growth. It's simply a great product. Can it improve? By all means! But it will only improve because of users and avid resellers like me.
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.
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.
You have to wait on hold for at least 45 minutes every call—the tech support person never knows the answer right away so they put you on 10 minute holds only to come back and say they're still looking for answers. The chat function could take days to get a response. Our "Dedicated Account Manager" never checks in or answers, nor are they ever in the office when we call. It's like they try to be as unavailable as possible until you forget why you even called in the first place. Insane.
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%
It is best to use the built-in features and recommended services for the most turn-key experience (ie. Skipjack for payment processing so that it can all be done from the Volusion backend).
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.
While k-eCommerce was very glamorous to us because it integrates with our main workflow, it just didn't have some of the marketing features that are so integral to the way we do business online. The set-up costs were also way too high. Volusion is so affordable and feature heavy, it makes it very difficult for any shopping cart provider to compete. You can find others who are competitively priced and have similar features, but they simply aren't as robust (at least for the way we use it)
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.
Honestly, when you're in the dashboard, the UX is simply horrendous. I mean, everything that should be 1-2 clicks away is 4-6 clicks away, and each pages takes at least four seconds to load. You just find yourself wasting a lot of time waiting for things to load. This should be more simple.
