fix: don't do check on all builds
Checks can be done with `nix flake check`, no need to slow down build process with this.
feat: add static binary build instructions to docs
feat: add max-perf package
feat: add build-nix workflow
chore: add changelog
fix: fix max-perf-static packages not statically linking
feat: improve docs for building with nix
chore: more descriptive name for binary build step of workflow
fix: resolve review comment about Haswell CPUs
chore: enable __structuredAttrs on build
This is a good practice for modern nix packages
* Rename "You're done" to "Starting Your Server"
* Add instructions for initial registration token flow
* Shorten "How do I know it works" section
* Beautify "What's Next" section
* Link docker builds to section in dev pages
* Delete old section on port forwarding
* Create new section on port exposing, near reverse proxy section
* Rewrite Other Reverse Proxies section to update specified routes
* Move reverse proxy software caveats into its own subsection
* Other wording and structure fixes and improvements
* Use indirect URLs
* Change your.server.name to canonical example.com
* Put Getting help section in a tip admonition
* Remove statement on Caddy preference
* Clean up "What's next" section
Add documentation for the new performance-optimised Docker images with
"-maxperf" suffix. These use the release-max-perf build profile with LTO
and target haswell CPU architecture on amd64 for optimal performance.
Also restructure the static prebuilt binary section in generic deployment
docs for better clarity and fix various UK English spelling issues.
