Some posts require packages to run

[javierluraschi]

We should try to disable code that actually runs r code, see for instance:

ai-blog/_posts/2020-07-30-state-of-the-art-nlp-models-from-r/state-of-the-art-nlp-models-from-r.Rmd

Lines 255 to 262 in 30a4bea

	```{r eval=T,echo=F}
	library(dplyr)
	res = data.table::fread('files/res.csv') %>%
	filter(rowname %in% 'val_auc') %>% arrange(desc(V2)) %>%
	rename(epoch_1 = V1, epoch_2 = V2, metric = rowname) %>%
	mutate(epoch_1 = round(epoch_1,3),epoch_2 = round(epoch_2,3))
	DT::datatable(res, options = list(dom = 't'))
	```

Otherwise, when building the blog automatically, this might break or change inadvertently.

[skeydan]

Does this also hold for displaying images with knitr? These are the only instances where I actually evaluate R chunks, otherwise in my posts all output is static.

Should I go through the externally-contributed posts and replace any dynamic output with static results?

I'll also update the "contributing" page to say that PRs should have Rmds only, and all output should be static.