francojc
commented
5 years ago First Building the website makes edits to the site files (not the RMarkdown files). Therefore it this set needs to take place before staging, committing, and pushing to GitHub. So the revised order is:
- Make edits.
- Save changes (to RMarkdown and other supporting files, i.e. .yml, .css, etc. files)
- Build website (in RStudio).
- Stage changes.
- Commit changes.
- Push changes.
Second
As your site grows and/or the code becomes more resource intensive (and therefore takes more time to build) it sometimes can make sense to only build those files that change, not the entire site (which is what happens by default when you click the 'Build > Build Website' button in the RStudio pane). If you are adding a new page to the site, however, and you need to add this page to the _site.yml file, then you will need to build the entire site (correct me if I'm wrong Mike).
To (re)build a specific page work from the console and use this command:
rmarkdown::render_site("page_name.Rmd")
brown-allen
medewitt
adanieljohnson
During Session 4 I was having trouble updating my website. I was making edits int he correct places, committing these changes, and pushing them to GitHub. However, I was forgetting to actually Build the website (it was either Jerid or Mike who pointed out this very straightforward error). Updating the website involves:
First - Does that process look correct?
Second - Is there any best practice for how often I Build the Website? For instance, these sites build pretty quickly, int heir current, but is that always the case? Is it worth simply knitting my .rmd to confirm that the edits I made are correct, rather than building each time to confirm? Perhaps it doesn't matter at all, and I should just do what's comfortable? Any thoughts?