Add section on viewing the artifact data

Author: coatless

README.md

@@ -12,11 +12,12 @@
 
 Welcome to this tutorial on combining compiling an R package for
 [webR](https://docs.r-wasm.org/webr/latest/) and creating a `{pkgdown}`
-website using GitHub Actions. In this guide, you will find sample GitHub
-Action workflows designed to generate developmental webR/R WASM Package
-binaries alongside a `{pkgdown}` website. If you’re eager to streamline
-the process of building and deploying your R packages for webR while
-also creating a `{pkgdown}` website, you’ve come to the right place.
+website using GitHub Actions. In this guide, you will find a sample
+GitHub Action workflow designed to generate in one workflow both
+developmental webR/R WASM Package binaries alongside a `{pkgdown}`
+website. If you’re eager to streamline the process of building and
+deploying your R packages for webR while also creating a `{pkgdown}`
+website, you’ve come to the right place.
 
 This repository is part of a series exploring three different
 approaches:
@@ -56,7 +57,11 @@ approaches:
     the deployed content. Explore this repository to understand how this
     approach can streamline your R package deployment workflow.
 
-# Overview
+Another approach would be to use
+[r-universe.dev](https://ropensci.org/blog/2023/11/17/runiverse-wasm/)
+to automatically build and supply R WASM package binaries.
+
+## Key Contents
 
 Interested in having your R package automatically be built for
 [webR](https://docs.r-wasm.org/webr/latest/) alongside a `{pkgdown}`
@@ -174,15 +179,20 @@ uploaded onto GitHub Pages through an artifact. The artifacts are stored
 for 90 days (by default) and can be found under the workflow summary:
 
 1.  Click on the **Actions** tab for the repository
-2.  Select a completed build
-3.  Press the **Summary** option
-4.  Under “Artifacts”, click on **github-pages** to download the built
-    repository
+2.  Under “All workflows”, select a the **R WASM & {pkgdown} deploy**
+3.  Choose a completed workflow run
+
+![Example showing how to select a completed
+job](man/figures/gh-select-job-for-artifact.png)
 
-![](man/figures/github-actions-webr-repo-github-pages-artifact.png)
+4.  Under “Artifacts”, click on **github-pages** to download the built R
+    WASM repository and `{pkgdown}` website or **rwasmrepo** to download
+    just the built R WASM repository.
 
-**Note:** The size of the `github-pages` deployment is 9.88 MB of
-compressed space, while the size of the `rwasmrepo` is only 3.97 MB of
+![](man/figures/gh-download-artifact-from-job.png)
+
+**Note:** The size of the `github-pages` deployment is 13.6 MB of
+compressed space, while the size of the `rwasmrepo` is only 6.87 MB of
 the total compressed space.
 
 ## Accessing Binaries
@@ -194,12 +204,6 @@ repository’s GitHub Pages URL, e.g.
 https://gh-username.github.io/repo-name
 ```
 
-Or, using the [r-universe](https://r-universe.dev/search/):
-
-``` default
-https://username.r-universe.dev
-```
-
 This can be set either using `options()` or specifying the location in
 each `webr::install()` call.
 
@@ -213,7 +217,6 @@ The easiest is probably to define the location webR should search for in
 list_of_repos = c(
     "https://gh-username.github.io/repo-name", 
     "https://other-gh-username.github.io/another-repo", 
-    "https://username.r-universe.dev", 
     "https://repo.r-wasm.org/"
   )
 

README.qmd

@@ -13,11 +13,12 @@ engine: knitr
 ## Introduction
 
 Welcome to this tutorial on combining compiling an R package for [webR](https://docs.r-wasm.org/webr/latest/) and creating
-a `{pkgdown}` website using GitHub Actions. In this guide, you will find sample
-GitHub Action workflows designed to generate developmental webR/R WASM Package
-binaries alongside a `{pkgdown}` website. If you're eager to streamline the
-process of building and deploying your R packages for webR while also creating
-a `{pkgdown}` website, you've come to the right place. 
+a `{pkgdown}` website using GitHub Actions. In this guide, you will find a sample
+GitHub Action workflow designed to generate in one workflow both
+developmental webR/R WASM Package binaries alongside a `{pkgdown}` website. 
+If you're eager to streamline the process of building and deploying your R 
+packages for webR while also creating a `{pkgdown}` website, you've come to the 
+right place. 
 
 This repository is part of a series exploring three different approaches:
 
@@ -46,7 +47,10 @@ This repository is part of a series exploring three different approaches:
     provides a transparent view of the deployed content. Explore this repository
     to understand how this approach can streamline your R package deployment workflow.
 
-# Overview
+Another approach would be to use [r-universe.dev](https://ropensci.org/blog/2023/11/17/runiverse-wasm/)
+to automatically build and supply R WASM package binaries.
+
+## Key Contents
 
 Interested in having your R package automatically be built for [webR](https://docs.r-wasm.org/webr/latest/) alongside a `{pkgdown}` website using a [GitHub Action](https://github.com/features/actions) that deploys with an **artifact** instead of a `gh-pages` branch?
 If so, this is the repository for you! Here's a summary of what you can find in the repository:
@@ -149,14 +153,19 @@ onto GitHub Pages through an artifact. The artifacts are stored for 90 days
 (by default) and can be found under the workflow summary:
 
 1. Click on the **Actions** tab for the repository
-2. Select a completed build
-3. Press the **Summary** option
-4. Under "Artifacts", click on **github-pages** to download the built repository
+2. Under "All workflows", select a the **R WASM & {pkgdown} deploy**
+3. Choose a completed workflow run
+
+![Example showing how to select a completed job](man/figures/gh-select-job-for-artifact.png)
 
-![](man/figures/github-actions-webr-repo-github-pages-artifact.png)
+4. Under "Artifacts", click on **github-pages** to download the built R WASM repository
+   and `{pkgdown}` website or **rwasmrepo** to download just the built 
+   R WASM repository.
 
-**Note:** The size of the `github-pages` deployment is 9.88 MB of compressed space, 
-while the size of the `rwasmrepo` is only 3.97 MB of the total compressed space.
+![](man/figures/gh-download-artifact-from-job.png)
+
+**Note:** The size of the `github-pages` deployment is 13.6 MB of compressed space, 
+while the size of the `rwasmrepo` is only 6.87 MB of the total compressed space.
 
 ## Accessing Binaries
 
@@ -167,12 +176,6 @@ the repository's GitHub Pages URL, e.g.
 https://gh-username.github.io/repo-name
 ```
 
-Or, using the [r-universe](https://r-universe.dev/search/):
-
-```default
-https://username.r-universe.dev
-```
-
 This can be set either using `options()` or specifying the location in each
 `webr::install()` call.
 
@@ -186,7 +189,6 @@ The easiest is probably to define the location webR should search for in
 list_of_repos = c(
     "https://gh-username.github.io/repo-name", 
     "https://other-gh-username.github.io/another-repo", 
-    "https://username.r-universe.dev", 
     "https://repo.r-wasm.org/"
   )