Is there life outside of the CMS?

Question

Drupal

Good evening, the question is stupid but I have been interested in it for a long time. For as long as I can remember, I have been creating turnkey websites on Drupal and occasionally on WP on the web. But I was very tired of this, of the inability to fully control the same front-end component (this applies to Drupal) and wondered if there was anything besides CMS and all sorts of engines.
I read a lot of different things both on frameworks and everything, there are plenty of front-end technologies, but what about backend / database? And in general, what kind of back end do people using technologies like angular, backbone, BEM work with now?
For me, this question is fundamentally important, you need to master new technologies, and working with the same Drupal on a stream, I have no practice, and now the requirements are hoo, whatever you want, you don’t want to, but you need to learn, practice as well as ask questions.
Thank you very much. I hope the question was asked correctly and clearly.

Answer 1

Decide whether you want to move to the frontend or still a full stack?
Between the frontend and the backend is usually a REST/JSON RPC apish (special attention should be paid to the jsonapi.org standard ). It is important to first deal with this thoroughly, because a lot of sensible backenders make apishki through one place, regardless of the technology stack.
As for choosing a database (if you yourself will write apishki) - I recommend that you immediately forget about MySQL and move to PostgreSQL. Problems will immediately become a little less.
It’s also worth poking around in various things to manage the environment (dockers, ansibles, vagrants). But again, if you want to do the backend normally.
I use Angular on ES2015 (babel.js) (Backbone was abandoned a couple of years ago), a very simplified version of BEM with minimal use of the cascade, although this is not particularly interesting. The backends are running on PHP, on Symfony2 + Doctrine2, I'm happy with everything. You can get carried away with OOP and DDD, and tools contribute to this.
For API documentation, I also recommend looking in the direction of RAML or Api-blueprint (for the latter, I am currently writing a documentation parser, because so far everything is fine with this only for node.js), on the basis of which it is good to think through APIs, as well as automate the routine a little. For example, generate stubs / mocks for an apish while writing a client and the apish is not ready yet. Well, etc.

Answer 2

The flight is normal :) Haven't you met when searching for Symfony / Laravel / Yii and so on. ? And this is only from the php world, and only a small part)
www.phptherightway.com
https://github.com/ziadoz/awesome-php#frameworks