Are you over 18 and want to see adult content?
More Annotations
![A complete backup of drivedominion.com](https://www.archivebay.com/archive2/53e66537-ab1c-4ded-a369-57da1728f803.png)
A complete backup of drivedominion.com
Are you over 18 and want to see adult content?
![A complete backup of statesidelegal.org](https://www.archivebay.com/archive2/2f2f3a60-f23f-4faa-9ed5-909c58ae29c2.png)
A complete backup of statesidelegal.org
Are you over 18 and want to see adult content?
![A complete backup of drafthousefilms.com](https://www.archivebay.com/archive2/810849ae-8c65-4746-823e-8e630a9a4965.png)
A complete backup of drafthousefilms.com
Are you over 18 and want to see adult content?
![A complete backup of grand-tirolia.com](https://www.archivebay.com/archive2/15fefbf1-a4bd-44e9-8c6c-e488288a7098.png)
A complete backup of grand-tirolia.com
Are you over 18 and want to see adult content?
![A complete backup of lohmann-rauscher.com](https://www.archivebay.com/archive2/ce7edf27-3619-4762-9d1d-b31c60cd4e59.png)
A complete backup of lohmann-rauscher.com
Are you over 18 and want to see adult content?
Favourite Annotations
![A complete backup of https://dropbox.tech](https://www.archivebay.com/archive6/images/ba7ac44f-7d47-4c2e-8f85-cddde1c46d9d.png)
A complete backup of https://dropbox.tech
Are you over 18 and want to see adult content?
![A complete backup of https://nmc.org.uk](https://www.archivebay.com/archive6/images/93b43480-d8a4-47e3-bffd-da0800ea1598.png)
A complete backup of https://nmc.org.uk
Are you over 18 and want to see adult content?
![A complete backup of https://greatapeproject.org](https://www.archivebay.com/archive6/images/c12c4869-9e36-4679-9dcb-5525c10df6ee.png)
A complete backup of https://greatapeproject.org
Are you over 18 and want to see adult content?
![A complete backup of https://skyakademie.de](https://www.archivebay.com/archive6/images/013a96ef-e92f-4c8c-be71-39b1d0f76fce.png)
A complete backup of https://skyakademie.de
Are you over 18 and want to see adult content?
![A complete backup of https://tiscali.com](https://www.archivebay.com/archive6/images/f2b58579-6ae7-4ff2-aa68-e2b4fa61c9f5.png)
A complete backup of https://tiscali.com
Are you over 18 and want to see adult content?
![A complete backup of https://humanrights.is](https://www.archivebay.com/archive6/images/6ccdb289-018e-4175-be31-69b6d836811b.png)
A complete backup of https://humanrights.is
Are you over 18 and want to see adult content?
![A complete backup of https://tokobunga.info](https://www.archivebay.com/archive6/images/36cf04a0-a92b-4b56-9f40-27a6c6156801.png)
A complete backup of https://tokobunga.info
Are you over 18 and want to see adult content?
![A complete backup of https://luckydoganimalrescue.org](https://www.archivebay.com/archive6/images/3495de6e-50fe-4fea-bc0f-7845fab8c93c.png)
A complete backup of https://luckydoganimalrescue.org
Are you over 18 and want to see adult content?
![A complete backup of https://rodneymoore.com](https://www.archivebay.com/archive6/images/26e8844e-cf3e-40b8-821e-b8e8fbd425fc.png)
A complete backup of https://rodneymoore.com
Are you over 18 and want to see adult content?
![A complete backup of https://climateneutralnow.org](https://www.archivebay.com/archive6/images/841dd394-ee0c-4b27-b7bf-29a3d310178e.png)
A complete backup of https://climateneutralnow.org
Are you over 18 and want to see adult content?
![A complete backup of https://avg-com-retail.com](https://www.archivebay.com/archive6/images/734123c8-78d8-4451-8545-a8a3459bd0d4.png)
A complete backup of https://avg-com-retail.com
Are you over 18 and want to see adult content?
Text
THEMESHAPER
Blockbase: A parent theme for block themes. Ben Dwyer, Posted on. May 27, 2021. June 1, 2021. Phase 2 of Gutenberg introduces Full Site Editing to WordPress; to make this possible, we need a new way of building themes – using blocks. . Continue reading. USING BLOCKBASE FOR A THEME EXPERIMENT A glitchy theme, built with Blockbase. Last week I spent a little time putting Blockbase to the test. I had some explorations into warping text and images using CSS and SVG filters gathering dust, and I thought it would be fun to explore pulling those into a highly-opinionated block theme. In the past when I’ve done a themeexperiment like
THEMATIC, A WORDPRESS THEME FRAMEWORK Thematic is a free, open-source, highly extensible, search-engine optimized WordPress Theme Framework featuring 13 widget-ready areas, grid-based layout samples, styling for popular plugins, and a whole community behind it. It's perfect for beginner bloggers and WordPress development professionals. Download it from the official WordPressThemes Directory.
CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to OPEN SOURCE FONT PAIRINGS FOR YOUR NEXT THEME THE THEMESHAPER WORDPRESS THEME TUTORIAL: 2ND EDITION The simple theme we’re going to build in this tutorial, The Shape Theme (yes, it’s the Shape Theme from the 1st Edition, updated for the 2nd Edition), is based on _s. Download it and check it out if you’d like to see the finished code we’ll be going through, live, in action. It’ll be a while before we get to the CSS lesson, but ifyou
THE WORDPRESS THEME INDEX TEMPLATE The WordPress Theme Index Template. Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR Add the following to your style.css, at the very top, immediately after the initial comments section. There’s no need to memorize the reset styles. Just paste them to the top of your stylesheet each time you start a new project. Reload your page and check how it looks in multiple browsers (if you can). CUSTOMIZING JETPACK’S SHARING MODULE Customizing Jetpack’s Sharing module. One of my favorite feature in Jetpack is sharing, but if you are a theme designer/developer like me, it can be really frustrating trying to customize it. By adding a simple filter to functions.php or inc/jetpack.php if your theme is based on _s, you can actually avoid the Sharedaddy stylesheet frombeing
THEMESHAPER
Blockbase: A parent theme for block themes. Ben Dwyer, Posted on. May 27, 2021. June 1, 2021. Phase 2 of Gutenberg introduces Full Site Editing to WordPress; to make this possible, we need a new way of building themes – using blocks. . Continue reading. USING BLOCKBASE FOR A THEME EXPERIMENT A glitchy theme, built with Blockbase. Last week I spent a little time putting Blockbase to the test. I had some explorations into warping text and images using CSS and SVG filters gathering dust, and I thought it would be fun to explore pulling those into a highly-opinionated block theme. In the past when I’ve done a themeexperiment like
THEMATIC, A WORDPRESS THEME FRAMEWORK Thematic is a free, open-source, highly extensible, search-engine optimized WordPress Theme Framework featuring 13 widget-ready areas, grid-based layout samples, styling for popular plugins, and a whole community behind it. It's perfect for beginner bloggers and WordPress development professionals. Download it from the official WordPressThemes Directory.
CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to OPEN SOURCE FONT PAIRINGS FOR YOUR NEXT THEME THE THEMESHAPER WORDPRESS THEME TUTORIAL: 2ND EDITION The simple theme we’re going to build in this tutorial, The Shape Theme (yes, it’s the Shape Theme from the 1st Edition, updated for the 2nd Edition), is based on _s. Download it and check it out if you’d like to see the finished code we’ll be going through, live, in action. It’ll be a while before we get to the CSS lesson, but ifyou
THE WORDPRESS THEME INDEX TEMPLATE The WordPress Theme Index Template. Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR Add the following to your style.css, at the very top, immediately after the initial comments section. There’s no need to memorize the reset styles. Just paste them to the top of your stylesheet each time you start a new project. Reload your page and check how it looks in multiple browsers (if you can). CUSTOMIZING JETPACK’S SHARING MODULE Customizing Jetpack’s Sharing module. One of my favorite feature in Jetpack is sharing, but if you are a theme designer/developer like me, it can be really frustrating trying to customize it. By adding a simple filter to functions.php or inc/jetpack.php if your theme is based on _s, you can actually avoid the Sharedaddy stylesheet frombeing
THEMES – THEMESHAPER This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to create BLOCKBASE: A PARENT THEME FOR BLOCK THEMES Phase 2 of Gutenberg introduces Full Site Editing to WordPress; to make this possible, we need a new way of building themes - using blocks. How do block themes work? Block themes use templates made entirely of blocks. The layout is configured using a combination of theme.json and CSS. The settings in theme.json are used THEMATIC, A WORDPRESS THEME FRAMEWORK Thematic is a free, open-source, highly extensible, search-engine optimized WordPress Theme Framework featuring 13 widget-ready areas, grid-based layout samples, styling for popular plugins, and a whole community behind it. It's perfect for beginner bloggers and WordPress development professionals. Download it from the official WordPressThemes Directory.
ADDING BLOCK PATTERNS TO YOUR THEME Adding Block Patterns to Your Theme. Block patterns are unique, predefined combinations of blocks you can use and tweak to create stunningly designed sections of your website. From global styles, to entirely block-based themes, the WordPress block editor is aiming high. Amongst the newest experimental features are block patterns. GETTING STARTED WITH BLOCK THEMES: GLOBAL STYLES Getting Started with Block Themes: Global Styles. Global Styles is a new mechanism for a theme to define a site’s styles. An important goal of Global Styles is to make it easier for users to change how their site looks without having to know or write any CSS. These theme styles are defined via a json configuration file. CREATING A BLOCK-BASED LANDING PAGE THEME The other day, my colleague Ian Stewart and I were discussing homepage templates, and this Carrd layout came up in conversation: . Its two-column design is friendly and simple. It’s also drastically different than most WordPress themes we see these days — it doesn’t have a traditional header and footer, or even a menu forthat matter.
EXPLORING GLOBAL STYLES The originating GitHub thread for the effort is a great primer on its goals and scope. From a technical perspective, Global Styles currently works by using CSS variables to define styles. A set of controls are being developed to allow users to edit those variables within the Gutenberg UI. A lot of Global Styles work is still in flux, but earlyINTRODUCING SEEDLET
A typography-led theme, built for the future of block-based theming. This week the Automattic theme team launched a brand new theme called Seedlet. Seedlet is a simple, typography-driven foundation for folks to build their websites on. Its styles are opinionated, but generic enough that the theme can apply to a wide variety of different usecases.
CREATING A WORDPRESS THEME HTML STRUCTURE Now we’re starting to get into the real meat of WordPress Theme development: coding the HTML structure.. The Goals of Any HTML Structure. When coding a web site, you should have 2 goals in mind: lean code and meaningful code. That is, using as little markup (HTML tags) as possible and making sure that the markup is meaningful by using semantic class and ID names that refer to their content HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeuedTHEMESHAPER
Global Styles is a new mechanism for a theme to define a site’s styles. An important goal of Global Styles is to make it easier Continue reading “Getting Started with Block Themes: GlobalStyles”
USING BLOCKBASE FOR A THEME EXPERIMENT A glitchy theme, built with Blockbase. This all worked pretty well in the editor too! Due to a combination of Gutenberg limitations and browser bugs, I ran into an issue getting my SVG filters loaded into the Site Editor’s iFrame, but aside from that, things looked justlike the frontend:
THEME LAUNCHES
We have three Automattic-made themes now available on WordPress.org. Rebalance is a fresh take on the classic Imbalance 2 theme. Designed by Mel Choyce and developed by Allan Cole, Rebalance is a contemporary portfolio theme for photographers, artists, and graphic designers looking to showcase their work, and features an elegant Masonry grid for displaying both blog posts and Jetpack portfolio CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to OPEN SOURCE FONT PAIRINGS FOR YOUR NEXT THEME THE WORDPRESS THEME INDEX TEMPLATE Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates (with the exception of THE THEMESHAPER WORDPRESS THEME TUTORIAL: 2ND EDITION Many of you have written or commented to tell us how much you liked Ian Stewart’s original tutorial, “How To Create a WordPress Theme: The Ultimate WordPress Theme Tutorial”. You'll be happy to learn that that we've created a second edition. HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued CUSTOMIZING JETPACK’S SHARING MODULE One of my favorite feature in Jetpack is sharing, but if you are a theme designer/developer like me, it can be really frustrating trying to customize it.. By adding a simple filter to functions.php or inc/jetpack.php if your theme is based on _s, you can actually avoid the Sharedaddy stylesheet from being enqueued. /** * Remove Jetpack'ssharing script.
HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR CSS can be tricky. It can also be incredibly easy. I had a lot of help getting my head wrapped around CSS when I was first starting out and I take great pleasure in helping others the same way I was first helped: with solid code examples to learn from. Here, we’re going to layTHEMESHAPER
Global Styles is a new mechanism for a theme to define a site’s styles. An important goal of Global Styles is to make it easier Continue reading “Getting Started with Block Themes: GlobalStyles”
USING BLOCKBASE FOR A THEME EXPERIMENT A glitchy theme, built with Blockbase. This all worked pretty well in the editor too! Due to a combination of Gutenberg limitations and browser bugs, I ran into an issue getting my SVG filters loaded into the Site Editor’s iFrame, but aside from that, things looked justlike the frontend:
THEME LAUNCHES
We have three Automattic-made themes now available on WordPress.org. Rebalance is a fresh take on the classic Imbalance 2 theme. Designed by Mel Choyce and developed by Allan Cole, Rebalance is a contemporary portfolio theme for photographers, artists, and graphic designers looking to showcase their work, and features an elegant Masonry grid for displaying both blog posts and Jetpack portfolio CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to OPEN SOURCE FONT PAIRINGS FOR YOUR NEXT THEME THE WORDPRESS THEME INDEX TEMPLATE Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates (with the exception of THE THEMESHAPER WORDPRESS THEME TUTORIAL: 2ND EDITION Many of you have written or commented to tell us how much you liked Ian Stewart’s original tutorial, “How To Create a WordPress Theme: The Ultimate WordPress Theme Tutorial”. You'll be happy to learn that that we've created a second edition. HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued CUSTOMIZING JETPACK’S SHARING MODULE One of my favorite feature in Jetpack is sharing, but if you are a theme designer/developer like me, it can be really frustrating trying to customize it.. By adding a simple filter to functions.php or inc/jetpack.php if your theme is based on _s, you can actually avoid the Sharedaddy stylesheet from being enqueued. /** * Remove Jetpack'ssharing script.
HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR CSS can be tricky. It can also be incredibly easy. I had a lot of help getting my head wrapped around CSS when I was first starting out and I take great pleasure in helping others the same way I was first helped: with solid code examples to learn from. Here, we’re going to lay THEMES – THEMESHAPER This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to create DESIGN – THEMESHAPER Mazius & Montserrat. Mazius is a gorgeous calligraphic serif by Alberto Casagrande, featuring not one, but two italic styles (the second of which is shown in this demo).. Montserrat by Julieta Ulanovsky has been around for a while, but was redrawn and expanded in 2017 with new weights.. Mazius works great for large headings, while Montserrat is versatile enough to take up the slack for smaller BLOCKBASE: A PARENT THEME FOR BLOCK THEMES Phase 2 of Gutenberg introduces Full Site Editing to WordPress; to make this possible, we need a new way of building themes - using blocks. How do block themes work? Block themes use templates made entirely of blocks. The layout is configured using a combination of theme.json and CSS. The settings in theme.json are used GETTING STARTED WITH BLOCK THEMES: GLOBAL STYLES Global Styles is a new mechanism for a theme to define a site's styles. An important goal of Global Styles is to make it easier for users to change how their site looks without having to know or write any CSS. These theme styles are defined via a json configuration file. Importantly, it opens the ADDING BLOCK PATTERNS TO YOUR THEME From global styles, to entirely block-based themes, the WordPress block editor is aiming high.Amongst the newest experimental features are block patterns.Block patterns are unique, predefined combinations of blocks you can use and tweak to create stunningly designed sectionsof your website.
THE WORDPRESS THEME INDEX TEMPLATE Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates (with the exception of the dreaded comments template; that’s just plain difficult no EXPLORING GLOBAL STYLES Note: The code samples here are out of date. Please be sure to check out the block editor documentation for the latest on how to implement Global Styles. Global Styles is an aspect of full site editing that will have a major impact on theme development. To further myunderstanding of
WORDPRESS CHILD THEME BASICS In this post you’ll learn all the basics of WordPress Child Themes: WordPress Child Theme file structure, how to make any WordPress Theme a blank framework, how to import Parent Theme CSS styles, how to override Parent Theme styles, and how to override Parent Theme Template files.You’ll also learn that all of this is incredibly easy and within your grasp and that it might just change how HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued A 1000-HOUR HEAD START: INTRODUCING THE _S THEME Have you checked out the Toolbox theme? Up until recently it was the starter theme we used to build free and premium themes on WordPress.com. Toolbox was (and is!) a great theme, but it could be better. Unfortunately, we wound up in a situation with Toolbox where we wanted to make some more drastic improvementsTHEMESHAPER
Jason Crist, Posted on. January 8, 2021. January 11, 2021. Global Styles is a new mechanism for a theme to define a site’s styles. An important goal of Global Styles is to make it easier . Continue reading. “Getting Started with Block Themes: Global Styles”. USING BLOCKBASE FOR A THEME EXPERIMENT 1 day ago · A glitchy theme, built with Blockbase. This all worked pretty well in the editor too! Due to a combination of Gutenberg limitations and browser bugs, I ran into an issue getting my SVG filters loaded into the Site Editor’s iFrame, but aside from that, things looked just like the frontend: BLOCKBASE: A PARENT THEME FOR BLOCK THEMES Phase 2 of Gutenberg introduces Full Site Editing to WordPress; to make this possible, we need a new way of building themes - using blocks. How do block themes work? Block themes use templates made entirely of blocks. The layout is configured using a combination of theme.json and CSS. The settings in theme.json are usedTHEME LAUNCHES
We have three Automattic-made themes now available on WordPress.org. Rebalance is a fresh take on the classic Imbalance 2 theme. Designed by Mel Choyce and developed by Allan Cole, Rebalance is a contemporary portfolio theme for photographers, artists, and graphic designers looking to showcase their work, and features an elegant Masonry grid for displaying both blog posts and Jetpack portfolio OPEN SOURCE FONT PAIRINGS FOR YOUR NEXT THEME CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to THE WORDPRESS THEME INDEX TEMPLATE The WordPress Theme Index Template. Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR Add the following to your style.css, at the very top, immediately after the initial comments section. There’s no need to memorize the reset styles. Just paste them to the top of your stylesheet each time you start a new project. Reload your page and check how it looks in multiple browsers (if you can). CUSTOMIZING JETPACK’S SHARING MODULE Customizing Jetpack’s Sharing module. One of my favorite feature in Jetpack is sharing, but if you are a theme designer/developer like me, it can be really frustrating trying to customize it. By adding a simple filter to functions.php or inc/jetpack.php if your theme is based on _s, you can actually avoid the Sharedaddy stylesheet frombeing
THEMESHAPER
Jason Crist, Posted on. January 8, 2021. January 11, 2021. Global Styles is a new mechanism for a theme to define a site’s styles. An important goal of Global Styles is to make it easier . Continue reading. “Getting Started with Block Themes: Global Styles”. USING BLOCKBASE FOR A THEME EXPERIMENT 1 day ago · A glitchy theme, built with Blockbase. This all worked pretty well in the editor too! Due to a combination of Gutenberg limitations and browser bugs, I ran into an issue getting my SVG filters loaded into the Site Editor’s iFrame, but aside from that, things looked just like the frontend: BLOCKBASE: A PARENT THEME FOR BLOCK THEMES Phase 2 of Gutenberg introduces Full Site Editing to WordPress; to make this possible, we need a new way of building themes - using blocks. How do block themes work? Block themes use templates made entirely of blocks. The layout is configured using a combination of theme.json and CSS. The settings in theme.json are usedTHEME LAUNCHES
We have three Automattic-made themes now available on WordPress.org. Rebalance is a fresh take on the classic Imbalance 2 theme. Designed by Mel Choyce and developed by Allan Cole, Rebalance is a contemporary portfolio theme for photographers, artists, and graphic designers looking to showcase their work, and features an elegant Masonry grid for displaying both blog posts and Jetpack portfolio OPEN SOURCE FONT PAIRINGS FOR YOUR NEXT THEME CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to THE WORDPRESS THEME INDEX TEMPLATE The WordPress Theme Index Template. Index.php is the most crucial WordPress Theme Template. Not only because WordPress needs to use it if you’re missing any of its brother and sister templates (like, archive.php or tag.php) but because the work we do here, getting this template right, will help us breeze through the rest of our templates HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR Add the following to your style.css, at the very top, immediately after the initial comments section. There’s no need to memorize the reset styles. Just paste them to the top of your stylesheet each time you start a new project. Reload your page and check how it looks in multiple browsers (if you can). CUSTOMIZING JETPACK’S SHARING MODULE Customizing Jetpack’s Sharing module. One of my favorite feature in Jetpack is sharing, but if you are a theme designer/developer like me, it can be really frustrating trying to customize it. By adding a simple filter to functions.php or inc/jetpack.php if your theme is based on _s, you can actually avoid the Sharedaddy stylesheet frombeing
THEMES – THEMESHAPER This post outlines the steps I took to create a block-based theme version of Twenty Twenty. Thanks to Kjell Reigstad for helping develop the theme and write this post.. There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. Block templates are an experimental feature of Gutenberg (as of 7.2.0), and using them to create HOW TO MODIFY WORDPRESS THEMES THE SMART WAY Want to know the secret of having a custom WordPress Theme just like the coding and design experts—without having to create your own custom WordPress Theme? Are you a WordPress site developer wanting to significantly cut your development time by using your own WordPress Theme Framework? Or do you just plain wish editing WordPress Themes THE THEMESHAPER WORDPRESS THEME TUTORIAL: 2ND EDITION The simple theme we’re going to build in this tutorial, The Shape Theme (yes, it’s the Shape Theme from the 1st Edition, updated for the 2nd Edition), is based on _s. Download it and check it out if you’d like to see the finished code we’ll be going through, live, in action. It’ll be a while before we get to the CSS lesson, but ifyou
GETTING STARTED WITH BLOCK THEMES: GLOBAL STYLES Getting Started with Block Themes: Global Styles. Global Styles is a new mechanism for a theme to define a site’s styles. An important goal of Global Styles is to make it easier for users to change how their site looks without having to know or write any CSS. These theme styles are defined via a json configuration file.GOOGLE FONTS
Google Fonts’ filtering tools allow you to view fonts that contain a minimum number of available styles, which can often be a proxy for quality. I’ll usually search font fonts with at least four available styles (usually regular, italic, bold, and bold italic), thoughsearching for
INTRODUCING SEEDLET
A typography-led theme, built for the future of block-based theming. This week the Automattic theme team launched a brand new theme called Seedlet. Seedlet is a simple, typography-driven foundation for folks to build their websites on. Its styles are opinionated, but generic enough that the theme can apply to a wide variety of different usecases.
HOW TO ADD GOOGLE FONTS TO WORDPRESS THEMES When enqueuing Google fonts, there are five things to consider: Is the font enqueued instead of included directly in the template files or CSS? Is the font enqueued on the correct hook? Is the font URL protocol independent? Can translators deactivate the font if their language's character set isn't supported? Can the font be dequeued HOW TO RESET & REBUILD WORDPRESS THEME CSS & DEFINE YOUR Add the following to your style.css, at the very top, immediately after the initial comments section. There’s no need to memorize the reset styles. Just paste them to the top of your stylesheet each time you start a new project. Reload your page and check how it looks in multiple browsers (if you can). WORDPRESS CHILD THEME BASICS WordPress Child Themes are located in /wp-content/themes/ like any other WordPress Theme. They’re activated from the WordPress admin like any other theme. They’ll always have a style.css file and may often include a functions.php file. They can A 1000-HOUR HEAD START: INTRODUCING THE _S THEME This is why: The lineage and continual development process of _s gives you what I like to call a a 1000-hour head start. That’s the approximate number of design and development hours you get for free every time you use it in a project. Weeks and weeks of refinement by dozens of WordPress theme experts over several years that you don’thave
Skip to content
THEMESHAPER
Shaping WordPress ThemesMenu
* About
* Contact
FEATURED
Categories Theme Development DESIGNING THEMES WITH GUTENBERG BLOCKS AND SKETCH Follow Kjell Reigstad’s process as he explores designing a block-driven theme with Sketch, for the Gutenberg era. Categories Theme Development STYLING THEMES FOR GUTENBERGCategories Themes
THE PROMISE OF GUTENBERG: THEMES AS MORE DESIGN, LESS BAGGAGE ADDING BLOCK PATTERNS TO YOUR THEME Block patterns are unique, predefined combinations of blocks you can use and tweak to create stunningly designed sections of your website.From global styles
, to
entirely block-based themes,
the WordPress block editor is aiming high. Amongst the newest experimental features are _block patterns_.
Block patterns are unique, predefined combinations of blocks you can use and tweak to create stunningly designed sections of your website. The possibilities for block patterns are extremely exciting, especially for those of us providing tools to help people create their own websites. Patterns start to tackle the user question of, _“How do I make my website look like this theme demo?”_ By providing our users with predefined portions of layout, they can build and customize their own unique pages with a click — no coding or advanced block building knowledge required.THE PATTERNS API
Gutenberg 7.8
introduced
a new, experimental API we can now use to register custom blockpatterns:
1
2
3
4
5
6
7
register_pattern(
'my-plugin/hello-world',array(
'title' => __( 'Hello World', 'my-plugin' ), 'content' => "\nHello World
\n",)
);
View Documentation
The API really only contains two things: a name for your pattern, and the raw HTML output that you can copy and paste from the Code editor view. This means you can design your patterns straight in the editor, no coding knowledge required. When you add a new pattern to your theme, it shows up in a new sidebar in the editor, along with any other pattern you might have installed: _Note: The new Block Pattern sidebar is a temporary proof-of-concept and is subject to change._ Using this API, we can start to introduce block patterns into ourthemes.
ADDING BLOCK PATTERNS TO TWENTY TWENTY Let’s take a look at adding a block pattern to the Twenty Twentytheme.
The Twenty Twenty demo site showcases content that highlights the strengths of the theme. We can grab some of that content, and make it into a pattern that can be included with the theme. Now, rather than trying to replicate the site demo by hand, people using Twenty Twenty can insert the pattern directly into their own sites. On the homepage, one of the sections that catches my eye is the exhibitions list, which is a mix of images and text displayed in a grid. Not only does it look great, the combination of content is generic enough to be used for many different purposes, making it an ideal pattern to abstract out for reuse. Let’s break this content down into its basic blocks:__ Columns
____ Column
________ Image
________ Heading
________ Paragraph
________ Button
____ Column
________ Image
________ Heading
________ Paragraph
________ Button
The Columns block here acts as a wrapper for the exhibitions content, and provides a structure for it to collapse down into one column onsmaller screens.
The single Columns block is the smallest atomic unit we can include to make this a complete pattern. Even if the demo shows multiple rows of exhibitions, we’ll stick to just this single row of two items. If someone wanted to add a bunch of exhibitions on their own website, they could reuse this pattern multiple times. In order to convert this into a block pattern, we’ll need to grab the HTML output from the block in the Code view of the editor: We need to copy this HTML, escape it, and add it to a register_pattern function inside of Twenty Twenty’s functions.php file. _(I’ve used onlinestringtools.com to escape the raw html output, but there are also code editor tools that can do this.)_01
02
03
04
05
06
07
08
09
10
11
/**
* Register Block Patterns.*/
register_pattern (
'twentytwenty/exhibitions-pattern',array (
'title' => __( 'Two columns of mixed content','twentytwenty' ),
'content' => "\nWorks and Days
\n\n\n\nAugust 1 – December 1
\n\n\n\n)
);
When we go over and create a new page or post, we now see this pattern listed in the Block Patterns sidebar: Voilà! Twenty Twenty now comes with a pattern. You can view these changes in the Theme Experiments GitHub repo.
------------------------- You can add any number of patterns to your theme, and even unregister core patterns if you only want your patterns to be available to people using your theme. Create some great patterns that show off just what your theme is capable of! The only limitation is your imagination. Have you added patterns to your theme already? Tell us about it by Mel Choyce Posted on April 8, 2020April 8, 2020Leave
a comment on Adding Block Patterns to Your ThemeCategories
Education Tags Blocks, Gutenberg
, Patterns
EXPLORING GLOBAL STYLES Global Styles is an aspect of full site editing that will have a major impact on theme development. To further my understanding of this feature, I explored adding support for it to the block-based version of Twenty Twenty that Jeff Ong recently shared.
Some background: Global Styles aims to bring site-wide controls for things like colors, typography, and spacing into Gutenberg. The originating GitHub threadfor the effort
is a great primer on its goals and scope. From a technical perspective, Global Styles currently works by using CSS variables to define styles. A set of controls are being developed to allow users to edit those variables within the Gutenberg UI. A lot of Global Styles work is still in flux, but early pieces are available for themes to experiment with. For example, while using the latest version of the Gutenberg Plugin, themes can define a base set of Global Style variables in an experimental-theme.json file. Here’s a simple example of what one might look like, courtesy of Andrés Manerio’s global styles demotheme:
01
02
03
04
05
06
07
08
09
10
11
12
13
{
"color": {
"background": "#fff","primary": "#00f",
"text": "#000"
},
"typography": {
"font-scale": 1.2,
"font-size": "16px","font-weight": 400,
"line-height": 1.5
}
}
Each of these are automatically rendered out as CSS variables that the theme can hook into. On the front end, this equates to:1
2
3
4
5
6
7
8
9
:root {
--wp--color--background: #fff; --wp--color--primary: #00f; --wp--color--text: #000; --wp--typography--font-scale: 1.2; --wp--typography--font-size: 16px; --wp--typography--font-weight: 400; --wp--typography--line-height: 1.5;}
Theme authors can pull those in like any other CSS variable. Forexample:
1
2
3
4
5
p {
color: var(--wp--color--text); font-size: var(--wp--typography--font-size); line-height: var(--wp--typography--line-height);}
To help wrap my head around this, I took Jeff Ong’s work on the Twenty Twenty Blocks theme, and adapted it to use CSS variables as defined in a brand new experimental-theme.json file. You can browsethis here:
https://github.com/WordPress/theme-experiments/pull/26 This exercise was relatively straightforward. The concept really shines when thinking a little farther out though. Once I had those new variables in place, I tried them alongside an in-progress Gutenberg PRto add a Global
Styles sidebar to the beta site editor. This provides a vision of how style editing might feel in the future: This is still very early and very buggy, but the ability to modify these values globally in a single place is still very exciting. This is something my colleagues and I are looking forward to implementing into our themes when it’s ready. In case anyone wants to dig in to the exploration, the full code and some instructions are available over in the WordPress/theme-experiments repository. Give it a
test, and try adding an experimental-theme.json file to your block-based theme experiments as well. For more information on Global Styles, follow the project board onGitHub , and
consider joining the bi-weekly Block-based Themes meeting in the #theme-review channel of WordPress.org’s Slack. Finally, if you’ve already given Global Styles a try, I’d love to hear about it! Please share your work in the theme-experiments repository , or drop a link into the comments.by Kjell Reigstad
Posted on March 20,
2020 1
Comment on Exploring Global StylesCategories
Uncategorized
CREATING A BLOCK-BASED THEME USING BLOCK TEMPLATES _This post outlines the steps I took to create a block-based theme version of Twenty Twenty ._ _Thanks to Kjell Reigstad for helping develop the theme andwrite this post._
There’s been a lot of conversation around how theme development changes as Full Site Editing using Gutenberg becomes a reality. BLOCK TEMPLATES are an experimental feature of Gutenberg (as of 7.2.0), and using them to create block-based themes is in exploratory stages of development. > A block-based theme is a WordPress theme with templates entirely > composed of blocks so that in addition to the post content of the > different post types (pages, posts, …), the block editor can also > be used to edit all areas of the site: headers, footers, sidebars,> etc.
> Gutenberg Handbook>
Before diving in, I’ll reiterate that much of how this works is subject to change. This spec is in a very early stage. I hope by writing this, your interest is piqued to learn more and contribute your own experiment to the WordPress theme experiments repository.
STEP 1: CREATE THE THEME PROJECT In its simplest state, a block based-theme’s structure should look something like this:1
2
3
4
5
6
7
8
9
theme
|__ block-templates
|__ index.html
|__ block-template-parts|__ header.html
|__ footer.html
|__ functions.php
|__ index.php
|__ style.css
This is refreshingly simpler than most WordPress theme boilerplates. Here’s a quick overview what each file and directory does: * block-templates/: page templates that are composed of blocks. These follow the same template hierarchyas
traditional themes.
* index.html: the primary / fallback template to generate a post or page. (Analogous to index.php in traditional theme templates.) * block-template-parts/: the common collections of blocks to be usedin block templates.
* header.html: The global header, expressed in Gutenberg-generatedHTML.
* footer.html: The global footer, expressed in Gutenberg-generatedHTML.
* functions.php: This contains the usual theme setup and any otherreusable functions.
* index.php: This is actually just an empty file. You can technically remove it, but it’s a good habit to include an index file in everydirectory.
* style.css: Contains your theme’s styles as usual. Recreating Twenty Twenty as a block-based theme required adding a few extra stylesheets. Overall, I chose to add no extra page templates to keep the demo as understandable as possible. STEP 2: CREATE THE BLOCK TEMPLATES + BLOCK TEMPLATE PARTS There were just two that needed to be totally rebuilt as blocks: the header and footer. The process for turning these areas into block templates was something along the lines of: * ATTEMPT TO CREATE THE TEMPLATE PARTS IN THE BLOCK EDITOR * This can be done in a draft post or page. If you’ve enabled the Full Site Editing experiment in the Gutenberg plugin, you’ll see a new admin panel area Appearance/Template Parts — an area where in the future I could create, store, and edit the block template parts inmy theme.
* STYLE THEM AS CLOSELY AS POSSIBLE USING THE EDITOR * ADD BLOCK STYLE VARIATIONS + ADDITIONAL THEME CSS TO ADDRESS ANY GAPS THAT THE CORE EDITOR * Most of these styles were already present somewhere in the Twenty Twenty theme CSS, so I just needed to make minor modifications to assign them to the new blocks. STEP 3: SAVE THOSE BLOCK TEMPLATES + TEMPLATE PARTS AS DISTINCT FILES When Full Site Editing is enabled via the Gutenberg > Experiments panel, Gutenberg will expect that your theme provides block templates, overriding the normal templating behavior: Once I had my template parts designed and displaying properly, I would switch over to the Code Editor view, copy the markup generated, and paste the code into its respective file within my theme directory’s block-template-parts folder. _Edit: there’s an easier way to do this without switching to the code editor. You can select all blocks (Meta+A), copy (Meta+C), and paste into your text editor. _ STEP 4: ADD THEME STARTER CONTENT In order for the theme to be populated with pages and content, I borrowed the official TwentyTwenty theme starter content.
This step wasn’t 100% necessary, but a nice addition to have some content when someone activates the theme on a fresh WordPress site.DEMO
Here is the result: a site running the block-based Twenty Twenty.
POTENTIAL BLOCK IMPROVEMENTS Converting the header and footer to blocks helped me identify some functionality that would be nice to add to core blocks. Some of these are already in the works. * _Navigation block_ * Control over how the menu is laid out and collapses in differentviewports (#16829
)
* _Columns Block_
* The ability control the padding and margins (#10730, #16660
)
* Adjusting the size of one column, the remaining columns don’t resize equally (#19515)
HOW IS THIS BETTER THAN WHAT WE HAVE NOW? The structural block-based theme changes are generally not obvious on the front end. The process of switching between the Code editor, a template file, and previewing the site to achieve the intended design was tedious. However, this is just an interim step before we’re hopefully able to create and edit our theme (and your entire site) viaGutenberg.
The end benefit will become most apparent when the user can edit every piece of the page individually using Gutenberg. Being able to compose, manage, and reuse parts of your theme all within one visual interface is an exciting idea and one that’s close to reality. The other exciting aspect of this process was that it required very little PHP — just a few block style variation declarations and standard theme support registration. Everything else is CSS and HTML generated by the editor. To me this feels like a step in the right direction, lowering the barriers to entry for folks that are new to theme development and WordPress. ------------------------- I invite you to try it out; your comments and feedback are more than welcome. The source code for this theme is available on GitHub: https://github.com/WordPress/theme-experiments/tree/master/twentytwenty-blocks In that repository, you’ll find a handful of other block-based theme experiments: converted versions of Twenty Nineteen, the Gutenberg
Starter Theme ,
and a theme called Parisienne.
Each contains instructions for installation and activation. By the way, the theme-experiments repository is open for PRs! I’d love to see more people creating and testing themes that use this method: that’s the only way it’ll grow and improve. Feel free to ask questions in the comments or in the repository, andthanks for reading!
by Jeff Ong Posted on January 21, 2020April 3, 20203
Comments on Creating a Block-based Theme Using Block TemplatesCategories
Education , Theme
Development ,
Themes Tags Block Templates, Featured Content
, Gutenberg
, Starter Themes
, TwentyTwenty
CUSTOMIZING GUTENBERG BLOCKS WITH BLOCK STYLES Block styles are a simple way to get started with Gutenberg development: With a few lines of CSS, you can build something that feels like a whole new custom block. _This post was updated on January 13, 2020 to adopt the server-side registration approach described in the Block Editor handbook. _ ------------------------- A few years ago, Matt Mullenweg urged us all to “Learn JavaScript Deeply.” Becoming more familiar and comfortable with JavaScript is increasingly important for those of us who build the web. In the world of WordPress, projects like Gutenberg have begun taking a major step into a JavaScript-powered future. For designers and developers who are still getting used to these new languages and workflows, creating and customizing Gutenberg blocks can be somewhat intimidating. There are excellent toolkits like CreateGutenBlock to help
you get started, but even using those, building a block requires quite a bit of JavaScript familiarity. You also have to make sure you’ve got the right version of Node, learn some terminal commands, install some dependencies, etc. There’s quite a bit of up-front work necessary before you can jump in and start actually buildingsomething.
Despite these hurdles, we’ve seen an inspiring number of new block plugins surface lately: CoBlocks , and Atomic Blocks are great examples. They each add a variety of rich blocks, and truly enhance the site-buildingexperience.
There’s a much simpler way to start customizing Gutenberg blocks though, and it’s something we haven’t seen utilized much at this point: block styles. They take only a few minutes to pick up, and mostly just require you to know CSS. You’ve likely noticed block styles while using Gutenberg. The Quote, Pullquote, Separator, Table, and Button blocks ship with some alternate styles by default. Block styles are an excellent but relatively unused area of Gutenberg customization. They’re a simple way to get started with Gutenberg development: With a few lines of CSS, you can build something that feels like a whole new custom block. Also, since they’re reusable across multiple sites, block styles help pave the way for a more flexible system of components that make up a site’s theme. Technically, block styles are very simple. They’re composed of twothings:
* A few lines of PHP (or JavaScript) to declare the block variation and give it a custom class name. * CSS styles to fine-tune the appearance. That’s it. A block style is a custom block class, with some stylesapplied.
IMPLEMENTATION
A block style can be implemented in a plugin or in a theme. For this example, I’m going to focus on making a plugin. One of the benefits of using a plugin is that it’s not tied to the user’s theme. This allows your block style to be used across any site, running any theme — as if you had built an entirely new custom block. Block styles can be defined in JavaScript,
or in PHP
.
To keep things simple, we’re going to focus on using the latter. This lets us set everything up with only two files: * index.php to set up the plugin, declare the block style, and enqueue the stylesheet * style.css to house the actual stylesINDEX.PHP
By default, index.php just needs to initialize the plugin with a DocBloc , enqueue the CSS file, and register a new block style:/**
* Plugin Name: Block Styles */
/**
* Register Custom Block Styles */
if ( function_exists( 'register_block_style' ) ) { function block_styles_register_block_styles() { /**
* Register stylesheet */
wp_register_style(
'block-styles-stylesheet', plugins_url( 'style.css', __FILE__ ), array(),
'1.1'
);
/**
* Register block style */
register_block_style( 'core/paragraph',
array(
'name' => 'blue-paragraph', 'label' => 'Blue Paragraph', 'style_handle' => 'block-styles-stylesheet', )
);
}
add_action( 'init', 'block_styles_register_block_styles' ); }
Let’s take a closer look at the block style registration portion: register_block_style( 'core/paragraph',
array(
'name' => 'blue-paragraph', 'label' => 'Blue Paragraph', 'style_handle' => 'block-styles-stylesheet', )
);
The second line tells Gutenberg which existing block to start with. In this example, we are going to create a block style for the Paragraph block. Any existing block can inherit a block style, so if you were to target a different block, you’d change core/paragraph to the name of a different block. Technically, these names are found in the Gutenberg block source code
,
but they’re usually easily guessable. For example: core/cover, core/separator, etc. The name parameter on the fourth line creates the custom class that’ll be assigned to the block. In this case, I’m calling it a blue-paragraph, but it can be anything you’d like. Since this will be used for a CSS class, be sure not to use any spaces. The label parameter corresponds to the text label for your block style. This will be shown in the interface when someone opens the “Block Styles” panel. Finally, style_handle points WordPress to the stylesheet where it can find the CSS for your block style. STYLE.CSS
The CSS file is pretty straightforward. Use the custom class name you created in block.js (along with a is-style- prefix), and insert your styles inside:
.is-style-blue-paragraph { // Custom CSS styles go here. }
Your styles here will build off of the default block styles, and will be loaded in before a theme’s editor styles. So be sure to keep your selectors specific enough to override those potentially competing styles.
BLOCK STYLES PLUGIN BOILERPLATE To help you get started, I’ve created a GitHub repository that you can clone and use to get started. It contains the three files detailed above, along with some light documentation. https://github.com/Automattic/gutenberg-block-styles Out of the box, the repository is a small plugin that adds a “Blue Paragraph” block style to the Paragraph block: With a few small adjustments, it’s possible to change this into something drastically different. There’s another branch on that GitHub repository that includes a _Music _
theme
-style
cover block variant: I’ve included a third branch that adds a somewhat ridiculous animation to the text (or emoji) inside of a Cover block: Both of these are accomplished by changing about a dozen lines of code in the repo. They took minutes to create, and work across any site that uses Gutenberg, regardless of the theme it’s using. WHAT WILL YOU CREATE? Block styles are ripe with possibility. I’d love to see a _CSS Zen Garden _-style plugin someday that showcases dozens of different ways to customize blocks through block styles.
In the meantime, have you built something cool using block styles? If so, I’d love to hear about it. Please share your explorations in the comments.
by Kjell Reigstad
Posted on February 15, 2019January 14, 2020 2
Comments on Customizing Gutenberg blocks with block styles Categories
CSS Tips , Tools
A SCHEMA FOR GUTENBERG BLOCKS At Jetpack we recently created a new Gutenberg block which displays “Related Posts”
.
This block is similar in content to the “Latest Posts” block in WordPress.org; it’s just a list of posts. The difference is the way the posts are displayed: * Latest Posts
* Related Posts
There are plans afoot to update the
“Latest Posts” block, so that it contains an image and a post summary (see image below). As these two blocks grow they seem to be converging on similar layouts, but with different content. There are similar overlaps with other blocks. For example the layout of the WordPress.org gallery block could also be used to display a list of posts, as could the recently launched Tiled Gallery block .
Evidently there are many layout possibilities for a list of posts! THE PROBLEM
As the number of Gutenberg blocks grows these overlaps become more obvious. As we start to build pages with Gutenberg it starts to become apparent that this is going to get very messy very quickly. Essentially blocks have a content and a presentation element. Taking the example we began with, we can see overlap between many different types of content:
LISTS OF CONTENT
One type of content is a list of text, images and links. These come in many different forms, but they share the same structure: * Latest posts
* List of posts in a category * List of post in a tag * Archive of posts by month/year etc * List of categories/tags * List featured posts * List of images
* List of authors
* List of
Similarly, all of the above types of content could be displayed in any of the following ways: LAYOUTS
Here are some examples of the different types of layout that this content could use:
* Vertical list
* Vertical list with images * a grid of items, with/without text * round items, with/without text * A slideshow with thumbnails * A slideshow
* Featured item with sub items The challenge is that each of these different types content can be displayed in each of these different layouts. If we wanted to create blocks for each of these combinations we’d end up with over a hundred different blocks. On the other hand we could build one single block which was so complex that it could display all these combinations within one block. Neither of these would be sensible solutions.
CAN WE USE BLOCK STYLE VARIATIONS? Block Style Variations offer an API which allows us to modify the CSS for a block – they let us overlay a presentation layer on top of an existing block. This is ideal when modifying the way a block looks. However many of the layout variations I have examined above require more than just a different CSS, they need different markup and additional JavaScript. SEPARATING CONTENT AND PRESENTATION One solution to this problem could be to separate content from presentation in our blocks. What if we were able to define semantics for the content in our blocks, which could be interpreted by different layouts? This would mean users would first think about the content they wanted to show, and then all display options would be open to them.
A SHARED DATA STRUCTURE The overlap between these blocks occurs because they all share the same data structure (an array of text, image and link). It would be possible to define a standard data structure that blocks can use. When blocks share a data structure, then it should be possible for them to share common layouts. This would mean a photo gallery display could be reused to display a list of posts, or a block that displays a list of recent posts could be reused to show a list of authors. HOW COULD THIS WORK? “Block Transformations” are an existing mechanism which converts one block into another. At present every transformation has to be coded separately.
Could we re-imagine the way that transformations work, so that if blocks share a common data-structure, they can easily be transformed into each other, without writing custom transformation code? Similarly, could we make changes to the way “Block Style Variations” work, so that they can apply a layout to our structured data?
FEEDBACK
What do you think? Is this a problem? Are there other solutions I haven’t considered? Leave a comment! by Ben Dwyer Posted on January 29, 2019January 29, 2019 7
Comments on A schema for Gutenberg blocks Categories
Uncategorized
BLOCKS, TEMPLATES, AND STYLES: ARCHITECTURE FOR A GUTENBERG WORLD Exploring ideas about the evolution of layout and presentation in a post-Gutenberg world _What described below is an broad idea, some thoughts on one way the WordPress ecosystem might evolve in response to the new capabilities of Gutenberg. Huge thanks to Kjell Reigstad and David Kennedy for helping me think through these concepts!_ Traditionally, themes have been the only authority when it came to the layout and presentation of a WordPress site. They provided the entire page structure, typography, the color scheme, the menu functionality, the responsive rules, and more. Themes generally had the full power to dictate if and how users could customize each of those elements. With the advent of Gutenberg, we’ve seen some of those responsibilities shift. Regardless of their theme, users can now add responsive column-based layouts to any page, assign custom colors to most of their content, and insert rich elements anywhere within a post or page. As a result, some of the responsibilities for the design of a site are blurred: The theme takes care of some aspects, while Gutenberg handles others. Much of that architecture is still to be defined as Gutenberg moves into Phase 2 and beyond. Gutenberg brings many opportunities to WordPress, but the biggest impact comes from the way it can enable a much clearer product architecture — one which enables modularity, consistency, and interoperability — and the positive impact that can have on the end user experience of WordPress. To that end, it can be helpful to think of layout and presentation not as the “Theme”, but as a set of interrelated pieces, each with their own set of responsibilities, working together to create a site. BLOCKS
A block is a component that exists visually a page. It can be a “simple block”, like a paragraph or an embed; or it can be a “complex block”, which has a layout of multiple nested blocks, like a testimonials section. This distinction doesn’t necessarily matter to the user as there’s a unified insertion and discovery mechanism. Blocks can contain PLACEHOLDER CONTENT THAT IS NEUTRAL — in other words, they start as a “blank slate”, except for placeholder content that guides users as to how to add content to the block.
A block can contain layout information, including media queries that define how the block behaves responsively in different viewports. A block could conceivably define styles that would override the ones provided by the template or the global styles, in order to create a unique presentation for a particular block. TEMPLATES
While Gutenberg makes it easy to create a custom, complex page layout from scratch, the process of starting with a blank slate and designing a layout that looks good will likely still be daunting for many users. Giving users access to a collection of pre-built Gutenberg page templates would enable them to get started more quickly and simply tweak the template to their needs. A template would define A COLLECTION OF BLOCKS IN A PARTICULAR ORDER AND LAYOUT that make up an entire page. In addition, templates can contain “STARTER CONTENT” — editorial boilerplate text and media so that a user can simply tweak and replace rather than having to start from scratch. The concept of a template library would mean that there could be a core library of basic templates, in addition to non-core templates that can be developed by anyone and installed separately (similar to how blocks work). STYLES
Styles would define the global aesthetics of the site, and would provide a central definition for typography, colors, spacing, icons, and more. Brent Jett has suggested some interesting ideas for how this might manifest on the user-facing side. Styles may also provide some global guidelines for layout, such as global settings for responsive behavior, etc. Layout that is specific to a page template or a block should be defined locally by that element, though. THEMES
Given all the new controls over layout that blocks and templates can provide, what does a theme mean in this new world? It seems that themes can become more lightweight. Perhaps a theme is simply a JSON wrapper that defines the components of that theme — identifying the blocks, templates, and styles that make up the theme. Rather than bundling all of the parts of the theme in a tightly coupled piece of software, the theme could simply be a high-level definition that identifies the modular dependencies (styles, templates, blocks) that need to be installed. When a theme is deactivated, a user could even have the option to keep the templates and blocks in their library for future use. This could allow for greater flexibility but also greater standardization, creating a consistent and modular framework for shaping how sites get built in the future. We all know that themes will evolve, and this is just one early idea. As we move forward together, WordPress will surely benefit from the sharing of ideas and explorations around the future of themes. If you have a vision yourself, please share it! Feel free to use the comments below, your own blog, Twitter (use the tag #gutenideas ), or wherever you can get the word out.
by Alexis Lloyd Posted on January 17, 2019
2
Comments on Blocks, templates, and styles: architecture for a Gutenberg world
Categories
Design , Ideas
, Themes
DESIGNING A GUTENBERG-POWERED THEME: MUSIC Kjell Reigstad walks through his experience designing a block-powered theme.
Last week, Allan Cole and I shared a new Gutenberg-powered theme called
_Music_.
In this follow up post, I’m going to take you through the design process for the theme. At its core, this felt a lot like a typical theme design process, but I did learn a lot about block-based design along the way.
BLOCKS
When Allan and I decided to make this theme, we already had a homepage comp featuring a handful of blocks. That comp did a great job of setting the tone for the design aesthetic. To get things going, I decided to apply that aesthetic to the other default Gutenberg blocks. I worked through the Gutenberg Blocks Sketch document from
my last post, updating styles as I went. Working this way was great for a couple reasons. First, it helped me focus — I’d never designed a block-optimized theme before, and this kept my design explorations squarely on the blocks themselves. I thought, “Gutenberg is all about blocks, right? I’ll design some blocks.”
Second, the Sketch file allowed me to see every single block style in one place. In effect, I was creating a sort of pattern library as I went. I thought this was pretty cool, and figured it’d come in handy later on when we began development. As I got further through these block designs, I realized the need to see all of these individual blocks in context; I’d design a wide-width cover image block, but I had no idea how it’d look in use. So I began dragging blocks around and stacking them up to get a sense of how they’d feel together. This helped a little bit, but still wasn’t enough. At this point, I realized something that should’ve been obvious: _blocks are not a theme_. They’re just part of a theme. By designing blocks first, I’d been avoiding the big picture. Users will never see blocks all by themselves — they’ll exist within full pages. I needed to design more pages.
PAGES
My initial homepage design comp introduced a rough idea of a header and an off-centered text column. I began by duplicating that initial page and clearing out all the blocks on it, then pulled together some sample content. Looking at the project through the lens of my imagined client (the band Superserious), I was able to think through examples of blocks and block combinations that might exist on a real site: the columns block to display album information, the table block to display tour dates. This felt much more effective than randomly placing blocks on a page.
Around this time, I hit my stride, design-wise. I’d lay out a page using my existing blocks and the sample content. Then I’d iterate and experiment with everything on that page. Once things looked right, I’d migrate any new block tweaks back to the global symbols and start fresh on the next page. After a little while, I ended up with a solid set of sample pages. Backing up and thinking about page design helped me shift focus to other, more traditional components that needed to be designed too: archive pages, page footers, post headers, etc. Designing these wasn’t all that different than it would’ve been without Gutenberg. In a way, we’ve all been designing with blocks all along — we just hadn’t called them blocks. Take a look at this entry summary: If I’d designed this theme pre-Gutenberg, I still would’ve designed each one of those pieces — they’re all fairly standard parts of a theme. But thanks to Gutenberg, each piece is part of a clear pattern library, to be reused throughout the design by me _and_ by the user. That’s pretty cool. I’d gone into this project thinking I’d spend most of my time styling individual blocks, but I ended up splitting my time pretty evenly between designing block variations and overall page elements. In that sense, this wasn’t as drastically different from a traditional theme design as I’d anticipated. PROTOTYPES
I’d been getting ongoing feedback from Allan throughout the process above, but once we were happy with the page designs above, we gathered with the rest of the Theme team to get broader design feedback. To help with that process, I pulled all my comps together into a prototype. This took just a few minutes to do, and really helped others get a sense of how the theme will work in practice. I created two separate prototypes with Invision: one for desktop and
one for mobile
.
If my transition from block design to full-page design was about looking at the bigger picture, these prototypes stepped back still further: they showed us the context _around_ that big picture. We were all able to see the designs on-device and test some basic interactions.
The team’s feedback was (as usual) very helpful — we made some subtle revisions to text contrast, adjusted a number of margins, and kicked off a lot of iteration on the mobile menu treatment. DEVELOPMENT
Allan had been focused on the build from the beginning, and had the majority of the framework in place at this point. After our design feedback session, I jumped into the code too. From the development angle, we’d already determined a few things in the design that we couldn’t do, or that would take too much effort. For instance, in my initial design comp I’d had a series of backgrounds run down the page. Gutenberg doesn’t have a method for doing something like that today; despite my wishful design thinking, there’s no method for layering a background behind a group of blocks. We could’ve accomplished it through customizer settings, but we shelved the idea in favor of keeping things simple. We also abandoned a bunch of the play buttons I’d originally included, since those’ll require some custom blocks (more on that later). Once I jumped into the code, my main revelation was that there were _way_ more block options than I’d originally anticipated. A number of blocks had options I’d never noticed before. I hadn’t realized that paragraph blocks could be set to full width, or that cover image blocks could be floated left or right. In addition, I realized some design decisions I’d made were actually supposed to be user-editable: I’d overlooked the fact that users can edit the text alignment and image opacity for the cover image block. This required more design exploration, but it guided us towards a much more customizable theme — definitely a win in the end. Beyond those updates, the majority of the design-oriented development work involved minor fixes and adjustments — polishing up the CSS to make sure it aligned with the intent of the original design. NEXT STEPS
Now that we’ve had our initial release, Allan and I plan to build a separate plugin with complementary music-centric blocks, like a tour dates block and a mashup of a cover image and an audio player. We’ll hope to showcase those at some point in the future. In the meantime, keep an eye out for the next post in the series: Allan’s experience from a development perspective. by Kjell Reigstad
Posted on June 4,
2018June 4, 2018
1
Comment on Designing a Gutenberg-Powered Theme: Music Categories
Design , Themes
Tags Design
, Gutenberg
, themes
MUSIC: A GUTENBERG-POWERED THEME Announcing the Music theme: an exploration of how Gutenberg can transform theme design and development. A couple months ago, I created a Sketch document to assist with
the design of block-driven themes. I posted about that here on Themeshaper
,
and provided a couple short examples of how it could be used in a theme design workflow. Since then, Allan Cole and I have been working to make one of those examples — a site for an imagined band named Superserious — into a working example of a Gutenberg-powered WordPress theme. We named the theme “_Music_.” Allan and I set out to experiment, learn, and create a resource for the community. We’ve documented our experience designing and building this theme, and will be publishing our notes in a series of posts here on Themeshaper. To kick things off, we’re releasing _Music_ on GitHub today. We’d love for you to give it a spin, tinker with it, and explore how it works with Gutenberg. Here are a few things to look out for: ------------------------- DESIGN
Our design goal for the theme has been to show that it’s possible (and encouraged!) to make a Gutenberg theme that doesn’t necessarily look like Gutenberg. We wanted to create something bold and a little experimental; a theme with somewhat aggressive, non-standard styles. Gutenberg gives users unprecedented control over their site design, opening the door for variety and experimentation. Our favorite example of this is our cover image blocks. They look great out of the gate, but users can adjust the image, alignment, and color to achieve a wide range of looks:
------------------------- DEVELOPMENT
You’ll be happy to hear that the overall theme development process wasn’t all that different with Gutenberg. Common patterns like headers, footers, and loops work just as you’d expect in a Gutenberg-powered theme. In many areas, Gutenberg makes things easier for both users and developers. For instance, full-width header images used to require a custom-built customizer or theme option solution, but now they’re essentially built in. This was important to keep in mind while building the theme, and was a very positive change for development. Creating stylesheets for blocks was pretty straightforward. Expanding on the built-in stylesheets in _s, we added a blocks.scss file to the SASS directory and placed all of our block-specific styles and overrides there. This kept everything nice and organized and is likely to appear in _s in the future .
Since Gutenberg is output by the_content(), we learned to take special care with any wrapper divs that might clip or obstruct the expected behavior of Gutenberg blocks. We’ll talk more about that in a follow up post.
------------------------- BLOCK STYLES
We’re truly excited about the custom editor styles that ship with _Music_. These styles are a breakthrough: they give users a much clearer sense of what their visitors will see on the front end. Best of all (for theme developers at least), the editor styles were a breeze to integrate! We built all of these in over the course of just a few hours.
------------------------- Like most of the work we do, the Music theme is open source. You can find it on GitHub:
https://github.com/automattic/musictheme/ If you’d just like to see the front end, feel free to click around our demo site here:
https://musictheme.mystagingwebsite.com/ In many ways, designing and building this theme was similar to the way we’ve made themes in the past — but we did carve out a few new practices along the way. Allan and I will be sharing them with you in upcoming posts. In the meantime, we encourage you to download, install, and experiment with _Music_ yourself! _Read part two of this series: Designing a Gutenberg-Powered Theme: Music
_
by Kjell Reigstad
Posted on May 22,
2018June 4, 2018
8
Comments on Music: A Gutenberg-Powered Theme Categories
Design , Theme Development , Themes
Tags Design
, development
, Gutenberg
, themes
DESIGNING THEMES WITH GUTENBERG BLOCKS AND SKETCH Follow Kjell Reigstad’s process as he explores designing a block-driven theme with Sketch, for the Gutenberg era. There’s been an exciting discussion happening around the changes that Gutenberg will bring to themes. At Automattic, we’ve begun to prepare for Gutenberg by reevaluating our theme design and development processes. As part of that work, I did some thinking about how I might start designing a block-driven theme today and what sorts of resources I’d want to have. The most important thing that came to mind was a way to access and customize all of the core Gutenberg blocks with a few clicks. This would allow me to quickly test and iterate on block design without having to dig into code. I do a good deal of my design work in Sketch , so I began to search for a way to make this possible there. Luckily, there are already a few Gutenberg-related Sketch files in the wild. The Gutenberg Contributors page on GitHub and the Design Principles & Vision page on
WordPress.org are great places to start. These are mostly aimed at the Gutenberg editing interface, however, and didn’t quite accomplish what I was looking for, so I ended up building a new file instead: This new Sketch file contains symbols for all of the default Gutenberg blocks (with the exception of all the embeds, since those aren’t very customizable). With this set of symbols, it’s possible to quickly build a layout composed entirely of Gutenberg blocks using Sketch:
It’s actually pretty fun to use! In a way, it’s Gutenberg — but for Sketch.
From here, it’s easy to start customizing styles: I took this method for a spin and tried to mock up a theme for an imagined restaurant. To get started, I built out the page structure using default Gutenberg blocks: From there, I started doing some light customizing. I cut myself off after a while, but the end result looked fairly decent: I find this pretty cool. It’s an example of what a block-driven theme might look like with just a little bit of CSS customization. From here, I could easily keep going and put together a complete, modular design system for this theme by customizing the rest of the Gutenberg blocks. I could view the blocks all at once on the Symbols page, and quickly build out a wide variety of layout options to make sure my styles held up to intense layout customization. ------------------------- I almost ended there, but I decided to confront a lingering concern I’ve had about Gutenberg: I’ve feared that if we lean too much on Gutenberg for theme layout, we’ll end up with lots of very similar, “blocky” themes. The restaurant site I designed above looks fine, but it’s also clearly made of blocks. I wondered if it’d be possible to create something more experimental using this same Sketch file as a base.
So I took another stab at a pretend site design (this time for a band named Superserious), and forced myself to break out of the blocks a little more. Again, I began with a pure-Gutenberg layout: But this time, I was much more aggressive in my customization and aimed for a more tailored mobile experience with bold typography: This was a fun exercise, and it helped allay my fears a bit. That first Cover Image has all the usual pieces, but they’re styled in a very opinionated way. The rest of the blocks are fairly standard, but they still stand out because they exist within a heavily stylized, off-balance frame. The overall effect is drastically different from the theme in the previous exercise. ------------------------- This process was very useful for me, and I’d love to see if it’s useful for the rest of the community as well. You can download and contribute to the Sketch files here: https://github.com/Automattic/gutenberg-themes-sketch The repository includes a basic Sketch file with just the symbols, plus all the text hierarchy styles (H1, H2, etc). I also created a library file in case that’s preferable for anyone. We hope to update these files periodically, and would love to hear feedback from others who use them. In the meantime, we’ll keep experimenting with ways to design themes in this new Gutenberg-based future. by Kjell Reigstad
Posted on March 7,
2018March 8, 2018
5
Comments on Designing Themes with Gutenberg Blocks and Sketch Categories
Theme Development
Tags Gutenberg
STYLING THEMES FOR GUTENBERG What we learned by developing three themes with Gutenberg in mind. At the Automattic Theme Team meetup in December, we focused on several Gutenberg-related projects. The first one we’re sharing is a set of Gutenberg-friendly themes based on Underscores .
The project’s goal was to help us think about our themes differently, dig into adding theme support for Gutenberg, and as a byproduct, do some testing of Gutenberg itself. Six team members participated in this project, and it resulted in three themes which are still in progress, and currently available on GitHub.
WHAT IS GUTENBERG?
Gutenberg is the new block-based content editor currently being developed in GitHub for WordPress 5.0. Until it’s merged into core, it’s available as a plugin .
It’s really going to change the WordPress publishing experience! From the WordPress.org Gutenberg page :
> The Gutenberg editor uses blocks to create all types of content, > replacing a half-dozen inconsistent ways of customizing WordPress, > bringing it in line with modern coding standards, and aligning with > open web initiatives. These content blocks transform how users, > developers, and hosts interact with WordPress to make building rich > web content easier and more intuitive, democratizing publishing — > and work — for everyone, regardless of technical ability. THE THEMES
The three themes we developed during the meetup are called _Fashion Blog_, _Handicraft,_ and _Ohana_. We decided to try to make these themes CSS-only to help keep the focus on Gutenberg itself and let us build on the recent work the team’s been doing with Style Packs. This
turned out to be an ambitious restriction — a little more on that later — but it made for an interesting design challenge. Fashion Blog
Handicraft
Ohana
_Fashion Blog _,
_Handicraft _ and _Ohana _ are currently available on GitHub; you can learn more about each theme there and check out exactly how they were set up. The themes are still works in progress and have some rough edges. The end goal is to get them ready for WordPress.com.
THE PROCESS
Over the course of a few days, we researched and decided on an audience for each theme, designed and built them, and added Gutenberg support.
We opted to use a one-column design for all three themes, to best accommodate the “full” and “wide” block alignment options in Gutenberg.
Though it can vary from theme to theme, this is how Handicraft styles Gutenberg’s wide alignment (on the left) and Fashion Blog styles the full alignment (on the right). ADDING GUTENBERG SUPPORT You don’t actually have to do anything to use Gutenberg with a theme, but by declaring theme support you can add two optional features: the “wide” alignments (full width and wide width), and custom colors for the block-color palettes. The following example, when included in the setup function in functions.php, will add both: 01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
/**
* Add support for Gutenberg. *
* @link
https://wordpress.org/gutenberg/handbook/reference/theme-support/ */
add_theme_support( 'gutenberg', array( // Theme supports wide images, galleries and videos. 'wide-images' => true, // Make specific theme colors available in the editor. 'colors' => array(
'#ffffff',
'#000000',
'#cccccc',
),
) );
Whether or not you include custom colors in your theme, Gutenberg will always include a color picker with the palette, for further customization.
Gutenberg’s
default color palette, shown while editing the Button block. STYLING THE THEMES
In general, the default blocks don’t need styling — Gutenberg already includes styles that match each block’s functionality. For example, the Gallery block already has the styles needed to split your galleries into different columns, and the Cover Image block will place the text and image added on top of each other, without the theme’s help.
If any of the styles don’t fully suit your theme’s design, you can adjust them as needed. One thing we noticed while we were developing these themes was Gutenberg’s distinct pill-shaped button style, which might not work with every theme. On the flip side, themes are fully responsible for figuring out how the “wide” and “full” alignment styles should be handled, if they support them. This makes sense, since support is optional, and exactly how they should look can vary depending on a theme’s individual style.
At the time of writing, the Gutenberg theme styles these two
alignments by setting max-widths for specific HTML elements ,
with a wider max width when either the .widealign or .fullalign classes are used.
In our three themes, we approached it a bit differently, setting a max-width for the page content, and instead using CSS to stretch those wider elements outside of it. We used vw and stretched the wider elements based on the screen size: 01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
@media (min-width: 750px) { .alignfull {
margin-left: calc(50% - 50vw); margin-right: calc(50% - 50vw); width: auto;
max-width: 1000%;
}
.alignwide {
margin-left: calc(25% - 25vw); margin-right: calc(25% - 25vw); width: auto;
max-width: 1000%;
}
}
This approach works, but because vw includes the width of the vertical scrollbar as part of the whole screen width, you can get a little horizontal scrolling. One fix is adding overflow: hidden to one of the page-width elements further up the HTML tree. If you didn’t want these elements’ widths to be based on screen size, you could also set a specific max-width. There’s no one “right” way to approach these styles, and I’m sure more and more examples will come out of the woodwork as more themes add styles for Gutenberg. For example, Justin Tadlock has shared his method using different calc values ,
and Joen Asmussen has blogged about his approach of applying max-widths to all child elements that aren’t wide or full width .
In our themes, we also kept any block-specific styles separate in their own stylesheet. ADDING EDITOR STYLES To make the editing experience more what-you-see-is-what-you-get, you can add Gutenberg editor styles using enqueue_block_editor_assets. It’s similar to how editor styles can be enqueued for the current TinyMCE editor. This makes sure what a user sees when building their pages best matches how the content will actually look with your theme when published.
Here’s an example of enqueuing an editor-specific stylesheet: 1
2
3
4
5
6
7
8
/**
* Enqueue editor styles for Gutenberg */
function theme_slug_editor_styles() { wp_enqueue_style( 'theme-slug-editor-style', get_template_directory_uri() . '/assets/stylesheets/editor-style.css' );
}
add_action( 'enqueue_block_editor_assets', 'theme_slug_editor_styles' );
Like with the TinyMCE editor, you can also include fonts. So for example, if your theme is enqueuing fonts from Google ,
you can include them in the Gutenberg editor, too: 1
2
3
4
5
6
7
8
9
/**
* Enqueue editor styles for Gutenberg */
function theme_slug_editor_styles() { wp_enqueue_style( 'theme-slug-editor-style', get_template_directory_uri() . '/assets/stylesheets/editor-style.css' );
wp_enqueue_style( 'theme-slug-fonts', theme_slug_fonts_url(), array(), null );
}
add_action( 'enqueue_block_editor_assets', 'theme_slug_editor_styles' );
Unlike the TinyMCE editor, Gutenberg’s editor styles include the post title:
An example of Ohana’s editor styles. The editor styles need to be pretty specific to make sure they’re not applied to other elements of the page outside of the editor — Rich Tabor has a good post here about his experience with this behavior
.
Gutenberg includes specific classes around different elements in the editor, so you can prefix selectors more generally with the class .editor-post-visual-editor, or use more specific classes to target individual blocks — for example, styles for .editor-block-list__block h1 would only be applied to h1s inside of a Heading block. WHAT WE LEARNED
Overall, this project was a great way to ramp up quickly on some Gutenberg-theming basics, and get our feet wet. Some specific things we learned from this process include: * The Gutenberg default block styles are numerous and can be a bit opinionated. This is good, in that you can rely on Gutenberg to do a lot of the heavy lifting, but there are some styles that would need to be updated to match individual theme styles. * It can be tricky to set up the wide and full-width styles; as more themes add styles for Gutenberg, it’ll be interesting to see all the different ways themes handle this. * Setting up the block styles for the back-end editing experience was more involved than any of us had anticipated. It’s very much like adding editor styles to the current TinyMCE editor, but some Gutenberg blocks have very specific classes that needed to be overridden.
We also learned a couple non-Gutenberg related things: * From a project-planning perspective, we could have spent more time narrowing down the kinds of themes we wanted to build — and the actual designs — prior to the meetup. This would have left more time to focus on the Gutenberg part of each theme. * In the end, it wasn’t possible to complete the project without making edits to these themes in addition to CSS. On top of the PHP changes needed to support Gutenberg’s optional features, we needed to make edits for common WordPress.com-functionality — like adding social menus, and more Content Options support — and for the designs themselves, like enqueuing Google fonts.
NEXT STEPS
Our goal is to get these themes launched on WordPress.com. To get there, they still need some WordPress.com-specific functionality, like the annotations for WordPress.com’s custom fonts and colors, WooCommerce support, and styles for WordPress.com widgets. We hope that sharing this process is helpful for your own Gutenberg journey as themers. We’d love to hear about your adventures. by Laurel Fulford
Posted on February 15, 2018February 16, 2018 12
Comments on Styling Themes for Gutenberg Categories
Theme Development
Tags Gutenberg
LODESTAR LAUNCHES
LODESTAR is now launched on WordPress.org. Designed by Mel Choyce and developed by Laurel Fulford , Lodestar is a precursor to Twenty Seventeen, and you’ll see echoes of that default theme throughout, starting with its multi-panel front-page layout. A filterable portfolio section is available through Jetpack , along with a stylish testimonials page .
Mel shares a bit about Lodestar’s origins: > Lodestar started as a restaurant theme named “Porterhouse.” I > designed it before we had a good solution for multi-panel homepages, > so it was tabled. Once we had a couple solid multi-panel homepage > themes, I redesigned it as a more generic business theme. Explore the Lodestar demo, study the setup guide, or download and give it a try. by Kathryn P. Posted on February 5, 2018
Categories Theme
Launches Tags
Lodestar
STUDYING TEXTBOOK
We’re pleased to announce the launch of TEXTBOOK in the WordPress.org directory. Created by Allan Cole , TextBook helps schools, colleges, and other non-profit organizations to distribute and archive information in an easy way. Supported by Jetpack , it includes a Featured Content area for highlighting key posts or pages, a social menu, and Testimonials, ideal for showcasing quotes from alumni, staff, and students. When designing TextBook, Allan researched some of the challenges facing schools when creating their sites, and noticed that many educational sites had little access to good photography. TextBook minimizes that problem: > One of the main goals for TextBook is how it’s designed to look > great when you only have a limited amount of content. Even if images > are smaller, or low quality, it doesn’t take away from the design. Check out the TextBook demo, peek at the setup guide, or download and take it for a spin. by Kathryn P. Posted on November 21, 2017
Categories
Theme Launches Tags
TextBook
POSTS NAVIGATION
Page 1 Page 2 … Page 32 Next page
Search for: Search
ABOUT THIS SITE
This is ThemeShaper, a WordPress-powered blog and home to the Automattic Theme Division. We shape beautiful and customizable themes that make the world a better place. RECENT COMMENTS
Tran Ngoc Tuan Anh on Exploring Global Styles Jeff Ong on Creating a Block-based Theme U… Miguel Fonseca on Creating a Block-based Theme U… Mel Choyce on Creating a Block-based Theme U… Kjell Reigstad on Customizing Gutenberg blocks w…
FOLLOW BLOG VIA EMAIL Enter your email address to follow this blog and receive notifications of new posts by email. Join 4,473 other followers Follow
TOPICS
* Asides
* Community
* CSS Tips
* Design
* Education
* Ideas
* Site News
* Thematic Child Themes * Theme Development
* Theme Launches
* Theme Team
* Theme Testing
* Theme Tips
* Themes
* Tools
* Uncategorized
* About
* Contact
* Twitter
Theme: Twenty Sixteen. ThemeShaper Blog at WordPress.com. Automattic Post to
Cancel
* Follow
*
* ThemeShaper
* Customize
* Follow
* Sign up
* Log in
* Report this content * Manage subscriptions * Collapse this bar
Details
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0