Login
where’s your line between “please manage Drupal for me” and “give me access to the code”?
the Webflow Source announcement sent me back into Acquia’s Source CMS product guide.
it explicitly says "customers can’t modify the underlying Drupal code or install contributed modules".
I understand the deal: less maintenance responsibility, fewer opportunities to make a beautifully customized disaster.
buttttt Drupal’s flexibility is also why a lot of people chose it.
where does that tradeoff work for you?
for a straightforward marketing site, I can see the appeal. for a project with specific integration or editorial requirements, I’d want to know where the escape hatches are.
what’s the requirement that would make you say “managed SaaS is fine”... or immediately ask for the keys?
I covered the two Sources on my Headless show, but this is the part I’d rather hear from people building and maintaining Drupal sites.
[link] [comments]
