Load Tailwind CSS (not site)

[egrace479]

Install link: https://tailwindcss.com/docs/installation/using-vite

[EmersonFras]

Copilot introduced Vite as the build tool for the Tailwind CSS integration, which is the standard/recommended approach per Tailwind's docs. However, since the project now requires a build step, the way GitHub Pages serves files needs to change, specifically, a GitHub Actions workflow needs to be added to auto-build the project before deployment, and the repo's Pages settings will need to be updated to use GitHub Actions as the build & deployment source rather than deploying directly from a branch.

An alternative is the Tailwind CLI, which simply generates a compiled CSS file without needing Vite at all. Since main.js has no npm package imports, Vite's JS bundling provides no benefit here. The downside is that contributors would need to manually compile the CSS before pushing changes, introducing a human-error risk (e.g. forgetting to run the compile step).

After discussion, using Vite is the preferred approach. While it requires more one-time setup overhead (GitHub Action + Pages configuration), it keeps the local dev experience simple (single npm run dev command) and removes the risk of contributors accidentally pushing uncompiled CSS. The initial overhead is a one-time cost, ongoing contribution stays straightforward.