WPTavern: Let’s Encrypt Passes 100 Million Certificates Issued, Will Offer Wildcard Certificates in January 2018

photo credit: Chris Anderson

Let’s Encrypt, the free and open certificate authority that launched in 2016, has issued more than 100 million certificates as of June 2017 and is currently securing 47 million domains. Earlier this year, the web passed a major milestone of getting more than 50% of traffic encrypted. Let’s Encrypt has been a major contributor to that percentage growing to nearly 58%.

“When Let’s Encrypt’s service first became available, less than 40% of page loads on the Web used HTTPS,” ISRG Executive Director Josh Aas said. “It took the Web 20 years to get to that point. In the 19 months since we launched, encrypted page loads have gone up by 18%, to nearly 58%. That’s an incredible rate of change for the Web.”

Aas also announced that wildcard certificates are coming to Let’s Encrypt in 2018. Wildcard certificates allow a site to secure an unlimited number of subdomains with the same certificate.

Currently, the process to get Let’s Encrypt working on a WordPress multisite installation is much more complicated than adding a certificate for a single domain. The WP Encrypt plugin claims multisite and multi-network compatibility but super admins have often run into failure on networks with higher numbers of sites. Wildcard support for Let’s Encrypt will provide a better way to secure multisite networks.

Let’s Encrypt will offer the wildcard certificates via the new ACME v2 API endpoint and will start by supporting base domain validation via DNS with the possibility of adding other validation options in the future. ACME is the protocol that Let’s Encrypt developed to allow subscribers to acquire and manage certificates. Those using the v1 endpoint are encouraged to move to v2 as soon as it’s available in January 2018. The v2 protocol was developed to be an IETF (Internet Engineering Task Force) standard so that ACME can work with more certificate authorities in the future.


Source: planet

WPTavern: WangGuard Plugin Author Shuts Down Splog Hunting Service Due to Trauma and Death Threats

After seven years of developing and supporting the WangGuard/SplogHunter service, José Conti has shut down the server permanently due to the stress and trauma associated with maintaining it. Conti is a WordPress plugin developer and consultant, and a member of the WordPress España translation team. His WangGuard plugin identifies and blocks sploggers, unwanted users, and untrusted users on WordPress, Multisite, BuddyPress, bbPress, and WooCommerce sites. It is currently active on more than 10,000 sites.

Speculation about why the service shut down was running rampant after Conti had collected donations via an Indiegogo campaign in October 2016 to fund support and server costs. Since that time SiteGround stepped in to sponsor WangGuard, eliminating the server costs. The only costs that remained were Conti’s time and effort that he put into supporting the plugin.

“My purpose with WangGuard was never money,” Conti said in his post explaining the reason for the shut-down. “I could have made WangGuard a paid plugin at anytime, and actually had a plan for that for years. But I didn’t do it because there is something inside me that would never let that happen. It was never, I repeat, never my plan to get rich with WangGuard, and I assure you that I could have done it easily: simply charging each of my users 24€/year, would have meant an income of more than 2 million euros per year. I just had to distribute a version of WangGuard I had collecting dust, with a checkbox on WangGuard’s server administration options but I never got it done. No matter the other reasons, which only people very close to me know: I simply didn’t want to, nor did I want to be a millionaire.”

Mafia Death Threats and Trauma from Exposure to the Dark Web: The High Cost of WangGuard’s 99.9% Accurate Detection of Splogs

WangGuard has long been known for its nearly perfect detection of registration spam. Not only did it completely block unwanted users, it also removed them from the database. The plugin was unrivaled in both accuracy and price – all users got everything the service offered for free. In order for WangGuard to provide its 99.90% accuracy, Conti bolstered the algorithm with manual curation and reviews.

“WangGuard worked in two different ways: as an algorithm that I had been refining for seven years, and which was getting better as the sploggers evolved, so that it was always one step ahead of them, and also as human curation, in which I reviewed many factors, among them sites of sploggers to see if their content could improve the algorithm and make sure that it worked correctly both when it was blocking or not blocking a site,” Conti said. “The great secret of WangGuard was this second part. Without it WangGuard would not ever have become what it was.”

Because of how effective WangGuard was at stopping unwanted users, Conti said for four years he received “almost daily death threats from mafias for making them lose millions of dollars.”

Through the process of manually curating splogger sites, Conti caught a glimpse of the some of the darkest places on the web, which he said had a damaging psychological impact on him.

