BCD is the source of data for all the Browser Compatibility tables that appear in MDN articles. As a W3C Developer Advocate, you can support developers by helping to improve the quality and completeness of the browser-compatibility data in BCD.
Add new BCD data for features defined in the specifications you’ve taken responsibility for as a W3C Developer Advocate, and raise pull requests in the BCD repo to get your contributions added to BCD. The contributing.md file in the MDN content repo provides detailed guidance on how to make content contributions to BCD.
Monitor the list of open issues in the BCD content repo, looking for any issues related to features from specifications you’ve taken responsibility for as a W3C Developer Advocate. If you find an issue which you’ve got the ability to resolve, post a comment to the issue asking that it be assigned to you, and then create a pull request with an BCD content change that resolves the issue.
Monitor the list of open pull requests in the BCD repo, looking for any pull requests related to features from specifications you’ve taken responsibility for as a W3C Developer Advocate. If you find a pull request which you’ve got the domain knowledge (technical knowledge) and browser-version knowledge to help review, then review the PR changes, and post a comment.