Kjell Reigstad 5:13 pm on August 18, 2020
Tags:   

Block-based Themes Meeting Agenda for August 19, 2020

Below is the agenda for this week’s Block-based Themes meeting.

Time: Wednesday, August 19th 2020, 16:00 UTC
Channel: #themereview

Agenda

  • Welcome
  • BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based theme related updates in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Discussion: Suggestions for improving this meeting
  • Sharing / Q&A / Open Floor

If you have any topics or demos you’d like to see in this or future meetings, please share below. We also need a volunteer to take notes!

+make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./ #agenda

Kjell Reigstad 3:37 pm on August 14, 2020
Tags:   

Gutenberg + Themes: Week of Aug 4, 2020

Hello! This is the 14th weekly roundup of theme-related discussions, fixes, and developments in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. 

Please weigh in on the tickets below — your voice and feedback are welcome! 

In progress / Discussions:

General:

  • Convert all front-end pixel values to rem. 24523
  • Consider the use of the prefers-color-scheme media query in Gutenberg + Themes. 24368
  • Remove --wp-admin-theme-color variable from front-facing styles. 24436
  • Avoid using Gutenberg’s $grid-unit variables in the front end. 24432

BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based Themes

  • Articulate requirements for porting existing themes. 24313
  • How to sync edits from theme to site editor. 22469
  • Improve template part visibility and enable browse mode. 24252

FSE Blocks

A set of blocks are available with the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to enable building templates in FSE.

  • Remove hardcoded colors from the Navigation block. 24462

Global Styles

  • Global styles affecting non-FSE themes. 24326
  • Tracking and consolidating style attributes for blocks. 22700 
  • Make theme.json cross-platform (web & mobile). 24165

Merged:

General

  • Remove editor-only styles from front-facing stylesheets. 24439
  • Remove hardcoded body text color from some block patterns. 24424
  • Remove hardcoded color in recent comments block. 24410
  • Remove hardcoded color from separator styles. 24366

Global Styles

  • Add support for more styles at the global level 24298

General Resources:

Thanks to @itsjusteileen, @jffng, and @joen for help pulling this post together. Please let us know if it was helpful in the comments!

#gutenberg-themes-roundup

williampatton 6:41 pm on August 11, 2020  

What should happen when a theme in the directory doesn’t follow the guidelines?

Sometimes a theme that is listed in the directory is updated in ways that don’t match expectations for themes outlined in the guidelines. The team has tried different ways to address issues like this.

Inconsistent results have come from warning theme authors that their theme could be suspended if they don’t resolve the issue. Suspending a theme immediately upon finding an issue is an effective way to motivate theme authors to fix problems, but it can be confusing for end users and stressful for theme authors and reviewers.

There’s been a lot of discussion (in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. and elsewhere) lately about the best way for this team to resolve these issues, moving forward. Collecting opinions and suggestions in one place, like this blog post, seems like a good way to ensure that good ideas aren’t lost in a backscroll. 

When sharing your ideas and feedback, please remember:

  • This team is staffed by volunteers.  
  • There is a lot of work to do, and not many people to do it. 
  • This discussion should follow WordPress.org etiquette. 

To help direct the discussion toward productive solutions, please consider answering the following questions in your comment:

  1. Are there teams in WordPress or in similar organizations whose policies / communication processes might be a good model for the Theme team? 
  2. What is the right balance between the needs of WordPress users and the needs of theme authors? 
  3. If you could change only one thing about this team’s policies / communication processes, what would it be? 

Thanks to @acosmin, @poena, and @andreamiddleton for their input with editing this post.

Jeff Ong 4:00 pm on August 7, 2020
Tags:   

Gutenberg + Themes: Week of Aug 4, 2020

Hello! This is the 13th weekly roundup of theme-related discussions, fixes, and developments in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. It was relatively quiet due to the focus on testing and improvements for 5.5.

Please weigh in on the tickets below — your voice and feedback are welcome! 

In progress / Discussions:

BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based Themes

  • Articulate requirements for porting existing themes. 24313
  • How to sync edits from theme to site editor. 22469
  • Improve template part visibility and enable browse mode. 24252

Global Styles

  • Global styles affecting non-FSE themes. 24326
  • Tracking and consolidating style attributes for blocks. 22700 
  • Add support for more styles at the global level 24298
  • Make `theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.` cross-platform (web & mobile). 24165

Merged:

FSE Blocks

  • Post title block: add style attributes 24246
  • Add color support to the post content block. 24014

General Resources:

Thanks to @itsjusteileen, @kjellr, and @joen for help pulling this post together. Please let us know if it was helpful in the comments!

#gutenberg-themes-roundup

Jeff Ong 3:50 pm on August 6, 2020
Tags:   

Block-based Themes Meeting Summary: Aug 5, 2020

This week we held our bi-weekly blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based themes meeting in the #themereview channel. The conversation starts here.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Theme-related Updates

“Keeping up with Gutenberg” was launched, a single place to follow Gutenberg related posts across the make blog universe. 

Discussion: porting existing themes to block-based themes

We had a discussion about easing the path for theme authors to make the switch to FSE, by allowing block templates to work with existing php templates. Specifically, the group discussed how template resolution could work, and the challenges that will arise around how the site editor will handle pages that use existing php templates.

The discussion arose from this GitHub issue, and continues there.

Open Floor

  • “it is difficult to get an overview of what we are working towards”
  • “Is FSE still targeted to being stable, in core, in 5.6? Or stable in Gutenberg at the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. of 5.6?”