“For seven years, I have visited places where I saw pederasty, pictures, and videos of murders (by razor blades, by gutting live people, by beheadings, dismemberments, to name a few), real videos of rape of all kinds (children, women, boys), photos of accidents in which people were totally disfigured, bizarre actions that I did not even know existed, and a very long ‘and so on,’ which I do not want to expand on,” Conti said.

The effects of viewing these types of websites every day took their toll and Conti decided to close the splog hunter service.

“Finally, a few months ago, I broke down,” Conti said. “I disappeared from everywhere and fell into a depression. The seven years of working at WangGuard finally took a toll on me. I had nightmares because of all the macabre deaths I had seen, an obsession with protecting my children from pederasty, OCD, depression, and many other symptoms. It took me about 6 months to recover (and honestly, I may be deceiving myself, since I do not think I completely recovered my life).”

I asked Conti if clicking through to the websites was necessary for maintaining the service. He explained that while WangGuard blocked emails, domains, IPs, and ISPs, without his manual curation of visiting the domains and clicking the links, users could get a lot of “sleepers” – registered and active accounts that remain silent until one day with a 0day vulnerability or a bug fix, they attack thousands of websites. The sleepers also wait to perform actions like create millions of sites on thousands of WordPress multisite installations in order to create a lot of bad content/links.

“Visiting many domains, I was able to minimize this problem,” Conti said. “The way I worked not only fixed the current spam / splog problem, but the wizard and database also fixed any future problems with sleepers.”

Another reason he visited the domains was to figure out what he needed to block, whether it was an email or a domain. The domain could be a spam domain or possibly a free email service.

“By visiting a website, I could detect whether it was a phishing website or a site camouflaged as an email service in order to try to cheat WangGuard,” he said. “I saw a lot of ‘techniques’ for trying to cheat WangGuard at Black Hat specialized forums. I had been subscribed to many spam/sploggers forums for investigation. Every time that a user described a real technique for cheating WangGuard, it was fixed immediately.”

If you’re still using the WangGuard plugin, it may continue to work but not nearly as well as in the past. Conti said that some parts of the code work without the API, but the most important parts require the WangGuard/SplogHunter server. The plugin is open source, so anyone can fork it. An English translation of his original post is available on the WordPress.org plugin forums.


Source: planet

WPTavern: WordSesh Asia Now in Planning for 2018, WordCamp Asia Targeted for 2019

photo credit: Sakin Shrestha

Yesterday Sakin Shrestha announced that WordCamp Asia is now in the preliminary planning stages. Shrestha is a key reviewer on the Theme Review Team, translates WordPress to Nepali, and organizes meetups and WordCamps in Nepal. He and other members of the WordPress community in Asia, including representatives from India, Japan, Indonesia, Thailand, Sri Lanka, Singapore, and Nepal, had the opportunity to meet at WordCamp Europe.

“We have been talking about WordCamp Asia informally when some of us attended WordCamp US for the first time,” Shrestha said. “That’s was in 2015, where I met Naoko Takano. She is the one with the main idea as the Japanese WordPress community was already doing well. Then we started meeting more people from Asia at WordCamp Europe 2016 and had an informal meeting there.”

After this meeting, Rahul Bansal created a Facebook group for WordPress Community Organizers in Asia to support each other in a more coordinated effort. The first formal meeting happened at WordCamp Europe 2017 where the team decided that trying for WordCamp Asia in 2018 would be too soon. Instead, they are planning to host a WordSesh Asia event in 2018 to work on their coordination and teamwork. The team is working towards hosting WordCamp Asia in 2019.

Organizers Consider Bangkok as a Possible Location for WordCamp Asia in 2019

Shrestha’s post identifies several challenges that are unique to hosting a large scale WordCamp in Asia, including the need for visas even for travel within Asia, political instability, and numerous currencies and languages in use.

“WordCamp Asia is really important for the WordPress community in Asia,” Shrestha said. “I am fortunate enough to attend WCUS and WCEU, which are some of the biggest WordCamps where we get to meet lot of WordPressers, share and exchange ideas, contribute to WordPress, start a new business, and think outside of the box. But for most of Asians, it’s really difficult to go that far and also it’s expensive to attain those. So, we are limited to WordCamps in our own country and neighboring ones. That is why we are thinking about WordCamp Asia in Bangkok, which will be really inclusive as it’s in the center part of Asia and it’s cheaper to go there and less time consuming for all.”

