"my website is one binary"
<link rel="stylesheet" href="/static/style.css" type="text/css">
Well then...
<link rel="stylesheet" href="/static/style.css" type="text/css">
Well then...
In this case, the content served in response to the identifier "/static/style.css" can very easily (and according to the author, is) baked directly into the (single) binary.
Seriously, people should try doing a lot more inlining than they do.
Then again, for 3KB the overhead of doing a cache check after parsing the HTML for the first time and then rendering it again may already be too much :)
It just uses go's built-in http.FileServer(..) to serve files from a directory.