History

Oscar Busk 077097b7f8 Remove `licence` from all `example/package.json` that has them (#28007 ) * Add licences to all example/package.json that lack them * Revert "Add licences to all example/package.json that lack them" This reverts commit 5d4e25012f7334772b8ef5924bc355277e827cba. * Update check-examples to remove `license` field from examples * Remove `license` from all examples. This was mentioned in vercel/next.js#27121 but it looks like it didn't end up being in the merge? Co-authored-by: JJ Kasper <jj@jjsweb.site>		2021-08-14 10:48:39 -05:00
..
components	Update layouts example to persist state across client-side transitions. (#26706 )	2021-06-28 22:19:15 -05:00
pages	Update layout-component example to use named functions (#27331 )	2021-07-20 14:02:51 +00:00
.gitignore	Added .gitignore to examples that are deployed to vercel (#15127 )	2020-07-16 10:52:23 -04:00
global.css	Update layouts example to persist state across client-side transitions. (#26706 )	2021-06-28 22:19:15 -05:00
package.json	Remove `licence` from all `example/package.json` that has them (#28007 )	2021-08-14 10:48:39 -05:00
README.md	Update layouts example to persist state across client-side transitions. (#26706 )	2021-06-28 22:19:15 -05:00

README.md

Layout component example

This example shows a very common use case when building websites where you need to repeat some sort of layout for all your pages. Our pages are: home, about and contact and they all share the same layout and sidebar.

Preview

Preview the example live on StackBlitz:

Deploy your own

Deploy the example using Vercel:

How to use

Execute create-next-app with npm or Yarn to bootstrap the example:

npx create-next-app --example layout-component layout-component-app
# or
yarn create next-app --example layout-component layout-component-app

Deploy it to the cloud with Vercel (Documentation).