Stop numbering files, Act Three

_bookdown.yml

@@ -27,11 +27,12 @@ rmd_files: [
   "connect-can-rstudio-use-git.Rmd",
   "connect-troubleshooting.Rmd",
 
-  "20_usage-new-project-github-first.Rmd",
-  "21_usage-existing-project-github-first.Rmd",
-  "22_usage-existing-project-github-last.Rmd",
-  "30_workflow-first-use-rmd-and-github.Rmd",
-  "31_workflow-first-use-r-script-and-github.Rmd",
+  "usage-intro.Rmd",
+  "usage-new-project-github-first.Rmd",
+  "usage-existing-project-github-first.Rmd",
+  "usage-existing-project-github-last.Rmd",
+  "usage-rmd-and-github.Rmd",
+  "usage-r-script-and-github.Rmd",
 
   "33_git-commands.Rmd",
   ## TODO: commit, diff

usage-intro.Rmd

@@ -0,0 +1,14 @@
+# (PART) Early GitHub Wins {-} 
+
+# Get started with GitHub {#usage-intro .unnumbered}
+
+Now that we've verified your Git/GitHub/RStudio setup, we can demo the workflows you'll use to get your work onto GitHub:
+
+  * [New project, GitHub first] is the easiest way to get a working project.
+  * [Existing project, GitHub first] is a deeply pragmatic way to get pre-existing work onto GitHub.
+  * [Existing project, GitHub last] is the more proper way to connect existing local work to a remote on GitHub, especially if there's already a Git history.
+
+This part concludes with two R-specific workflows that show off how well [R Markdown (the format)](https://rmarkdown.rstudio.com) and [rmarkdown (the package)](https://cran.r-project.org/package=rmarkdown) work with GitHub:
+
+  * [Test drive R Markdown]
+  * [Render an R script]

20_usage-new-project-github-first.Rmd → usage-new-project-github-first.Rmd

@@ -1,5 +1,3 @@
-# (PART) Early GitHub Usage {-} 
-
 # New project, GitHub first {#new-github-first}
 
 We create a new Project, with the preferred "GitHub first, then RStudio" sequence. Why do we prefer this? Because this method of copying the Project from GitHub to your computer also sets up the local Git repository for immediate pulling and pushing. Under the hood, we are doing `git clone`.