-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📝Editorial: Update resources/README.md #8140
Conversation
Improve prose for resources (i.e., `testharness.js`). I have been educating the community on the benefits of aligning testing with WPT. However, testharness is a little difficult to get head wrapped around from the feedback I am receiving. Also have recently been doing some prose updates in documentation over @ WHATWG. I am revisiting the WPT setup process and believe one should always leave code better than when they saw it. References: - whatwg/meta#48 - (in particular) whatwg/meta#48 (comment)
Build PASSEDStarted: 2017-11-10 02:04:03 View more information about this build on: |
I think the titles should ideally all be in title case, but sure we can merge this. |
@jgraham titles ARE in title case. Headers are not.
I referenced this multiple times above... |
CI appears to be stuck... @jgraham @gsnedders |
OK CI cleared @jgraham @gsnedders |
@snuggs FWIW, we don't necessarily follow WHATWG policies here. |
Make prose for resources more friendly to new adopters. (i.e.,
testharness.js
).I have been educating the community on the benefits of aligning testing
with WPT. However, testharness is a little difficult to get head wrapped around
from the feedback I am receiving. Also have recently been doing some prose
updates in documentation over @ WHATWG. I am revisiting the WPT setup process
and believe one should always leave code better than when they saw it.
If this is not of value please let me know the best way to contribute to improving documentation.
🙏
References:
This change is