Guidelines on how much code to include in the post?

[kevinykuo]

One way to do this is to point readers to files in analysis/ that they can execute sequentially, and include just a few snippets in the blog post itself so we don't cover most of it with code.

[TylerGrantSmith]

What is the downside of including the code, but keeping it folded by default?

[kevinykuo]

Yeah I think we can do that. Maybe also have an 'expand/collapse all code' button up top. The main drawback is that any changes we make to the executable code we also have to modify it in the post, but this seems standard in education.

[TylerGrantSmith]

Wouldn't necessarily need to do the double-duty if you add knitr chunk comments to the analysis code.
in analysis/map.R

## @knitr plot-brazil
brazil %>%
  leaflet(options = leafletOptions(minZoom = 4)) %>%
  addTiles() %>%
  addPolygons(
    data = bra_cutout,
    weight  = 0,
    opacity = 1,
    color = "white",
    fillOpacity = 1
  ) %>%
...

in manuscript/article.Rmd

## Exposures by state

```{r}
knitr::read_chunk('analysis/map.R')
```
```{r plot-brazil, eval = FALSE, echo = TRUE}
```
```{r plot-brazil, layout = "l-body-outset", fig.height = 6}
```

Once code folding is in place, that would be an easy way to keep the article in tune with the analysis code.