Thanks for your interest in improving these tools. This project is a set of static, offline PDF micro-apps. Please keep that design in mind.
- Fork the repository
- Clone your fork
- Create a branch:
git checkout -b feature/your-ideaorfix/issue-description - Make changes
- Test locally (see below)
- Commit with a clear message
- Push and open a Pull Request against
main
python3 -m http.server 8080Open http://localhost:8080/ and exercise the tool you changed. ES modules require HTTP — do not use file://.
- No backend — do not add server-side code, APIs, or required cloud processing
- Privacy first — do not upload user files or add analytics that capture document content
- Keep tools focused — each folder is one micro-tool; avoid merging unrelated flows
- Match existing UI — reuse
css/styles.csspatterns (cards, buttons, spacing) - Vendor locally — if you add a library, place a minified build under
vendor/and load it from the page (no required CDN at runtime) - Accessibility — preserve keyboard use, labels, and focus styles where possible
- Small PRs — easier to review than large multi-tool refactors
Open an issue with:
- Browser and OS
- Steps to reproduce
- Expected vs actual behavior
- Whether it happens offline / after hard refresh
Do not attach private PDFs or personal documents.
Open an issue first for larger features so we can discuss scope (especially anything that might affect privacy or offline behavior).
By participating, you agree to follow our Code of Conduct.
Contributions are accepted under the MIT License.