develwoutacause’s Twitter Archive

18 results for SSG

1. develwoutacause’s Twitter Archive—№ 1,252

   now have a fourth execution context. 1. Build time (traditional SSG). 2. SSR of SSG pages. <-- New 3. SSR pages. 4. Client side rendering (CSR).

2. develwoutacause’s Twitter Archive—№ 1,249

   This approach allows SSG and SSR routes to share the same implementation and evolve over time. A currently SSG route can become an SSR route just by changing the caching

3. develwoutacause’s Twitter Archive—№ 831

   its content can compose *another* component using some combination of SSG / SSR / CSR. Here, we have an outer component's SSR slice wrapping an inner component with SSG and

4. develwoutacause’s Twitter Archive—№ 1,248

   the cost normally paid at build time for a traditional SSG site. This means your SSG computations now fall under your request/response SLOs. 😱

5. develwoutacause’s Twitter Archive—№ 56

   @devongovett I was recently looking for a SSG, but skipped Gatsby precisely because it uses React. This shouldn't require loading a JavaScript framework onto end user devices.