+44 0330 223 3428
Call Us
+44 0330 223 3428

WPTavern: Gutenberg Blocks Design Library Offers Pre-Built Page Designs Using Existing Core Blocks

WPTavern: Gutenberg Blocks Design Library Offers Pre-Built Page Designs Using Existing Core Blocks

Gutenberg Blocks Design Library is a new plugin that provides pre-built page designs, including demo content, using only the default core blocks that come with WordPress. The free version comes with 50 different designs that users can import from the growing Gutenberg Blocks Design Library. These include simple designs for all kinds of page building items, such as text with images, columns with headers, call-to-action sections, team member listings, testimonials, contact page layouts, and more.

The plugin is fully compatible with other Gutenberg themes and plugins, since it simply adds styles to existing core blocks. It can be used in combination with block collections, such as Atomic Blocks, Editor Blocks, CoBlocks, Caxton, Kadence, GhostKit, WooCommerce blocks, and many others.

There are a few major advantages to this approach. Simply adding styles to core blocks means that the plugin doesn’t introduce a bunch of new blocks for users to scroll through in the block inserter. It also ensures data portability. If a user ends up deactivating and removing the plugin for any reason, the content is still there in the default block design.

Although Gutenberg Blocks Design Library is compatible with any WordPress theme that works with the new editor, the appearance of the the pre-made designs vary somewhat across themes. I tested various blocks with different themes and found that it seems to adapt to the active theme’s look and feel. This can be a positive feature or a negative one if the user is hoping for the designs to match the demo exactly.

After installing the plugin, the design library is available by toggling the carrot icon in the menu at the top of the editor. The user is then prompted to import 50 free designs.

The creators of the Gutenberg Blocks Design Library have also built a commercial subscription service to sell “pro designs.” Pricing during the beta period starts at $9/year for a single site. The company aims to have 1,000 commercial designs available to subscribers by November 2019. They plan to release new designs every other week.

The Gutenberg Blocks Design Library is helpful for users who don’t need the more advanced capabilities of a full-featured page builder plugin but still want some simple, pre-built page elements. The placeholder content makes it easy for users to know where to insert their own content. It is much more intuitive than importing an XML file for demo content. This plugin is a great example of the interesting new product opportunities that Gutenberg has introduced by replacing tools that previously might have been built with widgets or cumbersome shortcodes.


Gutenberg Blocks Design Library is a new plugin that provides pre-built page designs, including demo content, using only the default core blocks that come with WordPress. The free version comes with 50 different designs that users can import from the growing Gutenberg Blocks Design Library. These include simple designs for all kinds of page building items, such as text with images, columns with headers, call-to-action sections, team member listings, testimonials, contact page layouts, and more. The plugin is fully compatible with other Gutenberg themes and plugins, since it simply adds styles to existing core blocks. It can be used in combination with block collections, such as Atomic Blocks, Editor Blocks, CoBlocks, Caxton, Kadence, GhostKit, WooCommerce blocks, and many others. There are a few major advantages to this approach. Simply adding styles to core blocks means that the plugin doesn’t introduce a bunch of new blocks for users to scroll through in the block inserter. It also ensures data portability. If a user ends up deactivating and removing the plugin for any reason, the content is still there in the default block design. Although Gutenberg Blocks Design Library is compatible with any WordPress theme that works with the new editor, the…

Source: WordPress

Tagged

WPTavern: Open Source Initiative Calls Organizations to Reaffirm Support for Its Definition of Open Source

WPTavern: Open Source Initiative Calls Organizations to Reaffirm Support for Its Definition of Open Source

The Open Source Initiative (OSI) took a strong, unequivocal stance on its definition of open source this week, encouraging organizations to sign a public affirmation of its role in maintaining and stewarding the definition. The organization has been instrumental in combatting issues caused by license proliferation, as many open source licenses cannot be legally combined and this can be detrimental to the open source ecosystem.

The affirmation published this week explains the need for a standard definition of open source:

