Code_Descriptions
SSR W Hyrdration & caching
Do the usual squashing, optimising and baking to create a deployable directory of static assets.
Bake our local API to our deployable directory as a set of json files
Netlify can run the same build as we run locally with Gulp and deploy the result to its static hosting infrastructure. Better than that, it can be triggered to build whenever we push code changes to our git repository.
Now, how about for content authors? We want changes published in our CMS on Contentful to trigger a build too. We can do this thanks to webhooks which both Netlify and Contentful support. When content is published on Contentful, it fires a webhook on Netlify which then causes our build to run. The content is pulled in from the CMS and our build gets all the latest data. Nice.
Blog post-specific js embedded within he txt is hard. how can we inform webbpack of those assets
Webpack capacitor app hosted on gh pages w content delivery from colab/gh & wp
Dynamic routing of precompiled static html
App performs dynamic routing. Static html compiled from markdown.
Compile using nbdev and jekyll but use the wp templates or none at all then drop them as shortcodes in a page or post to display to the github page embedded within the wp one.. Duh.
But nbdev js no good for generating the optimized html. So that needs to be manual.
The ipynb convert/ rendering should be sperate from the pypi package creation and deployment.
The converter should loop through an xl sheet listing paths to notebooks to convert. Executed and files saved from the capacitor directory.
Capacitor is the wp app. Uses wp menu and prerender loader for everypath atop each ipynb markdown page being converted static and optimized.
https://htmx.org/essays/how-did-rest-come-to-mean-the-opposite-of-rest/