WordCamp Europe 2023 in Athens attracted more than 2,500 attendees from 94 countries, made possible by 112 organizers and 250 volunteers. The event is now looking forward to 2024, which will be hosted by the Italian WordPress community in Torino, Italy, June 13-15. This modern city is located at the foot of the Alps in northwestern Italy and has more than 2,000 years of history to explore.
WCEU 2024 is calling for organizers who will serve on one of a dozen teams that have been operating for the past few years, including attendee services, budget, design, sales and sponsors, communications, and more.
Those selected to organize will begin planning WCEU in September 2023 and will work with a distributed team on a weekly basis until June 2024.
WCEU 2023 organizers published a transparent account of the various selection processes used for organizers, speakers, media partners, and others involved in the event. The article states that organizers are shortlisted based on their skills, with an effort “to keep gender parity high whilst also selecting people from all available European WordPress communities.” It also states that applicants’ experience and enthusiasm are chief among selection factors but organizers also reach out to encourage underrepresented groups to apply:
During the selection process we don’t have anything that resembles a “positive discrimination†policy, whereby we choose people based on their race, color, background, gender, sexual identity, or any other attribute; we solely chose people based on their stated experience and enthusiasm to be part of the team…
Acknowledging that diversity within the Organizing team is important, we reach out to community groups and members before and during the application process, encouraging people to apply where we have historically seen underrepresentation.
The article concludes with a statement of willingness to modify this selection process if the organization is not able to achieve a diverse lineup:
WordCamp Europe is an iterative event; each year learns from the last and 2024 will be no different. We cannot take for granted that achieving diversity one year guarantees it the next. As a flagship WordCamp event we may need to positively discriminate to achieve gender parity, or fair representation of communities.Â
The call for 2024 organizers does not identify any changes that have been made to the selection process. Prospective organizers will need to fill out the application form highlighting their skills, experience, and desired role.
There has always been some confusion and overlap between reusable blocks and patterns. The difference was that reusable blocks can be created and edited in the block editor and then reused in other places – inserted into posts or pages. Block patterns, once inserted, can be edited and are not synced. They give users the ability to apply the same layout to different posts and pages.
Reusable blocks have now been renamed to patterns, with the option to be synced, which offers the same functionality as the former reusable blocks where all instances can be updated at once. Non-synced patterns are just regular patterns – those that can be edited independently of other other instances that have been inserted. These updates are coming in Gutenberg 16.1 and will be included in the upcoming WordPress 6.3 release.
WordPress contributor Aki Hamano posted a diagram to Twitter regarding the renaming, which was confirmed as an accurate representation of the changes.
I am trying to understand about the new naming of "Pattern" in WordPress. I currently understand it as this figure represents, is this correct? pic.twitter.com/WxKFRotB0V
— Aki Hamano / 浜野 哲明 (@tetsuaki_hamano) June 25, 2023
“Clients already find the pattern and reusable block concept very difficult to grasp,” WordPress developer Mark Howells-Mead commented on the pull request for the renaming. “This change will make things much harder for regular users to comprehend.”
Gutenberg contributor Paal Joachim Romdahl commented that it would be helpful to have more time to test this in a few versions of the Gutenberg plugin, as WordPress 6.3 beta 1 is expected this week. Learning materials and documentation will need to be updated with very little notice.
Gutenberg contributor Daniel Richards encouraged contributors to see the change as part of “the great unification,” an effort towards consolidating the many different block types into a single concept and streamlining the content and site editors.
“In the future it might also be possible for template parts to be considered ‘synced patterns’, and at that point things become much more streamlined and there are far fewer concepts for users to grasp,” Gutenberg contributor Daniel Richards said.
“So the hope is that this is a first step on the path to making things easier for users, rather than more difficult. But I do realize that for existing users it’s quite a shift.”
As part of this effort, WordPress 6.3 will also introduce pattern creation in the block editor using the same interface that it previously used for reusable blocks. Pattern creation necessitates having a place for users to view and manage their patterns. WordPress 6.3 will also include a first pass at a Pattern Library inside the Site Editor, which will include both patterns and template parts. Gutenberg designers shared a preview of what this would look like a couple weeks ago:
In May, contributors began a discussion about the concept of partially synced patterns, which Daniel Richards summarized:
Today, when you insert a pattern, the blocks from that pattern are completely decoupled and standalone. There’s no way to tell that those blocks originated from a pattern, especially since they can be edited to no longer resemble the source pattern.
Partially synced mode is different. When a pattern that’s partially synced is inserted, it retains a reference to the source pattern. The blocks within the pattern are locked so that they cannot be removed or reordered and new blocks cannot be inserted (this is called contentOnly locking). Only specific parts of the pattern considered ‘content’ can be edited (denoted by adding __experimentalRole: 'content' to a block’s definition).
When the source pattern is updated, all instances of blocks that reference the source pattern are updated too (much like a reusable block), but the content values the user entered are retained. The best way to think of this is that the user can update the design of a pattern, but doesn’t lose content that exists in templates and posts.
This concept will not make it into the upcoming version of WordPress, as contributors are still discussing one of many complex implementations, but it offers a glimpse of what might be more granular control coming to patterns in the future. Partially synced patterns would bring distinct benefits to many CMS and content design use cases where clients may be editing content.
“I am a site developer for an agency, and am actively making sites for clients using Gutenberg every day,” Eric Michel said. “Probably our biggest pain point right now is that the editor does not handle types of content that are mostly standardized with small content customizations per post – things like contact directories, majors at a university, products in a catalog.
“For us, the absolute dream scenario is what you are proposing, except with the inclusion of the ability to alter the primary template and have all of the pages that use that template automatically change as well.”
The discussion on making partially synced patterns possible continues in search of an implementation that will ensure users don’t modify the patterns in ways that destroy the ability to display the retained content. WordPress 6.3 will ship with synced and non-synced pattern options, and partially synced patterns may land further down the road in a future release.
Really Simple SSL, a popular plugin used on more than five million sites for installing SSL certificates, handling website migrations, mixed content, redirects, and security headers, has added a new feature in its most recent major update.
Version 7.0.0 introduces vulnerability detection as part of a partnership with WP Vulnerability, an open source, free API created by Javier Casares with contributions from other open source, freely available databases. Once enabled, it notifies users if a vulnerability is found and suggests actions.
“Really Simple SSL mirrors the free database with its own instance to secure stability and deliverability, but of course provides the origin database with an API to enrich, or improve its current data,” Really Simple Plugins developer Aert Hulsebos said.
The new vulnerability detection feature is not enabled by default, so users will need to enable it in the settings. A modal will pop up where users can configure their notifications and run the first scan.
When emailed about a vulnerability users can manually respond with an action or set the plugin to automatically force an update (when available) after 24 hours of no response. There are other automated actions the plugin can take based on how users configure the Measures section of the settings.
For the past several years Really Simple SSL has been providing SSL certificate configuration and installation via Let’s Encrypt as a first pass at securing WordPress sites. To finance this for the free users, the plugin also has a Pro version that handles Security Headers, such as Content Security Policies, which are highly complex for most and not easily configured.
“We figured that with our reach we could impact security on the web as a whole, by adding features in order of impact on security,” Hulsebos said. “So vulnerabilities, after hardening features specific to WordPress, was next.Â
“The nature of our partnership with Javier and WP Vulnerability is sponsoring the efforts of WP Vulnerability and appointing a security consultant ourselves to this open-source effort to improve, and moderate the open-source database daily. WP Vulnerability does not compensate us, nor does it have a stake in Really Simple SSL. Vulnerability detection is available for everyone and always will be.”
Because Really Simple SSL started as a lightweight SSL plugin, Hulsebos said they have taken a modular approach to minimize impact on users who only want or need certain features. Following the launch of the new vulnerability detection feature, the plugin’s authors plan to add login security with 2FA to better secure authentication on WordPress sites.
If you haven’t visited the WordPress Pattern Directory lately, it may look very different from when it launched two years ago. At first there was an emphasis on getting the community to contribute to the resource but the directory has now passed more than 1,500 patterns.
Contributors are making changes to provide a more curated experience ahead of the inclusion of a new Pattern Directory Explorer that is still in progress. A recent update to the Pattern Directory alters the homepage and category pages to show curated patterns by default, a change that has been a bit confusing for some when returning to the directory.
— Jamie Pootlepress – YouTuber and WP Plugin builder (@pootlepress) June 22, 2023
The curated patterns are those by WordPress.org – the core bundled patterns. Community-contributed patterns are available as a filter in the dropdown of the directory’s menu.
There are only 46 core patterns, so some category pages tend to look a little sparse and far less colorful than when community patterns are selected. At the moment, having curated patterns display by default does not offer the best experience for users coming to browse, as Pootlepress founder Jamie Marsland pointed out on Twitter. Automattic-sponsored contributor Rich Tabor responded that there is still more work to be done on providing a better curated experience in the Pattern Directory.
The top ones are the best. Still lots to do though.
“This change also prepares to support the Pattern Explorer in the editor,” Automattic-sponsored contributor Kelly Choyce-Dwan said in the announcement. “It’s still in progress, but it will be possible to search through community-submitted patterns directly from the editor.”
Choyce-Dwan referenced an effort that is currently underway to bring a new flyout to the patterns tab of the inserter inside WordPress, making the modal a place where users can more easily explore and access patterns from the directory.
There are also related discussions on how themes could create pattern bundles, enabling the possibility of users filtering by theme. In this discussion, Automattic-sponsored contributor Anne McCarthy suggested these pattern bundles could be automatically submitted to the directory upon the theme’s approval, which would make it effortless for theme authors to contribute them.
Updates to the Pattern Directory’s filtering are part of the redesign work on WordPress.org and more discussions are happening on the Pattern Directory GitHub repository.
WordPress.com has been known to experiment with its pricing from time to time, and the platform announced another major change today. Users on the Free plan are now able to use monetization features without upgrading.
In the past, WordPress.com users who wanted to earn money on their websites by collecting donations, creating a newsletter, or selling items or subscriptions, had to be on one of the paid plans. These monetization features are now available to all users on all tiers.
The fee structure varies, based on the user’s plan. Transaction fees are the highest for Free users at 10%, but it gives creators the opportunity to see if they can make money without it costing anything upfront. Commerce plan users ($70/month or $45/month billed annually) don’t pay any transaction fees. Stripe also collects 2.9% + US$0.30 for each payment made to a Stripe account in the US.
WordPress.com Plan
Payment Fees
WordPress.com Commerce
0%
WordPress.com Business
2%
WordPress.com Premium
4%
WordPress.com Personal
8%
WordPress.com Free
10%
Self-hosted WordPress users already have many free plugin options to monetize theirs sites but with that comes the requirement of knowing how to maintain and update their own sites. WordPress.com’s offering is targeted at creators who just want to get started making money online. The company is inching closer to being a one-stop shop for websites, especially as it makes a play for former Google Domains customers who are looking for somewhere to host domains after theirs were sold to Squarespace.
It’s important to note that creating a full-featured online store is still restricted to Business and Commerce plans. Using Pay with PayPal to accept credit and debit card payments via PayPal is also only available via an upgraded plan.
WordPress.com’s pricing page has not yet been updated to reflect monetization features as being free – i.e. the Personal plan still lists paid subscribers and premium content gating as an upgrade. It’s possible the team hasn’t edited that page yet or this may be another pricing experiment.
Expanding the availability of monetization features is likely to be received as a positive change, since users are not losing any features that were previously free. Instead, they have the opportunity to see if they can monetize and then adjust their plans based on their comfort level with the transaction fees extracted.
Up until yesterday, the Gravatar (Globally Recognized Avatar) blog lay dormant for nine years, the last post chronicling how the team set out to create a Gravatar app that somehow “morphed into a Selfies app.” Communication went silent after that, although the Twitter account posted occasionally.
The service has pivoted to become “a personal digital business card” where users can link to various apps and websites that help to establish their identities online.
Gravatar announced this week that it has launched new payment features for profiles. Users have the option to add links for PayPal, Venmo, and Patreon. The Gravatar team is looking at adding Cash App and more providers in the future.
On mobile, profiles appear with new “Send Money” and “Share Profile” buttons. Each profile has its own unique QR code that can be copied and shared.
The payment accounts show up as links that visitors can click through. Users can also display links to cryptocurrency wallet addresses, including Bitcoin (BTC), Litecoin (LTC), Dogecoin (DOGE), Ethereum (ETH), XRP, and Cardano (ADA).
Profiles can be customized with a background image, photo gallery, social links, and links to verified services.
Gravatar is used by Slack, Atlassian (owner of Jira and Trello), GitHub, Stack Overflow, and Disqus, serving millions of requests per day. Another new major user is OpenAI, which displays users’ Gravatar images when chatting with ChatGPT. The service is also integrated with every WordPress install, and an Automattic representative confirmed there are no plans to change this.
Automattic reported that the company does not receive a cut of any payments passed through Gravatar links, nor does it have financial partnerships with any of the payment providers. The company also has no visibility into the transactions that happen through Gravatar payment links.
During the past nine years, the small Gravatar team has been improving how profile pages look, adding services that can be verified, working to improve the hashing and security of data, and maintaining the infrastructure required to store and serve so many images and profiles.
“We aren’t currently working on a Gravatar app, but it is something we are considering,” an Automattic representative told the Tavern.
After the Selfies app was retired, some of the code went into Jetpack and is now part of the app. Jetpack users can manage their Gravatar profile information and avatar photo inside the app.Â
Blocknotes is a new experimental app that runs WordPress natively on the iPhone. It was created by WordPress core committer Ella van Durpe and is powered by WordPress Playground, a project that runs the software in the browser without a PHP server.
“WordPress’ ecosystem can now run anywhere – desktop, mobile, web, even fenced ecosystems,” WordPress Playground creator Adam ZieliÅ„ski said, sharing a screenshot on Twitter.
Meet Blocknotes, the first native iPhone app running WordPress on the device.@ellatrx built it with Playground. It saves notes to HTML and synchronizes them over iCloud.
WordPress ecosystem can now run anywhere – desktop, mobile, web, even fenced ecosystems. Exciting! pic.twitter.com/ko20RGP4hT
“Blocknotes allow you to create notes with Gutenberg, save them as HTML files to iCloud, and synchronize them across your devices. This paves the way for future WordPress-based mobile apps and that’s just a start.”
Zieliński eplained that this particular experimental app is technically a WebView that runs a HTML page where the WebAssembly version of PHP runs – the same one as on playground.wordpress.net.
“Browsers and other JavaScript runtimes all adopted a common standard that is WebAssembly,” he said. “Turns out you can build many ‘regular’ programs, including PHP, to that standard and then you can run them in the browser.”
The significance of this app running natively on iOS is that it demonstrates the possibilities of running WordPress in many new contexts without the requirement of a server. Zieliński believes this implementation can even be turned into an app template to build a WordPress app with the click of a button.
“Playground, as a WebAssembly software, brings WordPress to Node.js, mobile devices, desktop apps, ecosystems like VS Code that support JavaScript extensions,” ZieliÅ„ski said. “The mobile app, desktop app, and a hosted web app could all use the same code and also provide a Playground-based demo version.”
ZieliÅ„ski said he expects to see people building mobile apps in the future “with nothing more than a WordPress plugin.” This would drastically reduce the learning curve for creating and customizing mobile apps.
“Or even better, with no code at all – they’d just use the admin interface to configure a WordPress site to look and act like an app,” he said.
“Changing the app look and feel could be the same as switching a theme in WordPress.”
Zieliński has a virtually inexhaustible spring of ideas for how the WordPress Playground can benefit the ecosystem and his passion for the project is evident in a recent interview on The Code and Coffee Show.
The Blocknotes app offers a solid example of WordPress Playground working in the real world. It’s a use case that seems to have resonated strongly with developers as a new way to run WordPress across platforms.
Blocknotes is available for beta testing! Even though I already use it for my notes, be careful! Normally, if the app freezes, your notes should be safe in iCloud Drive.
WordPress Playground is being developed to become “the official WordPress previewer,” according to the roadmap – the officially supported tool for testing WordPress plugins, new features, beta/RC releases, without expensive infrastructure. Demos and testing sites can be launched instantly by clicking a link. The project also promises to provide an interactive learning experience for WordPress documentation to help new developers.
Opening new doors for WordPress is also on the project’s roadmap, for the creation of tools that run across multiple devices. WordPress Playground removes limitations developers have lived with for years.
“Let’s enable a new generation of WordPress tools running on desktops, mobile devices, in CLI, and inside web browsers,” ZieliÅ„ski said. “Imagine WordPress as a cross-device note-taking app, or WooCommerce as a ticket-scanning app running on a phone, or a code editor running on a tablet where you can build WordPress extensions.
“WordPress won over 40% of the web as an app that can only run on a server. What will happen now that WordPress can run on almost any device?”
A lively discussion is happening on the Gutenberg repository about renaming the Command Center. This new feature, designed to be an extensible quick search and command execution tool, was introduced in Gutenberg 15.6. In version 16.0, it came out of the experimental stage and its API is now public, ready for developers to create their own custom commands.
The Command Center is on track to land in the upcoming WordPress 6.3 release but may be arriving under a different name. Automattic-sponsored contributor Reyes MartÃnez opened the discussion and identified three main purposes the feature is meant to serve:
Quickly search, navigate, and switch between different types of content
Run commands to perform tasks or actions
Extend and customize the tool, also with AI, via third parties (plugins)
“The concept of a command center can convey the idea of a centralized location to execute commands and manage tasks, but it seems a bit technical and carries some militant connotations,” MartÃnez said. “Additionally, after reading some feedback left in Riad’s call for feedback, my impression (from a marketing perspective) is that this name may not fully convey its potential and different use cases.”
MartÃnez contends that “Wayfinder” as a name “better captures its different use cases” and “reflects benefits, and appeals to a less technical audience.” She also suggested that it “has the potential to evoke a sense of curiosity, exploration, and discovery in more types of users.”
Two Automattic-sponsored contributors responded with support for Wayfinder as the name shortly after the discussion was posted. Nearly every other participant has highlighted concerns about using Wayfinder and suggested other names that more clearly describe the feature. The term does not have a direct translation in many languages and leans heavily towards navigation, leaving out the other purposes the feature is meant to serve, such as running commands and actions, as well as AI and other third-party integrations.
I'm not sure I could articulate why I feel so strong about the naming of the command bar coming to the #WordPress Site Editor (and eventually the whole Dashboard ) in a tweet, but wow I have strong feelings. https://t.co/yP4dx1LEDl
“There’s two things here. One is ‘What is it?’ and the other is ‘What is it called?’” WP Engine developer Ross Wintle said.
“I would rather it was just called a command palette on both counts. This is by far the most common term in use to describe this kind of thing. I see no need to stray from popular convention. Anything else is either confusing or marketing and I don’t like either.”
He suggests WordPress adopt the term based on its well-documented use throughout the industry for similar features in apps like Sublime Text, VS Code, GitHub, Jira, and others.
“We did hear MatÃas call it a “Wayfinder tool” in the WordCamp Europe 2023 Keynote, so at this point perhaps making arguments for it to be called something else may be moot, I’m not sure,” WordPress developer Aurooba Ahmed said.
“However, I was curious about the argument that a term using the word command would be less appealing to non-developers, so I wanted to document names around the internet for command palettes that I’ve seen in non-developer tools/services (to augment @rosswintle‘s documenting of tools and what they call this feature as well).
Ahmed cited apps using “Command Palette,” including Miro, Reflect, and Obsidian. Another common name for this feature is “Command Menu,” used by Todoist and Cron. She also cited ClickUp as using “Command Center” and Missive using “Command Bar,” among other apps with similar terms.
“I’m sure there’s more, these are just the ones I could think of, off the top of my head,” she said. “I’m not sure I consider the argument that a name with the term Command would be less appealing to non-developers a very strong one.
“That’s not to say that WordPress shouldn’t choose a different or unique name for this feature. However, then at this point I’m wondering what kind of name is wanted: one that feels new and different or one that clearly communicates its purpose and easy to remember?
“Those ideas don’t have to be mutually exclusive, but going against a fairly internet-wide informally established naming convention and understanding of a certain feature should have a solid reason behind it.”
Automattic-sponsored contributor Nicholas Garofalo noted that the name itself will not be prominently featured in the interface, based on recent mockups.
“The name, like Gutenberg, will be used primarily for marketing and documentation,” Garofolo said. “That influences naming and translation concerns.”
“Even differences in US vs UK English make it extremely difficult to find a catchy (Ie. marketable) and universally understood (Ie. easily documented) name. That’s why I agree with the aforementioned recommendation that we treat this a bit like ‘Gutenberg’ or ‘plugin.’ If this were appearing frequently within the interface then I would perhaps feel different.”
Other suggestions from speakers of different languages include Actions hub, Finder, Quick commands, Quick actions, and Quick finder. Even if Gutenberg contributors are determined to emphasize the navigation aspect of the feature at the expense of its other capabilities, a term like Quick finder is more easily understood for the 52% of WordPress users who use the software in a language other than English.
“The term ‘Wayfinder’ is very much associated with navigation and not with taking actions or giving commands,” WordPress developer Ian Svoboda said. “This feature’s purpose is to make it easier to run commands and move about the dashboard.
“A term like Wayfinder feels like marketing speak more than an actual feature name. Consider the difference between saying: ‘use the Wayfinder’ and ‘use the command palette.’ In the later example, the meaning and purpose is immediately clear. So sure someone else may not know what a ‘command palette’ is but I’d wager way more folks know what a command palette is than a random feature in me specific app called Wayfinder.
“I would ask that we focus on being easy to understand and to translate above trying to be clever with a name.”
The issue for renaming the Command Center is still open on the Gutenberg repository and discussion is ongoing. The general consensus of participants is to use clear language over a term that evokes curiosity (and likely confusion since it doesn’t translate well). A decision has not yet been made but should be forthcoming as WordPress 6.3 Beta 1 is expected on June 27, ahead of the general release on August 8.
In May 2023, WordPress’ Community Team announced that it would be evolving the WordCamp format to promote adoption, training, and networking for professionals, leaving the flagship events to focus more on connection and inspiration. This major shift opens the door for more experimentation through varied formats. In a recent update, the team shared that progress on the discussions has generated 64 ideas with 59 organizers who are willing to follow up on their ideas.
There are also eight pilot events that have been confirmed and six of them will launch in 2023. These include some of the most creative concepts that WordPress has ever officially entertained, as the previous WordCamp format had become predictable and requirements somewhat inflexible. These pilot events offer a glimpse of what events could look like going forward.
The WordPress community in Leipzig, Germany, is planning the first ever Low-Cost WordCamp for July 1, 2023. Organizers will host 90 attendees and keep costs low with no swag, no social dinner, and no after party. They will offer just one track of presentations.
“The goal is to motivate and help new and veteran organizers to create a lighter, impactful event that is low cost and requires less time, financial resources, and fewer organizers/volunteers,” Automattic-sponsored Community Team contributor Isotta Peira said.
Contributors in Sevilla, Spain, are planning a “WordPress Day” on July 2, 2023, where the focus will be engaging 50 attendees in three different areas of contribution.
“The goal is to bring new contributors to the community and retain them by organizing multiple events every year,” Peira said. With these small numbers and limited goals, this effort could easily be organized as frequently as they anticipate.
The community in Tegal, Indonesia is planning a “Scale Up” Workshop for October 22, 2023. A group of 50 participants will join in a 1-day training event that will expand their WordPress skills by “diving into the world of WordPress for enterprise.”
The three other approved pilot events for 2023 include a Rural event for small towns/villages, a WP for Publishers in Bangalore, and a Community Day in Rome, Italy, designed for WordPress community organizers, scheduled for September 29.
All of the confirmed events fall within the new purpose for WordPress events that the Community Team identified earlier this year:
WordPress events spark innovation and adoption by way of accessible training and networking for users, builders, designers, and extenders. We celebrate community by accelerating 21st-century skills, professional opportunities, and partnerships for WordPressers of today and tomorrow.
Prospective event organizers who are inspired by the confirmed pilot events can submit their creative ideas via a dedicated form. The Community Team is still accepting pilot events for 2023 and is also scheduling into 2024.
The module was one of five projects, selected from 35 proposals, that was granted funding during the DrupalCon Pitchburgh innovation contest. The winners were announced as part of Dries Buytaert’s State of Drupal presentation at DrupalCon North America 2023 in Pittsburgh.
“Since Automattic is the main developer behind Gutenberg, I shared the Gutenberg proposal with Matt Mullenweg, co-founder of WordPress and CEO of Automattic,” Buytaert said. “Matt was really excited about the idea of more Drupal sites using Gutenberg, and he kindly offered to provide the full €20,000 in funding through Automattic. Furthermore, he will be sending some Gutenberg experts to join the sprint without any cost to the Drupal community.”Â
The Drupal Gutenberg module is used on more than 3,000 Drupal websites. Frontkom, a 120-person agency, uses it exclusively when building Drupal sites for clients.
“Our clients love it,” Frontkom sales director Thor Andre Gretland said. “In fact, we haven’t built a Drupal site without Gutenberg since we started the project back in 2018.”
In his pitch video (embedded below), Gretland said the requested funding will be used to take the project to the next level by arranging an in-person workshop for a few days. They intend to gather people from the WordPress core team who have built the editor, the Drupal core team that knows the needs and possibilities for the admin initiatives, and the Drupal Gutenberg team that built and maintains the module.
Gretland listed several things he hopes the teams can create together, including a Gutenberg starter theme and a starter pack, where Gutenberg is setup with a complete frontend as a base theme or theming reference, as well as the ability to make it work work within the layout builder.
“Our goal is to make sure that the Drupal Gutenberg of the future is always using the latest and greatest version from the WordPress team, and better enable Drupal developers to contribute back upstream,” Gretland said. “We want Gutenberg more tightly integrated with Drupal and to do this properly we need to gather the people that should be involved. This is a great opportunity to extend our cooperation across open source projects and to move forward making Drupal the most easy to use enterprise CMS.”
Even though I already use it for my notes, be careful! Normally, if the app freezes, your notes should be safe in iCloud Drive.
) in a tweet, but wow I have strong feelings. 