Carolina Nymark 3:04 am on November 11, 2020
Tags: ,   

Meeting notes Tuesday November 10 2020

Our agenda for this meeting can be found here https://make.wordpress.org/themes/2020/11/08/themes-team-meeting-agenda-for-november-10/

Weekly updates:

  • 266 tickets were opened
  • 275 tickets were closed:
  • 260 tickets were made live.
  • 18 new Themes were made live.
  • 242 Theme updates were made live.
  • 6 more were approved but are waiting to be made live.
  • 15 tickets were not-approved.
  • 0 tickets were closed-newer-version-uploaded.

A new requirement for links in content

The team decided to add a new accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) requirement that will affect all themes, not only themes that use the accessibility-ready tag. The full requirement can be read here: https://make.wordpress.org/themes/handbook/review/accessibility/required/#content-link

Links within content must be underlined.
When links appear within a larger body of 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.-level content, they must be clearly distinguishable from surrounding content.

Removing the requirement of specific CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. classes

Theme authors are encouraged to support the following WordPress CSS classes but are no longer required to do so. The themes team will not be checking for these classes during review.

.sticky
.bypostauthor
.alignleft
.alignright
.aligncenter
.wp-caption
.wp-caption-text
.gallery-caption

Please allow some time for the team to update the plugins to reflect this change.

Organizing documentation and Tutorials for Full Site Editing themes

During the meeting we discussed where to publish documentation and tutorials for Full Site Editing themes / block-based themes.

These can first be published on the Themes Team’s blog and be moved to the Theme Developer Handbook once Full Site Editing is no longer experimental. We expect further discussions to take places when there is more material.

The next Themes team meeting is Tuesday November 24 at 15:00 UTC.

#meeting-notes, #themes-team

Carolina Nymark 10:08 am on November 8, 2020
Tags: , ,   

Themes Team Meeting Agenda for November 10

The themes team conducts a meeting on the second and fourth Tuesday of the month.

Along with the fixed agendas, we have an open floor at the end where you can ask or share anything related to themes.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, November 10th 2020, 15:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Updating accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) requirements for links
  3. Removing the requirement of specific CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. classes
  4. Organizing documentation and tutorials for Full Site Editing themes
  5. Open floor

Weekly Updates

Current statistics can be found on: https://themes.trac.wordpress.org/ 

Themes TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket graph: https://themes.trac.wordpress.org/ticketgraph

Updating accessibility requirements for links

When the team started applying accessibility requirements on all themes in 2019, the intention was to introduce new requirements every few months. This was not followed up for a couple of reasons, but it has always been the intention to continue to improve the accessibility of the themes.

We would like to propose that the following requirement is applied to all themes in the directory:

Links within content must be underlined.
When links appear within a larger body of 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.-level content, they must be clearly distinguishable from surrounding content.

Links in navigation-like contexts (e.g. menus, lists of upcoming posts in widgets, grouped post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data) do not need to be specifically distinguished from surrounding content.

The underline is the only accepted method of indicating links within content. Bold, italicized, or color-differentiated text is ambiguous and will not pass.

https://make.wordpress.org/themes/handbook/review/accessibility/required/#content-links

Removing the requirement of specific CSS classes

This proposal is about removing the requirement for the following CSS classes:

.sticky
.bypostauthor
.alignleft
.alignright
.aligncenter
.wp-caption
.wp-caption-text
.gallery-caption

It is up to the theme author if they want to support legacy content, how they choose to implement post- and block alignments, and how they choose to implement sticky posts within the current requirements.

Organizing documentation and Tutorials for Full Site Editing themes

During last weeks block based theme meeting, there was a discussion about writing tutorials for full site editing themes.

Writing tutorials that will be kept up to date is going to be challenging, but that aside, this documentation needs to be placed somewhere.

Do we want to create a separate handbook for Full Site Editing themes? Or is it better to include it in the existing Theme Developer Handbook, or in the Block editors tutorial section?

Please comment in the comment box below if you have anything to bring up during the open floor.

#agenda, #meeting, #themes-team

