Learn ZeruxJS, one working step at a time

An eight-lesson, self-paced path from a first request to a verified application—with exercises and browser-local progress.

No assumed framework knowledge#

You do not need to know every package or understand every type table before starting. Begin with what a browser asks for, make one route respond, and add one responsibility at a time. Each lesson includes a plain-language explanation, a concrete example, an expected result, an exercise and a short knowledge check.

The course takes roughly two to three hours plus practice time. It teaches the implemented 0.0.4 package contracts used by this 0.0.4 documentation preview. It is not a certification, a production security review or a promise that every ecosystem package is complete.

Two ways through the handbook#

New to coding or building with AI? Follow the lessons in order. Keep the glossary open. Ask your tool to explain the change, inspect the files it touches, run the example and compare the real result with the expected result. Never paste a private environment file into an AI prompt or issue.

Already develop applications? Skip directly to configuration, request context, plugin contracts or the solution finder. The course still offers practical checks for ownership, request isolation, caches and deployment differences.

How progress and points work#

Each lesson has two questions worth 10 points each. Correct answers earn points once; retries do not farm more points. A lesson is complete after both questions are answered correctly and you confirm you tried its exercise. Lessons never lock the next page. Answers and explanations remain readable without JavaScript.

With browser storage available, your answers, exercise confirmations, bookmarks and recent pages stay in this browser for this documentation mount/version. There is no account, sync service, leaderboard or telemetry. Clearing site data removes progress; private browsing may discard it. These points are a learning aid, not a credential. Use the progress panel to export, reset or continue locally. The settings/help page explains offline reading and keyboard controls.

Learn by making and explaining#

After each working change, explain what the request reads, what it returns, who owns any stored data and what happens on failure. If you cannot explain it, reduce the example before adding another package. A small application you can verify is a stronger foundation than a large generated application you cannot debug.

Choose a lesson#

The lesson list below remains ordinary links without JavaScript. Enhanced progress is optional. You can revisit any lesson or jump straight to a task.