The portal-shell scaffold shipped a `postcss.config.js`, but
`@angular/build` (Angular 17+ esbuild pipeline) does not load that
file format — it only picks up `.postcssrc.json`. Result: the
`@tailwindcss/postcss` plugin was never registered, Tailwind ran
with no source files visible, generated only its `@theme` block,
and dropped every utility class on the floor. The page rendered
unstyled — black text on white — even though `nx build` reported
success and shipped a 23 KB styles.css.
Fix: rename / re-encode the config to `.postcssrc.json`. Same
plugin, same options, just the file format Angular's esbuild
adapter actually reads.
Verified locally:
- Before: ZERO class selectors in dist/.../styles*.css.
- After: 75 selectors in production build, including the ones
referenced from header/footer/home/accessibility templates
(`.text-3xl`, `.bg-amber-50`, `.font-semibold`, etc.).
The repo-layout walkthrough in `docs/development.md` is updated to
reflect the new file name and explicitly call out the gotcha so a
future contributor doesn't reach for `postcss.config.js` again.
Julien Gautier
bb9654cc32