Would it be possible to support an option in the yaml metadata of an .Rmd post which would tell blogdown not to build the file automatically?
Rationale: Sometimes I want .Rmd files in my site repo that have alternative output formats, e.g. a content/slides directory that has .Rmd files which already use an output: command to specify some slide format (e.g. slides for a lecture). I can knit these separately, but currently blogdown will compile these .Rmds as if they were regular posts, ignoring the requested output format and overwriting a previously-generated html. It would be simplest and most convenient if blogdown just ignored these .Rmds, and then their original outputs can still be part of the website in unaltered form.
Alternately, it would be nice if blogdown could recognize requested output: formats in yaml and render accordingly via rmarkdown, instead of following the usual knit command.
Would it be possible to support an option in the yaml metadata of an .Rmd post which would tell blogdown not to build the file automatically?
Rationale: Sometimes I want .Rmd files in my site repo that have alternative output formats, e.g. a
content/slidesdirectory that has .Rmd files which already use anoutput:command to specify some slide format (e.g. slides for a lecture). I can knit these separately, but currently blogdown will compile these .Rmds as if they were regular posts, ignoring the requested output format and overwriting a previously-generatedhtml. It would be simplest and most convenient if blogdown just ignored these .Rmds, and then their original outputs can still be part of the website in unaltered form.Alternately, it would be nice if blogdown could recognize requested
output:formats in yaml and render accordingly via rmarkdown, instead of following the usual knit command.