Skip to content

Latest commit

 

History

History
36 lines (23 loc) · 2 KB

File metadata and controls

36 lines (23 loc) · 2 KB

Contributing to EdTech Founder Stack

Thanks for helping make this better. If you've lived through the edtech founder grind, you probably have something to add.

What this is

A knowledge base for edtech founders, stored as plain markdown in data/. The point is to ground guidance in real sources — regulations, peer-reviewed research, named operators — instead of whatever a model happens to remember. Contributions keep it accurate and expand its coverage.

What we're looking for

High-value contributions

  • International regulatory data: We're very US-centric right now. GDPR, country-specific regulations, and international accreditation are all welcome.
  • New buyer personas: Procurement in the UK or India looks different than in the US. We need those maps.
  • Corrections: Education markets move fast. If the competitive landscape is stale or a regulation has changed, fix it.
  • More research: Add peer-reviewed papers to the corpus in data/research/.

Guidelines

  1. Cite the source. Every factual claim should trace to something checkable — a named regulation with a date, a paper with a DOI, a named operator. No guessing.
  2. Be opinionated. We don't do "on the one hand, on the other hand." If you add guidance, give it a point of view backed by real experience.
  3. Keep the format. Match the structure of the file you're editing. For regulatory and market files, keep the "last updated" date at the bottom. For research, follow the table format (a leading # column, then Title, Takeaway, Type, Year, Citations, DOI) and sort by citations descending.
  4. Segment matters. K-12, higher ed, and corporate L&D are different worlds. Say which one a claim applies to.

Process

  1. Fork the repo.
  2. Create a branch.
  3. Make your edits.
  4. Open a PR and tell us why it makes the knowledge base better for founders.

The ScaleU team reviews every PR to keep quality high and advice consistent.

Questions?

Open an issue or reach out to the ScaleU team. We're usually around.