First, please read the [CONTRIBUTING](CONTRIBUTING.md) document. This project adheres to the contributors covenant, https://www.contributor-covenant.org/.
The build and release process involves code generation in a few ways that aren't obvious.
1.`go generate ./...` generates error structures and sources used to bundle files in the compiled binary.
2.`openssl dgst -sha384 -binary the_file.whatever | openssl base64 -A` is used to create SRI hashes (`integrity="sha384-decafbad"`) in included CSS and JS files.
The `-tags prod` argument can be used to indicate prod vs non-prod sources. When the `prod` flag **is not** present, asset packages will load content from disk, but will still contain file path references. In other words, whenever you create or delete files including templates, migrations, or translations, you must run `go generate ./...`.