I'm no longer mostly doing web dev, so take with a grain of salt. But I believe you are looking for something that has been considered "not a best practice" for almost ten years now, which is why you are having trouble finding it.<p>Over the last decade, people moved away from thinking of a backend+frontend combo as being the correct abstraction, and more towards thinking of a web client as just another client, akin to a mobile client, which happens to be connected to an API. Because of the very different needs of the two parts, it became much more popular to split them up (either conceptually, or with actual separate codebases being deployed separately).<p>So nowadays, the standard way of looking at things is to pick some kind of framework for building a backend, e.g. Django, and some kind of front-end framework, e.g. ReactJS, and develop them separately.<p>I'm not saying this is the only way to do things, but I believe this is correct approach a lot of the time.