Filename Basics
The Big Idea
Files in a project reference each other by name. If names are inconsistent, links break and tools get confused. Using a standard naming convention keeps everything working across all operating systems and browsers.
Your Roadmap
| Section | Time | Required? |
|---|---|---|
| The rules | 2 min | ⚑ Required |
| Filenames in this handbook | 1 min | ⚑ Required |
The rules
| Rule | Example |
|---|---|
| Lowercase only | index.html |
| Hyphens between words | my-reflections-sprint-1.md |
| Letters and numbers only (a–z, 0–9) | — |
Why lowercase? Some operating systems are case-sensitive. Lowercase works everywhere.
Why hyphens, not spaces? Spaces break URLs. Some tools replace them with %20, which breaks links.
Why hyphens, not underscores? Search engines treat hyphens as word separators. Underscores are not handled the same way.
Filenames in this handbook
When the handbook specifies a filename, use that filename exactly. Your facilitator uses filenames to find and mark your work — a wrong name means your work may not be found.
Outside Foundations: keep names short (under 25 characters), descriptive, and avoid generic names like document1.html.
The Big Idea (revisited)
Lowercase, hyphens, alphanumeric only. When the handbook gives you a filename, use it exactly.