Deploying to gh-pages from @ 0d8c006 🚀

about.html

@@ -191,7 +191,7 @@ <h2 class="anchored" data-anchor-id="what-about-my-personal-r-universe">What abo
 
 </section>
 
-<p><br>© 2024 the R-releases project</p></main> <!-- /main -->
+<p><br>© 2024 the R-releases project.</p></main> <!-- /main -->
 <script id="quarto-html-after-body" type="application/javascript">
 window.document.addEventListener("DOMContentLoaded", function (event) {
   const toggleBodyColorMode = (bsSheetEl) => {

conduct.html

@@ -254,7 +254,7 @@ <h2 class="anchored" data-anchor-id="attribution">Attribution</h2>
 
 </section>
 
-<p><br>© 2024 the R-releases project</p></main> <!-- /main -->
+<p><br>© 2024 the R-releases project.</p></main> <!-- /main -->
 <script id="quarto-html-after-body" type="application/javascript">
 window.document.addEventListener("DOMContentLoaded", function (event) {
   const toggleBodyColorMode = (bsSheetEl) => {

contributors.html

@@ -208,7 +208,7 @@ <h1 class="title">Contributors</h1>
 </header>
 
 
-<p>The <a href="https://r-releases.github.io/conduct.html">code of conduct</a> governs all forms of participation in the R-releases project, including package contributions, issues, discussions, and the development of infrastructure. Administrators, moderators, and contributors are all subject to its terms.</p>
+<p>The <a href="conduct.html">code of conduct</a> governs all forms of participation in the R-releases project, including package contributions, issues, discussions, and the development of infrastructure. Administrators, moderators, and contributors are all subject to its terms.</p>
 <section id="how-to-register-your-package-with-r-releases" class="level2">
 <h2 class="anchored" data-anchor-id="how-to-register-your-package-with-r-releases">How to register your package with R-releases</h2>
 <p>The one-time registration process proceeds as follows:</p>
@@ -257,7 +257,7 @@ <h2 class="anchored" data-anchor-id="getting-help">Getting help</h2>
 
 </section>
 
-<p><br>© 2024 the R-releases project</p></main> <!-- /main -->
+<p><br>© 2024 the R-releases project.</p></main> <!-- /main -->
 <script id="quarto-html-after-body" type="application/javascript">
 window.document.addEventListener("DOMContentLoaded", function (event) {
   const toggleBodyColorMode = (bsSheetEl) => {

review.html

@@ -205,7 +205,7 @@ <h2 class="anchored" data-anchor-id="the-automated-review-process">The automated
 <h2 class="anchored" data-anchor-id="the-manual-review-process">The manual review process</h2>
 <p>If a pull request is flagged for manual review, an R-releases moderator will read the pull request and ask questions if necessary. Although the moderator may make optional suggestions on a case-by-case basis, package reviews must be consistent, reliable, and inclusive whenever possible. The decision to close or merge the pull request must be based exclusively on the following pre-defined list of requirements:</p>
 <ol type="1">
-<li>Each contribution must comply with the <a href="https://r-releases.github.io/conduct.html">code of conduct</a>. Examples of prohibited content include profanity, malicious behavior, security risks, copyright violations, and other conduct which could reasonably be considered inappropriate in a professional setting. All this applies to the package, the URL, any other metadata in the contribution, and the contents of the package itself.</li>
+<li>Each contribution must comply with the <a href="conduct.html">code of conduct</a>. Examples of prohibited content include profanity, malicious behavior, security risks, copyright violations, and other conduct which could reasonably be considered inappropriate in a professional setting. All this applies to the package, the URL, any other metadata in the contribution, and the contents of the package itself.</li>
 <li>Each contributed URL must point to an existing GitHub or GitLab repository.</li>
 <li>Each text file must apply to only one package.</li>
 <li>The text file name must be the name of the package.</li>
@@ -220,7 +220,7 @@ <h2 class="anchored" data-anchor-id="the-manual-review-process">The manual revie
 
 </section>
 
-<p><br>© 2024 the R-releases project</p></main> <!-- /main -->
+<p><br>© 2024 the R-releases project.</p></main> <!-- /main -->
 <script id="quarto-html-after-body" type="application/javascript">
 window.document.addEventListener("DOMContentLoaded", function (event) {
   const toggleBodyColorMode = (bsSheetEl) => {

search.json

@@ -4,7 +4,7 @@
     "href": "conduct.html",
     "title": "Code of Conduct",
     "section": "",
-    "text": "We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.\nWe pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.\n© 2024 the R-releases project"
+    "text": "We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.\nWe pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.\n© 2024 the R-releases project."
   },
   {
     "objectID": "conduct.html#our-pledge",
@@ -60,7 +60,7 @@
     "href": "contributors.html",
     "title": "Contributors",
     "section": "",
-    "text": "The code of conduct governs all forms of participation in the R-releases project, including package contributions, issues, discussions, and the development of infrastructure. Administrators, moderators, and contributors are all subject to its terms.\n© 2024 the R-releases project"
+    "text": "The code of conduct governs all forms of participation in the R-releases project, including package contributions, issues, discussions, and the development of infrastructure. Administrators, moderators, and contributors are all subject to its terms.\n© 2024 the R-releases project."
   },
   {
     "objectID": "contributors.html#how-to-register-your-package-with-r-releases",
@@ -109,7 +109,7 @@
     "href": "about.html",
     "title": "What is R-releases?",
     "section": "",
-    "text": "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.\nR-releases aims at a space just before production, commonly referred to as QA, in that:\n\nEach package release has the full endorsement of its own maintainer. R-releases always gives you a version that its developer chose to distribute for general use.\nThe user is still responsible for judging whether a package is appropriate to use. This judgement may require more than a novice understanding of testing, versions, and package compatibility.\n© 2024 the R-releases project"
+    "text": "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.\nR-releases aims at a space just before production, commonly referred to as QA, in that:\n\nEach package release has the full endorsement of its own maintainer. R-releases always gives you a version that its developer chose to distribute for general use.\nThe user is still responsible for judging whether a package is appropriate to use. This judgement may require more than a novice understanding of testing, versions, and package compatibility.\n© 2024 the R-releases project."
   },
   {
     "objectID": "about.html#the-quality-assurance-qa-for-r-packages",
@@ -137,7 +137,7 @@
     "href": "users.html",
     "title": "Users",
     "section": "",
-    "text": "Simply add R-releases to your repository settings:\noptions(repos = c(\"https://r-releases.r-universe.dev\", getOption(\"repos\")))\nR natively supports multiple repositories as a core language feature, and the above only needs to be set once per session. We recommend adding it to your .Rprofile so that it is always available.\nAlternatively, to prioritize CRAN over R-releases:\noptions(repos = c(getOption(\"repos\"), \"https://r-releases.r-universe.dev\"))\nThen proceed to use install.packages() or pak::pak() etc. as you would normally.\n© 2024 the R-releases project"
+    "text": "Simply add R-releases to your repository settings:\noptions(repos = c(\"https://r-releases.r-universe.dev\", getOption(\"repos\")))\nR natively supports multiple repositories as a core language feature, and the above only needs to be set once per session. We recommend adding it to your .Rprofile so that it is always available.\nAlternatively, to prioritize CRAN over R-releases:\noptions(repos = c(getOption(\"repos\"), \"https://r-releases.r-universe.dev\"))\nThen proceed to use install.packages() or pak::pak() etc. as you would normally.\n© 2024 the R-releases project."
   },
   {
     "objectID": "users.html#how-to-install-a-package-from-r-releases",
@@ -151,7 +151,7 @@
     "href": "users.html#a-home-for-non-cran-packages",
     "title": "Users",
     "section": "A home for non-CRAN packages",
-    "text": "A home for non-CRAN packages\nMany R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of current CRAN policy. By contributing a package to R-releases, you may conveniently install the latest released versions of these packages from a single repository location."
+    "text": "A home for non-CRAN packages\nMany R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of current CRAN policy.\nBy contributing a package to R-releases, you may conveniently install the latest released versions of these packages from a single repository location."
   },
   {
     "objectID": "users.html#a-guarantee-of-package-availability",
@@ -172,7 +172,7 @@
     "href": "review.html",
     "title": "Review Policy",
     "section": "",
-    "text": "As the contributors page explains, updates to the R-releases package listings come from pull requests to https://github.com/r-releases/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-releases moderator. This document describes this manual review process. The goals are to:\n© 2024 the R-releases project"
+    "text": "As the contributors page explains, updates to the R-releases package listings come from pull requests to https://github.com/r-releases/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-releases moderator. This document describes this manual review process. The goals are to:\n© 2024 the R-releases project."
   },
   {
     "objectID": "review.html#the-automated-review-process",

users.html

@@ -217,7 +217,8 @@ <h2 class="anchored" data-anchor-id="how-to-install-a-package-from-r-releases">H
 </section>
 <section id="a-home-for-non-cran-packages" class="level2">
 <h2 class="anchored" data-anchor-id="a-home-for-non-cran-packages">A home for non-CRAN packages</h2>
-<p>Many R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of current CRAN policy. By <a href="contributors.html">contributing</a> a package to R-releases, you may conveniently install the latest released versions of these packages from a single repository location.</p>
+<p>Many R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of current CRAN policy.</p>
+<p>By <a href="contributors.html">contributing</a> a package to R-releases, you may conveniently install the latest released versions of these packages from a single repository location.</p>
 </section>
 <section id="a-guarantee-of-package-availability" class="level2">
 <h2 class="anchored" data-anchor-id="a-guarantee-of-package-availability">A guarantee of package availability</h2>
@@ -238,7 +239,7 @@ <h2 class="anchored" data-anchor-id="a-direct-distribution-channel-from-maintain
 
 </section>
 
-<p><br>© 2024 the R-releases project</p></main> <!-- /main -->
+<p><br>© 2024 the R-releases project.</p></main> <!-- /main -->
 <script id="quarto-html-after-body" type="application/javascript">
 window.document.addEventListener("DOMContentLoaded", function (event) {
   const toggleBodyColorMode = (bsSheetEl) => {