308B.mnGet started

Contribute

How public readers and authorized collaborators can help improve 308B.mn, with the current lack of public correction intake and private repository access made explicit.

Verified against sources: October 15, 2026Last edited: October 16, 2026

Public readers and repository access#

The handbook is public, but its GitHub repository is private. Issues, pull requests, edits and repository history are available only to authorized collaborators. Signing up for GitHub does not grant access.

No public correction submission channel is currently available. The public corrections log is readable without repository access but is not a submission form. The publisher's GitHub profile is an identity link, not a verified corrections inbox. Public intake requires the owner to authorize and publish a reachable channel and a responsible recipient; none is represented as operating here.

Ways to help#

  • Identify errors. The most useful contribution. Record the page address, the incorrect sentence and the primary source supporting a correction. See Corrections for the current submission limitation.
  • Review a page as an attorney. A Minnesota-licensed attorney can review a page and have the review recorded in its frontmatter, with the reviewer's name, date and the scope of what was reviewed. Only then does the page lose its "unreviewed" banner. A review of one page does not extend to others.
  • Find authority for an open question. A relevant court decision, agency position or filing practice needs a source. Authorized collaborators can submit it through the repository; public readers currently have no available submission channel.
  • Evaluate the local-government pages. City and county staff can identify missing explanations; submitting that feedback has the same access limitation.
  • Add a guide or an FAQ. Follow the written standard first.

How a change is made#

The following workflow is for authorized collaborators, not a public submission route:

  1. Read docs/editorial-standards.md in the private repository.
  2. Edit or add a Markdown file under content/. Statute data under data/statutes/ is never edited by hand.
  3. Cite every claim from the source registry in data/sources/, adding a source when needed. Open the source before citing it.
  4. Run the check. It must pass without errors.
  5. Open a pull request.

The private repository's CONTRIBUTING.md has the commands. Record completed corrections on Corrections; do not turn a partial source check into a full-page verification or attorney-review claim.

What we will not accept#

  • Claims without a source, or sourced only from memory.
  • Material implying endorsement by an agency, firm or vendor, or presenting the site as official.
  • Legal advice about a particular person's situation.
  • Promotion of a product or service.

aboutcontribute

Edit (authorized collaborators only)History (authorized collaborators only)Corrections log & intake limitationNo public correction submission channel is currently available.