Sell coding lesson plans and computer science resources
Many teachers who now teach coding were never trained in it. Lessons that work on the first try, with clear setup notes, are what they are looking for.
Short answer: You can sell coding lesson plans and computer science resources on TeachLessons by applying with the short form and emailing your files, previews and Resource Submission List to support@stifo.de. You set your prices in US dollars and keep 70% of net revenue. Resources go live once set up, with no separate approval round.
Who buys coding lesson plans?
Three groups make up most of the demand. Elementary classroom teachers who have been asked to cover computational thinking once a week. Middle and high school teachers who moved over from math, science or business and now run an intro to programming course. And specialist computer science teachers who want ready projects, assessments and extension work so they can spend their time helping students debug.
Each group needs a different level of hand-holding. For the first two, write teacher notes that assume no coding background: what students will see on screen, the three most common errors and how to fix them, and what a finished project looks like. Specialists care more about the quality of the problems, the rubric and how the lesson builds on the last one.
Schools in different countries use different names. US teachers search for computer science and coding and often refer to the CSTA standards. In England the subject is Computing, from KS1 to GCSE and A level Computer Science. Australia has Digital Technologies. Use the term your main buyer uses in the title and mention the others in the description.
Which computer science resources are worth making?
Unplugged activities
Sorting algorithms with cards, binary bracelets, debugging a set of written directions. They need no devices, work in any school and suit younger grades.
Block-based project units
Step-by-step projects for block coding environments with a starter file, a finished example and challenge extensions.
Text-based programming units
Python or JavaScript lessons with starter code, worked solutions, test cases and a rubric.
Theory and vocabulary
Networks, data representation, cybersecurity basics and digital citizenship with diagrams you drew yourself.
Assessments
Quizzes, code-tracing questions, parsons problems and project rubrics with answer keys.
Physical computing
Lessons for microcontroller boards and simple robots, with wiring diagrams and a parts list.
Platform-neutral lessons have the widest market. An algorithm lesson that works in any block environment sells to more schools than one locked to a single paid product. When a lesson does depend on one tool, say so in the first line of the description.
Can I name coding platforms and tools in my resources?
You can describe what your resource works with, but you must not make it look official. A trademark identifies a company's product; using the name to describe compatibility is normal, using it as if your product came from or was approved by that company is not.
| Fine (descriptive) | Avoid |
|---|---|
| "Five project lessons for use with Scratch" | "Official Scratch curriculum" |
| "Python 3 practice problems" | Using a platform's logo on your cover or thumbnail |
| "Works with micro:bit boards" | Screenshots copied from a platform's own lesson materials |
| "Aligned to CSTA standards (teacher's alignment)" | "Approved by" or "certified by" wording you do not have |
Screenshots of your own code in a tool's interface are common in teaching materials, but read the tool's brand and terms pages, as some publish rules about this. Never copy lesson text, sprites, art assets or example projects from a platform's official resources, even if they are free for classroom use.
TeachLessons does not check resources for third-party rights. You confirm you created the resource or hold all rights, and you are responsible if a claim arises because of it.
How should I package code files and slides?
A coding lesson usually has more parts than a worksheet. Put them in one ZIP with a simple structure:
- Teacher-Guide.pdf with objectives, timing, setup steps and common errors.
- Slides as PPTX or a Google link, if teachers are meant to edit them.
- Starter and Solution folders with code files in the right format for the tool.
- Student handout as PDF, US Letter, A4 or both.
- README.txt listing the version you tested with (for example "tested with Python 3.12") and any libraries needed.
Version notes save you a lot of buyer emails. Tools and editors change their menus often; a line such as "screenshots from the 2026 interface" tells the teacher what to expect. Use clear file names like Loops-Lesson-3-Starter.py. Up to 100 MB per resource is possible, and large packs can go as one Drive, Dropbox or WeTransfer link that opens without a login.
Never include real student work, usernames or class codes in screenshots.
What should a coding resource preview show?
Teachers want to see the finished product and the support around it. A good preview set shows the final project (a screenshot of the running program), one page of step-by-step instructions, the teacher's troubleshooting notes and a slice of the rubric. A thumbnail with a large, readable label such as "Python Loops, Grades 8-10" works better than a busy screenshot of code. Required: previews and thumbnails as PNG or JPEG. More tips in how to make previews and thumbnails.
How should I price computer science units?
A tested unit with starter code, solutions and a rubric replaces many hours of a non-specialist's preparation. You set the price; our optional suggestion is a minimum of $4.99 for a single resource.
| Example | Price | Your payout per sale |
|---|---|---|
| Unplugged binary activity | $3.00 | $2.04 |
| Single project lesson with solution | $4.99 | $3.39 |
| Six-lesson intro to Python unit | $20.00 | $13.58 |
| Full semester course pack | $50.00 | $33.95 |
The payout formula is price x 0.97 x 0.70. No membership or listing fees. If you update a unit for a new tool version, email the new files and they replace the old ones. Run other numbers in the payout calculator.
How do I start selling my coding lessons?
- Apply with the short application form; it takes about five minutes.
- Read and sign the Seller Agreement we email you, and fill in the payout form and rights checklist.
- List each resource in the Resource Submission List, one row per resource, with the tool or language in the title.
- Send one email to support@stifo.de with documents, ZIP files, previews and thumbnails, or one shared link.
- We set everything up: product pages, SEO, your author page and landing pages. Resources go live once set up, so send tested, final versions.
For a large catalog, read how to submit many resources at once.
Frequently asked questions
Can I sell lessons that use a free coding platform?
Yes, if the lessons, code and images are your own work. Name the platform only to describe compatibility and do not imply your resource is official or endorsed.
Can I include screenshots of a coding tool?
Screenshots of your own work in a tool are common in teaching materials, but check the tool's brand guidelines and terms first. Do not copy its logos, art assets or official lesson materials.
What if the platform changes and my lesson goes out of date?
Email updated files to support@stifo.de and they replace the old version. Adding the tested version in a README helps buyers in the meantime.
Can I sell AI-assisted code examples?
You must hold the rights to everything you sell and check the tool's terms. Our page on selling resources made with AI tools covers the points to think about.
Do buyers need to be coding experts to use my lessons?
That is up to your design, but many buyers are not specialists. Clear teacher notes and troubleshooting tips make a resource far more useful to them.
How do I get paid?
Monthly by the 15th for the previous month's sales, via PayPal in US dollars, with a statement listing every sale.
Ready to sell your teaching resources?
Apply with the short form. We email you the seller documents, you send your final files with previews and thumbnails, and we set up your product pages, your author page and landing pages. You keep 70% of net revenue, with no fees and no exclusivity.
Keep reading
General information about the TeachLessons Seller Program, not legal, tax or financial advice. The signed Seller Agreement sets out the binding terms. Questions: support@stifo.de.