Entirely inside Ignition, you can use the Webdev module to ‘host’ a directory on the filesystem and expose it.
Or (my recommendation), you can put a webserver ‘in front of’ Ignition that will actually receive requests (and serve the static files) and then reverse-proxy to Ignition on appropriate routes. On a Linux system, nginx is my go-to for this, because it’s reasonably easy to set up, very well documented, and very performant/stable. I don’t know of equivalent software for Windows. If you are using SSL, this also makes it a bit easier, as usually SSL and renewal procedures are well documented for off-the-shelf server hosting solutions.