Without this single, standard definition of “open source,” software development as we know it would not be possible. There is no trust in a world where anyone can invent their own definition for open source, and without trust there is no community, no collaboration, and no innovation.

Recent controversy surrounding Redis Labs licensing some of its modules under the Apache 2.0 modified with a Commons Clause has highlighted the need for an authoritative definition of open source. Salil Deshpande, who helped create the Commons Clause (written by open-source lawyer Heather Meeker), wrote an article for TechCrunch two months ago about how he perceives large cloud infrastructure providers, such as AWS in this case, to be a threat to the viability of open source. He explained why he and collaborators commissioned the Commons Clause:

We wished to define a license that prevents cloud infrastructure providers from running certain software as a commercial service, while at the same time making that software effectively open source for everyone else, i.e. everyone not running that software as a commercial service.

With our first proposal, Commons Clause, we took the most straightforward approach: we constructed one clause, which can be added to any liberal open-source license, preventing the licensee from “Selling” the software  —  where “Selling” includes running it as a commercial service. (Selling other software made with Commons Clause software is allowed, of course.) Applying Commons Clause transitions a project from open source to source-available.

In referencing MongoDB’s Server Side Public License (SSPL), Deshpande questioned the authority and relevance of OSI:

OSI, which has somehow anointed itself as the body that will “decide” whether a license is open source, has a habit of myopically debating what’s open source and what’s not. With the submission of SSPL to OSI, MongoDB has put the ball in OSI’s court to either step up and help solve an industry problem, or put their heads back in the sand.

The Commons Clause, which has no chance of being approved by OSI, was a reaction to cloud-based services making a profit from open source software without contributing much back to the software’s creators. This is a common issue encountered by maintainers of popular open source projects. However, the Commons Clause isn’t a good solution for this problem, because it effectively neuters open source software, removing the vital freedoms identified in the open source definition, including free distribution and no discrimination against a specific field of endeavor. OSI President Simon Phipps called the Commons Clause an “abrogation of software freedom” after Redis changed its license.

In light of these recent conversations, OSI is calling organizations to band together in recognition of its authority to maintain a single, standard definition of open source:

Recently there have been efforts to undermine the integrity of open source by claiming there is no need for a single, authoritative definition. These efforts are motivated by the interests of a few rather than the benefit of all, and are at odds with the principles that have so demonstratively served us well in the past decades. If allowed to continue, these efforts will erode the trust of both users and contributors, and hinder the innovation that is enabled by open source software, just as surely as having multiple definitions of a kilogram would erode and undermine commerce.

OSI reached out first to its Affiliate Members, which includes the WordPress open source project, but not all members have responded in time for the publication of the post this week. The organization is still welcoming new signatories and will add more names to the list as it receives them.


The Open Source Initiative (OSI) took a strong, unequivocal stance on its definition of open source this week, encouraging organizations to sign a public affirmation of its role in maintaining and stewarding the definition. The organization has been instrumental in combatting issues caused by license proliferation, as many open source licenses cannot be legally combined and this can be detrimental to the open source ecosystem. The affirmation published this week explains the need for a standard definition of open source: Without this single, standard definition of “open source,” software development as we know it would not be possible. There is no trust in a world where anyone can invent their own definition for open source, and without trust there is no community, no collaboration, and no innovation. Recent controversy surrounding Redis Labs licensing some of its modules under the Apache 2.0 modified with a Commons Clause has highlighted the need for an authoritative definition of open source. Salil Deshpande, who helped create the Commons Clause (written by open-source lawyer Heather Meeker), wrote an article for TechCrunch two months ago about how he perceives large cloud infrastructure providers, such as AWS in this case, to be a threat to the viability…

Source: WordPress

Tagged

WPTavern: YoastCon Overshadowed by Twitter Storm: Joost de Valk, SEO Industry Leaders Called Out for Objectifying Women