Kjell Reigstad 4:18 pm on November 6, 2020
Tags:   

Gutenberg + Themes: Week of Nov 2, 2020

Hello! This is the 26th 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:

  • Polish search 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.. 26446
  • Wrap code block by default. 26623
  • Discussion: Allow themes to dynamically add CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. class names to the editor wrapper. 26494
  • Discussion: Try a wider vanilla / default column width. 26357
  • Bug: Background Colors assigned as ‘preset’ colors do not render correctly in the editor while in dark mode. 26506
  • Bug: Preset size dropdown includes empty li when only custom font sizes are enabled 26489
  • Bug: Toolbar buttons can inherit the editors text color when active. 26462
  • FSEFSE Short for Full Site Editing, a project for the Gutenberg plugin and the editor where a full page layout is created using only blocks.: Load content in an iFrameiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. 25775
  • FSE Discussion: Handling of templates and template parts duplicates. 26546
  • FSE Discussion: Provide a way for Gutenberg to provide alignment styles for the front end. 26633
  • FSE Bug: All blocks show up as full width, don’t match the post editor. 26630
  • Suggestion: Box-layout attribute. 26407

Merged:

  • FSE: Add wide and full alignment options to the post/site title blocks. 26601
  • FSE: Automatically enable FSE for block-based themes. 26500
  • FSE: Support other units in font size presets. 26475
  • Improvement to large font size display in the font size dropdown. 26705 
  • Use currentColor for the Quote block’s accents. 26684

Overview Issues:

  • Full Site Editing Milestones. 24551
  • Template Tags in Full Site Editing. 22724 
  • Tracking and consolidating style attributes for blocks. 22700 
  • Missing query block functionality. 24934
  • Query and LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. block tracking: 24762

General Resources:

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

#gutenberg-themes-roundup

Jeff Ong 5:26 pm on November 4, 2020
Tags:   

Block-based Meeting Notes — Nov 4 2020

Channel: #themereview

Facilitated by @kjellr

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/ + Themes Highlights

  • Gutenberg 9.3 launched: https://make.wordpress.org/core/2020/11/04/whats-new-in-gutenberg-4-november/
  • It’s no longer necessary to check the “Full-site editing experiment” to use a block theme: https://github.com/WordPress/gutenberg/pull/26500
  • How to treat dynamic content in block templates discussion: https://github.com/WordPress/gutenberg/pull/25316

Twenty Twenty-One (TT1) Blocks

Development for TT1 Blocks has started here: https://github.com/WordPress/theme-experiments/tree/master/twentytwentyone-blocks

We discussed the following question posed by @poena:

Where do we draw the line on where something is moved upstream [to Gutenberg], and when something is adjusted in the theme?

Full context here: https://make.wordpress.org/themes/2020/11/02/block-based-themes-meeting-agenda-november-4/#comment-44150

The full discussion starts here, and here are some takeaways:

  • There was consensus that we should lean on reporting issues in Gutenberg to support improvements to FSEFSE Short for Full Site Editing, a project for the Gutenberg plugin and the editor where a full page layout is created using only blocks., Global styles, and blocks — not adding one-off CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. and workarounds in the theme to achieve the desired functionality and design.
  • Attending the #core-editor meeting to flag issues and feature requests is a great way to get visibility and support.
  • More tutorials of how to build FSE themes would have a wide audience and be much appreciated!
    • Adding a handbook page to collect these tutorials was mentioned.

Contributing to TT1 blocks is a clear way to have impact on the future of WordPress, as it will be used as a baseline for Gutenberg development moving forward.

Please comment if you have any thoughts to add to this discussion, and contribute to TT1 blocks!

#meeting-notes

Kjell Reigstad 7:00 pm on November 2, 2020  

Block-based Themes Meeting Agenda: November 4

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

Time: Wednesday, November 4, 2020, 16:00 UTC
Channel: #themereview

Agenda

  • 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 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/
  • Check in & discussion about the Block-based Twenty Twenty-One Theme
  • Open Floor / Q&A

Please comment if you have any other topics you’d like to see discussed!

+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 #meeting