HUGO

Opinion: Tailwind CSS is pollution in the PostCSS tests

The supported activity is PostCSS yet most tests include and are thus polluted by TailwindCSS. Tailwind CSS should be removed from these tests and from Hugo documentation except where it is an example of framework specific configuration.

A developer reading the tests should not be forced to comprehend a specific framework. Rather, the test should isolate and be about the supported cabability, in this case PostCSS.