Shrestha also feels strongly about providing travel assistance for those with financial hardships, as the most expensive aspect of attending a WordCamp is usually the travel and accommodation.

“WordCamps are not just for the rich,” Shrestha said. “The primary motive of WordCamps is to grow the local community. So, WordCamp Asia’s mission will be to influence the community of WordPress Asia and help it to grow. That is why, instead of planning for a grand and pompous event, we need to make sure it is affordable and reachable to people of all financial backgrounds.”

Shrestha said he has seen major changes in working with the WordPress community in Nepal from 2012 – 2017, which he attributes to having a stronger local presence with the WordCamp. India has also benefited from hosting WordCamps and has approximately nine happening in various cities. They are working towards hosting a WordCamp India in the future. There are also emerging communities in Singapore, Thailand, Indonesia, Sri Lanka, Cambodia, and Vietnam.

“It’s time for pursuing WordCamp Asia,” Shrestha said. “We really have good talents here in Asia but we lack exposure. WordCamp Asia can create buzz and make more people aware, inspire, and provide opportunity.”


Source: planet

WPTavern: Jesse Petersen, Founder of Genesis The.me Passes Away

Petersen Family

Jesse Petersen, founder of Genesis The.me and Petersen Media Group, has passed away at the age of 38. Petersen had been battling Cystic Fibrosis for the past several years and suffered a massive lung bleed earlier today. He passed out before paramedics could reach him and could not be revived at the emergency room.

Petersen was on a double-lung transplant list with a lung allocation score of 38.859. The LAS is a score used to prioritize waiting list candidates based on a combination of wait list urgency and post-transplant survival. Last month, Petersen received the phone call he had been waiting for.

Unfortunately, the lungs were determined not to be in a suitable condition for transplant.

He shared his experience in a raw, emotional post that describes the highs and lows he felt that day. “While the day was an emotional roller coaster, with the highs being WAY up there, the lows were surprisingly mild,” Petersen said. “They just weren’t the right lungs, and this protected me from years of issues, so it’s all good. The call for the perfect lungs for me will come in God’s timing. I am content to wait.”

On July 2nd, a patient with a higher LAS score than Petersen’s was taken into surgery to receive a double-lung transplant. This made Petersen the highest priority pending a match was found but a match wasn’t found in time.

I did not have the opportunity to meet him in person. From those who knew him personally, Petersen was a great husband, father, and a caring individual who despite his medical situation, would help out the best way he could. There are two stories that highlight the kind of person he was. The first is a Twitter thread he published two days ago.

When you meet a 5 year-old who needs a heart and double-lung transplant but has been turned down everywhere, your situation doesn’t seem so bad. That family doesn’t care about politics, social class, keeping up with the Joneses, or whether their clothes match. They are enjoying life.

Because when it comes down to it, all we really need is to know our worth and love everyone else because they have equal worth. That doesn’t mean you have to agree with everyone, but you don’t have to seek out opposition or turmoil. Random acts of kindness rock.

Can you look over your life and say you’d be leaving those connected to you better off having known you? If not, start today.

The second is from his Facebook account about an encounter he had with a mother pushing her small boy in a wheelchair with a surgical mask on.

I finally got out of the house to go do a God & Country service followed by fireworks. While waiting to go outside, a mom I’d seen pushing a small boy in a wheelchair with a surgical mask and oxygen on him came over to me.

‘I just wanted to say how cool I think your double tank cart is. I’m going to call my supplier tomorrow to get one for our wheelchair.’

We started talking (most unlike me) and she said her son needed a heart and a double lung transplant… but they’ve been turned down everywhere, starting with the very forgiving Pittsburgh center.

‘I’m so sorry.’

[nodded her head with a pained look] ‘We’re just making the most of our time now.’

My heart broke. I’ve already lived 7 of his lifetimes. I’ve played sports, graduated from college, stood on the equator, married my best friend, and have two healthy boys.

So kick me the next time I complain about my wait, OK?

Members of the WordPress community are using social media to share memories, grieve, and pass along condolences to his family.

Petersen’s family has created a crowd-funding campaign to help offset funeral and medical expenses. Since its creation, the community has donated more than $12K of $20K. If you are able, please consider donating as Petersen was the sole provider of income for his family.

