Submodule Title Goes Here
Program: program nameModule: module nameSubmodule: submodule name
Framing paragraph — 2–4 sentences describing what this submodule covers and which questions it answers. Optionally list the questions as a numbered list.
1. Section Title
1.1 Subsection
Prose. Prefer short paragraphs, bullet lists, and tables over long walls of text. Bold key terms on first use.
| Column A | Column B |
|---|---|
| ... | ... |
1.2 Subsection
...
2. Section Title
...
3. Section Title (with a diagram)
Explanation of the diagram.
4. Key Takeaways
- One-line summary of the most important idea.
- Another key idea.
- Common misconception this submodule corrected.
- Forward pointer: "the next submodule builds on X".
5. Glossary
| Term | Definition |
|---|---|
| Term A | Definition. |
| Term B | Definition. |
6. What's Next
- Next submodule title — one-line description of what it covers.
- Later submodule — one-line description.
Style rules for this repository
- One file per submodule. Do not concatenate submodules into a single file.
- Section numbering (1, 2, 3, ...) is stable. Every submodule has sections 1 (main content) through 6 (What's Next). Add subsections as needed.
- Bold on first use for terms that appear in the glossary.
- Prefer tables for definitions/comparisons; prefer mermaid for relationships.
- Keep sentences short. This is a study reference, not an essay.
- When referencing another submodule, use a relative markdown link so it works both on GitHub and on the VitePress site.
- Any term added to a submodule glossary should also be added to the shared glossary if it is likely to be reused across programs.
- Do not use bare angle brackets (like
<placeholder>) in markdown files — VitePress will try to parse them as Vue components and fail the build. Use italics or backticks instead.