Ways to contribute to the WebDX CG efforts

Hello WebDX community group friends,

Not every one of us can attend the regular group meetings<https://www.w3.org/groups/cg/webdx/calendar/>, or join the chat<https://matrix.to/#/#web-platform-dx:matrix.org>, so here is an email to share some of the ways you can get involved and contribute to our work anyway.
We have a lot of work happening, across different areas, and are always looking for more people to help.

I hope this is helpful.
Of course, let François and I know if you have any questions, or if the work that's happening isn't visible enough to you, or not easy enough to jump into.
We're happy to make changes to our processes and make WebDX more inclusive and easier to contribute to.


Contribute to web-features

The bulk of our work happens in the web-features repository on GitHub<https://github.com/web-platform-dx/web-features>. That's where we create and maintain the catalog of web platform features, which Baseline, and other tools, are based on.

You can contribute to web-features by:


  *
Reviewing pull requests that add new features<https://github.com/web-platform-dx/web-features/pulls?q=is%3Aopen+is%3Apr+label%3A%22feature+definition%22>:
     *
Does the feature name and description make sense?
     *
Is the specification link correct?
     *
Is the feature granularity appropriate for a web developer audience?
     *
Check out: What makes a feature<https://github.com/web-platform-dx/web-features/blob/main/docs/CONTRIBUTING.md#what-makes-a-feature>.

  *
Improving existing features:
     *
Did you find a feature that has a confusing name, description, granularity, or Baseline status?
     *
File an issue<https://github.com/web-platform-dx/web-features/issues> about it.
     *
Or edit the file directly. One simple way to do this is:
        *
Find the feature at https://web-platform-dx.github.io/web-features-explorer/
        *
At the bottom of the page, click Edit this feature.

  *
Creating a missing feature:
     *
Know of an upcoming web platform feature that's not yet in the repo?
     *
Found a page on MDN that didn't have a Baseline banner, but should?
     *
Either open an issue<https://github.com/web-platform-dx/web-features/issues/new?template=new-feature.yml> with a description of the feature and a link to a spec (even if that spec is an early proposal or explainer document, or a spec PR).
     *
Or create a pull request on the repo for the new feature. Check out Contributing to the web-features project<https://github.com/web-platform-dx/web-features/blob/main/docs/CONTRIBUTING.md>.


Contribute to browser-compat-data

Our group does not own the browser-compat-data project on GitHub<https://github.com/mdn/browser-compat-data/>, and there are many people who work on it already.
But its data is crucial to web-features. It's what makes the Baseline status calculation possible.

If you see anything wrong with the data, such as an incorrect Baseline status, or an incorrect browser compat table on MDN:


  *
Open an issue<https://github.com/mdn/browser-compat-data/issues/new?template=data-problem.yml> on the repo, detailing the data problem.
  *
Or, create a pull request to fix the problem.


Jump into one of our 2026 projects

We create a roadmap for our group each year.
Check out this year's roadmap<https://github.com/web-platform-dx/admin/issues/8>.

You'll see that each project on that roadmap is linked to one or more GitHub issues.
To contribute to one of the projects:


  *
Find a project that interests you.
  *
Check out the existing GitHub issues that are linked to it.
  *
Comment on the issue(s) which you want to help with, and explain how you want to help, or get started right away!

Example: let's say you know a lot about polyfills or progressive enhancements, and want to help:


  *
Check out the Enable guidance for progressive enhancement project in our roadmap<https://github.com/web-platform-dx/admin/issues/8>.
  *
Review the existing issues<https://github.com/search?q=org%3Aweb-platform-dx+label%3AR26%3Aprogressive-enhancement&type=issues>, and leave comments.
  *
Or file new issues if you think more ideas need to be discussed.
  *
Or open pull requests to get us started.
  *
 Tag any new issue or PR with the corresponding label: R26:progressive-enhancement in this case. Each project has its own label.


Improve the Web platform features explorer website

Our group also maintains the explorer site at https://web-platform-dx.github.io/web-features-explorer/
Though this project started as a simple web viewer for the features, its scope grew and it now also displays additional data for each feature, as well as release-notes-styles pages.

To contribute to the site:


  *
Use the site and report any issue<https://github.com/web-platform-dx/web-features-explorer/issues/new> you experience.
  *
Help fix existing issues<https://github.com/web-platform-dx/web-features-explorer/issues>. The search tool is especially in need of improvements. See https://github.com/web-platform-dx/web-features-explorer/issues/54.
  *
To build and run the site locally, see Local development<https://github.com/web-platform-dx/web-features-explorer/blob/main/README.md#local-development>. The site uses the Eleventy static site generator.


Help improve the WebDX website

We also maintain another static website for the WebDX group at https://web-platform-dx.github.io/web-features/.
This is our canonical place to talk about Baseline, web-features, and what our group does.
You can help improve the site:


  *
Use the site and report any issue<https://github.com/web-platform-dx/web-features/issues/new> you experience.
  *
Open pull requests to improve the site. In particular, we have this existing issue about improving the site's URLs<https://github.com/web-platform-dx/web-features/issues/3783>.


Help gather more developer signals

We recently started gathering developer signals about web features that aren't yet Baseline.
Signals are collected on the developer-signals repo, in individual issues<https://github.com/web-platform-dx/developer-signals/issues?q=is%3Aissue%20state%3Aopen%20label%3Afeature>.
Developers can find these issues via caniuse.com, and other sites that display web-features.
Collecting more reactions from real developers about upcoming features, as well as their use cases, helps a lot.

If you talk about a feature on your site or blog. Or if you're building an app that uses the web-features data, consider linking the features to the developer-signals repo.
The mapping from web-features IDs to developer-signals issues is here: https://github.com/web-platform-dx/web-features-mappings/blob/main/mappings/developer-signals.json


If there are other ways in which you want to help WebDX, please let us know!

Patrick