Otherwise, the editor won’t actually look like the front-end at all… Fine-tuning theme styles within Gutenberg Here’s an example of how I declared support for editor styling in my popular WordPress theme, Tabor:Īpart from registering the Gutenberg-specific stylesheet, theme developers will absolutely need to fine-tune elements within the new editor to ensure that each displays with relative parity to the actual front-end output.
To start, you’ll want to use the add_theme_support() function to declare support for editor styles.
Even worse, your theme could end up causing a whole slew of styling issues within the new editor, and even on the front-end.Īdding WordPress theme styles to Gutenberg is not as “plug-and-play” as one would think. If your WordPress theme is not properly optimized for WordPress 5.0, it’ll assuredly become hopelessly obsolete in this post-Gutenberg era of WordPress.
#Wordpress theme 2017 change font style in title code#
The good news is, I’ve re-written this guide with up-to-date code examples from a my Gutenberg-optimized WordPress themes like Wabi. So after an inspiring trip to Nashville for WCUS, I decided to jump on the Gutenberg ship myself and start styling the upcoming editor within my latest WordPress theme, Tabor.Įdit: Since posting this article, many of the details of applying editor styling to WordPress themes has changed quite significantly. If Gutenberg will become the de facto editing experience for the average WordPress user, why not make it the best experience possible? Innovation can’t happen without WordPress theme developers committing to the Gutenberg experience. It’ll finally bring a much-needed standardized content creation experience to WordPress. There’s just one small caveat.
In a couple months or so, Gutenberg will revolutionize WordPress publishing as we know it.