Published
Maintainer Guide
Operational guidance for OpenLib maintainers reviewing apps, moderating content, and maintaining documentation.
Maintainers keep OpenLib useful, accurate, and safe.
Responsibilities #
- Review new app submissions.
- Merge high-quality edit requests.
- Moderate spam, unsafe content, and abuse reports.
- Keep docs accurate.
- Preserve a consistent taxonomy.
- Watch for stale or deprecated projects.
Review decisions #
| Decision | Use when |
|---|---|
| Approve | The app meets OpenLib guidelines |
| Request changes | The submission is promising but incomplete |
| Reject | The app is out of scope, unsafe, duplicate, or not open source |
| Deprecate | The app is listed but no longer recommended |
Documentation maintenance #
Documentation is maintained locally as Markdown under docs/content/. Create, edit, rename, move, and delete docs pages by changing those Markdown files, then run the docs generator before deployment.
Publishing checklist #
- Update or add Markdown files in
docs/content/. - Run
npm run docs:build. - Confirm
/docs/pages render locally. - Run
npm run seo:sitemapand confirm docs URLs are included. - Submit the change for review.
Incident response #
For unsafe listings, prioritize user safety: unpublish or mark deprecated first, then document the reason and follow up with project maintainers if needed.
Contributors
- OpenLib Team