In crisis or unsafe? Emergency: 911 Call or text 988 DV Hotline 1-800-799-7233 Safety resources →

ohio-family.lawyer Ohio family court reform

Educational information, not legal advice. This site is not a law firm, and reading it does not create an attorney-client relationship. Written by AI and published without human review. Check the sources. Why AI · Read the disclaimer.

Contribute

This site is an open-source community project. Anyone can correct a claim, track a bill, verify county links, draft a guide, or improve the code on GitHub.

ohio-family.lawyer is built in the open. Every essay, guide, data file, and line of code lives in a public repository: github.com/acharneski/ohio-family.lawyer. There is no back office and no mailbox. The project moves when people like you pitch in.

Ways to help

No coding required

  • Report an error. Open a correction issue with the page, the claim, and a source. Accuracy is this site’s only real asset.
  • Suggest a bill to track. Open a bill issue with the bill number and a link to legislature.ohio.gov.
  • Propose a topic or guide. Open a content issue.
  • Fix a typo or unclear sentence. Every page has an “Improve this page” link in the footer. It opens the source file on GitHub, where you can edit it in your browser and propose the change.

Research and verification

  • Verify a county. The county pages need checked links to each county’s domestic relations court, juvenile court, local rules, and child support enforcement agency. Edit counties.json and cite where you checked.
  • Write a statute summary. The Ohio law index needs short, plain-language summaries. Edit statuteInfo.json.
  • Find sources. Essays contain CITE markers where a claim still needs a primary source. Search the repo for CITE: and add one.
  • Public records. Help with the research projects by filing records requests and publishing the results.

Writing and review

  • Steelman us. If you disagree with a position, write the strongest objection. Briefs are required to answer it.

Code and design

The site is static: Eleventy, Nunjucks, plain CSS, and small ES modules. It has no trackers and no third-party scripts. Accessibility, performance, print styles, and data tooling are all open for help. See CONTRIBUTING.md to run it locally.

How changes land

  1. You open an issue or a pull request.
  2. Automated checks run (pnpm test). Content should meet the publishing checklist: sources, “law as of” dates, labeling, and preserved abuse protections. There is no human editorial review. See Written by AI.
  3. Once merged, the change ships on the next deploy, and the commit history records who changed what and when.

House rules

  • Cite everything checkable.
  • Criticize systems, rules, and public acts. Never attack private individuals.
  • Every reform keeps fast, low-barrier protection from genuine abuse.
  • Be civil. Disagreement is information; harassment isn’t.

Text you contribute is published under CC BY 4.0, like the rest of the site.

Start on GitHub →

  • Draft a guide or brief. Follow the templates and the editorial standards. Drafts start with status: draft and move to status: review once they are sourced and pass the automated checks.
  • Practitioners, mediators, clinicians, and DV advocates: nobody checks this AI-written content before it publishes, so what you know is worth more here than anywhere. Open an issue on anything you can show is wrong.