-
@rob_dodson Yeah, the big one is templates that publish and consume collections—this essentially segments the build. I do have some tricks there and we’ll have some room for improvement too. e.g. 11ty.dev/authors/zachleat/ reuses a build-time generated collection for the sidebar navigation
-
@rob_dodson Internally we have a list of templates that populate collections we could use to improve this knowing where collections are consumed might require API changes to facilitate e.g. collections.get("all") instead of collections.all
-
@rob_dodson (I did play around with proxies to make this happen transparently but some template languages ended up triggering the getters even if the data wasn’t used 😭)