Laravel/symfony are just one component. It's the approach of organizing your site as packages, and properly namespacing and exposing well-documented class libra

Laravel/symfony are just one component. It's the approach of organizing your site as packages, and properly namespacing and exposing well-documented class libraries of your own that's becoming the dominant approach even for websites. Even the concept of a 'website' as simply rendering pages is something fewer people need a custom install for - squarespace et al have the basic sites covered, and for anyone who needs a pretty specific feature there's plenty of other platforms: shopify (commerce), nationbuilder (nonprofits), etc. Having worked with many PHP CMSes, the config for managing various drupal plugins is often far more complex to setup, maintain, and migrate than simply writing that feature in my own little class in concrete5, joomla, or even without a CMS. I get the appeal behind wordpress (even if I think it's implementation is complete garbage), because non-technical people can still setup and manage their plugins. Most of my clients who are/were on drupal, became my clients after they were inevitably crushed under a pile of drupal config.