Book an AI strategy call
Nexus Drivers Ed sells four Texas course paths to six audiences and issues state certificates on completion. Conventional learning platforms treat a course as a single live structure, so every edit risks breaking an enrolled learner’s progress, and the link between the certificate and the course it certifies. Nexvix built four applications around one rule instead.
Regulated educationLearning platformBilingual EN / ESContent versioningCertificatesEvery figure on this page is the brand’s own published reporting or a countable property of the platform. Nexvix does not publish a client metric without permission.
A compliance constraint, not a feature request. It shaped the whole build.
Driver education is not a hobby course. When a learner finishes, the provider issues a state certificate that a licensing office will rely on. The certificate has to be traceable to the exact course the student took: which lessons, which exam, which pass mark, on which version of the material. “We changed the course last month” is not an acceptable answer to a licensing question.
Off-the-shelf platforms share one failure mode. A course is a single live structure that editors change in place, and a learner’s progress is a position inside that list. The moment an editor inserts a lesson, reorders a chapter or removes a quiz, every enrolled learner’s saved position quietly changes meaning: some get stuck on content that no longer exists, some are marked complete on content they never saw, some find their course rearranged under them mid-way.
For a hobby platform that is an annoyance. For a state-approved provider it is a compliance exposure: the course a learner certifies against is no longer the course they were taught. The brand had already lived through it.
The second constraint was parity. The Spanish course is not a translated brochure; it is a full course that must earn the same certificate and behave identically on every screen.
A mutable syllabus and a stored position cannot coexist safely. That is the problem the platform was built to remove.
SYSTEM DESIGN, WEEK 2
Texas does not have one driver-education course. Each path is tied to a different legal requirement, a different certificate and a different buyer, and the marketing site reads all of them from the catalog the API publishes.
Adults 18–24 who must complete an approved adult course, and adults 25+ preparing for or bypassing the DPS written test. Issues the ADE-1317 certificate with the DPS-approved written exam included.
Teens beginning the licensing process with the online classroom portion. Issues the DE-964 certificate used to apply for a learner licence.
Families who complete the classroom portion online while a parent leads behind-the-wheel practice. Eleven milestones, finishing in a timed final exam drawn from a question bank.
The full adult course in Spanish, earning the same certificate as the English course, not a translation layered over an English original.
Learners already enrolled finish the revision they started; learners who arrive after a publish receive the new one. Three independent layers make that real, and each one deliberately knows nothing about the others.
Every course belongs to a family. A draft is a complete copy of the structure; lessons and assessments carry over by stable identity. A Validate action runs every publishing rule and reports plain-language remedies, not error codes.
Opened by a personEach publish writes an immutable, checksummed content version including a complete copy of every embedded quiz. A learner is pinned to the version they first opened, and quiz answers are scored against that version.
Handled by the systemPublishing an assessment freezes the pass mark, time limit, attempt allowance, review policy and selection logic. Starting an exam snapshots the exact questions and their order with the attempt.
Handled by the systemBefore any publish or delete, the editor sees two panels side by side: what happens to learners who are already here, and what happens to learners who arrive after this.
Approved by a personEditors never have to remember the versioning rules, because a published revision simply does not open as an editable form.
Course authoring follows the curriculum hierarchy exactly: a course is a sequence of milestones, a milestone holds chapters, assessments and to-do items in order, a chapter holds lessons, and a lesson carries text, video or audio content plus optional embedded quizzes. Every structural page is revision-aware: a draft is fully editable and carries a reminder that nothing reaches a learner until publish; a published revision renders as a read-only outline with the reason stated.
Deletion needed its own rules. When an editor deletes a row from a draft the platform decides what that means per row and says which outcome applied: a row born in the draft and seen by no learner is removed outright, a row shared with a published revision is detached from the draft only, and a row any learner’s history references is protected: the deletion is refused and nothing changes.
A learner signs up, works through sequential lessons with pacing timers and embedded quizzes, sits a timed final exam and downloads the state certificate. The versioning is almost invisible: a small plain note says whether they are seeing content preserved for their enrolment or the current live content, and nothing more.
Course catalog, regulatory explainers, FAQ and search presence. Prices and course details are read from the API, never copied by hand.
Sign-up, checkout, sequential lessons, pacing, quizzes, timed final exam, progress and certificate. Mobile-first.
Revision-aware authoring, plain-language validation, question banks, media, orders, coupons, enrolments, certificates and analytics.
Who may edit what, which version a learner sees, whether an attempt counts, whether a payment is complete: all decided here, never in a browser.
The first two figures are the brand’s own published record over fifteen-plus years. The third is a countable property of the delivered system.
A curriculum change stopped being a risk and became a routine release.
Freedom to improve the course every day, and a guarantee that every learner finishes exactly the course they started and certifies against exactly the exam they sat. The trade-off, more moving parts on the server, is hidden from editors and learners alike, who see only a calm, predictable product.
One call, thirty minutes. Nexvix maps the process, names the measurable outcome and tells you whether a system is worth building. If it is not, you will hear that instead of a proposal.