Mark Root-Wiley's guest appearances

Mark Root-Wiley

WP Tavern

WP for Nonprofits

Jukebox

OwlTail

On the podcast today we have Mark Root-Wiley. He’s on the show to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Mark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching. He’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It’s very much the kernel of an idea at present, but thought provoking nonetheless.

#28 – Mark Root-Wiley on Creating Standards for CSS in WordPress

On the podcast today we have Mark Root-Wiley. Mark builds WordPress websites for nonprofits in Seattle, Washington, USA with a focus on accessibility and usability. He's a long-time WordPress community member in Seattle and has previously helped organise WordPress Seattle meetups and WordCamp Seattle speakers. He maintains Nonprofit WP, a free guide for people building WordPress websites for their nonprofits, and has a few free plugins available on WordPress.org. He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Over the years, as WordPress has evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You could do what you like, and that worked very well, after all, we all have preferred ways of doing things. Now however, the reach of WordPress has outgrown those early roots and some 40+ percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites as they try to unpick the way that the CSS is built and implemented. Mark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching. He’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It’s very much the kernel of an idea at present, but thought provoking nonetheless.Useful links.Standardized Design Tokens and CSS for a consistent, customizable, and interoperable WordPress future Standardized block markup, theme.json design tokens, and CSS classes to improve interoperability Variable Design Token Scales with Static CSS Classes (Proof of Concept) Core Styles and Theme Customization: the next steps Explore options to add back semantic classnames to block wrappers Add a Style Engine to manage rendering block styles

On the podcast today we have Mark Root-Wiley. Mark builds<a href="https://mrwweb.com" rel="nofollow" target="_blank"> WordPress websites for nonprofits</a> in Seattle, Washington, USA with a focus on accessibility and usability. He's a long-time<a href="https://wpseattle.org" rel="nofollow" target="_blank"> WordPress community member in Seattle</a> and has previously helped organise WordPress Seattle meetups and WordCamp Seattle speakers. He maintains<a href="https://nonprofitwp.org" rel="nofollow" target="_blank"> Nonprofit WP</a>, a free guide for people building WordPress websites for their nonprofits, and has a few<a href="https://profiles.wordpress.org/mrwweb/#content-plugins" rel="nofollow" target="_blank"> free plugins available on WordPress.org</a>. He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Over the years, as WordPress has evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You could do what you like, and that worked very well, after all, we all have preferred ways of doing things. Now however, the reach of WordPress has outgrown those early roots and some 40+ percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites as they try to unpick the way that the CSS is built and implemented. Mark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching. He’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It’s very much the kernel of an idea at present, but thought provoking nonetheless.Useful links. <a href="https://mrwweb.com/standardized-design-tokens-css-wordpress-future/" rel="nofollow" target="_blank">Standardized Design Tokens and CSS for a consistent, customizable, and interoperable WordPress future</a> <a href="https://github.com/WordPress/gutenberg/issues/38998" rel="nofollow" target="_blank">Standardized block markup, theme.json design tokens, and CSS classes to improve interoperability</a> <a href="https://codepen.io/mrwweb/pen/bGYQKae" rel="nofollow" target="_blank">Variable Design Token Scales with Static CSS Classes (Proof of Concept)</a> <a href="https://make.wordpress.org/core/2022/04/13/core-styles-and-theme-customization-the-next-steps/" rel="nofollow" target="_blank">Core Styles and Theme Customization: the next steps</a> <a href="https://github.com/WordPress/gutenberg/issues/38719#issuecomment-1087145463" rel="nofollow" target="_blank">Explore options to add back semantic classnames to block wrappers</a> <a href="https://github.com/WordPress/gutenberg/issues/38167" rel="nofollow" target="_blank">Add a Style Engine to manage rendering block styles</a>