My deepest condolences go out to his friends and family. Petersen is survived by his wife and two sons.

Related Reading:

The Loss of One of Our Own


Source: planet

WPTavern: WPWeekly Episode 280 – Behind the Scenes of Tuniversity

In this episode, John James Jacoby and I are joined by Kiko Doran and Travis Totz, Senior Web Strategist at Modern Tribe. Doran helped create Tuniversity, a revolutionary new way of learning music through a highly interactive iBook.

The project was so large, Doran outsourced some of the work to Modern Tribe, a web design and development firm. During the show, we learn the benefits of working with an agency you trust. Doran also explained what it was like to be a client as he’s normally fulfilling the agency role.

Two major takeaways from the Tuniversity project include:

  1. Work on things you’re passionate about with people who share the same passion.
  2. Approach problems with a positive mindset.

Near the end of the show, we discussed the news that WangGuard is officially closed.

Picks of the Week:

WPHierarchy.com is a WordPress resource created by Rami Abraham in 2013. The site is an interactive version of Michelle Schulp’s colorful diagram of WordPress’ template hierarchy. Each template is linked to documentation that explains its function

Dr. Russell A. Barkley (30 essential ideas everyone should know about ADHD)

WPWeekly Meta:

Next Episode: Wednesday, July 12th 3:00 P.M. Eastern

Subscribe To WPWeekly Via Itunes: Click here to subscribe

Subscribe To WPWeekly Via RSS: Click here to subscribe

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

Listen To Episode #280:


Source: planet

WPTavern: Gutenberg Contributors Explore Adding Drag-and-Drop and Multi-Column Support for Blocks

photo credit: ruudgreven DSC_0012(license)

The new Gutenberg editor has an open ticket for allowing users to sort blocks via drag and drop. Blocks can currently be sorted with up and down arrows located to the left of the content but the beta only allows for single-column stacking.

One of the goals for Gutenberg is to provide “a page building experience that makes it easy to create rich post layouts.” As far as layout building goes, the first planned versions of the new editor are very primitive as compared to Wix and Weebly’s drag and drop website builders where nearly every element on the page can be easily moved to a different position.

Contributors have been discussing the intricacies of adding this feature to Gutenberg since February. James Nylen summarized some of the challenges that make drag and drop more complicated to implement:

Dragging and dropping a block is not really a one-step operation. It is more like 3:

  1. Press and hold mouse button or screen
  2. Move to desired location
  3. Release

Step 2 is incredibly difficult to get right, and requires a lot of complicated behaviors like duplicating an item (or at least its general shape and size), scroll handling, and determining the intended new location, especially at the beginning and end of the content. We have all used bad drag-and-drop experiences, and I would argue they are worse than not having it at all.

That said, for two-dimensional movement with columns, I agree that arrows alone are probably not a good solution. Though mobile support for that is going to be very tricky no matter how it works.

Several commenters on the ticket agree that repeatedly clicking arrows to move blocks is cumbersome and will become untenable in the future when multi-column support is added. This would require up, down, right, and left arrows to rearrange content. Users have come to expect a drag-and-drop interface, because nearly every page builder application offers it.

“We are thinking of drag and drop as a progressive enhancement for desktops,” Joen Asmussen said. “One that would be great to have, but we should build it after we have explicit button actions in place for doing the same, including splitting into columns in the future. This decision is based on a desire to ensure accessibility as well as mobile devices can play the same game.”

Asmussen marked the ticket priority as low in May and removed it from the beta milestone. At this point, users are not likely to see drag and drop in the first release that ships with WordPress core.

Multi-Column Layouts Planned for Gutenberg V2

The discussion surrounding adding drag-and-drop to the editor naturally leads into adding multi-column support. Limiting users to a single column is a one-dimensional approach to designing pages, but contributors don’t plan to leave Gutenberg without multi-column support for long.

Geoarge Olaru, a designer at PixelGrade, shared a prototype for adding a simple two or three-grid column layout to Gutenberg.

“Extending WordPress further from the default Blog Posts automatically implies the need of multi-column layouts for presentation pages,” Olaru said. “I would prefer to tackle this feature upfront, rather than letting every developer do it on his own (see the multitude of page builders plugins).”

