You’ve got two major paths in front of you. 1 -> JavaScript/Typescript on the server side and the node.js ecosystem. 2 -> Everything else. Once you decide wh

You’ve got two major paths in front of you. 1 -> JavaScript/Typescript on the server side and the node.js ecosystem. 2 -> Everything else. Once you decide which one of these you want to explore you can just do some research and play around with the documentation of a framework or two and start building up experience building APIs and small matching demo front end UIs that use them. There’s a lot of potential framework choices behind 2 so don’t feel daunted. Step one should be choosing a language to learn first and you might want to do that based on your own level of existing familiarity with a language or use this as a chance to learn a new one. Some of the back end frameworks are going to be a very close match to your experience building front end tools as they are designed to efficiently create APIs for front ends to use. A few will even have interesting things that bride the gap between front end and back end, like C# and ASP.Net (or ServiceStack) have Blazor which is bringing C# code to the Browser via WASM. Or LiveView from the Phoenix framework in the Elixir language which automagically renders backend partial updates and sends them quickly to the front end with minimal extra code, a feature so nice several frameworks now have their own versions of it, including one for Django (a Python framework) which doesn’t even use Web Sockets (most live view setups tend to use WebSockets)… regardless of what you chose to check out first, don’t be afraid to try a few backend frameworks to get a feel for things since there’s a big difference between more minimal ones like (using Python examples) Flask and FastAPI “micro frameworks” and more fully featured frameworks like Django and Django Rest Framework. Good luck on your new journey!