In the beginning there is no real rhyme or reason why you store your html files, because usually it's just a plus css file or something else.
However, when you go into real development, as is the case with the framework for the front-end + back-end code, you will find that there is a need to separate it on the server side and the public in the interests of controlling access to files and naming conventions.
If so, you are in the โAssetsโ folder, or โpublicโ or something like that. The boiler tends to follow this convention.
In order for the template template to automatically expand to all of your html files, you must develop your view files in order to be modular.
Main template file |
Also note that at this point your html will no longer be stored as a .html file type; you must use a language capable of combining files as chunks. PHP does it beautifully, and as you know, django can handle this as well. Ruby on rails, etc. You will need to decide what language you want to work in. OTHERWISE, the old html chunks concatenation method is the back end (aka SSI or .shtml)
The issue of the base URL is resolved if your server side language works with your web server directives. For apache, you use mod_rewrite, and then you can pass arg in a url that targets some classes / models / views, etc. MVC frameworks have actually solved this problem for you if you don't mind using it.
source share