Implement a GH Page Action instead of relying on Quarto's Publish and…

… Render

.github/workflows/publish-docs.yml

@@ -24,8 +24,27 @@ jobs:
           with:
             version: "pre-release"
 
-        - name: Publish to GitHub Pages (and render)
-          uses: quarto-dev/quarto-actions/publish@v2
-          with:
-              target: gh-pages
-              path: docs
+        # Change to the docs directory
+        - name: "Switch to docs directory"
+          shell: bash
+          run: |
+            cd docs/
+
+        # Render the Quarto file
+        - name: "Render working directory"
+          uses: quarto-dev/quarto-actions/render@v2
+
+        # Upload a tar file that will work with GitHub Pages
+        # Make sure to set a retention day to avoid running into a cap
+        # This artifact shouldn't be required after deployment onto pages was a success.
+        - name: Upload Pages artifact
+          uses: actions/upload-pages-artifact@v2
+          with: 
+            retention-days: 1
+
+        # Use an Action deploy to push the artifact onto GitHub Pages
+        # This requires the `Action` tab being structured to allow for deployment
+        # instead of using `docs/` or the `gh-pages` branch of the repository
+        - name: Deploy to GitHub Pages
+          id: deployment
+          uses: actions/deploy-pages@v2