Technical review of R Markdown PDF report

miraisolutions / SmaRP

Shiny app for projecting retirement funds / benefits

https://mirai-solutions.ch/gallery/smarp

20 stars 9 forks source link

Technical review of R Markdown PDF report #130

Open riccardoporreca opened 5 years ago

riccardoporreca commented 5 years ago

The R Markdown PDF report should be cleaned-up, so that it is technically cleaner.

Examples:

Review / cleanup LaTeX code in header.tex and the main report
library(...) statements at the beginning
HTML-releated statements like <br>
general code organization review

We probably also want to switch away from leaving metadata like title and author in the YAML header and using a customized first page, which means the PDF output does not have such properties. An option for this is to switch to a custom Pandoc template, which would be a nice maintenance refactoring, especially if we want to customize the appearance of the report in the future.

riccardoporreca commented 5 years ago

Details to be discussed, see premature PR https://github.com/miraisolutions/SmaRP/pull/138#pullrequestreview-262056241 comment.

RolandASc commented 5 years ago

Maybe update (replace) the link to .../apps/smarp at the same time

gabrielfoix commented 5 years ago

Ready to start. Roland's comment will be addressed in another issue together with similar updates. Talk to @riccardoporreca to define scope and approach.

riccardoporreca commented 5 years ago

Maybe update (replace) the link to .../apps/smarp at the same time

Covered by #143

riccardoporreca commented 5 years ago

Note that, in general, we shall reconsider if we want to keep using xelatex as engine, as well as whether PDF version (vector graphics) of the figures can be created and used instead of PNG.

Originally posted by @riccardoporreca in https://github.com/miraisolutions/SmaRP/issues/152#issuecomment-548811684