Corrections and contributions
Every row on this site is a claim about a language, and any of it can be wrong. Publishing something does not settle it. Reports go in the issue tracker, fixes go in as pull requests, and both are public from the moment they are filed.
Report something wrong
A form no speaker would use, a gloss that misreads the morphology, a date taken from an edition the field has moved past, a table row that flattens variation. Naming the language and the problem is enough to file; the forms ask for more only where it helps.
Change it yourself
Each entry is one TypeScript file named after its slug, so /patterns/existence is src/lib/data/patterns/existence.ts. Every entry page links to the file it was rendered from, and editing on GitHub opens a pull request without cloning anything.
Propose an entry
An entry starts as a question that several unrelated languages answer in a handful of ways. Two to six recurring answers, with a language or two under each, is enough to open one.
What a report needs
Something a reader can go and check. A grammar, a dictionary, a corpus hit, a wiki page, a thread, a recorded talk, and your own judgement as a speaker all count as evidence, and every kind of it gets named. Speaker judgement stays recorded as speaker judgement, with the variety and the date, instead of being folded into somebody else's citation.
How firm a claim is
Each attestation carries high, medium, or low. High means a description or a speaker states it directly. Medium means the sources hedge, or one row is standing in for variation. Low means it is inferred or contested. A report that a claim is graded too high is as welcome as a report that it is wrong.
Licence
Content is under CC BY-SA 4.0, and contributions are taken under the same licence. Contributors keep authorship of what they write, and the file history records who added which claim.