We had @dontcallmeDOM representing us there - great project (look at their 2017 results!), great people, great plans for 2018
2
2
1
5
A particular @w3cdevs objective in the MDN PAB is to bring the standardization and documentation workflows closer together
1
1
For instance, the @w3ctag has been pushing @w3c groups developing specs to develop at the same time explainer docs, which puts features in the context of their expected usage by developers docs.google.com/document/d/1…
1
1
Replying to @w3cdevs @MozDevNet
Hopefully we can facilitate the adoption of these explainers as seed to future MDN content. Some groups have also developed dev-focused material that might usefully migrate to MDN github.com/w3c/payment-reque…

Jan 24, 2018 · 10:21 AM UTC

1
1
2
Replying to @w3cdevs @MozDevNet
We are also looking at bringing more visibility to existing best practices from @w3c_wai and @webi18n from MDN github.com/mdn/pab/issues/1
1
2
There are also low hanging fruits in ensuring data about @w3c specs is kept uptodate e.g. via the github.com/w3c/w3c-api - early work toward that at github.com/mdn/kumascript/pu…
1
1