generate css again

.github/workflows/main.yml

@@ -38,6 +38,11 @@ jobs:
           ghc-version: ${{ matrix.ghc }}
           stack-version: ${{ matrix.stack }}
 
+      - uses: actions/setup-node@v3
+        name: Setup NodeJS
+        with:
+          node-version: 18
+
       - uses: actions/cache@v3
         name: Cache ~/.stack
         with:
@@ -54,6 +59,11 @@ jobs:
       - name: Build site
         run:  stack exec --system-ghc site rebuild
 
+      - name: Build CSS
+        run:  |
+          npm ci
+          npm run build:production
+
       - name: Deploy
         # Deploy only from non-pull-request changes to hakyll branch
         if: ${{ github.event_name != 'pull_request' && github.ref == 'refs/heads/hakyll'}}

.gitignore

@@ -22,6 +22,9 @@ _site/
 stack.yaml.lock
 dist-newstyle/
 
+### NodeJS ###
+node_modules/
+
 ### General ###
 *~
 .DS_Store

assets/css/tailwind.css

@@ -0,0 +1,20 @@
+/**
+ * WARNING: This file will be overwritten when the site is built.
+ * Do not put anything in here that is unrelated to tailwind.
+ *
+ * NOTE: The underlying implementation details of how this works are as follows
+ * 1. tailwindcss needs these directives in order to know where to generate the
+ *    output
+ * 2. first, hackyll is run and will copy this file to
+ *    _sites/assets/tailwind.css
+ * 3. then, after hackyll is done, postcss will be ran on _this_
+ *    assets/tailwind.css file. Postcss will, during execution, invoke
+ *    tailwindcss. tailwindcss (the compiler) will scan all the files in the
+ *    site for tailwind classes (including _this_ assets/tailwind.css file).
+ * 4. postcss's output file is configured to be _site/assets/tailwind.css
+ *    (which causes this file to get overwritten with the correct contents)
+ */
+
+@tailwind base;
+@tailwind components;
+@tailwind utilities;