000 Orientation

Start the Stackpress course path by learning how the site is organized and why the lessons are numbered. The course is meant to feel like a guided book, so each page gives you enough context to continue without turning the first visit into a reference hunt.

Course context: This is the first course page, so there is no earlier Stackpress lesson to review. Use it to understand how the course path works before the technical pages begin.

000.1. Why The Course Starts Here

Stackpress combines runtime code, generated code, database access, views, built-ins, and AI workflows. That is useful, but it can feel like too many doors at once if the first page tries to explain every package and every API.

The course path solves that by giving you one surface at a time. You start with a running app, then add plugins, pages, data, generated output, built-ins, Studio concepts, and AI workflows after the earlier ideas have somewhere to attach.

000.2. How The Numbering Works

The first pages use 000, 001, and 002 for orientation and first success. After that, 100 through 150 cover runtime development, 200 covers data, 300 covers build and deploy, and the later levels add project structure, idea files, built-ins, Studio, and AI.

The tens digit usually marks a parent topic. For example, 110 Plugins introduces the plugin group, and 111 Composition plus 112 Local Plugins teach the focused runtime lessons inside that group.

000.3. How To Read Ahead

You can open any page directly, but the course assumes earlier levels have already introduced the vocabulary. If you jump to a later page and a word feels unfamiliar, go back to the nearest parent page first because it explains why that group exists.

Reference pages have a different job. A course page teaches the path and the mental model, while a reference page helps you look up exact exports, options, method names, and field shapes after you know what problem you are solving.

000.4. What Comes After Orientation

The next page, 001 What Stackpress Is, explains the framework at a high level. Read it before creating the first app because it gives names to the runtime, generation, data, and view pieces you will meet later.

After that, 002 Getting Started starts the hands-on path. The early goal is not to understand every Stackpress package; the early goal is to make a small app answer a request and know which file made that happen.

Learning checkpoint: Before moving on, make sure you can explain why the course uses numbered levels and why parent pages exist. You should also know the difference between reading a course page and opening a reference page.

Next course: Continue with What Stackpress Is. The next page gives names to the main Stackpress pieces so the first hands-on lesson has a map to follow.