![]() ![]() To date, there are three default themes that support full-site editing: ![]() ![]() This is where experimental features are often given a dry run.Īnother way we can get a feel for where we are is by looking at the evolution of default WordPress themes. One way we can get an idea of what’s coming in future releases is by using the Gutenberg plugin. The new developmental features that are included in WordPress 6.1 get us closer to a system of styles that are completely defined in theme.json, but there is still be plenty of work to do before we can fully lean on it. There’s a lack of documentation for styling block themes in the WordPress Theme Developer Handbook, so everything we’re covering here is what I’ve gathered about where things currently are as well as discussions about the future of WordPress theming. So, what does styling actually look like in these WordPress FSE days? That’s what I want to cover in this article. That said, the fact is that theme.json is still in active development, meaning we’re in a transitional period where you might find styles defined there, in styles.css or even at the block level. In fact, style.css is still a required file in block themes, though its role is greatly reduced to meta information used for registering the theme. Wait, no style.css file? We still have that. I recently shared a technique for adding fluid type support in WordPress by way of theme.json, a new file that WordPress has been pushing hard to become a central source of truth for defining styles in WordPress themes that support full-site editing (FSE) features. The way we write CSS for WordPress themes is in the midst of sweeping changes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |