Announcing Tide 1.0.0-beta

At WordCamp US last December we introduced Tide.  Tide was our reaction to what we, and many other in the WordPress community, believe is critical to the future of the Open Web.  A future where the standard of code in WordPress is high and its users can be confident in its performance, security, reliability, and accessibility.  Tide is a very practical solution to achieving this, ultimately improving the quality of code across the web.  The WordCamp US announcement represented the proof of concept stage for Tide and helped highlight ways in which updating WordPress plugins and themes based on WordPress Coding Standards could make the open web more performant, secure, reliable, and accessible.  Since then, we’ve been spending time reviewing feedback from WCUS, meeting weekly with the community, and enhancing Tide based on what we’ve learned.

Tide’s vision is inspired by the proverb “A rising tide lifts all boats”, when we lower the barrier of entry to writing and choosing quality code for enough people, it will lift the quality of code across the whole WordPress ecosystem.  Tide helps to make it easier to improve the quality of code throughout the WordPress ecosystem and help WordPress site owners make better choices about plugins and themes.

As of today, we’re excited to announce Tide 1.0.0-beta, now available on GitHub and at  This version adds Google Cloud Platform (“GCP”) and local-only infrastructure support, integrates Lighthouse performance analysis, and provides documentation for the entire platform to help onboard contributors and developers looking to improve their own code.  Please update any forked repositories or local instances of the previous version of Tide as it will be deprecated later this month.

GCP migration

The prototype version of Tide from WordCamp US was based on Amazon Web Services (“AWS”), but with the release of Tide 1.0.0-beta we’ve migrated to GCP and have rewritten the Tide services in the Go programming language.  This helps to provide a better integration point with as the GCP environment and Go services are more performant and cost effective.  This is the first step towards integration.

You can find the code for Tide on GitHub at

Local-only option

In order to minimize the needs for developers or contributors to setup GCP or AWS infrastructure to use Tide, we’re providing a local-only option.  This way you can run all the Tide services locally on your computer and not need to rely upon or pay for anything additional.  Note that for now we’ve only fully tested on MacOS, so non-MacOS setup and usage will vary a bit until we can test across non-MacOS platforms and provide resolutions to any issues there.  In order to run Tide locally, you’ll need Composer, Docker, Go, and Glide; additionally for Windows you’ll need Make installed based on our testing so far.  Full setup instructions are available in the Tide documentation (see below).

Lighthouse integration

Along with the WordPress Coding Standards and PHP Compatibility results for plugins and themes in the Tide API, we’ve also added support for Google’s Lighthouse auditing to include performance, accessibility, and other results for themes in the Tide API.


The prototype version of Tide from WordCamp US was built as a proof-of-concept and had limited documentation; what did exist then was mainly within the README file for setup instructions on AWS.  For 1.0.0-beta, we’ve significantly extended the documentation to include installation instructions for GCP and the local-only option, details on the various Tide services (API, Sync Server, PHPCS Server, Lighthouse Server), working examples of the Tide API, as well as how to contribute to better utilize and improve Tide.

The documentation site is available at (including a searchable demo of the Tide API search).  The source for the documentation is available at


The next step on the Tide roadmap is working with the systems team to integrate the PHP Compatibility results from the Tide API into the repository database so that it can be displayed on plugin and theme pages.  You can follow along via the roadmap we’re establishing at  Note that we’re using ZenHub to manage Tide’s product development process and that you may need to install the ZenHub Browser Extension to see all the details within the Tide roadmap.

This plan represents what will take Tide from concept to practical application for the WordPress community.  If you have feedback for the integration, then please comment in GitHub or ZenHub.  If you have ideas or feedback on future Tide roadmap ideas, then please add those as GitHub Issues at


Thank you to everyone who contributed to Tide 1.0.0-beta:

Alberto Medina, Bart Makoś, Brendan Woods, Daniel Louw, David Cramer, David Lonjon, Derek Herman, Jeffrey Paul, Justin Kopepasah, Jonathan Wold, Joshua Wold, Leo Postovoit, Lubos Kmetko, Luke Carbis, Maxim Siebert, Miina Sikk, Mike Crantea, Rheinard Korf, Rob Stinson, Sayed Taqui, Tammie Lister, Utkarsh Patel.

Please join us for our weekly meeting on Tuesday’s at 21:00 UTC in the #tide channel in WordPress Slack.  See you then!

#1-0-0, #gcp, #lighthouse, #roadmap, #tide

Tide Chat Summary: December 12th

This post summarizes the Tide chat meeting from December 12th in the #tide Slack channel (Slack archive).

Tide focus

  • Current focus/priority/goal is integrating PHP Compatibility data from Tide into
  • Once PHP Compatibility is integrated into, we’ll assess the next focus/priority/goal to provide the biggest impact to the community

Progress on code open sourcing

  • @valendesigns: we are working towards being 100% Open Source and having the API back online (with re-audit) no later than December 20th, likely sooner. The transition to Open Source is not a straight forward task and has been pretty much been the teams singular focus since last week. We are rebuilding the local dev environment to make it easier to contribute. We can't open the sources without exposing sensitive data so all the repos are being rebuilt.
  • @valendesigns @rheinardkorf @danlouw @jbpaul17 from XWP are working on Tide
  • Tide API will include WPCS and PHPCompatibility output, scoring will no longer exist
  • site from WCUS was a client to demo what COULD be done, it wasn’t meant to be what WILL be done on actual Tide integration to
  • Demo from WCUS wasn't 100% functional, some things may have worked better than others
  • After code is available as open source, we'll need lots of testing to help ensure results are faultless
  • @sergey has done work on some PHP-related tickets, would be good to have him gloss over the PHP compat part of the code when released
  • @williampatton able to assist with docs if there is guidance on what's needed
  • @barry to handle integration, @otto42 waiting until API is ready to query against

UX for integration of PHP Compat from Tide into

  • @joshuawold is the design lead at XWP managing UX for how PHP Compatibility could be integrated into, working with @maximsiebert on UX options
  • We'll want input from someone on the Meta and Design teams as feasible to review the UX/design
  • @obenland can cover Design from Make/Plugins
  • #40934 is prior work covering UX around not being able to install a plugin when your PHP version is not compatible, @joshuawold to review this and as input on PHP Compat UX for
  • @joshuawold to review UX with @mapk who was the original designer for the plugin directory
  • Updates on UX/design to be shared in #tide as they're available

Next week’s meeting

The next meeting will take place on December 19, 2017 at 22:00 UTC / December 19, 2017 at 22:00 UTC in the #tide Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#summary, #tide-chat

New Home

Welcome to the new website for the Tide project!

Tide already has a private code repository and an issue tracker, which will be made public in the next few weeks. Subscribe to this blog for updates when it becomes public, or join us in the #tide channel on Slack.

The mission of Tide is to raise the code quality of all the plugins and themes in the directories. Tide’s name reflects this mission, derived from the proverb “a rising tide lifts all boats”.