https://twill.io logo
Twill vs Drupal
# ❓questions
m
quick question, thinking of using Twill for eCommerce store, need custom integrations with some level of security so pros of shopify quickly dwindle as would need to make microservices for them. Shortened list of enticing options to migrate site off squarespace to Twill and Drupal, is anyone familiar enough with both to tell me what might be a better option? I have JS PHP and Laravel experience, have used dynamic frontend frameworks like angular and vue.js in the past. Any advice would be appreciated
i
Hi @millpreet, with your Laravel experience, I would definitely favor Twill over Drupal. To quote Rob our main contributor last year: "It’s important to make a distinction between what’s easy for a configurator vs a developer. As a developer, I feel 10x more productive using Twill over WordPress or Drupal."
a
Hello @millpreet , I'm a Laravel (10+ years) and Twill (3 years) developer, that did a single Drupal website 1,5 years ago. What I found doing Drupal is that, if you just need to build a website and your work would be mostly on frontend, it can be very easy, maybe easier than Twill, but if you need to do custom backend stuff, interact with external services or APIs, you need to know very well Drupal inner-workings. As soon as you need to change a simple query to do what you want, things get very complex on Drupal, while on Twill you have access to your Models, you can query them easily and just do what you want. On Drupal you need to be also fluent in hooks, in order to inject your custom (and very simple) stuff on it, and hooks are hard to "get". On Twill you won't have access to many ready-to-use modules, but this also means that you are free to use anything available for PHP or Laravel very easily, it doesn't get on your way. If it's not something you need from Twill's CMS dashboard, you just install a package, create your routes, controllers, models and service classes, and you are good to go. If it's something you need to integrate on the CMS, you just edit a Twill controller, repository or model and it's done, you have access to them all. On Drupal I had to go over a bunch of steps and hire a contractor that said to me a bunch of time, "oh, yeah, you need to create a module do to this..." or "oh, no, this is not the right hook, you needed to use this other one" or "wait, I believe this module has to be patched to work on 8, I have the patch right here if you want to apply".
While Drupal has a huge sea of modules to be installed, you also need a fair amount of luck finding what you need, what works for you, what actually works, and what's actually available for your Drupal version. Drupal 6,7,8,9 were not really compatible as I understood, it advanced a lot, but it also broke a lot of modules out there, so it's basically a Googling nightmare, because you find what you need, but it doesn't work for us. If you need to deal with things like multi-language or responsive images, or even if your site may have different image crops for the same image, I would just say: don't do Drupal. It was very hard on us on both areas that I believe we never really got them right on Drupal, also because we were spoiled by Twill, which is amazing on both. Usabiity on Drupal is also not great compared with Twill. Having all content types of placed on the same structure (that can probably be better organized), that you need to filter or search for, it's also a bit lame, sorry. Twill's CMS organisation is a delight for your users. The block editor, core on Twill, it's pretty hard and cumbersome to get working on Drupal. We had to use paragraphs and it was a nightmare to get it working and also get them translated properly. Drupal has a huge community, and people in Discord are also helpful. Here on Twill you have access to the creator itself and some of the core maintainers 😉
m
Thank you both very very much! Really appreciate the detailed answers. Lol originally put my question in general and thought I'd get the spam Ban lol
I saw ppl complaining about similar things on old reddit posts. And the vus.js parts also speak to me. I'll take a look side by side at both just a tad, just to ensure it, but Yeh. Docs look good for twill too
Drupal ones don't look too bad but seem all over the place a tad
2 Views