Hello John,
As Jane alluded to, for your scripts, css, images, etc., you just have to ensure your link headers point to the correct location. Here's an excerpt from one of my apps:
<link rel="manifest" href="/manifest.json" />
<link href="/themes/base/theme.css?c=1" rel="stylesheet" />
<link href="/redactor/redactor.min.css?c=1" rel="stylesheet" />
<link href="/styles/firefox.css?c=1" rel="stylesheet"/>
<script src="/scripts/all.js?c=1" type="text/javascript"></script>
<script src="/serviceworker.js" type="text/javascript"></script>
<script src="/scripts/pwa.js" type="text/javascript"></script>
<script src="/redactor/redactor.min.js?c=1" type="text/javascript"></script>
<script src="/scripts/custom.js?c=1" type="text/javascript"></script>
<script src="/scripts/jquery.timepicker.min.js?c=1" type="text/javascript"></script>
For a static site, I simply use the existing defeult NetTalk folders and adjust the static pages' headers to point to the NetTalk folders.
As Jane mentioned, by adding the tag <!-- Net:WebServer --> at the top of your static pages' html you can embed dynamically generated NetTalk pages, forms, and browses into your static content.
Come to think of it, there's liitle you cannot do with a NetTalk webserver. It's a very powerful platform and you get the added benifit of consistant security upgrades as long as you keep your NetTalk up to date. I guess that's why so many of us have committed to NetTalk and never looked back.
Best of luck on your project and feel free to ask for help.
Don