Thanks for your interest! SmartDocs is an open-source project and we welcome contributions of all kinds.
Found something broken? Open an issue. Include:
- What you were doing
- What you expected to happen
- What actually happened
- Browser / Node version if relevant
Have an idea? Open an issue. Describe:
- The problem you're trying to solve
- How SmartDocs could help
- Any alternatives you've considered
Start a discussion. No question is too small — the community is here to help.
- Fork the repo
- Create a branch:
git checkout -b feature/your-feature - Make your changes (see AGENTS.md for AI coding agent guidance)
- Run
npm run build— must succeed with zero TypeScript errors - Push and open a pull request
Docs live in content/. Fix typos, add examples, or write new pages. Same PR process as code.
Built something with SmartDocs? Show it off in Discussions!
git clone https://github.com/jm27/smartdocs.git
cd smartdocs
npm install
npm run build:graph
npm run devOpen http://localhost:3000. See README.md for full setup instructions.
- TypeScript compiles:
npx tsc --noEmit - Build succeeds:
npm run build - Graph index is up to date:
npm run build:graph - Your change follows existing code style (we optimize for readability, not cleverness)
- If you added content pages, they follow the existing naming conventions
- TypeScript: strict mode, no
anyunless unavoidable - Components: client components only when needed (
"use client"directive) - CSS: custom properties for theming, no Tailwind utility classes (we use a hand-crafted design system)
- Comments: only for non-obvious decisions. The code should be self-documenting.
- Commits: concise, imperative mood ("fix:", "feat:", "docs:", "refactor:")
- GitHub Discussions: https://github.com/jm27/smartdocs/discussions
- Email: jme2791@gmail.com
- Issues: https://github.com/jm27/smartdocs/issues
By contributing, you agree that your contributions will be licensed under the MIT License.