Jekyll build strategy

[AlexanderPico]

What if...

• Site pages are hosted at pf-db(gh-pages branch), serving 3GiB of pre-built HTML (over 1GiB limit, but seems ok)
• The pf-db-jekyll repo builds only the latest ~1000 figure pages (per month) directly from md files (and maybe also front page, about, help, etc), and then commits them to pf-db(gh-pages) as pre-built HTML
• pf-db(main) would hold the full collection of md files and run R code to generate JSON, table, wp and ndex pages, and then commit them to pf-db(gh-pages) as pre-built HTML as well. It could also hold all all TSVs (~800MiB).

The pf-db-jekyll repo provides a lightweight Jekyll solution that GH can manage (should be smaller that WP). Any pages requiring all of the content (e.g. JSON, search and browse pages) would be handled as independent Gh Actions running R code which should complete within 6 hours no problem.

This would eliminate need for local builds and support a monthly pipeline.