Skip to content

Latest commit

 

History

History
53 lines (30 loc) · 2.44 KB

README.md

File metadata and controls

53 lines (30 loc) · 2.44 KB

This is a Next.js project bootstrapped with create-next-app.

Segmented Rendering Demo

Read the article: https://www.smashingmagazine.com/2022/07/new-pattern-jamstack-segmented-rendering/

More on the theory of SSR (advanced): https://tinyurl.com/ssr-theory

This Next.js application demonstrates a Jamstack pattern named "Segmented Rendering", which enables static personalization.

It is very similar to "Personalization at-the-edge" as Vercel puts it. Segmented Rendering is a more generic pattern, that can also be implemented in a more traditional architecture.

The key ingredients are:

  • a static rendering framework. It's even better if it supports per-request or deferred server-rendering (Next, Gatsby).
  • a proxy server that can rewrite URLs. For instance Next.js Edge middlewares.
  • optionnaly a backend that can set cookies using the Set-Cookie header (you can also set cookies client-side with JS)

Live demo: https://segmented-rendering-demo.vercel.app

Getting Started

First, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.js.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.