fix hyperlink issue

docs/minutes.html

@@ -221,7 +221,7 @@ <h1 class="title">Meeting Minutes</h1>
 </tr>
 </thead>
 <tbody class="list">
-<tr data-index="0" data-listing-date-sort="1709856000000" data-listing-file-modified-sort="1711728737705" data-listing-reading-time-sort="2.96" data-listing-title-sort="Minutes 2024-03-08" data-listing-filename-sort="index.qmd">
+<tr data-index="0" data-listing-date-sort="1709856000000" data-listing-file-modified-sort="1711734865623" data-listing-reading-time-sort="2.96" data-listing-title-sort="Minutes 2024-03-08" data-listing-filename-sort="index.qmd">
 <td class="listing-date">
 Mar 8, 2024
 </td>

docs/minutes.xml

@@ -44,14 +44,14 @@ View Attendee List
 <section id="meeting-minutes" class="level2">
 <h2 class="anchored" data-anchor-id="meeting-minutes">Meeting Minutes</h2>
 <ul>
-<li>Eric shared the status of his initial tests of the web-assembly version of the application available at https://github.com/RConsortium/submissions-pilot4-webR
+<li>Eric shared the status of his initial tests of the web-assembly version of the application available at <a href="https://github.com/RConsortium/submissions-pilot4-webR" class="uri">https://github.com/RConsortium/submissions-pilot4-webR</a>
 <ul>
 <li>Application works successfully when using work computer browser (Edge), however on his Linux machine certain browsers (Edge) were not able to view the application, while other chrome-variant browsers had no issue</li>
 <li>Sam mentioned he encountered a few issues running the app in his work browser, but was successful after discussions with IT</li>
 <li>Additional testing will be paramount prior to transfer to FDA</li>
 <li>Eric will prepare the repository with a few minor enhancements in preparation for wider testing amongst the group. Ben mentioned that with the Pilot 3 effort winding down, there could be additional resources available for testing soon.</li>
 </ul></li>
-<li>When the web-R binary packages are being pulled down from the webR CDN, there isn’t a clear way to pin those to a specific version, unlike renv when we can indeed control versions of packages installed. A comment on a separate issue https://github.com/posit-dev/r-shinylive/issues/56 indicates there will be a future state when pinning package versions is possible.</li>
+<li>When the web-R binary packages are being pulled down from the webR CDN, there isn’t a clear way to pin those to a specific version, unlike renv when we can indeed control versions of packages installed. A comment on a separate issue <a href="https://github.com/posit-dev/r-shinylive/issues/56" class="uri">https://github.com/posit-dev/r-shinylive/issues/56</a> indicates there will be a future state when pinning package versions is possible.</li>
 <li>Ben mentioned an issue they encountered with the emmeans package being updated such that it requires R version 4.3 or greater. We leverage this package in the pilot 4 app. Eric’s testing did not encounter any issues with this package, but this note has been logged in the issue tracker for awareness.</li>
 <li>It is unclear whether that will change, but we will be interested in a future keynote presentation from George Stagg at the upcoming ShinyConf 2024 which is going to address reproducibility in the context of web-assembly and web-R.</li>
 <li>With the latest CRAN releases of shinylive and httpuv, the pilot 4 setup instructions will ensure the CRAN releases for this packages are installed by the user prior to running the web-assembly version of the application</li>

docs/minutes/2024-03-08/index.html

@@ -189,14 +189,14 @@ <h2 id="toc-title">On this page</h2>
 <section id="meeting-minutes" class="level2">
 <h2 class="anchored" data-anchor-id="meeting-minutes">Meeting Minutes</h2>
 <ul>
-<li>Eric shared the status of his initial tests of the web-assembly version of the application available at https://github.com/RConsortium/submissions-pilot4-webR
+<li>Eric shared the status of his initial tests of the web-assembly version of the application available at <a href="https://github.com/RConsortium/submissions-pilot4-webR" class="uri">https://github.com/RConsortium/submissions-pilot4-webR</a>
 <ul>
 <li>Application works successfully when using work computer browser (Edge), however on his Linux machine certain browsers (Edge) were not able to view the application, while other chrome-variant browsers had no issue</li>
 <li>Sam mentioned he encountered a few issues running the app in his work browser, but was successful after discussions with IT</li>
 <li>Additional testing will be paramount prior to transfer to FDA</li>
 <li>Eric will prepare the repository with a few minor enhancements in preparation for wider testing amongst the group. Ben mentioned that with the Pilot 3 effort winding down, there could be additional resources available for testing soon.</li>
 </ul></li>
