Not sure it makes sense as an official feature. On one hand there are many technical constraints and expectations that come with static HTML export; on the other hand when it comes to rendering a page Kirby is a rather light PHP solution, so it’s not like the speed gain would be that significant (almost negligible with Kirby’s default caching). I built this plugin mostly for a use case where we needed to host the website as static HTML both online and offline (think thumb drives, HTML documentation distributed in a ZIP file, that kind of thing).
There’s no API for that yet in the plugin, though it would be possible to call the main class and ask it to build just one page.
But there are other constraints tied to "saving a page":
- Does the page have static assets to copy over?
- Is it listed on some archive page? You have to rebuild the archive page too.
- Is it listed on the home page? You have to rebuild the home page too.
- Is it listed in a RSS or Atom feed? You have to rebuild that "page" too.
Because Kirby and its APIs where not build with the "static HTML export" constraints in mind, like say Jekyll, it offers many features that make it trivial to display content on as many pages you like and however you want, which makes it difficult to do single-page builds or even to do a full-site static build. You have follow the Best practices for static sites and perhaps have some understanding of how PHP, HTTP and HTML work to make it work.
So it’s difficult to go from this current reality to "built-in Kirby feature that works easily for clients without technical supervision" (most likely: it’s not happening).