#GUTENBERG WORDPRESS ARCHIVE#

Turn Classic Content into Gutenberg BlocksĪnother option, albeit a more complex one, is to break your legacy content into Gutenberg blocks.

#GUTENBERG WORDPRESS ARCHIVE#

However, for content you want to keep as part of the new site - but that you won’t be going back and regularly editing - such as an archive of blog posts, this is the easiest way to bring your existing content over. One drawback to this approach is that all of your content for each post is within a single block, so while you can add new blocks before or after it, you can’t easily, say, insert a brand-new custom CTA block in between two paragraphs. You’ll also need to make sure your new site styles look good with your legacy content.) Export the content of the posts from your old site, import it into the new site, and you’ll be ready to go! (Okay, it’s probably not quite that easy. Any content that isn’t inside a Gutenberg block is automatically treated as being inside a Classic block.īecause this is WordPress’s fallback if content isn’t already marked up to be Gutenberg-ready, you don’t have to do anything special to use it for migrated content. It’s like turning off Gutenberg just for that block of content - while still letting you add new blocks around it.

The Classic block uses the familiar TinyMCE editor and WordPress shortcodes. WordPress offers a very easy, out-of-the-box way to handle legacy content. Here’s what we learned from migrating our own content over to the new CMS: We actually just went through this exact dilemma ourselves - the site you’re visiting right now uses Gutenberg WordPress. But what about your old content that was created using WordPress 4 (or WordPress 5 with the Classic Editor plugin activated)? How do you migrate your pre-Gutenberg content into your brand-new site? You’re using the new Gutenberg editor to take full advantage of the flexibility of blocks. Kelli Monahan, Director of Technology Operations

Gutenberg wordpress