Contributing
This is a living corpus, not a finished publication. Publishing here doesn’t mean “done”; it means
there’s enough to be useful to someone else. Please help us make it more useful.
How it grows
- Cadence by substance, not milestones. We publish when something of real relevance changes; we’re not
a hyper-growth project.
- Watch the repo to get notified of changes, and pull the latest before you build.
- It can change direction. It’s community-driven and community-led.
How to contribute
- Raise an issue to flag a gap, a question, or “this doesn’t make sense to me as a builder” (that last
one is genuinely useful feedback right now).
- Open a pull request to propose a change. A committee review decides what merges into the canonical
corpus.
- Nonprofits: tell us whether these are your problems, or send us others. Get in touch with your ideas here.
Content conventions
- Plain markdown + YAML front matter (Open Knowledge Format). The only required field is
type.
- Tag every item with
validation: validated | hypothesized and the relevant food-security
category (availability, utilization-safety, economic-physical-access, stability-resilience).
- Where useful, write the problem in two languages, nonprofit framing and developer translation, so
both audiences recognize it as the same thing.
- Follow the
_template.md in each folder for the structure of each content type.
Co-design
Whatever you build, build it with the community. Recommend and design with local food banks, pantries,
and the people they serve. TechSoup can help make those connections. Get in touch with your ideas here.
Licensing
Licensed CC BY-SA 4.0 (Creative Commons Attribution-ShareAlike). You’re free to share and
adapt the material, including commercially, as long as you give credit and license your contributions
under the same terms. It’s share-alike: if you build on this and improve it, your changes flow back to
the community so everyone benefits.