Built in the open, useful to everyone
OELTKit is Apache 2.0 and developed in public. The fastest way to shape it is to tell us what component your courses are missing.
Contribute
Component proposals are the on-ramp. You don't need to write code to make OELTKit better — describe an interaction you keep building by hand (the markup you wish an LLM could write, how a keyboard user should drive it, what it should report to the LMS) and open it as a proposal. Specs that start from real course needs become the best components.
- Open a component proposal or bug report
- Contributing guide — code, docs, and testing contributions all welcome
- Accessibility reviews are first-class contributions: if you use assistive technology and something doesn't work, that's a priority issue.
Governance
OELTKit is maintainer-governed during the beta, with decisions made in public issues and ADRs in the main repo. As the contributor base grows, governance formalizes — the commitment that doesn't change is below.
Vendor neutrality: OELTKit is incubated by BCL Training, and it stays useful to people who never become BCL clients. No feature is held back for a paid tier, no LMS or AI vendor gets preferential treatment, and the standards targets are decided by what practitioners need — not by anyone's product roadmap.
Roadmap
The roadmap lives on GitHub where you can comment on it, not in a slide deck: OELTKit project board.
Sponsorship via Open Collective is planned; the link will appear here when the collective is live — not before.