-<li>When the web-R binary packages are being pulled down from the webR CDN, there isn’t a clear way to pin those to a specific version, unlike renv when we can indeed control versions of packages installed. A comment on a separate issue https://github.com/posit-dev/r-shinylive/issues/56 indicates there will be a future state when pinning package versions is possible.</li>
+<li>When the web-R binary packages are being pulled down from the webR CDN, there isn’t a clear way to pin those to a specific version, unlike renv when we can indeed control versions of packages installed. A comment on a separate issue <a href="https://github.com/posit-dev/r-shinylive/issues/56" class="uri">https://github.com/posit-dev/r-shinylive/issues/56</a> indicates there will be a future state when pinning package versions is possible.</li>
 <li>Ben mentioned an issue they encountered with the emmeans package being updated such that it requires R version 4.3 or greater. We leverage this package in the pilot 4 app. Eric’s testing did not encounter any issues with this package, but this note has been logged in the issue tracker for awareness.</li>
 <li>It is unclear whether that will change, but we will be interested in a future keynote presentation from George Stagg at the upcoming ShinyConf 2024 which is going to address reproducibility in the context of web-assembly and web-R.</li>
 <li>With the latest CRAN releases of shinylive and httpuv, the pilot 4 setup instructions will ensure the CRAN releases for this packages are installed by the user prior to running the web-assembly version of the application</li>

docs/sitemap.xml

@@ -10,7 +10,7 @@
   </url>
   <url>
     <loc>https://rconsortium.github.io/submissions-pilot4/minutes.html</loc>
-    <lastmod>2024-03-29T16:12:25.581Z</lastmod>
+    <lastmod>2024-03-29T17:54:27.047Z</lastmod>
   </url>
   <url>
     <loc>https://rconsortium.github.io/submissions-pilot4/about.html</loc>
@@ -30,6 +30,6 @@
   </url>
   <url>
     <loc>https://rconsortium.github.io/submissions-pilot4/minutes/2024-03-08/index.html</loc>
-    <lastmod>2024-03-29T16:12:19.833Z</lastmod>
+    <lastmod>2024-03-29T17:54:27.875Z</lastmod>
   </url>
 </urlset>

minutes/2024-03-08/index.qmd

@@ -14,12 +14,12 @@ date: 2024-03-08
 
 ## Meeting Minutes
 
-* Eric shared the status of his initial tests of the web-assembly version of the application available at https://github.com/RConsortium/submissions-pilot4-webR
+* Eric shared the status of his initial tests of the web-assembly version of the application available at <https://github.com/RConsortium/submissions-pilot4-webR>
     + Application works successfully when using work computer browser (Edge), however on his Linux machine certain browsers (Edge) were not able to view the application, while other chrome-variant browsers had no issue
     + Sam mentioned he encountered a few issues running the app in his work browser, but was successful after discussions with IT
     + Additional testing will be paramount prior to transfer to FDA
     + Eric will prepare the repository with a few minor enhancements in preparation for wider testing amongst the group. Ben mentioned that with the Pilot 3 effort winding down, there could be additional resources available for testing soon.
-* When the web-R binary packages are being pulled down from the webR CDN, there isn't a clear way to pin those to a specific version, unlike renv when we can indeed control versions of packages installed. A comment on a separate issue https://github.com/posit-dev/r-shinylive/issues/56 indicates there will be a future state when pinning package versions is possible.
+* When the web-R binary packages are being pulled down from the webR CDN, there isn't a clear way to pin those to a specific version, unlike renv when we can indeed control versions of packages installed. A comment on a separate issue <https://github.com/posit-dev/r-shinylive/issues/56> indicates there will be a future state when pinning package versions is possible.
 * Ben mentioned an issue they encountered with the emmeans package being updated such that it requires R version 4.3 or greater. We leverage this package in the pilot 4 app. Eric's testing did not encounter any issues with this package, but this note has been logged in the issue tracker for awareness.
 * It is unclear whether that will change, but we will be interested in a future keynote presentation from George Stagg at the upcoming ShinyConf 2024 which is going to address reproducibility in the context of web-assembly and web-R.
 * With the latest CRAN releases of shinylive and httpuv, the pilot 4 setup instructions will ensure the CRAN releases for this packages are installed by the user prior to running the web-assembly version of the application