Reference pages for maker learning paths.

Pick the reference by what you are checking

If you are about to run a command, start with safe command patterns or the command-line checklist. If a site does not load, use the DNS troubleshooting page and VPS lab. If a term is blocking understanding, use the glossary. If you need spaced review, use the Linux and VPS flashcards.

The reference index exists to make repeatable checks easy to find. It should keep project pages shorter while still giving learners a place to inspect terms, warnings, and next commands.

For a first website deploy, keep this page open beside the VPS project path. Use the glossary when words like apex domain, server block, certificate, current release, or rollback stop making sense. Use the command checklist when you know the question but need the smallest read-only command. Use the safe command patterns page before deleting files, changing permissions, syncing releases, opening ports, or restarting services.

For a project notebook, turn references into short notes instead of copying every page. A useful note says what you checked, which reference explained the term, which command proved the next fact, and what you will try next. That keeps the reference system connected to the thing you are building.

For review practice, pair references with decks and labs. The deck helps remember terms and traps; the lab asks you to choose commands and interpret output; the project path ties the same ideas back to a finished artifact. This loop is more useful than rereading one page many times.

If a reference page feels too broad, use the related project and related asset links on each card. They are meant to route you to the context where that reference matters. A glossary term should not live alone; it should point to a command, a project, a lab, or a troubleshooting path.