You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WordPress has a new editing experience, codenamed Gutenberg, in development scheduled to be released with WordPress 5.0.
The new editing experience is built on React and has the concept of blocks. I would like to use WordPress as a source for Gatsby. Ideally, the React components used in Gutenberg blocks can be reused in Gatsby so that the visual representation of what is shown in the WordPress editor is accurate to what the Gatsby built front-end will look like.
Gutenberg, by default, saves block and attribute data as JSON in HTML comments. My initial concept is to read the content from WordPress and repopulate the blocks and their attributes at build time in Gatsby.
I've built a simple site on Gatsby 1 with Markdown as a source. I have also built custom Gutenberg blocks and have a decent grasp of React. I'm curious if this is possible/worth attempting before digging in deeper.
The text was updated successfully, but these errors were encountered:
Summary
WordPress has a new editing experience, codenamed Gutenberg, in development scheduled to be released with WordPress
5.0
.The new editing experience is built on React and has the concept of blocks. I would like to use WordPress as a source for Gatsby. Ideally, the React components used in Gutenberg blocks can be reused in Gatsby so that the visual representation of what is shown in the WordPress editor is accurate to what the Gatsby built front-end will look like.
Gutenberg, by default, saves block and attribute data as JSON in HTML comments. My initial concept is to read the content from WordPress and repopulate the blocks and their attributes at build time in Gatsby.
I've built a simple site on Gatsby 1 with Markdown as a source. I have also built custom Gutenberg blocks and have a decent grasp of React. I'm curious if this is possible/worth attempting before digging in deeper.
The text was updated successfully, but these errors were encountered: