static content is delivered via the content folder. but this causes use, be prefent the delivering of raw markdown files, which are located in that folder.
the basic idea is to add a new folder, maybe named www, where all static content like robots.txt or favicon.ico. every content in that folder will be public available.
the request processing may check if the current requests matchs one of the static files, if yes deliver it, otherwise do the default request processing.
static content is delivered via the content folder. but this causes use, be prefent the delivering of raw markdown files, which are located in that folder.
the basic idea is to add a new folder, maybe named www, where all static content like robots.txt or favicon.ico. every content in that folder will be public available.
the request processing may check if the current requests matchs one of the static files, if yes deliver it, otherwise do the default request processing.