I would highly recommend it. A lot of the big CMS developers like WordPress have certain conventions that you have to follow. If you need something outside of that "box" you really have to tie yourself in knots to get something custom.
Craft, on the other hand, leaves most of the structural design up to the developer. It also has a slick, built-in, live preview feature and easy localization.
Last but not least, they have a plugin that easily outputs your content as a RESTful API if you want to do a more modern JS front-end.
For small sites, the license is 100% free and then there's a nominal fee for larger sites.
Wonderful article! As a JavaScript developer, this is the first time I have seen a well-written critique of the language shortfalls. Usually these counter-arguments can't help but feel like flame wars.
That said, I think every JS feels these pressures internally. In 2015, some were even brave enough to give it a name — "JavaScript Fatigue". I personally work with TypeScript. But each time you kickoff a new project these days, the task of getting past all the boilerplate work seems to be increasingly difficult.
I would highly recommend it. A lot of the big CMS developers like WordPress have certain conventions that you have to follow. If you need something outside of that "box" you really have to tie yourself in knots to get something custom.
Craft, on the other hand, leaves most of the structural design up to the developer. It also has a slick, built-in, live preview feature and easy localization.
Last but not least, they have a plugin that easily outputs your content as a RESTful API if you want to do a more modern JS front-end.
For small sites, the license is 100% free and then there's a nominal fee for larger sites.