Really trying to up my game building a standardized package of docs for use in my resume editing business. I have scrutinized most of the CVs and resumes on github. One of the things I am struggling with is many users have either: 1) a mix of rmd and latex in the rmd doc leaving the heavy lifting to the tex file, 2) code a bunch of params in metablocks and pass to tex file, or some custom balance between the two.
As I am building a fast, flexible template system, is #2 the right way to go or is there a better path? Ultimately (version 2.0) I would like a shiny app where I can expand/contract/omit sections, dump in params (client's particulars) and render quickly.
As an aside, I can pass params to the tex file w/o a problem, but I can't understand yet how rmd gets passed the same file. Some examples I have seen do not have any tie-in between the "body" of content in the rmd file and the "body" of content rendered by the tex file.
Note: I am aware of the 'resumer' package and other similar attempts but I do not want to negotiate CSVs to input data for large volumes of clients. Spreadsheets are the devil.