Thanks for your interest in contributing.
Inbox Archeology is meant to be approachable for both technical and non-technical contributors. Small contributions are welcome.
You can help by:
- reporting bugs
- suggesting features
- improving documentation
- refining the UI
- adding data visualizations
- improving onboarding for first-time users
- contributing code fixes or new features
Please check the Issues tab for open tasks, ideas, and discussion topics.
Good places to begin:
- issues labeled
good first issue - issues labeled
help wanted - documentation improvements
- beginner-friendly UI polish
git clone https://github.com/monapdx/Inbox-Archeology.git
cd Inbox-Archeology
npm install
npm run devThen open the local dev URL shown in your terminal.
- Fork the repository
- Create a new branch for your change
- Make your edits
- Test your changes locally
- Commit with a clear message
- Open a pull request
Please try to keep pull requests:
- focused on one change
- clearly described
- easy to review
Helpful things to include in a PR:
- what changed
- why it changed
- screenshots, if the UI was updated
- steps to test, if relevant
Here are good starter contributions:
- improve README clarity
- add screenshots or GIFs
- improve loading states
- improve mobile responsiveness
- add demo/sample data
- add search or filter improvements
- add export options
There is no need to be overly formal. Prioritize:
- readability
- small, understandable changes
- clear variable names
- minimal unnecessary complexity
If you are not ready to submit code, that is completely fine.
You can still contribute by:
- opening an issue
- sharing feature ideas
- suggesting UX improvements
- discussing privacy/local-first design choices
This project is part of a broader effort around:
- data portability
- digital sovereignty
- local-first tools
- personal archives
Contributions that support those goals are especially welcome.
If you are unsure where to start, open an issue and describe what you want to help with.