chore: use md instead of qmd (#28)

.github/workflows/render.yaml

@@ -23,7 +23,7 @@ jobs:
           path: |
             docs
             _freeze
-          key: site-render-${{ hashFiles('**/*qmd') }}
+          key: site-render-${{ hashFiles('**/*md') }}
           restore-keys: site-render-
 
       - name: Render

_quarto.yml

@@ -2,7 +2,7 @@ project:
   type: website
   output-dir: docs
   render:
-    - "*.qmd"
+    - "*.md"
     - "*.md"
 
 website:
@@ -19,12 +19,12 @@ website:
     - text: "About"
       menu:
         - text: Community repository
-          url: community.qmd
+          url: community.md
         - text: Production repository
-          url: production.qmd
-    - users.qmd
-    - contributors.qmd
-    - team.qmd
+          url: production.md
+    - users.md
+    - contributors.md
+    - team.md
     - text: "Policies"
       menu:
         - review.md

community.qmd → community.md

@@ -18,7 +18,7 @@ Some releases may still have issues, as indicated by their check results, public
 
 ## Continuous maintainer-driven deployment
 
-Anyone can [contribute](contributors.qmd) packages to Community via GitHub.
+Anyone can [contribute](contributors.md) packages to Community via GitHub.
 Each package only needs to be registered once.
 
 Every new [release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository) then automatically deploys to the repository without needing to go through R-multiverse again.

contributors.qmd → contributors.md

@@ -57,7 +57,7 @@ In these cases, your text file may instead contain a JSON list with fields `pack
 
 To add a dynamic 'R-multiverse' badge for package readme files, like the one above, copy the following markdown snippet, replacing 'pkgNAME' with the actual package name in both places it appears:
 
-```{.md}
+```md
 [![R-multiverse status](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fcommunity.r-multiverse.org%2Fapi%2Fpackages%2FpkgNAME&query=%24.Version&label=r-multiverse)](https://community.r-multiverse.org/pkgNAME)
 ```
 

index.qmd → index.md

@@ -8,15 +8,15 @@ title: "R-multiverse"
 
 #### Community
 
-[community.r-multiverse.org](community.qmd)
+[community.r-multiverse.org](community.md)
 
 An open and inclusive R package repository with transparent governance standards, built on open source infrastructure.
 
 #### +
 
 #### Production
 
-[production.r-multiverse.org](production.qmd)
+[production.r-multiverse.org](production.md)
 
 A quarterly snapshot release of R packages, designed for deployment in production environments.
 

review.md

@@ -2,7 +2,7 @@
 title: "Review Policy"
 ---
 
-As the [contributors](contributors.qmd) page explains, updates to the R-multiverse package listings come from pull requests to <https://github.com/r-multiverse/contributions> from members of the R community. In the vast majority of cases, a GitHub app automatically merges the pull request. However, some pull requests need to be manually reviewed by an R-multiverse moderator. This document describes this manual review process. The goals are to:
+As the [contributors](contributors.md) page explains, updates to the R-multiverse package listings come from pull requests to <https://github.com/r-multiverse/contributions> from members of the R community. In the vast majority of cases, a GitHub app automatically merges the pull request. However, some pull requests need to be manually reviewed by an R-multiverse moderator. This document describes this manual review process. The goals are to:
 
 1. Ensure that all pull requests are reviewed using a consistent set of standards and principles that do not vary according to moderator.
 2. Ensure these standards and principles are clear and transparent for the R community.

team.qmd → team.md

@@ -102,7 +102,7 @@ He is one of the maintainers for the [Rocker](https://rocker-project.org/) proje
 ## Roles
 
 * Administrators build the team, develop the infrastructure, and write the policies that govern R-multiverse.
-* Moderators review [package contributions](contributors.qmd) according to the [package review policy](review.md).
+* Moderators review [package contributions](contributors.md) according to the [package review policy](review.md).
 
 ## Support
 

users.qmd → users.md

@@ -28,7 +28,7 @@ Then proceed to use `install.packages()` or `pak::pak()` etc. as you would norma
 
 Many R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of CRAN policy.
 
-By [contributing](contributors.qmd) a package to R-multiverse, you may conveniently install the latest released versions of all these packages from a single repository location.
+By [contributing](contributors.md) a package to R-multiverse, you may conveniently install the latest released versions of all these packages from a single repository location.
 :::
 
 ::: {.callout-tip collapse="true"}
@@ -41,7 +41,7 @@ A package may become unavailable on CRAN at any time due to its strict archival
 - Sometimes due to the archival of a dependency, and outside the maintainer's direct control.
 - Situations can be temporary, but may take an extended time to resolve.
 
-By [contributing](contributors.qmd) a package that you rely on, you can ensure it always remains available for your critical workflows.
+By [contributing](contributors.md) a package that you rely on, you can ensure it always remains available for your critical workflows.
 :::
 
 ::: {.callout-tip collapse="true"}