Help users avoid pitfalls about javascript-dependent content / interactivity

[kmasiello]

A common pitfall when crafting emails is the assumption that the email contents can have the same level of interactivity and reactivity that they might have in a Shiny app or RMD. However, javascript-dependent content will generally not render when emailed -- not due to a limitation of blastula, but as result of how email clients process HTML.

Blastula documentation could be expanded to include best practices in how to email certain types of content, for example:

• ggplot2 output can be rendered in blastula directly
• for tables, use gt (non-interactive mode) for nicely formatting tables
• use webshot2 to capture a rendering of widgets

Additionally, it's worth exploring whether blastula could employ helper functions to automatically transform certain content into an email-friendly version.

[D3SL]

It's more complicated than this as well. Even using gt and other options it's notoriously difficult to get things like a decent table with some basic conditional formatting in major clients like outlook.