As I sit here once again counting the tens of minutes before a custom.css rebuild happens, I feel like for blogging some one-two punch of both static and dynamic site generation would be better. For example, if I have thousands of blog entries, rebuilding every single post when I change the navigation menu seems a pretty fucking dumb way to go about things. How about static partials or includes, but then each page dynamically loads those few necessary static partials. That might mean a blog post is dynamically loading, say, a static header file, a static navigation file, a static post file, and a static footer file, but I feel like that’s a decent middle-ground between “every element is generated on-the-fly from a database” and “every single post and page you have has to rebuild from scratch whenever you change a common site-wide element”.
Addenda
-
I’m not saying that happens in the case of
custom.css; I’m actually assuming otherwise. It’s just that waiting for that rebuild reminded me of some things I was thinking about before I took my brief vacation. -
I feel like this basically is what I was doing once upon a time with
.phpfiles usinginclude, but that would have been a decade or more ago, so I could be wrong or there could be some pretty good reasons why people aren’t still doing that.