“For the V1 editor, I’m afraid columns like this is out of scope,” Asmussen said in reply to a Olaru’s ticket with mockups and a prototype for multi-column support. “That’s not a ‘no’ — rather, we need some technical foundations to be solid first, before we commit to the really interesting stuff. But it might be a V1.1, or at the very least something for the customization folks later on in the year. Even before that, it would be good to keep this UI in mind, so that perhaps a plugin can add this even earlier.”

Other commenters on the ticket feel more urgency about getting multi-column support into the first version of the editor. One of the concerns is that plugin developers will rush to add columns immediately based on demands from users, who will then have to migrate once core adds support.

“Multi column layouts are a must-have,” Anthony Hortin commented on the ticket. “At the moment, Gutenberg isn’t solving any issue. You still end up with one long column of content. The whole reason page builders are so popular, and why hundreds of thousands of people are using them, is because they provide the ability to easily make multi-column layouts. Without this functionality, you’re not providing any reason to use Gutenberg over a page builder plugin.”

One of the main challenges of adding multi-column support is figuring out what type of grid system to use and making sure that it scales from mobile to desktop. Weston Ruter joined the discussion to say that the foundational work for nested block support is being done now in version 1, but the UI for displaying them hasn’t been implemented yet.

“I appreciate the excitement and urgency to wanting columns,” Asmussen said. “We feel the same urgency. It’s not about not wanting columns, it’s purely about managing resources at this point.”

The good news is if you’ve been testing Gutenberg and wondering where some of these features are on the roadmap, they will be coming in later versions. While there may be disagreements about how much of a priority drag-and-drop and multi-column support should have for version 1, contributors agree that laying a solid technical foundation for these features is crucial for future extensibility.


Source: planet

WPTavern: Gutenberg 0.3.0 Adds Front-End Styles for Core Blocks, Notices Framework, and Text and Image Quick Inserts

Gutenberg development is marching ahead with version 0.3.0 released today. New releases are shipping out on a weekly basis, so testers will get to discover another round of new additions after updating to the latest. The changelog has a full list of the 50 additions and improvements included in this release, but here’s a quick visual tour of a few of the most interesting user-facing features added this week.

Gutenberg developers have added front-end styles for core blocks, which means that content like cover images will now appear the same as they look in the admin in the editor. The demo content in the plugin has also been updated to display a full-width cover image. Below is an example of a standard width cover image on the front-end.

Version 3.0 also includes new text and image quick inserts, which appear when hovering over the blank space beneath the post content. This makes it faster to add the types of content that are used most frequently.

This release adds a framework for notices, which provides developers with reusable notices components, showing how to trigger notices and where they will show up. Gutenberg now displays notices on post save, schedule, and update.

Version 0.3.0 adds a new block descriptions component to blocks with inspector controls. Several of the core blocks now display descriptions. These will be especially useful when plugin developers begin adding their own custom blocks, offering users a quick way to see the purpose of the block.

This release adds more placeholder text to various blocks, as “placeholders are key,” according to the newly added design blueprints and principles included in Gutenberg’s documentation:

If your block can have a neutral placeholder state, it should. An image placeholder block shows a button to open the media library, a text placeholder block shows a writing prompt. By embracing placeholders we can predefine editable layouts, so all you have to do is fill out the blanks.

Version 0.3.0 also adds several enhancements that make it easier to edit and customize the image-oriented blocks with more options and settings:

  • Added “edit image” button to image and cover image blocks
  • Added option to visually crop images in galleries for nicer alignment
  • Added option to disable dimming the background in cover images
  • Added option to display date and to configure number of posts in LatestPosts block
  • Added text formatting to CoverImage block
  • Added toggle option for fixed background in CoverImage
  • Added placeholder for all text blocks
  • Added placeholder text for headings, quotes, etc

Active installs for the Gutenberg plugin have nearly doubled since last week and are at more than 900 sites. This is roughly 1% of the goal Matt Mullenweg set for testing on 100,000 sites before replacing the edit screen. The plugin may also be advertised in the dashboard in a future release, possibly 4.8.1, which is slated for the end of July.


Source: planet

WPTavern: Popular WordPress Plugins Slow to Add Meta Box Support for Calypso

During the State of the Word at WordCamp US 2016, Matt Mullenweg announced that Calypso was plugin aware. Calypso is a REST API and React powered application for the desktop created by Automattic in 2015.

Developers with plugins active on 1M sites or more received an email invitation from Andy Peatling to begin building support for Calypso.

