Christophe Dervieux

I'll reopen as currently the pandoc variable needs to be passed at a document level, and not a site level. Full reprex: https://github.com/daviddalpiaz/rmd-lang-test

Setting a pandoc variable for the all website outputs can be done using `pandoc_args` argument in `_site.yml` definition ```yaml name: "my-website" output: html_document: pandoc_args: !expr rmarkdown::pandoc_variable_arg("lang", "en") navbar: title: "My...

Thanks @jooyoungseo ! To be clear, you are recommending for this attribute to be set in the html produced by rmarkdown, right ? Because currently, it seems this attribute is...

This is related to #2062 regarding the lang attributes. This issue is also about how to set pandoc variables for all the document in a website.

Yes you are right. We should do that. I think we use 18 because I kept the version when migrated from Travis but using the latest should be fine. However,...

@atusy this is great ! However, tabpanel is trickier as I don't think the toc will allow to navigate in the headers that are inside the tabbed panel. In my...

I also think this should be looked into after #1260 when bootstrap upgrade is done because it will change some things. Maybe bs4 will also help with this.

> I think the above trick needs lots more improvements which is still difficult for me. What are the improvement to be made ? What makes it more difficult to...

I took time on this one because I needed to think about it. I really don't like adding a new YAML field, all the more not under a format function...

Oh that is interesting. So you are running pandoc on each file ? and not on all separate file at once ? I see that this can be useful in...