Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
WordPress 5.3 progress
@gziolo continued by saying it would be important to merge https://core.trac.wordpress.org/ticket/48154, which would simplify updating npm packages in WP core. But there is still this pending issue to address:
Where to put generated asset files to be consumed by PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher? At the moment they are generated in the folder, which in usual is exposed as client-side assets.
In case you have any ideas, please provide your insights on the ticket Created for both bug reports and feature development on the bug tracker..
CSS Cascading Style Sheets. support in wordpress/scripts
@gziolo introduced the subject by saying that it is something that we discussed some time ago in core-js chat. It’s tracked under https://github.com/WordPress/gutenberg/issues/14801, and it was primarily explored by @fabiankaegy in https://github.com/WordPress/gutenberg/pull/14847.
Participants started discussing the challenge of CSS support in wordpress/scripts.
@gziolo shared some context:
In Gutenberg 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/ we don’t import CSS in JS files. Instead, we have a separate build step that converts the SCSS files into CSS files which are published to npm. There is some additional step performed by webpack, but I guess it’s mostly about ensuring the LTR version is produced as well.
I do think we should have @wordpress/scripts as a utility that builds CSS as well. But getting to something that addresses the various needs of those consuming it is the difficulty here.
@nerrad concluded that we need to decide the defaults for the CSS build system with ways to override them via CLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. args.
@gziolo continued and said that ideally, we should be able to reuse as much as possible of what Gutenberg uses internally. This is the only way to ensure plugin 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/theme developers get all updates out of the box.
@gziolo continued the conversation and said that the mobile team is exploring how to build cross-platform UI User interface components.
This is the PR https://github.com/WordPress/gutenberg/pull/17614 which explores styled-system and styled-components.
@pinarol said we want to reach a point where we can build blocks with a cross-platform components library which enables us to implement a block 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. once and run it on both web/mobile.
@gziolo said that the approach used for multiplatform comments is directly related to work of making wordpress/scripts support CSS.
@gziolo announced that we are considering adding Storybook to help with the development of UI components.
It is possible to leave feedback on the PR’s that propose this addition https://github.com/WordPress/gutenberg/pull/17475 and https://github.com/WordPress/gutenberg/pull/17173. They are alternative versions for a similar goal.
@ajitbohra also implemented a similar solution outside of the Gutenberg repository and said he would love to consolidate efforts.
Custom element interoperability
@flixos90 proposed a PR that includes CustomElement interoperability for block types.
If you care about the support for web components in Gutenberg, give the PR https://github.com/WordPress/gutenberg/pull/17649 a spin and help to land it.
In case, you have any insights or suggestions please share them on the PR.