33 min read
Advanced Document Engineering
Style architecture, fields, master documents, and WordprocessingML.
Style and section architecture
IT asks James for a map: Heading 1 = chapter, Heading 2 = policy clause, each major part starts with a Next Page section break. Headers change per section (Roman TOC vs Arabic body).
Document the map in a one-page table inside the project folder — which styles, which breaks, which numbering restarts.
Field and caption systems
Figures use SEQ Figure, tables SEQ Table, equations SEQ Equation. Headings must use styles so TOC \o "1-3" field works. StyleRef in headers pulls current Heading 1 text.
Avoid manual "Section 3.2" typing anywhere — if numbers appear in prose, they should be cross-references or multilevel lists.
Hands-on steps
Goal
Document the handbook's section-break and heading map on an internal page.
James Okonkwo adds this to NorthgateHandbook.docx as part of one polished student handbook, policy pack, and open-day collateral before families arrive.
List sections
Where
Do this
You should see
- Breaks visible.
Verification
Check your work
You are correct if all of these are true:
- Every major handbook part (cover, TOC, body, appendix) has a documented section break.
- Navigation Pane shows no Heading 3 before Heading 2.
- Architecture table matches what you see with ¶ turned on.
More lessons in Microsoft Word · Next: Long Documents · Previous: VBA & Macros