WPTavern: YoastCon Overshadowed by Twitter Storm: Joost de Valk, SEO Industry Leaders Called Out for Objectifying Women

The third edition of YoastCon kicked off today in Nijmegen, the Netherlands, but for those following remotely the conference has been overshadowed by a discussion that erupted on the #yoastcon hashtag prior to the event. Several parties began circulating tweets and unsavory videos involving Joost de Valk, for which he has since publicly apologized.

The story was complicated and confusing to follow, as many of these decade-old tweets were deleted and the videos made private by the websites that are hosting them. The parties who were publishing screenshots from archive.org alleged that de Valk was sexually harassing women in the SEO industry.

One of the women to whom some of the tweets were directed has publicly stated that she did not perceive them as harassment and that the tweets were taken out of context.

de Valk responded yesterday with a public apology, acknowledging the tweets and videos.

He also provided a statement to the Tavern with more context on the after party videos.

“The videos are of an event I’ve attended over the last decade called SEOktoberfest, which is an SEO conference at Oktoberfest,” de Valk said. “I’m honestly ashamed of those videos when I see them now… It looks bad and I wouldn’t behave like that now, but I don’t think anything I did myself at those events was ever out of line.”

Marieke van de Rakt, who recently took on the role of CEO of Yoast, said she thought the tweets were brought to public attention in retaliation for the company announcing a project to empower women working at Yoast. de Valk left the CEO role to focus on product development at Yoast and his new role of Marketing and Communications Lead at WordPress.org.

I feel like it started after I was announced CEO and later on talked about a project to empower women working at Yoast. I got some really upsetting tweets. After that it started focusing on #yoastcon. It seems like they want to show the hypocrisy in our statements about women. I never spoke at SEO events before, though I have been to SEOktoberfest. It felt totally welcoming back then. That being said, the pictures and movies aren’t something I particularly enjoy watching. I do think they’re bad, but also a bit out of context. The environment at Yoast is nothing like that. And although my husband likes to party (as do I), I feel he’s always been a strong believer in equal rights and opportunities. I think we all make mistakes and learn from them. At Yoast, we’re really trying to improve inequality with both the diversity fund and my empowerment project.

For those watching the #yoastcon hashtag, the way the situation unfolded it almost seemed like a coordinated personal attack on de Valk, especially given how the SEOktoberfest videos were spliced together with the YoastCon promotional videos. David Cohen, a Philadelphia-based Digital Marketing Director who previously worked at a large SEO agency, started the conversation by publishing de Valk’s old tweets that he had found years ago when researching Yoast and its founder.

“As far as the tweets from Joost are concerned, I’ve known about them since 2014,” Cohen said. “I just never knew what to do with them or how to proceed questioning why that behavior was perfectly acceptable for him.

“As far as the harassment and abuse in the SEO industry, particularly at the SEO conferences, I’ve known about this since 2011 after seeing it firsthand while working at a large SEO agency in Philly, Seer Interactive.”

Cohen said that he began publicly criticizing people he calls “SEO celebs” in 2014, for “saying they are against the SEO harassment and abuse, claiming to be ‘male feminists,’ yet knowingly covering up the abuse and enabling the abusers who happen to also be their friends, peers, colleagues, etc.”

While the discussion on the #yoastcon hashtag seems centered around de Valk’s admitted indiscretions, Cohen said his objective in publicizing the old tweets goes beyond de Valk. He’s calling out other leaders in the industry who he alleges have harassed and abused women for years.

“This started a solo mission to take action as a messenger of questions for the group of SEOs most prominent figures who hold the power of influence over the industry about the 10+ year ongoing issue of alleged harassment and abuse of women in the SEO world, particularly at SEO conferences between 2009 and 2012 era.”

Cohen said the timing with YoastCon was “a mission looking for direct and public answers on this topic once and for all while they were all gathered together at the event.” He began tweeting about these issues well before the event and was using the #yoastcon hashtag to call out other SEO industry leaders for the past few months.

