The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

Short introduction

Introduction

This package is intended as a drop-in replacement for flexdashbaord. It will split the board in sub-pages, one for each menu entry (e.g. # Item 1 {data-navmenu="Menu 1"}). It should work out of the box by replacing the output format from

output: flexdashboard::flex_dashboard

to

output: flexsiteboard::flex_site_board

Please ensure, that any JavaScript needed in more than one menu entry related sub-page must be included before the first sub-menu-headline, i.e., lines like # Headline {data-navmenu=Main1}, is given.

Please also note, that this package is quite new and does things depending very much on the output of flexdashbaord, so there may be errors.

Additional features

Because this package needs Pandoc internally, it also features functions similar to pander::Pandoc.convert or rmarkdown::pandoc_convert, but it converts also fragments (pander sets the -s argument for pandoc always creating full documents). flexsiteboard’s Pandoc functions handle all temporary file creation/deletion automatically getting their input as a file or a character-vector function-argument and providing the conversion result as character-vector return values. flexsitebaord’s functions do so in a two-step process using Pandoc’s internal json format as a general format.

flexsiteboard::pandoc_convert(text = c("# Test", "# Test2\nTest3"), 
                              from = "markdown",
                              to = "html")
#> [1] "<h1 id=\"test\">Test</h1>\n<h1 id=\"test2\">Test2</h1>\n<p>Test3</p>"
flexsiteboard::pandoc_convert(text = "This is a <i>test</i>.", 
                              from = "html",
                              to = "markdown")
#> [1] "This is a *test*."

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.