Disclosure: I'm a Winter CMS maintainer and former October CMS maintainer.
I wrote the "Features for Developers" page (https://wintercms.com/features/for-developers) on the Winter CMS site, which pretty much summarises my thoughts on the advantages of Winter CMS development.
I was using October CMS for years before I became a maintainer, and the thing that hooked me was the plugin architecture. It is incredibly simple to extend nearly every facet of the CMS to do what I want for my clients.
I've developed (and still do) develop WordPress sites, and I find trying to "extend" or customise some plugins to be like pulling teeth if they're not using the hook system correctly.
The fact it's built on, and supports most of the API of, Laravel is a bonus to me too.
I've dabbled a little in Drupal but don't have enough experience to give a good comparison in between those two.
I wrote the "Features for Developers" page (https://wintercms.com/features/for-developers) on the Winter CMS site, which pretty much summarises my thoughts on the advantages of Winter CMS development.
I was using October CMS for years before I became a maintainer, and the thing that hooked me was the plugin architecture. It is incredibly simple to extend nearly every facet of the CMS to do what I want for my clients.
I've developed (and still do) develop WordPress sites, and I find trying to "extend" or customise some plugins to be like pulling teeth if they're not using the hook system correctly.
The fact it's built on, and supports most of the API of, Laravel is a bonus to me too.
I've dabbled a little in Drupal but don't have enough experience to give a good comparison in between those two.