“Calypso is now plugin-aware,” Mullenweg said. “This pull request was merged today, and as a way to bootstrap this, we’re opening up for what I just described for plugins to create Calypso interfaces for what they’re doing.

“Basically saying, if you’re using Calypso on a site that has one of these plugins, let’s say WooCommerce, all of a sudden in the interface, there will be all the WooCommerce stuff. It’ll talk to the API, it will run on the desktop just like the rest of Calypso, and it will only be loaded if the plugin is active.”

One of the major differences between Calypso and WP-Admin is that custom meta boxes added by plugins are not accessible in Calypso.

Nearly seven months since the announcement, popular WordPress plugins have struggled to add meta box support, including those maintained by Automattic. WordPress SEO, active on more than 3M sites, is among the plugins that were selected to take part in the experiment.

When asked about the progress of making WordPress SEO Calypso aware, Joost de Valk, founder of Yoast.com, declined to comment.

Automattic has seen little progress on the initiative, “No news to report at this time, but hope to have some soon,” Automattic representative Mark Armstrong said. WooCommerce has yet to add meta box support and settings pages in Calypso.

Gutenberg, WordPress’ new editor, is also built using React. One of the chief concerns expressed by users and developers is how it will support custom meta boxes built using the current PHP framework.

“I miss a lot of the meta boxes I’m used to seeing on the screen,” Aaron Jorbin said. “Things like Yoast SEO (on some sites) and custom taxonomies are just not shown. If every meta box ever made for WordPress needs to be remade, it sure is going to make developers lives a living hell.”

I want to use Calypso as a replacement for WP-Admin because it’s fast and I like the interface. However, I can’t do that until it supports meta boxes for the plugins I rely on, such as Edit Flow. Is the lack of custom meta box support for Calypso a sign of what’s to come with Gutenberg?


Source: planet

WPTavern: WordCamp Netherlands Reinstated for 2018

At WordCamp Europe I had the opportunity to speak with WordCamp Netherlands organizers Marcel Bootsman and Luc Princen, along with WordPress Global Community Team members Josepha Haden and Andrea Middleton. The group has had several conversations about the future of WordCamp Netherlands, which was shut down earlier this year in favor of city-based WordCamps, and have decided to reinstate the camp with a few conditions.

WordCamp Netherlands organizers are now allowed to begin planning the event again based on the requirement that the country host three city-based WordCamps first. There are currently two local camps on the schedule and a few others in the pre-planning stage. Lead organizer Marcel Bootsman is aiming to have 500 attendees for the next WordCamp Netherlands in 2018.

In a recent interview with Torque, Matt Mullenweg indicated that the outlook is good for future regional WordCamps.

“I think we got to the point where we were too rules-based and now we’re starting to open up the process and be more agile in the approach to WordCamps,” Mullenweg said. “We can start to think about regional WordCamps and topic-focused WordCamp…we want to think about which WordCamps make sense to move the community forward.”

In our interview below, WordPress Global Community Team members said they plan to take similar country-based WordCamp proposals on a case-by-case basis. WordCamp Netherlands is pioneering the way for other countries with active local communities to continue to push the boundaries of the previously “one-size-fits-all” approach to WordPress events.


Source: planet

WPTavern: WPWeekly Episode 279 – The Future of Underscores with David A. Kennedy

In this episode, John James Jacoby and I are joined by David A. Kennedy. Kennedy is a Theminator at Automattic and an accessibility advocate. Kennedy joined us to talk about the future of Underscores, a starter theme created by Automattic in 2012.

We discussed how Gutenberg may impact theme development in general and some of the lessons learned from their Components project. Kennedy tells us what trends he’s noticing with WordPress themes today and what the state of accessibility looks like for the theme landscape.

After the interview, Jacoby and I have a candid conversation about Gutenberg, what it means for WordPress, our experience with it thus far, and how it’s being developed.

Stories Discussed:

WordPress 4.9 to Focus on Managing Plugins and Themes, Gutenberg Targeted for 5.0

Links Mentioned:

Accessibility Weekly – Kennedy’s hand-curated newsletter about web-accessibility delivered weekly.
WordPress Theme Review Team
Gutenberg
Underscores

WPWeekly Meta:

Next Episode: Wednesday, July 5th 3:00 P.M. Eastern

Subscribe To WPWeekly Via Itunes: Click here to subscribe

Subscribe To WPWeekly Via RSS: Click here to subscribe

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

Listen To Episode #279:


Source: planet