Executive summary
This opening paragraph uses a drop cap. Keep the executive summary tight: the problem, the proposed first step, and the outcome. The first sentence here doubles as a good TOC anchor — pick a distinctive phrase and put it in the config.
6–7
weeks
$XX K
investment + tax
4
milestones
01
Understanding
A lede paragraph introduces the section in a slightly larger size. Distinctive opening text makes a reliable TOC anchor.
1.1The pipeline
Source→
Transform→
Platform→
Output
Key risk to validate. Use accent callouts for the one or two things the reader must not miss. Use the
.cool variant for neutral notes.02
Scope
Body text for the scope section, with a distinctive opening phrase for the anchor.
| Layer | Technology | Version |
|---|---|---|
| Backend | .NET | 10 |
| Frontend | Angular | 21 |
| Database | PostgreSQL | 16 |
Stage 0 — Discovery~1 week
Short description of the stage and its deliverable.Stage 1 — Core~2 weeks
Short description of the stage and its deliverable.| Stage | Hours | Investment (MXN) |
|---|---|---|
| Discovery | 18 – 22 | $10,800 – $13,200 |
| Core | 32 – 39 | $19,200 – $23,400 |
| Total | 50 – 61 h | $30,000 – $36,600 |
A
Appendix
Traceability
Appendices start on a fresh page via the .break class. Distinctive opening phrase for the anchor here too.
Legend: ✅ Covered · ⚠️ Partial · ❌ Deferred
| ID | Requirement | Coverage | Notes |
|---|---|---|---|
| RF-01 | Example requirement | ✅ | Included |
| RF-02 | Another requirement | ⚠️ | Partial in MVP |
| RF-03 | A deferred requirement | ❌ | Later phase |
Your Name
Role · City