update r-universe links for community

_quarto.yml

@@ -33,7 +33,7 @@ website:
             url: https://github.com/r-multiverse/help
       - icon: rocket-takeoff
         aria-label: "R-multiverse Community Universe"
-        href: https://r-community.r-universe.dev/
+        href: https://r-multiverse-community.r-universe.dev
   page-footer:
     center: "© 2024 the R-multiverse project."
 

about.qmd

@@ -6,14 +6,14 @@ title: "What is R-multiverse?"
 
 A traditional software version cycle begins with the development phase, where bugs are expected and ironed out, and ends with the production phase, which promises a seamless user experience.
 
-R-multiverse currently aims at a space just before production, commonly referred to as Quality Assurance (QA). This means that:
+R-multiverse Community currently aims at a space just before production, commonly referred to as Quality Assurance (QA). This means that:
 
 1. Each package release has the full endorsement of its own maintainer. R-multiverse always provides a version that its developer chose to distribute for general use.
-2. The user is still responsible for judging whether a package is appropriate to use. Some releases may still have issues, and these may be indicated by the check results at <https://r-community.r-universe.dev>.
+2. The user is still responsible for judging whether a package is appropriate to use. Some releases may still have issues, and these may be indicated by the check results at <https://r-multiverse-community.r-universe.dev>.
 
 ## Continuous maintainer-driven deployment
 
-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) automatically deploys to <https://r-multiverse.org> without needing to go through R-multiverse again. In other words, the package maintainer is in complete control. This frictionless, maintainer-driven experience was made possible by the incredible infrastructure of [rOpenSci's R-universe system](https://r-community.r-universe.dev) managed by [Jeroen Ooms](https://github.com/jeroen/).
+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) automatically deploys to <https://community.r-multiverse.org> without needing to go through R-multiverse again. In other words, the package maintainer is in complete control. This frictionless, maintainer-driven experience was made possible by the incredible infrastructure of [rOpenSci's R-universe system](https://r-community.r-universe.dev) managed by [Jeroen Ooms](https://github.com/jeroen/).
 
 ## What about my personal R-universe?
 

contributors.qmd

@@ -47,12 +47,12 @@ In rare cases, the package may be in a subdirectory of a GitHub repo. In these c
 
 ## How to create a badge
 
-[<img src="https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fr-community.r-universe.dev%2Fapi%2Fpackages%2Fmirai&query=%24.Version&label=R-multiverse" alt="R-multiverse status" />](https://r-community.r-universe.dev/mirai)
+[<img src="https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fcommunity.r-multiverse.org%2Fapi%2Fpackages%2Fmirai&query=%24.Version&label=R-multiverse" alt="R-multiverse status" />](https://community.r-multiverse.org/mirai)
 
 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}
-[![R-multiverse status](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fr-community.r-universe.dev%2Fapi%2Fpackages%2FpkgNAMEquery=%24.Version&label=R-multiverse)](https://r-community.r-universe.dev/pkgNAME)
+[![R-multiverse status](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fcommunity.r-multiverse.org%2Fapi%2Fpackages%2FpkgNAMEquery=%24.Version&label=R-multiverse)](https://community.r-multiverse.org/pkgNAME)
 ```
 
 ## How to edit or remove packages
@@ -65,7 +65,7 @@ An automated process periodically scans each new pull request to <https://github
 
 ## How the R-multiverse universe is built
 
-Periodically, a GitHub Actions workflow collects all the packages and URLs from the [`packages`](https://github.com/r-multiverse/contributions/tree/main/packages) folder and builds the `packages.json` file for the universe at <https://github.com/r-multiverse/r-multiverse.r-universe.dev>. <https://r-multiverse.r-universe.dev> periodically refreshes to include the latest release of each package in `packages.json`.
+Periodically, a GitHub Actions workflow collects all the packages and URLs from the [`packages`](https://github.com/r-multiverse/contributions/tree/main/packages) folder and builds the `packages.json` file for the universe at <https://github.com/r-multiverse/community>. <https://r-multiverse-community.r-universe.dev> periodically refreshes to include the latest release of each package in `packages.json`.
 
 ## Ownership and attribution
 

index.qmd

@@ -6,6 +6,6 @@ title: "R-multiverse"
 
 A community-curated collection of R package releases, powered by [R-universe](https://r-universe.dev), available for installation from the repository at <https://community.r-multiverse.org>.
 
-Anyone can contribute packages to the GitHub repository at <https://github.com/r-multiverse/contributions>. Once a package is registered, every new release is automatically built and checked with results available at <https://r-community.r-universe.dev>. Package maintainers retain complete control over deployment.
+Anyone can contribute packages to the GitHub repository at <https://github.com/r-multiverse/contributions>. Once a package is registered, every new release is automatically built and checked with results available at <https://r-multiverse-community.r-universe.dev>. Package maintainers retain complete control over deployment.
 
 The R-multiverse project originated from the [R Consortium Repositories Working Group](https://github.com/RConsortium/r-repositories-wg).