When asked about his motive, Cohen said he simply wants answers from de Valk, Rand Fishkin, his wife Geraldine, John Doherty, Martin MacDonald, Marcus Tandler, and others regarding what he perceives to be hypocrisy in the SEO industry.

“Why has it been totally cool for the SEO celebs, rock stars, ninjas, and conference speakers to be misogynists, to objectify and sexualize women, to hire Playmates for their SEO events, and to engage in behavior that would easily be classified as ‘toxic masculinity?’” Cohen said. He claims that industry leaders have been covering up harassment and abuse that they have known about and have refused to help the women who have been abused. Cohen and several others who have been circulating the tweets claim that victims of this abuse have been contacting them to share their stories but have not yet gone public with them.

“As for Joost, going with the ‘if I offended anyone’ apology approach is empty and lacks personal accountability for behaviors that are completely misaligned with words,” Cohen said. “He had to respond publicly. But the question remains open – why?”


The third edition of YoastCon kicked off today in Nijmegen, the Netherlands, but for those following remotely the conference has been overshadowed by a discussion that erupted on the #yoastcon hashtag prior to the event. Several parties began circulating tweets and unsavory videos involving Joost de Valk, for which he has since publicly apologized. The story was complicated and confusing to follow, as many of these decade-old tweets were deleted and the videos made private by the websites that are hosting them. The parties who were publishing screenshots from archive.org alleged that de Valk was sexually harassing women in the SEO industry. @yoast can scrub @jdevalk history of thirsty sexual harassment tweets but The Wayback Machine knows all. If it’s not harassment why was it deleted yesterday? #YoastCon pic.twitter.com/amctSWHqEw — Dan Leibson (@DanLeibson) February 6, 2019 Looks like somebody whose name rhymes with toast has been busy deleting tweets ahead of #YoastCon … wonder if any of them are in https://t.co/7s6vq2FNXD? pic.twitter.com/Oi7uAexukv — David Cohen (@explorionary) February 6, 2019 No seriously, fucking don’t try and excuse behaviour like this. (9/41) pic.twitter.com/DoK1zOl3p2 — Tom Rayner (@tjprayner) February 7, 2019 One of the women to whom some of the tweets were directed…

Source: WordPress

Tagged

Dev Blog: WordPress 5.1 Release Candidate

Dev Blog: WordPress 5.1 Release Candidate

The first release candidate for WordPress 5.1 is now available!

This is an important milestone, as the release date for WordPress 5.1 draws near. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.1 is scheduled to be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time!

There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

What’s in WordPress 5.1?

Inspired by Archie Bell & The Drells, WordPress’s theme for 2019 is to “tighten up”, and WordPress 5.1 focussed on exactly that.

With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.

Furthermore, when installing new plugins, WordPress’s Site Health features will check whether a plugin requires a version of PHP incompatible with your site. If so, WordPress will prevent you from installing that plugin.

The new block editor has kept improving since its introduction in WordPress 5.0. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother. There are more features and performance improvements planned in upcoming WordPress releases, you can check them out in the Gutenberg plugin.

Plugin and Theme Developers

Please test your plugins and themes against WordPress 5.1 and update the Tested up to version in the readme to 5.1. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.

The WordPress 5.1 Field Guide has also been published, which goes into the details of the major changes.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.1 release schedule.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.


This is my release
candidate. There are many
like it. This is mine.

..


The first release candidate for WordPress 5.1 is now available! This is an important milestone, as the release date for WordPress 5.1 draws near. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.1 is scheduled to be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time! There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip). What’s in WordPress 5.1? Inspired by Archie Bell & The Drells, WordPress’s theme for 2019 is to “tighten up”, and WordPress 5.1 focussed on exactly that. With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress. Furthermore, when installing new plugins, WordPress’s Site Health features will check whether a plugin requires a version of PHP incompatible with your site. If so,…

Source: WordPress

Tagged

