In order to help ensure that data gets filled out and we don't wind up with strays, we stopped allowing the null value for a version, so you can no longer indicate "unknown" as support level for a feature in BCD's data store. If you don't know the values, you can submit a patch but someone will have to add the missing data before it can be accepted, as it will fail the automated testing without data for every browser supported by the JSON.
that seems in scalable and adds such a burden to adding data that it will have the unintended consequence of discouraging participation.
I only have a dataset of 1 but it seems like it would be useful data for devs to see so they know they can not use features X, Y, and Z if they want to be cross platform because of bugs in specific implementation but given I can't add the data without going through all the browsers, given that "unknown" is not the right label for conforming browsers, and given that I don't have time to dig up proof the other browsers conform I opted to remove my pull request
That's sad.
While understandable if you were overwhelmed with poor half-hearted "stray" PRs, still I doubt that any random developer will sift trough open PRs to add his two cents of knowledge about "invisible" (unpublished) feature to make it complete for acceptation. Seeing blanks-to-be-filled directly in public documentation feels far more motivating for quick ("wiki") edit.
So, we're aware that the examples being way at the bottom of the page are frustrating to a lot of people because of the usefulness of having a simple example you can learn from or even snag and use in your own code.
That's why we have work ongoing to not only place examples at the tops of pages, but to make the examples interactive so you can make changes to the code right on the page. There's some info about it here: https://discourse.mozilla.org/t/interactive-editors-in-beta/....
I'm glad you approve of our use of <label> to correctly label inputs. We are not yet 100% consistent about this, but we're on the job!
For what it's worth, if anyone wants to open an MDN account to contribute (whether to fix a typo or document a new API), you can ping any of the admin types in irc.mozilla.org #mdn, and we can help you get an account set up.
I appreciate the kind words! We have a ton more to do to get our docs as complete and clean as we want, but with the help if our volunteers, we will make it happen!
Our volunteers are rock stars. Klez is one of our superstars.
One of the best parts of my job is working with volunteer contributors. My favorite experiences often involve helping a new volunteer get started, then watching then help the next one to come along. Klez is one of those.
It's always fun to meet up with our best and/or most prolific contributors at Mozilla-sponsored events, when we fly a bunch of people to one spot to plan the next wave of work, too.