feat: add release workflow to build and attach rendered site as release asset

.github/workflows/release.yml

@@ -0,0 +1,55 @@
+on:
+  release:
+    types: [published]
+
+name: Attach Rendered Site to Release
+
+permissions:
+  contents: write
+
+jobs:
+  build-and-attach:
+    name: Build Site and Upload Release Asset
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v5
+
+      - name: Overwrite _quarto.yml
+        if: github.repository == 'maehr/open-research-data-template'
+        run: |
+          cp .github/_quarto.yml _quarto.yml
+
+      - name: Set up Quarto
+        uses: quarto-dev/quarto-actions/setup@v2
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+
+      - name: Setup R
+        uses: r-lib/actions/setup-r@v2
+        with:
+          r-version: renv
+      - uses: r-lib/actions/setup-renv@v2
+
+      - name: Render Quarto Project
+        uses: quarto-dev/quarto-actions/render@v2
+        with:
+          to: html
+
+      - name: JamPack Optimization
+        run: |
+          npx @divriots/jampack ./_site
+
+      - name: Package site into ZIP
+        run: |
+          cd _site
+          zip -r ../site-${{ github.event.release.tag_name }}.zip .
+
+      - name: Upload release asset
+        uses: softprops/action-gh-release@v2
+        with:
+          files: site-${{ github.event.release.tag_name }}.zip

AGENTS.md

@@ -114,6 +114,7 @@ Place new files accordingly.
 ## 10) Zenodo Integration and DOI (Project instances)
 
 - **Enable Zenodo–GitHub integration** to archive releases and mint DOIs.
+- The `release.yml` workflow automatically builds the rendered site and attaches it as a `site-<tag>.zip` release asset so that Zenodo archives the HTML documentation alongside the source code.
 - After first release:
   - Record your **`ZENODO_RECORD`** and **`DOI`**.
   - **Zenodo DOI badge**: replace `GITHUB_REPO_ID` with the numeric repo ID from `https://api.github.com/repos/USERNAME/REPO_NAME` (`id` field). Badge will display your DOI after Zenodo links the release.

README.md

@@ -34,7 +34,7 @@ Conventional data publication as static supplementary files offers limited repro
 ### Open Research Data
 
 - Citable via [DOI](https://www.doi.org/) and [CITATION.cff](https://citation-file-format.github.io/)
-- Automatic long-term archiving with [Zenodo](https://zenodo.org/)
+- Automatic long-term archiving with [Zenodo](https://zenodo.org/), including the rendered documentation site as a release asset
 - Licensed under [AGPL 3.0](https://www.gnu.org/licenses/agpl-3.0.html) and [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed) according to [The Turing Way](https://the-turing-way.netlify.app/reproducible-research/rdm/rdm-sharing.html#step-3-choose-a-licence-and-link-to-your-paper-and-code)
 - Template for reporting data issues via `github/ISSUE_TEMPLATE/data_issue_report.yml`
 
@@ -67,7 +67,7 @@ Conventional data publication as static supplementary files offers limited repro
 ### Ethics
 
 - `CODE_OF_CONDUCT.md` following the [Contributor Covenant](https://www.contributor-covenant.org/)
-- Supportive first interactions via [Greetings](https://github.com/actions/starter-workflows/blob/main/automation/greetings.yml)
+
 
 ## Selected Use Cases
 

TODO.md

@@ -36,6 +36,8 @@ Complete the following steps after creating your project from this template to c
 
 - [ ] **Review Project-Management Files**: Populate or remove the files in `project-management/` before publishing. These are placeholder templates for meeting notes and project plans.
 
+- [ ] **Rendered Site in Releases**: The `release.yml` workflow automatically builds the Quarto site and attaches a `site-<tag>.zip` to each GitHub release. This ensures the rendered HTML documentation is preserved alongside the source archive when Zenodo captures the release.
+
 ## Verification Steps
 
 After completing the checklist: