Wordpress News

WPTavern: Tiny Raises $4M in Series A Funding, Publishes Gutenberg FAQ

Wordpress Planet - Fri, 10/12/2018 - 03:57

Tiny, the company formerly known as Ephox has raised $4M in Series A funding from BlueRun Ventures. Tiny is the company behind TinyMCE, a popular text editor used in many opensource projects, including WordPress.

In addition to the funding, Jeff Tannenbaum, partner at BlueRun Ventures is joining Tiny’s board of directors. The company has also launched Tiny Drive, a preview of TinyMCE 5, and the Tiny App Directory.

TinyMCE’s Relationship With Gutenberg

Gutenberg is built on top of TinyMCE and this has led to few misconceptions about the project. To alleviate these misconceptions, Tiny published a Gutenberg and TinyMCE FAQ earlier this year.

TinyMCE is used by the Classic Editor but as the FAQ explains, they are not one in the same and never have been.

The Classic Editor is less than TinyMCE in that it exposes just 6 of the 54 of the official plugins and a fraction of the UI. A popular WordPress plugin called TinyMCE Advanced created by Andrew Ozz exposes more of TinyMCE’s UI, core features, and plugins.

The Classic Editor is also more than TinyMCE in that there is significant custom code in WordPress. This includes WordPress-specific UI components and backend code for embedding, links, media, and more. Some of the filtering code is specific to WordPress.

Andrew Roberts

Gutenberg uses TinyMCE to provide rich text editing and provides a Classic editor block that contains some UI elements from TinyMCE, but that’s about it.

Both projects have a close relationship but as Roberts noted on TechCrunch, the two are not mutually dependent on each other.

“Tiny’s core business comes from a mix of software vendors, large enterprises, and agencies building custom solutions for clients that has little to do with the WordPress ecosystem,” Roberts told TechCrunch. “It is a popular and commercially viable project in its own right.

While TinyMCE 5 features a brand new UI, earlier versions such as 4.7 were inspired by beta versions of Gutenberg. Tiny is not yet committed to making block based editing the default but is keeping a close eye on how Gutenberg rolls out.

TinyMCE and WordPress are open source projects that will continue to benefit each other as it makes sense.

“The TinyMCE and WordPress projects have had a symbiotic relationship over the years. We hope that this goodwill and sense of community continues for many years to come,” Roberts said.

WPTavern: WPWeekly Episode 333 – Interview With Mike ‘Shredder’ Schroder

Wordpress Planet - Thu, 10/11/2018 - 09:07

In this episode, John James Jacoby and I are joined by Mike Schroder. Schroder co-led the release of WordPress 3.9 and in 2016, he led the release of WordPress 4.5.

In the interview, we learn his WordPress origin story, his thoughts on Gutenberg and whether or not he sees it as the future of WordPress, the WordPress media component, and near the end of the show, he explains how he received the nickname Shredder.

Useful Links Mentioned:

A Detailed List of Meetings of the Various WordPress Core Teams
New Contributors Bi-Monthly Meeting
WordPress Core Contributor Handbook
Mike Schroder and Tammie Lister’s Presentation from WCUS 2017 – Media Matters
GoDaddy Hires Mike Schroder to Contribute to WordPress Core Full-Time

WPWeekly Meta:

Next Episode: Wednesday, October 17th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #333:

WPTavern: Gutenberg 4.0 RC 1 Released, Testing Ramps Up Amid Critical Accessibility Concerns

Wordpress Planet - Thu, 10/11/2018 - 04:31

A pre-release of Gutenberg 4.0 RC 1 is now available for testing. During today’s core developer chat, Matias Ventura, the project’s technical lead, said he plans to post a full changelog and a video tomorrow. In the meantime, a call for testing 4.0 RC 1 has been posted to the make.wordpress.org/test blog with a list of 15 specific testing items highlighted for attention.

Gutenberg 4.0 introduces several new features, (including but not limited to) the following:

  • Add ability to change overlay color in Cover Image
  • New Font Size Picker with clear labels and size comparison
  • New RichText data structure to allow better manipulation of inline content
  • Add Pullquote style variation and color palette support
  • Add support for post locking when multiple authors interact with the editor
  • Add support for shortcode embeds that enqueue scripts.

A running list of the enhancements, bug fixes, and other changes is available on GitHub in the changelog. Deprecations for 4.0.0 are outlined in the Gutenberg handbook.

Grzegorz Ziółkowski has published Gutenberg’s npm packages this evening, so the team can move forward on core integration with Gutenberg.

Accessibility has been one of the recent concerns with the project, as there are many outstanding tickets with this tag. One of the most prolific contributors to testing, Andrea Fercia, has stated that the editor in its current state is “barely usable” for those with accessibility needs. Joe Dolson, another WordPress accessibility contributor, wrote a reaction post that concurs with Fercia’s assessment.

“The leadership within the Gutenberg project has not taken seriously the scope of accessibility problems in Gutenberg,” Dolson said. “I do not want to diminish the dedication to accessibility issues at some levels. The dedication to producing accessible content is still very high. But I’m not seeing dedication to developing an accessible authoring tool. It’s as if there’s no awareness of the needs of authors with disabilities; only consumers.”

If WordPress 5.0 is released on schedule, Dolson said he believes it is “almost a guarantee that the first release of Gutenberg in WordPress will not be accessible,” as there are too many major accessibility issues left to resolve.

Matthew MacPherson, the new accessibility lead for WordPress 5.0, said he is willing to bet that Gutenberg is more accessible than the Classic Editor and that the perception of its inaccessibility is based on older evaluations of earlier releases:

I think there’s a notion of Gutenberg being inaccessible because of older accessibility audits that identified a lot of issues in the very early versions. Things have changed a lot since the early days, and when the plugin was labeled “1.0” it was hardly a ready-to-ship product. I worry that many of those sentiments haven’t been re-examined and updated, so there is a prevailing idea that Gutenberg is not accessible or is entirely less accessible than the Classic Editor.

What I’d venture is that Gutenberg is selectively less accessible, but overall more accessible feature-for-feature. Something like a date picker or a certain interaction being inaccessible does not make the entire editor inaccessible. Feature-for-feature, compared to a classic editor with similar capabilities (eg a bunch of plugins installed), I’d bet* Gutenberg is more accessible.

Despite his suggestion that Gutenberg’s current accessibility issues are likely not as critical as contributors have claimed, MacPherson is willing to coordinate an independent accessibility audit to get an outside opinion. Selection of the company to perform the audit is currently in process.

After the recent resignation of team rep Rian Rietveld, accessibility contributors are meeting next Monday to get reorganized and discuss the leadership and decision processes of the team.

Many have speculated outside of official channels on whether the recent shakeup in the leadership of the accessibility team is a referendum on the aggressive timeline for Gutenberg’s inclusion in core or simply the natural turnover in open source projects when friction cannot be resolved. A truly independent accessibility audit, with results that are shared transparently to the WordPress community, will reveal whether current perceptions of Gutenberg’s lack of accessibility are accurate.

In the meantime, a new “Needs Accessibility Feedback” label is available for use on the Gutenberg GitHub repository to facilitate communication between developers and accessibility contributors. There is also a label for regressions where changes broke accessibility along the way.

WPTavern: Jetpack 6.6 Improves Site Verification Tools, Asset CDN Module Now in Beta, Gutenberg Blocks Coming Soon

Wordpress Planet - Tue, 10/09/2018 - 22:19

Jetpack 6.6 was released today with an update to the Site Verification tools that enables one-click verification and sitemap.xml registration with Google.

This release also introduces the beta of Jetpack’s Asset CDN. The new module, built on the same infrastructure as the Photon CDN, speeds up sites by cloud-hosting widely-used Jetpack and core WordPress scripts, styles, and assets. It takes a load off of users’ servers and increases the allowed maximum concurrent connections through Photon. Once it is ready for use in production, the Asset CDN will be a new opt-in feature that can help speed up Jetpack’s 5+ million active installations.

Version 6.6 also adds the necessary infrastructure for new Gutenberg blocks. The activity on the plugin’s GitHub repository indicates the team is working on a number of blocks for existing features, including things like recipes, shortcodes, Jetpack subscription form, Simple Payments, Publicize, the contact form, tweet shortcode, VR shortcode, Giphy, and more. Everything touching the editor is in the process of being ported to blocks. Many of the blocks are already complete and some are still in progress. Some features, such as support for tiled gallery layouts, have bugs that need to be sorted before Jetpack will be ready for WordPress 5.0.

Jetpack 6.6.1 will be going out soon to address a bug with social icons that this release introduced. In the meantime, users can paste the CSS in this gist into Appearance > Customize > Additional CSS to provide a temporary fix.

WPTavern: WordPress Accessibility Team Lead Resigns, Cites Political Complications Related to Gutenberg

Wordpress Planet - Tue, 10/09/2018 - 16:27

WordPress Accessibility Team lead Rian Rietveld has resigned due to what she describes as political complications and problems with working on Gutenberg accessibility.

“The last year, especially the last few weeks have been too politically complicated for me,” Rietveld said. “It’s better that someone else takes the lead now.”

Her post outlines challenges the accessibility team has encountered in working with Gutenberg without having a skilled React developer on their team. Their contributions have primarily been limited to testing and reporting issues. Rietveld said team members experienced frustration when they tested and improved functionality but saw it changed at a later stage, breaking accessibility requirements again. She also cites a lack of commitment to keyboard testing new features before implementation.

Rietveld said she used her network to try to get more companies and developers with React skills involved in Gutenberg accessibility contribution. In March, tests they ran on the plugin revealed a staggering number of Gutenberg accessibility issues that remain unresolved.

“The results indicated so many accessibility issues that most testers refused to look at Gutenberg again,” Rietveld said. She included a statement from fellow contributor Andrea Fercia, who has been highly active in testing Gutenberg functionality and reporting issues:

While the Gutenberg team has worked hard to implement some fundamental accessibility features (e.g. focus management, navigate landmark regions), the overall user experience is terribly complicated for users with accessibility needs at the point the new editor is barely usable for them.

The main reason for this lack of overall accessibility is in the overall Gutenberg design, where accessibility hasn’t been incorporated in the design process.

Feedback from accessibility users has been constantly evaluated and Gutenberg is actually a regression in terms of accessibility level, compared to the previous editor.

The Gutenberg project now has a dedicated developer from Automattic, Matthew MacPherson, who is working on accessibility issues and Rietveld said she hopes the core accessibility team will continue to offer him all the support he needs.

Rietveld’s resignation is a major loss to the WordPress project. For years her leadership and contributions have demonstrated the project’s commitment to serving those with a disability.

In 2016, she was instrumental in WordPress adopting accessibility coding standards for all new and updated code. Rietveld was recognized by Knowbility.org as “a knowledgeable, dedicated, and effective advocate for accessibility in the global WordPress community,” whose achievements had a major impact on the application used by more than 25% of the world at that time. She took first place in the Individual Achievement category of the Heroes of Accessibility Awards.

News of Rietveld’s resignation roused an outpouring of sadness and gratitude on Twitter. The WordPress community thanked her for her work and that of other accessibility contributors, whose efforts often go unappreciated.

“I’m not leaving WordPress nor accessibility, and in fact maybe now I can actually work on accessibility again,” Rietveld said. “I will keep giving talks and workshops. I also want to do research and work on tickets. But in my own pace.

“I will join the a11y table if asked on contributor days, but maybe I’ll just go to a museum instead.”

WPTavern: Alexis Lloyd and Riad Benguella Will Lead Phase Two of Gutenberg

Wordpress Planet - Tue, 10/09/2018 - 01:52

As activity ramps up to try to get WordPress 5.0 released in November, Matt Mullenweg has announced who will lead phase two of the Gutenberg project. Phase two focuses on Customization and entire site layouts.

Alexis Lloyd, Head of Design Innovation at Automattic, will handle the design and product side. Riad Benguella, a JavaScript Engineer at Automattic, will handle the technical side of the project.

One of the goals of phase two is to replace widgets with blocks and menus with a navigation block. Lloyd and Benguella commented on the post, introducing themselves to the community.

“Hi all! I’m thrilled to be working on phase 2 of Gutenberg,” Lloyd said. “I think there’s a huge opportunity to take the ease of use that has been brought to page/post editing in phase 1 and extend that to the full site experience.

“I’m coming from many years leading design and product teams in news organizations (including designing and building custom CMSes), and am looking forward to bringing my experience to WordPress, as well as learning from the deep expertise in the community!”

“Hi all! I’m so excited to be working with you all alongside @alexislloyd to build upon the amazing technology that is Gutenberg in order to bring the content creation experience in WordPress to a whole new level,” Benguella said.

“For those who don’t know me yet, I’m a JavaScript engineer at Automattic. I’ve been fortunate to have contributed to the Gutenberg project since its beginning, including a lot of work on Gutenberg APIs, JavaScript in Core, and Accessibility.

“I look forward to bringing my humble expertise to achieve the second phase of this project, as we look into things like widgets, menus, templates, and site-building in general.”

Theseus’s Paradox Makes More Sense Now

In episode 331 of WordPress Weekly, one of the items we discussed with Gary Pendergast is the future of Gutenberg beyond the editor. At its core, Gutenberg is supposed to unify a number of areas of WordPress.

Blocks are the unifying evolution of what is now covered, in different ways, by shortcodes, embeds, widgets, post formats, custom post types, theme options, meta-boxes, and other formatting elements. They embrace the breadth of functionality WordPress is capable of, with the clarity of a consistent user experience.

From the Gutenberg Plugin Page

I hypothesized that since Gutenberg is an interface to manage blocks and that menus as well as widgets will become blocks, the menus and widget management pages in the WordPress backend can be replaced or removed in favor of Gutenberg.

In this way, the Menu and Widget management boards on the Ship of Theseus would be replaced without sinking or disrupting the entire boat.

With Mullenweg’s announcement regarding phase two, the Ship Of Theseus or Theseus’s paradox begins to make more sense. Gutenberg becomes the foundation for bringing many areas of the WordPress project up to par without starting from scratch.

WPTavern: Miami WordPresser Todrick Moore Passes Away

Wordpress Planet - Tue, 10/09/2018 - 00:24
Todrick Moore Courtesy of David Bisset

Fellow WordPresser Todrick Moore, a member of the Miami WordPress community and volunteer organizer of WordCamp Miami 2015 and 2016  passed away last week of Leukemia.

“Todrick Moore was one of the kindest and strongest members of the South Florida WordPress community, and I still to this day remember meeting him first at his local meetup,” David Bisset said.

“Like many people who come to meetups he was eager to learn, but also as I would quickly come to realize, he would be eager to help others as well.”

To learn more about Todrick and how to help out his wife with their WordPress business site, please read this post by David Bisset.

WPTavern: How the Student-Owned Pelham Examiner Uses WordPress to Empower Young Journalists

Wordpress Planet - Mon, 10/08/2018 - 20:52

When the News of Pelham became another casualty of the blighted newspaper industry, student journalist contributors lost a platform for their voices to be heard. Their advisor, Rich Zahradnik, called a meeting to address the paper’s closure. More than a dozen middle and high school kids showed up and decided to start their own paper: The Pelham Examiner.

Zahradnik is a former journalist who has been volunteering for years in the local elementary schools, teaching kids how to write news stories. Before the News of Pelham shut down he was acting as a liaison to recruit student contributors. He registered the Examiner as a corporation and the paper is also part of the New York Press Association.

The Pelham Examiner is an online-only publication that covers everything from local politics and crime to sports and entertainment. It is running on WordPress, using plugins like All-in-One Event Calendar and WP Polls to enhance students’ stories. The site uses the FLEX WordPress Theme by SNO, an organization that sells publishing solutions for scholastic news programs.

WordPress provided a cost-effective way to launch a student-run newspaper and students also found it to be intuitive for publishing.

“We chose to use WordPress mainly because of the ease with which we could use it and create a website look that worked for our goal,” Executive Editor Ben Glickman said. Zahradnik had used the platform with prior publications he had worked on with students at Colonial Elementary School.

“Several of the students who had worked on The Colonial Times loosely remembered some aspects of WordPress, but most of us had to learn from the beginning,” Glickman said. “I started with the basics (creating new articles, saving drafts, etc.) and worked my way up to the more complex stuff.” Most students contributing to the Pelham Examiner didn’t require much training to get up to speed with publishing articles.

“Personally, I thought that much of WordPress was rather intuitive, so learning was not too hard,” Glickman said. “I haven’t had any problems with WordPress so far. I’ve been especially impressed with how easy it is to integrate all kinds of story elements into a given story.”

Poynter published a story last week about the enthusiastic and highly motivated group of young journalists behind the Pelham Examiner. For now the publication is self-sustaining with volunteer contributions, but Zahradnik told Poynter that he is open to ads or investors in the future.

Sustaining the news as a business is another skill the students will need to learn as the publishing industry is increasingly demanding more creative revenue models from journalists who want to work independently. Zahradnik told Poynter that the Pelham Examiner’s student-owned online paper could be a model for other places that are no longer able to support traditional local newspapers.

The News of Pelham was a bi-weekly, print-only publication before it closed its doors. With a WordPress-powered website, students can get the news out faster, publishing every day with virtually no overhead costs.

“I think the model for the Examiner is absolutely reproducible,” Glickman said. “For the relatively small price of a startup fee and annual hosting and support fees, you can essentially have the same type of town or city coverage with a conventional town newspaper.”

YG Logistics

Drupal Themes - Mon, 10/08/2018 - 15:09

YG Magazine

Drupal Themes - Mon, 10/08/2018 - 15:07

YG Magazine is modern and feature-rich Drupal theme developed to help you to create a stunning website for Magazine and News.


  • Drupal 8 core
  • Bootstrap v3.0.0
  • Lastest News
  • Featured News

Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation

Other YG Business themes


Drupal theme by Young Globes

YG Medicare

Drupal Themes - Mon, 10/08/2018 - 11:32

YG Medicare is modern and feature-rich Drupal theme developed to help you to create a stunning website for Clinics and Hospitals.


  • Drupal 8 core
  • Bootstrap v3.0.0
  • Treatments
  • Gallery
  • Patient Information
  • Team
  • Testimonials

Theme Dependency : Bootstrap

Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation

Other YG Business themes


Drupal theme by Young Globes

YG Simple

Drupal Themes - Sat, 10/06/2018 - 14:45

YG Simple Drupal 8 responsive theme for websites.


  • Drupal 8 core
  • Bootstrap v3
  • Services
  • About
  • Team

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation

Other YG themes

  • YG Booster: A free bootstrap based Drupal 8 theme with modern design for products and business
  • YG Newage: an app landing page theme built using bootstrap
  • YG Agency: Theme perfect for portfolio and agency websites
  • YG Flew: Theme perfect for business websites


Drupal theme by Young Globes

YG Insurance

Drupal Themes - Sat, 10/06/2018 - 11:57

YG Insurance Drupal 8 responsive theme for Insurance Agents, Agencies and similar.


  • Drupal 8 core
  • Bootstrap v3
  • Services
  • Testimonials
  • Clients

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation

Other YG themes

  • YG Booster: A free bootstrap based Drupal 8 theme with modern design for products and business
  • YG Newage: an app landing page theme built using bootstrap
  • YG Agency: Theme perfect for portfolio and agency websites
  • YG Flew: Theme perfect for business websites


Drupal theme by Young Globes

WPTavern: WordPress Theme and Plugin Shops are Pioneering the First Layout Blocks for Gutenberg

Wordpress Planet - Thu, 10/04/2018 - 15:24
photo credit: Jeffrey Betts

Many WordPress theme shops started out with themes as their only products but over the years have moved into selling plugins that enhance their core products. This came about partially because theming standards evolved to encourage developers to put non-presentational functionality into plugins. For many, the revenue from plugins quickly eclipsed that of their theme products. In the past, theme shops have often partnered with page builder plugins to enhance their users’ capabilities in customizing the themes. This may soon change, as the advent of Gutenberg is bringing new product opportunities to theme and plugin shops shops.

The first iteration of the new editor focuses on blocks and the post editing experience. After Gutenberg is in core, the project will move on to the second phase – full site customization. This will venture into page builder type functionality. Matt Mullenweg predicts this phase will happen much faster than phase 1, since all of the infrastructure is already in place. The plugin already has a columns block in beta.

Gutenberg is scheduled to debut in WordPress 5.0 in November, but site customization functionality won’t arrive until 2019 at the earliest. In the meantime, plugin developers have been experimenting with various implementations of “section” and “container” blocks while the Gutenberg team explores a core container block for phase 2.

Marie Comet’s WP Container Block is a fork of the core columns block that offers columns structure, spacing, and backgrounds (with both image and color controls). Felix Arntz recently published a tutorial on how he built a reusable Gutenberg section block. Marc Lacroix created his own container block, out of necessity, with capabilities for spacing and background customization.

Section/container blocks are a precursor to using Gutenberg for building more complex layouts. Some of these explorations may inform the Gutenberg team’s implementation of a core container block in the future.

A few more full-featured layout blocks are starting to pop up on WordPress.org. Kadence Themes, a theme and plugin shop based in Missoula, Montana, released its Kadence Blocks – Gutenberg Page Builder Toolkit at the end of August. The plugin brings the editor closer to delivering the features users expect from popular page builders, such as better control of columns for different screen sizes and a row/layout block with controls for padding, backgrounds, alignment, and overlays with gradients.

A live “Frontenberg” style demo of Kadence Blocks is available where you can see the plugin’s options for manipulating page layout.

Pootlepress, a WordPress plugin and theme shop, has added a new Layouts block to its free Caxton plugin. The company is one of the earlier Gutenberg adopters in the WooCommerce space with its recent release of the Storefront Blocks plugin.

Caxton bills itself as a “page layout plugin” for Gutenberg. Its layout block allows users to select from a number of preset layouts and then add blocks within those layouts. It supports nesting rows and row backgrounds. A Frontenberg demo site gives users the chance to play around with the page builder functionality before installing the plugin.

Until Gutenberg adds core support for more layout capabilities, WordPress may see an influx of these layout blocks that introduce basic page builder functionality. Some of these plugins may need to be refactored once there is more direction for these features in core, but they offer a glimpse of what Gutenberg will bring to site customization. Combined with Gutenberg 3.9’s reusable, exportable templates for multiple blocks, page layouts will become more portable than ever. In 2019, we may see new sites popping up that enable users and developers to share the layout designs they have created.

WPTavern: WPWeekly Episode 332 – The WordPress 5.0 Release Cycle Begins

Wordpress Planet - Thu, 10/04/2018 - 00:30

In this episode, John James Jacoby and I discuss the headlines making the rounds in the WordPress community. This includes the start of the WordPress 5.0 release cycle, the 5th annual Hacktoberfest, and theme developers marketing their themes as Gutenberg-compatible. Near the end of the show, I describe how much of the press surrounding WordPress security issues is poorly written and John talks about the benefits of being in the same physical space as your co-workers at least once or twice a year.

Stories Discussed:

WordPress Theme Developers Begin Marketing Themes as Gutenberg Compatible

First Wave of WordCamp Europe 2019 Tickets Sells Out in 3 Hours

5th Annual Hacktoberfest Kicks Off Today, Updated Rules Require 5 Pull Requests to Earn a T-shirt

Matt Mullenweg Announces WordPress 5.0 Release Plan, Estimates Release Candidate to Ship in November

GoDaddy Hires Mike Schroder to Contribute to WordPress Core Full-Time

WPWeekly Meta:

Next Episode: Wednesday, October 10th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #332:

WPTavern: WordPress 5.0 Slated for November 19, 2018

Wordpress Planet - Wed, 10/03/2018 - 23:23

A tentative 5.0 release schedule was published during today’s core dev chat. The official release is targeted for November 19, 2018 with beta 1 expected October 19 and RC 1 released October 30.

In addition to getting Gutenberg merged into core, the scope for 5.0 includes a few new items that Gary Pendergast outlined in his post:

  • Updating the default themes to work well with the block editor, and creating the new Twenty Nineteen theme.
  • Creating an upgrade experience to remove the Gutenberg plugin and offer the Classic Editor plugin.

November 19 is the week of the Thanksgiving holiday in the U.S., when many are traveling or spending time with friends and family. As this is scheduled during a busy time of year and may have unexpected delays, the release leads have come up with a backup plan that includes a secondary schedule.

“We know there is a chance that 5.0 will need additional time, so these dates can slip by up to 8 days if needed,” Pendergast said. His post proposes an additional timeline that would have 5.0 land in January:

Secondary RC 1: January 8, 2019

Secondary Release: January 22, 2019

“The current release date is November 19, but it can be pushed as late as November 27 if needed,” Pendergast said. “To avoid the numerous holidays from the end of November through to January, we’ll move the release to January if more time is needed.”

Although the backup timeline should allay concerns about December holidays, if the release is at all delayed, it will run up against the Thanksgiving holiday.

“Should we need to switch to the secondary dates, this will be communicated as soon as we’re aware,” Pendergast said. “It’s also important to note that we have some updates for PHP 7.3 compatibility that must be released in 2018 regardless, and we would have a short 4.9.9 release cycle for them if needed.”

Contributors had the opportunity to ask questions of the release leads during today’s 5.0 kickoff meeting. There was some uncertainty in yesterday’s announcements about whether 5.0 will ship a new default theme. Matt Mullenweg confirmed that they are aiming to get Twenty Nineteen into 5.0.

“It’s the biggest variable though, so if it takes longer we won’t delay the release for it,” Mullenweg said.

Twenty Nineteen development will happen on GitHub and contributors can join the discussion in the #core-themes Slack channel where regular meetings will happen.

Gutenberg engineer Riad Benguella posted a technical overview of the integration process for merging the new editor into core. He also laid out a plan for how Gutenberg development will continue in the future.

“After WordPress 5.0 is released, the Gutenberg plugin will continue to exist,” Benguella said. “Its purpose will be changed to the development and the maintenance of the WordPress npm packages, including the editor itself, and will also serve to develop the second phase (site customization) of the Gutenberg project. Plugin updates will continue to be released during the 5.0 cycle.

“The PHP part of the plugin won’t be needed anymore, as the plugin will just register new versions of the scripts of the packages to replace the ones already registered by Core.”

Mullenweg confirmed during the dev chat that the team plans to add a link to the Classic Editor plugin in the admin when 5.0 ships. Overall, contributors in attendance seemed excited about the prospect of finally having the new editor in core, despite the ambitious timeline proposed for release.

“A big benefit even beyond the user improvements is that plugin and theme developers will be able to truly use it as a base in a way that they can’t right now as a plugin,” Mullenweg said. “If previous adoption curves hold true, we’d be on 10m sites (20x current adoption) by new year.”

Gutenberg development has been moving quickly and after it is shipped to millions of WordPress users there are bound to be more issues discovered. Mullenweg said quick point releases may be an option for maintaining the flexibility to introduce fixes and improvements in a timely way for users.

“Since 5.0 will be very tight (just Gutenberg, PHP 7.3, and possibly theme) I am open to having 5.0.x releases that are like the 4.9.x releases that bring in some larger updates or improvements we push off, like servehappy stuff,” he said.

Gutenberg technical lead Matias Ventura has outlined the tasks remaining on the editor. An updated schedule for the 5.0 release cycle is now available for the public to follow. Gary Pendergast, who is shepherding the merge, said he expects WordPress 5.1 will be available around March 2019.

WPTavern: GoDaddy Hires Mike Schroder to Contribute to WordPress Core Full-Time

Wordpress Planet - Wed, 10/03/2018 - 05:57

Mike Schroder known at GetSource on Twitter and Mike on WordPress’ Slack instance is joining Aaron Campbell at GoDaddy to contribute to WordPress full-time.

Since 2011, Schroder has contributed to nearly every version of WordPress. In 2014, Schroder co-led the release of WordPress 3.9. In 2016, he lead the release of WordPress 4.5. He’s also an accomplished speaker presenting on various topics at WordCamps across the world.

According to Gabriel Mays, WordPress products and strategy leader at GoDaddy, Schroder will continue to work on the Media component in WordPress, lead the WordPress Hosting Community work group, and help merge Gutenberg into WordPress 5.0. 

WPTavern: Matt Mullenweg Announces WordPress 5.0 Release Plan, Estimates Release Candidate to Ship in November

Wordpress Planet - Wed, 10/03/2018 - 03:19

Matt Mullenweg has announced a plan for releasing WordPress 5.0 with a tentative estimate for a release candidate to ship in November.

“With known knowns and known unknowns, I believe we will be at RC in about a month,” Mullenweg said. “However, I’ll be keeping a close eye on feedback during the beta process and adjust as needed and keep the community fully up-to-date with our best estimate.”

Gutenstats.blog shows that the beta plugin has passed 490,000 active installations, which Mullenweg said “far exceeds pre-release testing of anything that has ever come into core.” The Classic Editor plugin also has more than 400,000 installations, indicating nearly half a million site owners have already prepared to preserve their existing workflows.

“If we keep the 5.0 release to strictly 4.9.8 + Gutenberg, we will have a release that is both major and a non-event in terms of new code,” Mullenweg said. “It’s all battle-tested. In some ways 5.0 is already de facto out in the wild, with some forward-looking hosts already installing and activating Gutenberg for new installs.”

Mullenweg is leading the release but has designated 11 other leads to head up various focuses, including triage, design, JavaScript packages, REST API, merge process and several other important aspects of the release.

WordPress users can also expect a new default Twenty Nineteen theme to ship with 5.0. Designer Allan Cole will be leading that project, which involves adapting an existing Gutenberg theme for use as WordPress’ next default theme.

Last week’s developer chat left many attendees wondering about the status of WordPress 4.9.9. Contributors discussed the possibility of making it a quick PHP 7.3 compatibility release but it now appears to be all hands on deck as the focus shifts to 5.0.

Based on today’s announcement, it seems very likely that WordPress 5.0 will land before the end of 2018, barring any major impediments. The timeline for this major release falls during a busy time of year for many who will be responsible for preparing their products and client sites. Mullenweg said he will keep the community up-to-date as the release cycle progresses. The agenda for tomorrow’s dev chat will focus on 5.0 planning.

HeroPress: There Are No Shortcuts

Wordpress Planet - Wed, 10/03/2018 - 00:00

My name is JC and I make things for the web. I wear a lot of hats but my favorite one is as a WordPress developer. And I am here to tell you about my journey. It was not easy. There were no shortcuts. I had to crawl my way up every single step of the way. And I still have to, it did not become easier – not by a long shot. But I’ve accepted that in order to succeed I have to take the long way and that is basically two words long – WORK HARD.

When I was young, I wanted to be and do a lot of things. I wanted to be an astronaut, a lawyer, a geophysicist. I wanted a pet unicorn or a tiger or a lion or a snake. I wanted to be the first woman to roam the solar system, I wanted to be a world-renowned author. I never became nor did any of those but I did get a pet snake named Yudi and I have a lot of “pet” unicorns.

I studied engineering because it was the “IT” course during my time. Did I like it? Let’s just say that I had a lot of fun, a lot of heartaches, a lot of sleepless nights and leave it at that. But if you really want to know – what I really, really want to be right now is to be a TimeLord STAT, but I digress. I think, the main reason I took that course was because I didn’t want to be with a lot of girls. I didn’t want to compete and I was not really into all that girly-girly stuff. It all changed, by the way. I graduated and took the board – I did not pass. Much to the horror of my engineer dad. I never really wanted to be an engineer so I did not bother taking the board again, instead, I worked in a call center. My first work was as a tech support for Dell computers. I got to tinker with laptops and help seniors fix theirs thousands of miles away and I even got to experience them happily shouting telling me that I do not know what I am doing. Fun times.

I did that for a year and I decided that that was not the life for me nor the life I wanted my daughter to see me in.

So we went back home to Iloilo and had my second job there, this time as a Search Engine Optimization Analyst. Fancy title, but all I did was search Google for stuff and write stuff for Google to digest. My boss’ site was built on WordPress and I created content for him. That was my first contact with WordPress.

Working in that position for a few months bothered me, I know I am capable of more than just that (I am impatient and hard-headed and can’t keep my mouth shut – the perfect combination). So I read about web development. I didn’t know how to code – give me mathematical equations and I’ll solve it right away but all these HTML, CSS and whatnot were alien to me.

But I persevered, I never took a shortcut.

I studied for about a month and decided that I was ready. Plus, I’ve heard about this online job site where you can register to be a freelancer – it was quite new at that time but I gave it a go. If you’ve heard of oDesk (now Upwork), I was one of the first freelancers to join and I had the shirt to prove it. I don’t have the shirt now, but they sent it to me when they ran this contest for the freelancer with the longest work record.

I applied to one job and one of the requirements was WordPress. I didn’t know WordPress aside from using it as a blog, and I know HTML/CSS (in theory). Lucky me, the client who eventually turned into my longest online friend, took a chance on me. I did not exactly tell him that I did not know WordPress, instead I told him what he wanted to hear – That I CAN DO IT. And I did. I worked on designing and developing his website while studying WordPress.

And that was when my love affair with WordPress started. I continued to learn and gain experience throughout the years.

There are NO SHORTCUTS. Believe me, I tried looking for one and I failed. In order to succeed, you have to work hard and not take the easy way out. Learn, read, listen – do this every single day for as long as you can.

Although, my first client never really knew until now that I never had any idea what I was doing when I started working for him, I did get the job done (Dr. T, if you’re reading this – Thank you! I won’t say sorry, because that will denigrate all the things I’ve done and all the things I’ve learned over the years I was working with you). I persevered, I didn’t quit when the going got rough. Plus, WordPress has an amazing community and they are more than willing to help you out if you ever get stuck and I used them as a lifeline more times than I can remember.

Let me say this again, it was not easy. I went through a lot. Moving forward, all of my clients were from abroad, most of them naturally assumed that I am male because of my name. And I think that contributed to how they were responding to my emails or chat.

They treated me as an equal and responded in a way they wouldn’t had they known I am female.

And once they knew, it was really hard for them to back out since they know that I am capable of getting the job done.

I was brought up to always question the norm, to not back down simply because I am part of the so-called “weaker gender”. I speak my mind when I have to and when and where I choose to. Working in a male-dominated industry is pretty hard, gender bias is palpable in this industry. Plus, there are not a lot of women developers and that is really sad because without women – computing as we know it would not exist.

You see, women have a harder time getting into the world of information technology because it has become male-dominated. I have a first-hand experience in this, imagine me – a woman, an Asian and a Filipino at that working in a space where men are the be-all end-all. I will say it again, it was not easy.

Have you heard about the competence/likeability dilemma? The Heidi/Howard Roizen Case Study concluded that when women exhibit characteristics associated with leaders – like assertion, authority, and dominant behaviors – they tend to be disliked. Hence, women cannot be both competent and likeable.

So according to this study: My competence is inversely proportional to my likeability. Meaning the more competent I am the less my colleagues like me. I may completely and vehemently disagree with this conclusion on a personal level, but there is truth to it. What can we do about this? I guess the first step is to acknowledge that it exists and work from there. But do not just be aware of the problem, acknowledge it and make a conscious effort to see when you are unconsciously adding to the problem and act on it. I don’t have a magic solution, what I can do is help empower girls to realize that they are stronger than they think they are and that they can do more. I did it without any shortcuts, I studied, I persevered, I worked my ass off to get where I am right now and I am not done yet. I still have to study, to preserve and to work every single day.

My journey doesn’t end here, I still have a ways to go. I will continue to love what I do and I assure you, once you love what you do – you’ll work your ass off to make sure you continue to have and experience the joy of being able to do that thing that you love. Do not let your gender, your race or any of your biases define you. It is not a walk in the park, sure, but you have to always, always do your best to not regret doing something because you think you can’t. The only limit is YOU and nothing or no one else.

The post There Are No Shortcuts appeared first on HeroPress.

WPTavern: 5th Annual Hacktoberfest Kicks Off Today, Updated Rules Require 5 Pull Requests to Earn a T-shirt

Wordpress Planet - Tue, 10/02/2018 - 02:07

DigitalOcean, along with GitHub and new partner Twilio, are sponsoring the 5th annual Hacktoberfest. The event was created to encourage participants to make meaningful contributions to open source projects. Last year 31,901 completed the challenge, opening 239,164 pull requests in 64,166 repositories.

In previous years, participants were required to submit four pull requests to GitHub-hosted public repositories during the month of October in order to earn a limited edition Hacktoberfest t-shirt. The event’s organizers have increased the number of required PRs to five this year and only the first 50,000 will earn a t-shirt.

No open source project is too small to benefit from Hacktoberfest. Maintainers who want to attract new contributors can apply the “Hacktoberfest” label to issues that are appropriate for newcomers to work on. A few projects are highlighted on the event’s homepage and there are already more than 17,000 issues designated for Hacktoberfest that are ready for contributors to tackle over the next 31 days.