Medication Tracker
Documentation
This folder holds the guides for Medication Tracker. The first group is for families who use the app. The second is for developers who change it. The project README shows how to install the app. The same pages are on the Medication Tracker website.
For families
- User guide: how to use every screen, with pictures.
- Words to know: the pharmacy, insurance and app words, in plain language.
- How the app works: how the app picks refill dates, why it keeps a backup supply, how it estimates insurance rules, and what stays private.
- Compliance: the security and accessibility checks, what they found, and what a person still has to check.
For developers
- Architecture: the parts of the app, page navigation, the rules for browser scripts, the product box, the portal reader and the drug references.
- Data model: every table, its grain, the meaning of each column, which fields hold personal or health information, and the exact refill date rules.
- How to set up a development copy: run the app from a clone while you change it.
- How to run the tests: the lint, the unit tests, the supply tests and the smoke test.
- How to build the starter catalog: the script that writes the catalog the app ships, its sources and their licenses.
- How to update the screenshots: the invented household and the script that takes the pictures in these guides.
- How to publish a release: set the version, tag a
release, and let GitHub attach the
meds.zippeople install. - How to update the website: how the documentation website is built from these pages, and how to preview a change.
- Documentation template: a starting structure for a new page.
- Skill authoring examples: optional recipes for AI assistant skills.
Conclusion
If you use the app, start with the user guide. If you are about to change the app, start with the architecture page and the data model.
Additional resources
- Project instructions
- Skills index
- The app folder
- Privatium, the framework this app runs on.