Very reasonable question—having a user-specific header does make it tricky to have whole-page prerendering/caching, but we’re working on making partial prerendering worthwhile (mostly for post pages, which admittedly do change more often, due to comments and votes, though the cache hit rate would still be pretty high).
In the case of collection pages like R: A-Z, we also have user-specific info like read statuses indicated in checkboxes, which are part of the expensive query responsible for hydrating most of the page contents. We could split that out, and since we did recently enable cacheComponents it’s possible that’d allow us to cache much of the page, but I’m not sure if it’s worth prioritizing.
Very reasonable question—having a user-specific header does make it tricky to have whole-page prerendering/caching, but we’re working on making partial prerendering worthwhile (mostly for post pages, which admittedly do change more often, due to comments and votes, though the cache hit rate would still be pretty high).
In the case of collection pages like R: A-Z, we also have user-specific info like read statuses indicated in checkboxes, which are part of the expensive query responsible for hydrating most of the page contents. We could split that out, and since we did recently enable cacheComponents it’s possible that’d allow us to cache much of the page, but I’m not sure if it’s worth prioritizing.
Oh, I see, that makes sense. And yeah the navbar issue in particular is one I’ve struggled with before.
(Thank you for answering.)