Open LeoDog896 opened 1 year ago
Very much agree. The project could stick with the default SSR strategy, but give the option to build the site into static files. The performance would be much improved.
It's kinda annoying and detrimental, for example, that the avantar picture has to be downloaded every time the home page is hit.
We could split the current BlogSettings
interface into 3: BaseBlogSettings
, BuildBlogSettings
, and ServeBlogSettings
(or similar naming -- we shouldn't bikeshed on this), given that the current settings takes in middleware fields and some may be untranslatable to a dev server.
Also in need of a solution for static generation here. Any ideas how it would be architected? Could it be a middleware? Part of the blog config options? A separate mirror process all together? Any good examples out there already we could follow?
Given some direction, maybe I could hack something together...
Or probably just make more sense to use lume or something...
Given that (at some point) the deno blog isn't fetching dynamic data but rather a website for all users, the deno blog should be able to generate static files.