WPTavern: Gutenberg 5.0 Adds New RSS Block, Amazon Kindle Embed Block, and FocalPointPicker Component

WPTavern: Gutenberg 5.0 Adds New RSS Block, Amazon Kindle Embed Block, and FocalPointPicker Component

Version 5.0 of the Gutenberg plugin was released yesterday with a new RSS block. Riad Benguella, the project’s technical lead for phase 2, published a demo of the block and its settings. Users can set the number of items displayed and also toggle on/off the author, date, and excerpt.

RSS is still relevant today as one of the linchpins of the open web and Gutenberg makes it possible to easily place a feed inside a post or page. (This feature was previously limited to widgetized areas.) The creation of this block is part of a larger effort to port all of WordPress’ existing core widgets over to blocks.

Version 5.0 also introduces a new Amazon Kindle embed block, providing an instant preview from an Amazon Kindle URL. WordPress already has oembed support of Amazon Kindle URLs but it was missing from the Embeds section of the accordion in the block inserter.

One of the most exciting additions in this release is a new FocalPointPicker for the Cover block. It allows users to visually select the ideal center point of an image and returns it as a pair of coordinates that are converted into ‘background-position’ attributes. The result is that the user has more control over how the image is cropped. This feature solves so many problems users have experienced in cropping and displaying images in their WordPress themes and content. The FocalPointPicker was created as a reusable component so that developers can use it to build other blocks with the same capabilities, providing an experience that is consistent with core.

Focal point picker

The changes included in Gutenberg 5.0 are immediately available for those running the plugin on their sites but only for WordPress 5.0+. This release drops support for earlier versions of WordPress. The updates in Gutenberg 5.0 are planned to be rolled into WordPress 5.2.


Version 5.0 of the Gutenberg plugin was released yesterday with a new RSS block. Riad Benguella, the project’s technical lead for phase 2, published a demo of the block and its settings. Users can set the number of items displayed and also toggle on/off the author, date, and excerpt. RSS is still relevant today as one of the linchpins of the open web and Gutenberg makes it possible to easily place a feed inside a post or page. (This feature was previously limited to widgetized areas.) The creation of this block is part of a larger effort to port all of WordPress’ existing core widgets over to blocks. Version 5.0 also introduces a new Amazon Kindle embed block, providing an instant preview from an Amazon Kindle URL. WordPress already has oembed support of Amazon Kindle URLs but it was missing from the Embeds section of the accordion in the block inserter. One of the most exciting additions in this release is a new FocalPointPicker for the Cover block. It allows users to visually select the ideal center point of an image and returns it as a pair of coordinates that are converted into ‘background-position’ attributes. The result is that the…

Source: WordPress

Tagged

Post Status: Building Multidots, with Anil Gupta

Post Status: Building Multidots, with Anil Gupta

Welcome to the Post Status Draft podcast, which you can find on iTunesGoogle PlayStitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard.

In this episode of Draft, I talk to Anil Gupta, the founder of Multidots. Multidots is a 100+ person company and Anil has established a very people-first environment. We discuss his journey and philosophies building the company.

I met Anil at CaboPress and we had a great chat, which we followed up with in this episode, recorded at WordCamp US. Anil has a great story and a lot of insight. I hope you enjoy.

Sponsor: Jilt

Jilt offers powerful email marketing built for eCommerce. Join thousands of stores that have already earned tens of millions of dollars extra sales using Jilt. Try Jilt for free


Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard. In this episode of Draft, I talk to Anil Gupta, the founder of Multidots. Multidots is a 100+ person company and Anil has established a very people-first environment. We discuss his journey and philosophies building the company. I met Anil at CaboPress and we had a great chat, which we followed up with in this episode, recorded at WordCamp US. Anil has a great story and a lot of insight. I hope you enjoy. Sponsor: Jilt Jilt offers powerful email marketing built for eCommerce. Join thousands of stores that have already earned tens of millions of dollars extra sales using Jilt. Try Jilt for free

Source: WordPress

Tagged