Attach built Quarto site to release assets and add maintainer docs

[Copilot]

Pull request

Proposed changes

Manual releases should archive the rendered Quarto site as a release asset so Zenodo captures the deployed documentation without committing build artifacts. This update adds release-time packaging and upload of the built site, and includes maintainer documentation in .github for release handling and upkeep.

• Release publish workflow: rebuild/optimize the Quarto site on release.published, archive _site, and upload the archive to the existing release.
• Asset packaging: provide a single site.tar.gz payload for downstream archiving tools.
• Maintainer docs: add .github/MAINTAINERS.md with release asset guidance and routine maintenance steps.

- name: Compress built site
  run: tar -czf site.tar.gz -C _site .
- name: Upload site to release
  run: gh release upload ${{ github.event.release.tag_name }} site.tar.gz --clobber

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Original prompt

Implement #33

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[maehr]

@copilot add documentation in .github folder for maintainers

[Copilot]

@copilot add documentation in .github folder for maintainers

Added .github/MAINTAINERS.md with maintainer guidance and release asset notes in 55e7409.

[Copilot]

Pull request overview

This PR adds a release-time workflow to rebuild and archive the Quarto site as a site.tar.gz asset on manual GitHub Releases, and updates documentation to guide maintainers and template users on archiving and workflow behavior.

Changes:

• Introduces .github/workflows/release-site.yml to render the Quarto site on release: published, JamPack-optimize it, archive _site as site.tar.gz, and upload it to the corresponding GitHub Release.
• Removes the generic built-site upload artifact from the Quarto publish workflow, keeping only the Pages deployment artifact.
• Updates README, TODO, AGENTS, and new .github/MAINTAINERS.md to explain the archiving model (CI artifacts vs Pages vs release assets vs Zenodo) and to expand template customization guidance.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
TODO.md	Adds CITATION.cff and DESCRIPTION to the placeholder-update checklist and a new checklist item describing the site.tar.gz release archive workflow.
README.template.md	Documents the new “Archiving and Artifacts” model, including the site.tar.gz release asset and Zenodo integration, for downstream projects.
README.md	Mirrors the “Archiving and Artifacts” explanation for the template repository’s own documentation.
AGENTS.md	Extends placeholder replacement and repository-structure guidance, adds a protected-files section, updates section numbering, and clarifies archiving via releases and Zenodo.
.github/workflows/release-site.yml	New workflow that builds, optimizes, tars, and uploads the Quarto _site directory as site.tar.gz to a published GitHub Release using gh release upload.
.github/workflows/quarto-publish.yml	Removes the now-redundant generic actions/upload-artifact step for _site, leaving only the Pages upload (actions/upload-pages-artifact).
.github/MAINTAINERS.md	New maintainer doc explaining routine maintenance, formatting/linting, and how manual releases trigger release-site.yml to attach site.tar.gz to releases.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

For the template repository itself (maehr/open-research-data-template), this workflow renders using the templated _quarto.yml instead of the template-specific .github/_quarto.yml, so the archived site.tar.gz for releases won’t match the site that GitHub Pages deploys from quarto-publish.yml (which conditionally overwrites _quarto.yml). To keep the release archive consistent with the deployed documentation, consider adding a conditional “Overwrite _quarto.yml” step here mirroring the one in .github/workflows/quarto-publish.yml (guarded with if: github.repository == 'maehr/open-research-data-template') before the Quarto render step.