And, make no mistake, the site editor and block-based themes fundamentally change how WordPress’s theme and customization system has worked for years. This has made for a far gentler transition, allowing early adopters to test the waters before the rest of the world. Users must explicitly activate a block theme to access them. However, the site editor and global styles have been entirely opt-in FSE features thus far. Developers and end-users have often needed to scramble for solutions without an appropriate transition period before switching the features on when ready. Some FSE features like block-based widgets and nav menus have also had problematic rollouts. Removing the beta label from the Site Editor could be just as problematic. I think a lot of that had to do with how things were presented and a bunch of PR issues. talked about the impact and experience of social proof not being on Gutenberg’s side early on in the project. Plus, the lack of a built-in method of staying on the classic editor without installing a plugin made for a rough transition.Īurooba Ahmed noted a similar risk with removing the beta label early:
#Bartender 4 accident delete software
It just felt very much like beta software that was switched on overnight - the platform’s users its guinea pigs. It was not that the block editor was in and of itself a poor product. The problem was more about communication than anything. The block editor was arguably the worst feature rollout in the platform’s history, one that has left a fractured community that is, over three years later, still picking up some of the pieces of itself. Dave Ryan added items that theme authors were still hard-coding because they are unsupported in the editor.Īvoiding the WordPress 5.0 Gutenberg debacle should be a priority. “Before removing the label, we need feedback about the expectations when there is no beta label,” she wrote.Īlex Stine noted accessibility issues as a blocker for removing the beta label.
“What would the community’s expectation be for supporting resources related to beta, and what capacity do teams have to reach that goal?” she asked. In response, Courtney Robertson said she would like to see a unified effort on creating support material across LearnWP, HelpHub, and DevHub. In order to track this concern and have a place to point people, I’m opening this issue so, when the time comes, a decision can be made and folks can be notified. While not explicitly stated in the 6.0 post, I know it’s been discussed around having it removed for 6.0 as this was meant to be a temporary label to communicate that the site editor is still in early stages.
She posted:Īcross the community, I’m getting questions around when the beta label for the site editor will be removed. Even with a slightly extended cycle, major updates come fast.Īnne McCarthy opened a discussion in the Gutenberg repository on Tuesday. WordPress 6.0 is scheduled for launch on May 24, 2022. It will depend on many things going right over the next couple of months.
0 kommentar(er)
