One person builds this · help is welcome
Build it and keep it standing.
Lrnon is written, coded and maintained by one person. That is fine for a start
and useless at scale — lessons go stale, bugs sit, and accessibility gets tested
by the person least able to test it honestly.
So the roles below are small on purpose. Proofread one lesson. Test one page with
your screen reader. Fix one bug. Nothing here asks for an open-ended commitment,
and nothing needs a meeting.
Pick a role and email us See the roles
What we promise you
- A defined task, not a vague ask. You get a specific lesson, page or issue, and you are done when it is done.
- A reply within two working days. If we go quiet, chase us — silence is a failure on our side.
- Your hours in the public ledger, tagged in-kind, exactly like a cash gift. Name only if you want it.
- You can stop at any time, mid-task, with no explanation. Just tell us so it can be picked up.
What we can't offer
- Payment. Nobody is paid from contributions, including the founder.
- A reference on letterhead — Lrnon is not yet a registered organisation. We will happily confirm what you did, in writing, as an individual.
- Fast decisions on big changes. One person reviews everything.
The roles
Take one. Take a second only if the first went well. The time given is for one unit
of work — one lesson, one page, one issue. None of these is a rota and none of them
expects you next week.
Content
Lesson proofreader
Read one lesson end to end and mark typos, wrong facts, broken examples, and sentences you had to read twice.
- Time ·
- About 45 minutes per lesson
- Who suits ·
- Careful reading. No AI expertise needed — confusion is the signal we want.
- Credit ·
- A named credit at the foot of the lesson, if you want it.
Take this role → Content
Subject reviewer
Check a lesson is technically correct and current. AI moves fast and some of our examples will age badly.
- Time ·
- 1–2 hours per lesson, occasional
- Who suits ·
- Working knowledge of the topic. Practitioners preferred over academics.
- Credit ·
- Named as reviewer, with the review date.
Take this role → Accessibility
Narrator
Record the read-aloud track for a lesson so screen-reader users and slow readers get a real voice rather than a synthetic one.
- Time ·
- 2–3 hours per lesson
- Who suits ·
- A quiet room and a decent microphone. We will send a pronunciation sheet.
- Credit ·
- Voice credit, and hours logged in the public ledger.
Take this role → Accessibility
Accessibility tester
Use the site the way you actually use the web — screen reader, keyboard only, magnification, high contrast — and tell us where it fails.
- Time ·
- 1 hour, one page or flow
- Who suits ·
- Lived experience of assistive technology. This is the role we most need and can least fake.
- Credit ·
- Findings published as dated fixes, credited to you.
Take this role → Content
Translator
Translate a lesson into your first language. Human translation only; we are not shipping machine output as a language edition.
- Time ·
- 3–4 hours per lesson
- Who suits ·
- Native fluency in the target language and comfortable technical English.
- Credit ·
- Named as translator on every page you touch.
Take this role → Build
Front-end contributor
Pick up an open issue — a layout bug, a keyboard trap, a slow page. The stack is Astro, plain CSS variables, no framework churn.
- Time ·
- Whatever an issue takes
- Who suits ·
- HTML and CSS. Astro helps but is learnable in an afternoon.
- Credit ·
- Commit history is yours, plus a credit on the contributors list.
Take this role → Build
Exercise author
Write a practical AI exercise — a task a learner does with a real tool, with a way to tell whether they got it right.
- Time ·
- 3–5 hours per exercise
- Who suits ·
- You have taught something before, or wish someone had set you this task.
- Credit ·
- Named as author on the exercise.
Take this role → Community
Learner advocate
Answer questions from new learners, flag repeated confusion, and tell us which lesson keeps generating the same question.
- Time ·
- 2–3 hours a month, ongoing
- Who suits ·
- Patience. Being one lesson ahead is enough to help someone.
- Credit ·
- Listed as an advocate, with as much or as little visibility as you want.
Take this role → How it works
No application form, no interview, no onboarding call.
- Email the role name. One line is enough: which role, and roughly when you have the time.
- We send you one unit of work. A specific lesson, page or issue, plus whatever you need to do it — the pronunciation sheet, the style note, the repo link.
- You do it and send it back. Or tell us you would rather not, which is a perfectly good outcome and costs nothing.
- It ships, credited and logged. Your change goes live, your hours enter the public ledger, and your name appears if you asked for it.
Ground rules
- Lessons stay free. Anything you contribute is published under the same open terms as the rest of the site.
- Do not submit material you do not have the right to give us — no lifted text, no copied images, no employer's work.
- AI-assisted drafting is fine if you have checked it. Unchecked machine output is worse than nothing, and we can tell.
- Learners come first. If a change makes the site prettier but harder to read, it does not ship.
Not sure you're qualified?
Proofreading and accessibility testing need no credentials at all — a learner who
got stuck is the best person to say where.
If you are under 18
You are welcome to volunteer, and younger contributors are often the best
proofreaders — you notice the sentence that lost you. But volunteering means we
hold an email address, and where the contributor is a child the law asks for a
parent or guardian's consent first. That is India's DPDP Act, and the GDPR and
COPPA equivalents elsewhere.
So the first email is a short one:
- Tell us the role you want and that you are under 18.
- Give us a parent or guardian's email address.
- We write to them, explaining exactly what you would be doing and what we
would hold. They reply to confirm — that reply is the consent,
not a box you tick for them.
- Then we send you the work.
We never publish an under-18 contributor's name or contact details, even with
consent. Your guardian can withdraw it at any time by emailing us, and we act on
that immediately. Full detail on the privacy page.
Start with one lesson
Say which role and we will send you something specific within two working days.
If it turns out not to suit you, that is useful information too.
lrnon.org@gmail.com · +91 81782 31945
Lrnon