Publish previews using netlify (#166)

* Publish previews using netlify

* Remove GH preview workflow

* Remove staging explanation from contrib guide

* Remove pr-target-test job

* Add build with Netlify badge for open source program

Author: maxrjones

.github/workflows/ci.yml

@@ -8,18 +8,7 @@ on:
   pull_request:
 
 jobs:
-  pr-target-test:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Fail if target is not staging (for PRs only)
-        if: github.event_name == 'pull_request'
-        run: |
-          if [[ "${{ github.event.pull_request.base.ref }}" != "main" || "${{ github.event.pull_request.head.ref }}" == "staging" ]]; then
-            echo "Target branch is acceptable."
-          else
-            echo "Only PRs from staging can target main."
-            exit 1
-          fi
+
 
   tests:
     runs-on: ubuntu-latest

.github/workflows/preview.yml

@@ -10,18 +10,6 @@ We encourage contributions to this guide. The guide's goal is to provide documen
 
 If you wish to preview the site locally, install [quarto](https://quarto.org/). You will also need to be familiar with [quarto markdown](https://quarto.org/docs/authoring/markdown-basics.html).
 
-## Contribution Workflow
-
-Due to previews only working from branches within the repository and not external forks (see: [#74](https://github.com/cloudnativegeo/cloud-optimized-geospatial-formats-guide/issues/74)), all PRs should target staging. More specifically, the contribution workflow follows these steps:
-
-1. PR is made with `staging` as target.
-
-2. Maintainer will merge the PR to staging and then open a PR to main (build preview will run).
-
-3. Maintainers merge to main which triggers the production deployment.
-
-The process is not ideal, and we are open to suggestions on how to improve upon it. The main constraint is the [`pr-preview-action`](https://github.com/rossjrw/pr-preview-action) not supporting previews on external contributions. 
-
 ## Communication Channels
 
 Discussions can occur in [GitHub Discussions](https://github.com/cloudnativegeo/cloud-optimized-geospatial-formats-guide/discussions) and issues can be raised at [GitHub Issues](https://github.com/cloudnativegeo/cloud-optimized-geospatial-formats-guide/issues).

contributing.qmd

@@ -97,3 +97,9 @@ Most of the data formats covered in this guide have a Jupyter Notebook example t
 5. How much of your data is typically rendered or selected at once?
 
 {{< include _thankyous.qmd >}}
+
+```{=html}
+<a href="https://www.netlify.com">
+  <img src="https://www.netlify.com/assets/badges/netlify-badge-color-accent.svg" alt="Deploys by Netlify" />
+</a>
+```

index.qmd

@@ -0,0 +1,2 @@
+[[plugins]]
+package = "@quarto/netlify-plugin-quarto"

netlify.toml

@@ -0,0 +1,5 @@
+{
+  "dependencies": {
+    "@quarto/netlify-plugin-quarto": "^0.0.5"
+  }
+}