How To Build A Package With The "Rmd First" Method

[Abstract]
You know how to build a Rmardown, you were said or would like to put your work in a R package, but you think this is too much work? You do not understand where to put what and when? What if writing a Rmd was the same as writing a package? Follow the "Rmd-first" method and let {fusen} guide you to build a documented and tested package, to ensure the sustainability and sharing of your work.

[Bio]
Sébastien Rochette (@statnmap) is R trainer and consultant at ThinkR (https://rtask.thinkr.fr/).

He participates in the development of open-source R packages proposed on GitHub by ThinkR (https://github.com/thinkR-open/) and himself, including {fusen} and {attachment}. He also has created multiple internal packages for ThinkR and different clients.

He gave different presentations and tutorials on package development with the 'Rmd first' method as summed up in "Rmd first: When development starts with documentation" (https://rtask.thinkr.fr/when-development-starts-with-documentation/) and blogs about R on his website (https://statnmap.com/).

He is co-author of the book "Engineering Production-Grade Shiny Apps" (https://engineering-shiny.org/) that promotes an adapted RMDD method for Shiny application using {golem}.

[About]
This event (in English) is organised by the R Lille user group (Lille, France).