From Proprietary Platform to Standards-Grounded Course
How a single district CS program replaced a licensed third-party platform with a custom, backwards-designed course that maps to every required state indicator — and how that work generalizes across a five-course pathway.
The district's computer science pathway ran on CodeHS, a proprietary platform. The arrangement carried three structural costs. First, a recurring license fee for content the district did not own and could not modify. Second, an alignment black box: the platform asserted coverage of Nevada CTE standards, but that mapping was the vendor's, not the district's, and could not be independently audited against the state's Appendix A indicators. Third, instructional rigidity — teachers delivered pre-built sequences they had no hand in designing, which made local adaptation, pacing changes, and standards remediation difficult.
For a program preparing for state CTE review, "the platform says it's covered" is not the same as "we can show, indicator by indicator, where it's covered." The goal became to close that gap.
- Recurring license cost for non-owned, non-modifiable content
- Vendor-asserted alignment that could not be locally verified
- Pre-built lessons that resisted teacher adaptation and remediation
The course was authored using backwards design: start from the required outcomes, then build instruction to meet them — the inverse of adopting a platform and hoping its scope matches the state's.
Indicator inventory
Every Appendix A indicator for the course was extracted into a structured inventory — the authoritative checklist the course had to satisfy, parsed directly from the state framework text.
VEX AIM robotics
A concrete, hands-on through-line (VEX AIM) anchors abstract technology-literacy indicators in physical, demonstrable student work rather than slideware.
Day-level anchoring
Each lesson names the indicators it addresses in a machine-readable standards block, so coverage is a property of the day plan itself — not an afterthought spreadsheet.
Automated crosswalk
A parser reads the lesson standards blocks, joins them against the indicator inventory, and surfaces any uncovered indicator as a gap — the same tool published in the Standards Auditor.
The decisive move is Step 4. Because the day plans are the single source of truth and the audit reads them directly, alignment stops being a claim and becomes a reproducible result. Edit a lesson, re-run the parser, and the coverage number updates. The crosswalk on this site is that pipeline, live.
The finished CET course maps to all 51 of 51 Appendix A indicators across a 5-block, 18-week plan — full coverage the district owns outright, with the license cost removed and every indicator traceable to a specific day of instruction.
The 51/51 figure is not a marketing number. It is the output of the same auditor any curriculum director can run here: select the CET course, and inspect each indicator against the lesson that covers it.
More important than the single course is the method. The same framework-out, audit-verified pipeline now backs a five-course pathway, each with its own published auditor:
Computer Education Technology
The featured build. CodeHS replacement on a VEX AIM spine; complete Appendix A coverage.
Advanced Computer Science I
A 17-unit course in JavaScript targeting dual compliance with Nevada CTE Level 1 and AP CSP, with an AI-literacy scaffold woven through every unit.
WDD I · DGD I & II
Web Development & Design and the Digital Game Design sequence round out the pathway — each built and audited on the identical standards-grounded method.