[ad_1] Extendify has been scooping up some successful block-related plugins in recent months. It acquired the Redux Framework in November 2020 and followed it up with a purchase of Editor Plus and Gutenberg Hub in December. Its latest pickup? EditorsKit. This ownership change was an adoption rather than an acquisition. The company is compensating Jeffrey Carandang, EditorsKit’s creator, for helping during the transition. “The main motivation was to ensure that EditorsKit has a good home,” said Extendify co-founder Chris Lubkert. “Jeffrey had taken a full-time role with 10up, and the plugin hasn’t seen any updates in 9 months. So we are both excited about Extendify building on what Jeffrey has built and continuing to serve the user base.” EditorsKit is a playground of extensions on top of the existing blocks. From visibility logic to text formatting to extra block options, it has a little bit of everything. Carandang has often launched features long before something similar has landed in WordPress. It has grown to over 20,000 active installs since he first submitted it to the plugin directory. Taking on a new role with 10up as a web engineer left him little time to devote to the plugin. “My time was occupied by my full-time work and adjusting through my shifts, personal stuff, and with what’s happening in the world due to lockdowns; and the covid virus,” he wrote in his own farewell post. “I hate to admit it but I think I’ve neglected my role in the EditorsKit plugin/community that I’ve built for the past couple of years. With this, my sincere apology to the plugin users and the whole community.” Changes to EditorsKit When a plugin changes owners, users sometimes must brace themselves for changes. Right now, EditorsKit is the same plugin it has always been. However, the Extendify team has introduced some additions. The first is a part of what will eventually be a commercial aspect of the plugin: the Extendify Library. The team added this feature to both the Redux and Editor Plus plugins earlier this year. EditorsKit users will see a new “Library” button at the top of the editor. Once they click it, it opens an overlay for importing patterns and templates from Extendify’s collection. Popup library for importing Extendify patterns and templates. The amount of imports allowed is limited to three without signing up. “EditorsKit users have access to the same library of patterns and templates and can import three patterns and/or templates,” said Lubkert. “Anyone who signs up for the beta program will then receive unlimited imports during the beta period. We expect this to continue for a few more weeks.” Essentially, the commercial aspect of EditorsKit, Editor Plus, and Redux will be a shared library from the Extendify team. Users of any one of the plugins can continue using their preferred plugin with the option of importing patterns and templates. Lubkert said they still have no plans of rolling all of the plugins into one “super plugin,” keeping them each as a separate project. “It makes sense for us to invest our energy into a single library and creating the best experience possible for our users,” he said. The second change the team has implemented is making the EditorsKit Typography add-on a free download. The plugin allows users to select from a list of hand-picked Google Fonts and use them anywhere. It also has a customizable set of default font combinations. It makes sense to drop the commercial aspect of this add-on. WordPress is already starting to provide theme authors with the tools for typography options at the block level. EditorsKit Typography may be the better of the two right now, but the average user will not need it as the core platform continues to improve. ShareABlock and Other Projects The handover includes Carandang’s related sites. ShareABlock, CopyGlphys, and CopyGradients are all tools for helping WordPress users build on top of the block system. The Extendify team plans on keeping them alive. Carandang launched ShareABlock in December 2019. Essentially, it was a block patterns directory. Only, block patterns were merely an idea in the bowels of the Gutenberg GitHub repository at the time. The upcoming pattern directory, expected to officially open next month, was not even a blip on most people’s radar. ShareABlock homepage with downloadable “patterns.” ShareABlock has had time to mature. Its designs are more modern than the current offering from the pattern directory. The downside is the reliance on EditorsKit to import them via a JSON file instead of copy-paste block HTML code. With a few tweaks, it could be a serious contender as an alternative directory. If the WordPress development team follows through with a ticket I opened for allowing third-party vendors to hook into the system, it would be easy to do. “In general, we don’t see ourselves competing with the pattern directory (or anything else in core Gutenberg),” said Lubkert. “We’d like to solve unmet needs for the community and do so in a way that is complementary to core.” The team already has the patterns in place. Hooking in its existing library would be more of a value-add. The official directory is limited to what can be done with core block options. Extendify would have the wiggle room for adding designs built with its more robust EditorsKit and Editor Plus toolsets. Like this: Like Loading… [ad_2] Source link
Continue readingTag Archives: Block
Gutenberg 10.8 Adds New Typography Controls and Block Previews – WordPress Tavern
[ad_1] On Wednesday, Gutenberg 10.8 landed in the WordPress plugin directory. The release includes new typography options for controlling the Heading block’s font-weight and the List block’s font family. The Audio and File blocks now show preview content in the inserter. Gutenberg 10.7 felt like it introduced flashier features than 10.8. But, this was still a solid release. Sometimes the things that you do not see are just as important as those that you do. Full Site Editing (FSE) components continue to move along at a swift pace. Most changes were bug fixes rather than enhancements. One of the primary theme-related FSE upgrades allows developers to set the padding for nav menu links via theme.json. This may be a small win, but it is unlikely to address the numerous issues with styling navigation items and nested lists. The change also does not affect the Page List block links, which can be set as a nav menu item. The Navigation block will be one of the toughest nuts to crack before site editing is a possibility. Enhancements like this help, but it is a long and winding road to a solution that satisfies both theme authors and users. Users should see the post title in template-editing mode. The template details modal also includes more detailed information, such as how to best name custom templates. New Typography Options Gutenberg 10.8 enables the font-weight control for Heading blocks. This allows theme authors to define the default weight via their theme.json files, and users can override this via the sidebar panel in the editor. Testing font weights for the Heading block. The control displays all nine possible weights: Thin Extra Light Light Regular Medium Semi Bold Bold Extra Bold Black While each weight is selectable, it does not mean all fonts support a specific weight. For example, users will see no difference between Extra Bold and Black with the Twenty Twenty-One theme. In the long term, this should be coupled with the font family control. This would allow theme authors to define which weights are supported by a specific family, making those the only options for users. The List block is jumping ahead of others with its support of the font family option. Generally, we would see the Heading or Paragraph blocks gain such features first. Setting a custom font family for a List block. The Site Title, Site Tagline, and Post Title blocks all currently support the font family control. It is a welcome addition to see expanded typography options, but I look forward to the day they are offered across every block. Theme authors can also define custom letter spacing for the Site Title and Site Tagline blocks. However, the feature does not currently appear in the block options sidebar, which would allow users to customize it. There is an open ticket to address this missing piece of the UI. Audio and File Block Previews Audio block preview in the inserter. The development team added new previews for the Audio and File blocks in the inserter. This is a nice-to-have enhancement, adding long-missing previews of some of the remaining core blocks, but it is also a bug fix. In previous versions of the block editor, users who attempted to upload media via the Audio or File blocks would get a duplicate upload. This only happened in situations where their theme or a plugin registered a custom block style. Adding a preview apparently fixed this odd bug. This change also nearly gives us a complete set of previews for the pre-WordPress 5.8 blocks. Classic, Spacer, Shortcode, and Legacy Widget do not have them, but they are unique cases. The upcoming theme-related blocks also lack previews. “Archives” Label Now Shown for Archives Dropdown Duplicate archives heading and label. When using the Archives block as a dropdown, it now outputs a label titled “Archives.” While it is a seemingly trivial change, it could impact how themes typically present this block. This enhancement changes some existing expectations. The primary use case throughout WordPress’s history has been to show the Archives dropdown in a widget. In that case, there is almost always a widget title with the “Archives” text preceding it. I expect most other use cases would follow a similar pattern. This essentially creates duplicate text. Themes Team representative Carolina Nymark had an alternate suggestion: What if the label was visible by default, but there was an option for hiding it? Similar to the search block, except there would be an actual label hidden with a screen reader text CSS class when the option is toggled. That would have been my suggestion too if I had seen the ticket earlier. For now, theme authors who need to hide it should target the .wp-block-archives-dropdown > label class in their CSS. Like this: Like Loading… [ad_2] Source link
Continue reading“The Block Editor Gets Ready to Become a Site Builder” – WordPress Tavern
[ad_1] Matt Mullenweg and Matías Ventura joined WordCamp Europe to chat about what’s happening with the Gutenberg project and celebrate the progress contributors have made over the past four years. “For me, 2020 was the year that really felt like people started to see the vision of Gutenberg from four or five years ago, when it was very abstract and they saw it as kind of like the old WYSIWYG editor with some extra lines on it or something,” Mullenweg said. “The first 17 or 18 years of WordPress democratized people putting text into a box. Now we’re democratizing design, allowing people to control the boxes.” Ventura commented on how transformative patterns have been for making page design approachable for users. “Perhaps it was a smaller part of the roadmap initially but it’s becoming a centerpiece – especially because it allows…world class designers to provide a starting point for users and users get to learn design as they are interacting with themes,” Ventura said. He began his WordPress developer journey by “tinkering with themes,” as many others did, and believes that blocks can unlock a similar experimental learning experience. “I think we are getting into a chapter where people will be able to tinker with things that were sort of hidden for you in WordPress – more advanced things like queries and loops, that we can now expose through blocks,” Ventura said. “They can be stepping stones for people to learn how to work with WordPress.” Mullenweg commented on how things that previously would have required a fairly experienced WordPress developer to do, like creating a home page with a column that shows five recent posts from a particular category, and another column that shows featured posts in a different category, you can now do with just a few clicks. “It’s no code – it’s like expanding the layers of accessibility of what people are able to do with WordPress,” Mullenweg said. “That, to me, is very core to our mission.” Mullenweg and Ventura debuted a new “Gutenberg highlight” video that covers current and new features coming to the block editor, as it “gets ready to become a site builder.” These kinds of marketing videos are so valuable because users don’t always know what is possible, even if the tools are approachable for anyone to use. The video demonstrates new design features for different blocks, including the transform live previews, dragging media into container blocks, inline cropping without leaving the editor canvas, the template editor, duotone image filters, more customization options for navigation, improvements to the list view browser, and the new global styles design that is coming soon. Check out the video below and you can also watch Mullenweg and Ventura’s conversation that was recorded during the event. Like this: Like Loading… [ad_2] Source link
Continue readingA Progress Bar Block Plugin Done Right by the Tiles Team – WordPress Tavern
[ad_1] I have been on the hunt for a decent progress bar solution for a while now. Most of them are bundled in large block libraries, requiring me to install another 20 or 30 blocks in which I have no need. Others seem to miss the mark entirely with odd configurations and block options. Some of the remaining plugins still use shortcodes and widgets, but it is 2021. I am looking for a block. A couple of days ago, the Tiles Progress Block landed in the directory. It seems to be a smaller piece of a larger project named Tiles. I have been keeping an eye on the team’s work since its initial design and patterns framework plugin launched last week. That project is still in beta, and only time will tell if it becomes a competitive project in the block space. However, the team’s new progress bar block was just what I was looking for. Other than one bug, which I reported to the developer, I found no serious issues. The plugin does what it says on the tin. It registers a Progress Bar block: Small and Large progress bars with default colors. Out of the box, it includes Small and Large styles, allowing the user to adjust the size of the bar. Its strength is that — I cannot stress this enough — the block’s content is editable within the editor canvas area. This includes the label and percentage. This is a refreshing change from the many others that require users to jump back into the block options sidebar to change simple text. Because the block uses Rich Text fields for its label and percentage, end-users can use inline formatting tools like bold, italic, and more. The block also uses the standard typography and color palette controls from core WordPress. This provides access to the theme’s font sizes and colors. Adding custom labels, percentages, and colors. Plus, users can choose wide and full-width layouts, an often overlooked feature in block plugins. Overall, I am digging this block plugin. If I had one feature request, it would be to add a border-radius option. By default, the progress bar is rounded, but some users might prefer squared corners. Extending the Block In theme previews, I almost always see progress bars showcased alongside how much PHP, HTML, and JavaScript the demo’s faux developer has learned. It is rarely a real-world representation of progress bars. How do you quantify how much of a coding language you have mastered? I have been doing this for nearly two decades and cannot answer that. Progress bars should be of measurable things. For example, steps someone has taken in an online learning course, percentage of total donations received, and any number of things that can be counted are far more realistic. My favorite use of progress bars also happens to be on my favorite novelist’s website. I like to keep an eye on Brandon Sanderson’s work, looking forward to getting my next literary fix (yes, I am a fanboy). Brandon Sanderson’s writing progress. Currently, Tiles Progress Block does not handle that exact layout. However, because it is built on the block system and does not do anything out of the ordinary, theme authors can change that with custom styles. And that is just what I did. My Sanderson-esque book progress bars (rough, unpolished code available as a Gist): Progress bars with custom block style. The thing I love about the block system is that themers can extend blocks in this way. There is no needless checking for active plugins, loading additional per-plugin stylesheets, or figuring out each plugin’s unique system. If a block is coded to the current standards, theme authors merely need to hook in with their own styles. Users can then select those styles via the editor and even make them the default. I want to see more of this from the block plugin ecosystem. Like this: Like Loading… [ad_2] Source link
Continue readingOpen Invitation To Contribute to the WordPress Block Pattern Directory – WordPress Tavern
[ad_1] The upcoming block pattern directory is launching alongside WordPress 5.8 in July. The goal is to make several high-quality designs available for users right off the bat. However, the official submission process will not open until the directory launches. In this chicken-and-egg scenario, the Design team is asking for early contributors to submit their pattern candidates via GitHub. “The project needs a collection of high-quality, diverse, community-designed patterns to populate it with during development,” wrote Kjell Reigstad in the announcement post. “These patterns will set the tone for quality in the repository and will make the directory useful for folks upon its launch.” Alongside Reigstad, Beatriz Fialho and Mel Choyce-Dwan have already added several block patterns. They are available through the Gutenberg plugin now. Several of the current block patterns. The trio has also submitted the majority of the 18 current potential patterns. While they have produced solid work thus far, the directory needs a more diverse set of designs from the community to launch with a bang. Creating a pattern requires no coding skills. It is possible directly via the block editor. Just design, copy, and submit. The team already has a GitHub template in place for submitting patterns. Be sure to use CC0 (public domain) images if they are a part of your creation. Copying a pattern from the WordPress editor. I have somewhere between 40 and 50 patterns lying around. You could say that I have been doing a bit of dabbling in the art of block-pattern design in my free time. Many of these patterns rely on custom block styles, so they are not suitable for the directory. However, I have several that are general enough for submission. As always, I try to pay it forward when possible. Therefore, I cleaned a couple of patterns today using the Twenty Twenty-One theme and submitted them for inclusion. The first was a three-column section of “about me” or “connect with me” boxes. This has been one of my favorites to play around with. About me boxes. It is not on par with my original design, but I like how it turned out. If you have read any of my past posts on blocks and patterns, I will sound like a broken record. However, I must say it for those who did not hear the message the first 100 times. The main limiting factor for block patterns is the lack of spacing options on almost all blocks. Blocks like Group and Column have padding controls, which are a nice feature. However, vertical margin options are must-haves for the directory to be as successful with its goals as it intends to be. A prime example is in my first pattern. My original mockup closes the gap between the heading and subheading. In my submission, I tightened the space by setting the line height, but I needed an option for zeroing out the vertical margin. If you compare it to the original idea built with some features not yet available, you can see how much improved the overall layout’s spacing is. Original about me boxes with tighter margin control. I ran into the same issue with my second pattern, Team Social Cards, between the Image and Separator blocks. The gap there has more to do with Twenty Twenty-One’s inconsistent spacing. I may revisit the giraffe photo, but it is growing on me. It is fun. Plus, end-users are meant to actually replace it. I will probably submit one or two more during this early phase, and I will definitely contribute more once the pattern directory is officially open. For now, I want to see our talented design community giving a little something back to the WordPress project. This is such an easy way to contribute that has no coding requirement — just a little time. Like this: Like Loading… [ad_2] Source link
Continue readingUpdating a Publishing Plugin to the Block Editor • WPShout
[ad_1] Helen Hou-Sandí is certainly one of the most important people making (core) WordPress better, and she’s been doing it for years. So I take a pretty keen interest in what she’s working on. So when this post about updating a “legacy” WordPress post-meta post so that it was compatible, I knew I had to read it. And a few months later, I finally did. 🤪 I really appreciated both the article’s style and comprehensiveness. So please give it a read if “modernizing an old plugin for Gutenberg” is somewhere on your to-do list. The article tackles a number of things I’d meant to understand better for years in an approachable way: writing compatible JavaScript and using wp-scripts are the two that leap to mind. Visit helen.blog → [ad_2] Source link
Continue readingBuilding Featured Boxes With the WordPress Block Editor – WordPress Tavern
[ad_1] It is a new day with another chase for that elusive block plugin that will bring a little joy into my life. Today’s experiment comes courtesy of the Feature Box plugin by Sumaiya Siddika. It is a simple block that allows end-users to upload an image and add some content to an offset box. The plugin’s output is a typical pattern on the web. As usual, I am excited to see plugin authors experimenting with bringing these features to WordPress users. I want to see more of it, especially from first-time plugin contributors. I was able to quickly get the block up and running, adding my custom content. The following is what the block looked like after entering my content and customizing it. I envisioned myself as a recipe blogger for this test. Inserting and modifying the Feature Box block. On a technical level, the plugin worked well. I ran into no errors. Everything was simple to customize. However, it never felt like an ideal user experience. The first thing I immediately noticed is that image uploading happens in the block options sidebar. Core WordPress blocks have a dedicated button in the toolbar for adding images and other media. I also found myself wanting more direct control over individual elements. How could I change the heading font size? Where were the typical button styles like Outline and Solid Color? How do I insert other blocks, like a list? None of those things were possible. Like many other blocks, the developer has created a system with specific parameters, and the user cannot move outside of them. There are times when that rigidity makes sense, such as when building custom blocks for clients. However, more often than not, publicly-released plugins should be far more open. This tightly controlled block is reflective of how WordPress worked in the past. It was often inflexible, leaving users to what theme and plugin developers thought was best for their sites. The block system is about tossing out these overly rigid concepts and giving users power over their content. The job of plugins and themes is to define the framework the user is operating under. They set up some rules to more or less keep things from breaking, but the users get to strap themselves into the driver’s seat. Their destination is their own. The block would have been far more well-rounded if users could control all of the content in the box. Ideally, they could put whatever blocks they wanted into the “content” area of the Feature Box block. The design would match their theme better too. A couple of weeks ago, I wrote a post titled You Might Not Need That Block. The premise was that users could recreate some blocks with the current editor and that themers could make this easier by offering patterns. I knew replicating this particular block would be impossible without at least a little custom code. WordPress’s editor does not have a feature for offsetting a block’s position. A theme author could easily duplicate this functionality. Typically, I would create a custom pattern, complete with all the existing pieces in place. However, I wanted to approach this with custom block styles. This would allow end-users to select the content offset from the sidebar and switch it around if needed. Note: For those who wish to learn how to create custom block styles, Carolina Nymark’s tutorial is the best resource. The Cover block made an ideal candidate for this. Because it has an existing “inner wrapper” element, it meant that I could target it with CSS and move it around. The following is a screenshot of the Offset Left style I created: Offset Left Cover block style. I simply replicated the code and changed a few values to create an Offset Right style immediately after. The code is available as a GitHub Gist. It is a simple proof-of-concept and not a polished product. There are various approaches to this, and several Cover block options are left unhandled. Theme authors are free to take the code and run with it. These block styles looked far better because they matched my theme. Everything from the spacing to the border-radius to the button looked as it should. Offset Left and Right block styles. The big win was that I had design control over every aspect of the content box. I could select the button style I wanted. I could change my font sizes. The default spacing matched my theme as it should. The problem I ran into with the block style method is allowing users to control the content box’s background color. The Feature Box plugin wins in the user experience category here because it has an option for this. The block style I created inherits its background from the Cover block parent. It may not be immediately obvious how to change it. The other “problem” with the block style is that it does not handle wide and full alignments for the Cover block. That is because I did not take the experiment that far, only replicating the plugin’s layout. I will leave that to theme designers to tinker around with. There are many possibilities to explore; don’t wait for me to provide all the ideas. My goal with this post and similar ones is to show how I would approach these things as both a user and developer. As a user, I want flexibility in all things. As a developer, I want to provide the solutions that I desire as a user. I also want to see plugin and theme authors thinking beyond their initial use case when building blocks, patterns, styles, and more. Lay the groundwork. Then, expand on that initial idea by thinking of all the ways that users might want to customize what you have built. Like this: Like Loading… [ad_2] Source link
Continue readingJetpack 9.8 Introduces WordPress Stories Block Alongside Forced Security Update – WordPress Tavern
[ad_1] Jetpack 9.8 was released this week, introducing WordPress Stories as the headline feature. The Story block, which allows users to create interactive stories, was previously only available on mobile. It can now be used in the web editor. Stories went into public beta on the Android app in January 2021, and were officially released on the mobile apps in March. Version 9.8 also included a security patch for all sites using the Carousel feature. The vulnerability allowed the comments of non-published pages/posts to be leaked. It was severe enough for the Jetpack team to work with WordPress.org to release 78 patched versions – every version of Jetpack since 2.0. Sites not using the Carousel feature were not vulnerable but could be in the future if it was enabled and left unpatched. In a rare move, WordPress.org pushed a forced update to all vulnerable versions, surprising those who have auto-updates disabled. Several Jetpack users posted in the support forums, asking why the plugin had updated automatically without permission and in some cases not to the newest version. So this update was a forced update on WordPress sites even with auto-updates disabled? We had this go live on a prod site at 2am last night that has auto-updates disabled for very specific reasons. Not cool Jetpack. https://t.co/55upBmyeHp — Brad Williams (@williamsba) June 3, 2021 Jetpack team member Jeremy Herve said the vulnerability was responsibly disclosed via Hackerone, allowing them to work on a patch for the issue. After it was ready to go, the Jetpack team reached out to the WordPress.org security team to inform them of a vulnerability impacting multiple versions of the plugin. “We sent them the patch alongside all the info we had (a PoC for the vulnerability, what features had to be active, what versions of Jetpack were impacted),” Herve said. “They recommended we release point releases for older versions of Jetpack as well. “We created those new releases, and when we were ready to release them, someone from the WordPress.org team made some changes on the WordPress.org side so folks running old, vulnerable versions of the plugin would get auto-updated, just like it works for Core versions of WordPress.” Jetpack team member Brandon Kraft estimated the number of vulnerable sites at 18% of the plugin’s active installs. He said that Jetpack was not part of the discussion about the pushing out a forced update. We weren’t part of the discussion. Provided details and got the response, but I wouldn’t expect a security convo to be public. But, yes. Single feature impacted. A few things need to be all true for it to matter on a site, which looked like qualified about 18% of sites IIRC. — A Guy Called Kraft 😷💉 (@Kraft) June 3, 2021 “What probably adds to the confusion is that WordPress 5.5 added a UI for plugin (and theme) autoupdates,” Herve said. “That UI, while helping one manage plugin autoupdates on their site, is a bit different from Core’s forced update process. Both of those update types can be deactivated by site owners, just like core’s autoupdates can be deactivated, but I don’t believe (and honestly wouldn’t recommend) that many folks deactivate those updates.” Brandon Kraft dug deeper into the topic and published a post that explains the differences between auto-updates and forced updates. It includes how to lock down file modifications if you don’t want to receive any forced updates in the future. Forced updates, however, are exceedingly rare, and Kraft counts only three for Jetpack since 2013. In this instance, the Jetpack team followed the official process for reporting a critical vulnerability to the plugin and security teams who determine the impact for users based on a set criteria. Users who received an email notification about an automatic update from Jetpack, despite having the UI in the dashboard set to disable them, should be aware that these forced updates can come once in a blue moon for security purposes. Tony Perez, founder of NOC and former CEO at Sucuri, contends that forcing a security update like this violates the intent users’ assign when using the auto-updates UI in WordPress. He highlighted the potential for abuse if the system were to become vulnerable to a bad actor. “The platform is making an active decision that is arguably contrary to what the site administrator is intending when they explicitly say they don’t want something done,” Perez said. “Put plainly, it’s an abuse of trust that exists between the WordPress user and the Foundation that helps maintain the project. “My position is not that it shouldn’t exist. That’s a much deeper ideological debate, but it is about respecting an administrators explicit intent.” Like this: Like Loading… [ad_2] Source link
Continue reading