Cache the output that readers actually hit
CMS performance is rarely about one trick. It is about making the common request path boring: resolve the route, read the content, render the template, and serve a cached page when possible.
GoPress keeps this path explicit so teams can reason about what is cached, when it is invalidated, and how it behaves during publishing bursts.