Outlining secure coding practice is important because it'll provide your development team with a set of standards to follow in order to write code securely. It'll reduce the risk of security vulnerabilities being introduced to the project during...

Our hybrid cache system is already quite capable but does present some challenges if we want to use routes or controllers to serve our content. The responses from these routes or controllers will be cached unless we exclude their URL patterns in...

In this section, we will update our ResponseCreatedListener implementation to prevent caching pages containing Laravel's CSRF token. As stated during the introduction, this will help simplify the management of pages containing forms we don't want...

To take a break from the more involved experimentation and code changes, we will work on improving how our cache system manages headers. Our cache doesn't do anything explicit with the headers, including the Date header. While we could get away...

This article series covers implementing a custom cache system for Statamic, which provides near-static cache response times while preserving some of the text-editor workflows that make Statamic great. The cache system we will build together may...

In the last section, we explored the relative response times of different Statamic caching strategies and experimented with the response times of short-circuiting both Laravel and Statamic. We also discovered that the response times resulting from...

Before going much further, we will take some time to get some structural changes and organization done. As we progress further along the development of our cache system, we will interact with our App\HybridCache\Manager implementation and from...