Documentation
¶
Overview ¶
Command tailwind-build compiles the web UI's static Tailwind CSS using the Tailwind standalone CLI — a self-contained binary from the tailwindlabs release page. Nobody (contributor or CI) needs Node.js or npm: the wrapper downloads the pinned CLI release for the host platform into the user cache directory, verifies its sha256, and runs it.
Invoked by `go generate` from internal/web (see static.go):
go run github.com/dotwaffle/peeringdb-plus/cmd/tailwind-build \
-in tailwind.input.css -out static/tailwind.css
The output is committed like the *_templ.go files; the CI drift gate re-runs generation and fails on any difference, so a stale tailwind.css cannot ship silently.
Upgrading Tailwind: bump cliVersion, refresh cliSHA256 from the release's sha256sums.txt, run `go generate ./...`, commit the CSS churn alongside.