Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Link to gatsby-plugin-layout from the "Life after Layouts" blog post #9933

Merged
merged 1 commit into from
Nov 16, 2018
Merged

Link to gatsby-plugin-layout from the "Life after Layouts" blog post #9933

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/blog/2018-06-08-life-after-layouts/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ So the Gatsby V2 beta is out, and Gatsby's [layout components are going away](ht

This article will dive into the Gatsby V2's approach to layouts, talk about what changed and why, and walk through the migration process to get your existing projects updated to V2.

If you still need the v1 layout behavior, checkout [gatsby-plugin-layout](/packages/gatsby-plugin-layout/).

## What changed?

In Gatsby V1, layouts were a special kind of component that automagically wrapped generated page components. They were stored in `src/layouts/`, and received a prop called `children` that needed to be executed as a function.
Expand Down