Closed bbest closed 3 years ago
This is something I have been craving so that I can build on top of the infographics work and push improvements back upstream. I think it makes sense to have two repos: A) the package of core files that makes everything work (infographiq) and B) a boilerplate of minimal example locally-required files to be forked and used as a template for new infographic sites (info-demo or similar).
Ok, I'm liking this architecture. I think we should put this into the infographiq documentation.
This hierarchy was also visualized by Jenn:
Closing since moved to marinebon/infographiq#4
Let's consider one place, probably infographiq, for a set of functions and templates using Github Releases (ie versions of product) with potential for backward compatibility, multiple output types (Rmd website, Rmd standalone page, Drupal Module, HTML standalone page, ...).
Present: Jumble of Repos
Presently the interactive infographics core files and functions live in too many locations:
Instances:
Future: Consolidated Framework — Single instances using core infographiq R package
Can core files be pulled over the web remotely? Commonly, Content Delivery Network (CDN) versions of JS and CSS files are pulled over the web. For example, for a quick start to Bootstrap v4.5, the following HTML lines include these core files:
infographiq::update_website()
or similar?