understanding static vs dynamic content

Hi, all! I'd really appreciate some clarification on what static vs interactive/dynamic content is for the purposes of understanding which use cases are permissible with Connect's "no logon required" option for an org without unlimited licenses.

I am an end-user (analyst) without a deep understanding of the magic behind R packages and in an org with very little experience with Connect. I am trying to get clarity here so that I can give less bad advice when encouraging people to use Connect.

  1. dynamic/interactive content definition within a document

My understanding about what is dynamic/interactive:
(1) all Shiny apps
(2) most Rmd/qmd output with any user interactivity

What I don't yet understand are the details of (2) and what I should use as a heuristic, for those of us who are unaware of what magic is powering the back end. Are there any instances where a user would be able to click around an html and yet it would not be considered 'dynamic/interactive'?

Examples on my mind are:

  • interactive tables: {gt}, {reactable}, table filtering, download as csv
  • interactive graphs and maps: {plotly}, {leaflet}
  • tabsets in quarto -> html output
  • quarto revealjs presentations
  1. Does publishing impact the dynamic/ interactive definition?

Let's assume I have a qmd/Rmd -> html that pulls from a database and produces something very basic output (a static table).

If I publish this with source code and schedule this document, does that make this html "dynamic"? Or, as long as the html itself is static, is the publishing/scheduling irrelevant to this definition?

Many thanks for any clarifications!