Skip to main content

πŸ“ Lesson 8.3: Capstone β€” A Complete, Polished, Structured Document

This is it β€” the finale. Across twenty-three lessons you learned to write, structure, style, and present documents by meaning rather than by hand. Now you'll put every one of those skills together in a single guided build: a complete, polished, professionally structured document you'll be genuinely proud to send. We'll follow the through-line that's run through the whole course β€” Content β†’ Structure β†’ Presentation β€” and finish with a rubric so you can grade your own work like a pro.

πŸ“š What You'll Learn

By the end of this lesson, you will be able to:

  • Build a complete document end-to-end using the Content β†’ Structure β†’ Presentation flow
  • Apply a full Style hierarchy β€” Title, Heading 1/2/3, and body β€” as the document's backbone
  • Add real structure: a cover page, automatic table of contents, sections, headers/footers, page numbers, and footnotes
  • Place visuals β€” an image with wrapping and alt text, a table, and optionally SmartArt or a chart β€” cleanly
  • Polish and finish: a consistent theme, an accessibility check, and an export to PDF β€” and optionally share via OneDrive with Track Changes

⏱️ Estimated Time: 90 minutes

🎯 Project: Build one complete, polished, structured document β€” a project report or a professional portfolio piece β€” from blank page to accessible, exported PDF, graded against a rubric.

In This Lesson

The Whole Course in One Document

Everything you've learned was leading here. A capstone isn't a new topic β€” it's the moment you stop learning skills one at a time and use them all together, the way a real document demands. That's a different kind of confidence. Anyone can apply a heading style in a lesson about heading styles; the mark of real fluency is reaching for the right tool automatically, in the right order, while your attention is on the content where it belongs.

So we'll build in the order the whole course has taught β€” the order a good document naturally comes together:

graph LR A["✍️ Content
draft the words first"] --> B["πŸ—οΈ Structure
Styles · TOC · sections · footnotes"] B --> C["🎨 Presentation
visuals Β· theme Β· polish"] C --> D["πŸš€ Finish
accessibility Β· export Β· share"] D -. "restyle any time via" .-> B

Notice the same dotted arrow from Lesson 1.1: because presentation flows from structure, you can restyle the whole document at the end by changing its Styles and theme β€” no hunting through pages to re-format headings. That one idea is the hinge the entire document turns on, and this capstone is where you feel its full weight. Build the skeleton right, and the polish is almost free.

🧠 Mindset

Don't aim for perfect on the first pass β€” aim for done in layers. Get the content down without fussing over how it looks. Then add structure. Then polish. If you try to write, style, and lay out simultaneously, you'll grind to a halt. Trust the order: it's exactly the discipline that makes professionals fast. You already know every step here β€” this is a victory lap, not an exam.

Step 1 β€” Content: Draft the Words

Start with a blank document and write the content first, plainly, without touching formatting. Resist every urge to bold, resize, or center as you go β€” that's the habit we've spent the course unlearning. Just get the words down as ordinary paragraphs, using the built-in Normal style for body text. It's fine if it looks unstyled and flat right now; that's the point of the layer.

Pick a document with real substance so the structure has something to hold. Two great choices:

  • A project report β€” an executive summary, background, findings organized under a few headings and subheadings, a data table, a chart, and a conclusion. This is our worked example below.
  • A professional portfolio document β€” an intro/bio, sections for skills, projects, and experience, an image, and contact details. Great if you'd rather build something about you.

As you draft, think in terms of the outline you'll need β€” top-level sections, subsections under them β€” even though you're not applying any heading styles yet. Just type each heading on its own line as plain text; you'll promote them to real Heading styles in the next step. Aim for enough content that a table of contents will genuinely help: a few pages, several headings, a couple of subheadings.

πŸ’‘ Our worked example: a project report

Throughout the steps below we'll build a report titled "Community Garden Proposal." Its plain-text outline before any styling: a title line, then sections β€” Executive Summary, Background, Proposal (with subsections Site, Budget, Timeline), Expected Impact, and Conclusion β€” as ordinary paragraphs. You'll follow the same steps with your chosen document.

⚠️ Remember the golden rule: spacing lives in paragraph settings, not blank lines; indents use the ruler or paragraph dialog, not spaces; and headings are Heading styles, not hand-bolded lines. Draft now in plain Normal text and you'll have nothing to undo when you add structure next.

Step 2 β€” Structure: Styles, TOC, Sections, Footnotes

Now give your words a skeleton. This is the heart of the whole course, and doing it in the right sub-order makes everything downstream β€” the table of contents, the navigation, the polish β€” build itself.

2a. Apply the full Style hierarchy

Go through your draft and apply styles from the Home > Styles gallery by meaning:

  • Your document's main title β†’ Title style (once, at the top).
  • Each top-level section heading β†’ Heading 1.
  • Each subsection β†’ Heading 2; sub-subsections β†’ Heading 3. Don't skip levels.
  • All ordinary paragraphs β†’ Normal (body) β€” usually already set from drafting.

Open the Navigation pane (View > Navigation Pane) and watch your outline appear. If it looks right there, your structure is right β€” and the table of contents is now trivial.

2b. Add the cover page and automatic table of contents

  • Cover page: Insert > Cover Page and pick a built-in design; it drops in title/subtitle/author placeholders you fill in. (At the time of writing, the Cover Page gallery is a desktop-app feature; on the web, build a simple cover β€” a Title-styled title, a subtitle, and your name, followed by a page break β€” exactly as in Lesson 7.1.)
  • Table of contents: place your cursor on a fresh page after the cover, then References > Table of Contents and choose an automatic style. Because your headings are real Heading styles, Word builds the TOC from them instantly β€” and you can Update Table whenever the document changes.

2c. Sections, headers/footers & page numbers

  • Section break: use Layout > Breaks > Section Breaks so the cover and TOC can have different (or no) page numbering from the body.
  • Headers/footers: Insert > Header / Footer β€” add the document title or your name.
  • Page numbers: Insert > Page Number; typically start numbering at the first body page, not the cover. Use the steps from Lesson 7.1: in the first body page's footer turn off Link to Previous, insert the number, then set Page Number > Format Page Numbers > Start at 1. (On the web, if those controls aren't available, tick Different First Page so the cover stays clean β€” Lesson 7.1's web route.)

2d. Footnotes

Where you cite a source or add an aside, put your cursor there and use References > Insert Footnote. Word numbers them automatically and keeps them anchored to the right page, renumbering if you add or move one.

⚠️ Web vs desktop

The full cover-page gallery, some section-break precision, and the richest footnote/reference tools are strongest in the desktop app. Word for the web handles the essentials β€” Styles, an automatic TOC, headers/footers, page numbers, and footnotes β€” very well, but you may find fewer design choices. If a specific gallery item isn't there, the underlying structure is what matters and it still works. Menu names shift between versions and platforms; trust the concept over the exact label.

Stop and appreciate this: you now have a navigable document with a self-building table of contents, consistent headings, page numbers, and footnotes β€” and you got it almost for free because you built with Styles. That is the entire promise of the course, delivered.

Step 3 β€” Presentation: Visuals, Theme & Polish

With content and structure solid, presentation is the fun, fast part. Because everything is styled by meaning, you polish by adjusting definitions, not by hand-editing every element.

3a. Add visuals β€” placed cleanly

  • An image with wrapping + alt text: Insert > Pictures, then set text wrapping via the Layout Options handle (e.g., Square or Tight) so text flows around it. Immediately add alt text (right-click > View Alt Text) β€” you learned in Lesson 8.2 why this matters.
  • A table: Insert > Table for your data (in the report, a budget table). Give it a header row via Table Design and keep it simple β€” no merged-cell mazes.
  • Optional β€” SmartArt or a chart: Insert > SmartArt for a process or hierarchy diagram, or Insert > Chart to visualize the data in your table. Add alt text to these too.

3b. Apply a consistent theme

Here's the payoff moment. On the Design tab, pick a Theme (and a Style Set / color and font scheme). (Themes are a desktop-app feature at the time of writing; on the web, adjust the Heading and Normal styles' fonts and colors instead, as in Lesson 7.1 β€” the effect is the same.) Because your headings and body are real Styles, the entire document restyles at once β€” fonts, heading colors, spacing β€” all coordinated, in a single click. Try two or three themes and watch the whole document transform instantly. That is what formatting by meaning buys you.

3c. Polish pass

  • Update the TOC (References > Update Table > Update entire table) so page numbers reflect the final layout.
  • Check that headings don't dangle at page bottoms and that images sit where you want relative to their text.
  • Run Editor (Home > Editor) for a last spelling/grammar/clarity sweep.
  • Read it once, top to bottom, as a reader would.

πŸ’‘ The theme test

If switching themes on the Design tab (or, on the web, changing the Heading and Normal styles' fonts) cleanly restyles your whole document β€” every heading, every body paragraph β€” congratulations: your structure is genuinely sound. If some text stubbornly keeps its old look, that text was hand-formatted rather than styled, and it's ignoring the theme. That little test is a perfect diagnostic for whether you built by meaning.

Step 4 β€” Finish: Accessibility, Export & Optional Share

The last mile, straight from Lesson 8.2 β€” this is what makes it a finished document rather than a draft that looks nice on your screen.

4a. Accessibility check

Run Review > Check Accessibility. Fix Errors first (usually alt text and table header rows), then Warnings and Tips (heading order, link text, contrast, reading order). Re-run until it reports "No accessibility issues found." Because you built with real Styles, most of this passes already β€” you're mostly confirming and adding alt text.

4b. Export a tagged PDF

Use File > Export (or Save As > PDF). In the desktop app, open Options and keep "Document structure tags for accessibility" on so your headings, alt text, and reading order travel into the PDF. Open the PDF and confirm the cover, TOC, page numbers, and visuals all came through. This is your shippable, universal final form.

4c. Optional β€” share via OneDrive with Track Changes

To get feedback like a professional, save to OneDrive, turn on Review > Track Changes, and use Share to invite a reviewer (Lessons 5.1–5.2). Their edits and comments come back marked so you can accept or reject each one β€” real collaboration on a real document, the way it works in a workplace.

# Step Key commands
1Content β€” draft plainly in NormalJust type; no formatting
2Styles β€” Title, Heading 1/2/3, bodyHome > Styles; View > Navigation Pane
3Cover + TOCInsert > Cover Page; References > Table of Contents
4Sections, headers/footers, page numbersLayout > Breaks; Insert > Header/Page Number
5FootnotesReferences > Insert Footnote
6Visuals β€” image + wrap + alt text, table, chart/SmartArtInsert > Pictures / Table / Chart / SmartArt
7Theme β€” consistent look in one clickDesign > Themes (desktop; on the web adjust Styles/colors as in Lesson 7.1)
8Polish β€” update TOC, Editor, read-throughReferences > Update Table; Home > Editor
9Accessibility checkReview > Check Accessibility
10Export tagged PDF (optional: share via OneDrive)File > Export; Review > Track Changes

The Rubric β€” Grade Your Own Work

A professional checks their own work against a standard before it goes out. Here's the rubric for your capstone, organized by the three layers. Aim to answer "yes" to every line β€” and where you can't, you know exactly which lesson to revisit.

Layer Criterion Standard to meet
Content Complete & clear The document says what it needs to, in your own clear voice, with no placeholder text left
Proofed Editor run; no spelling/grammar errors; reads cleanly aloud
Structure Style hierarchy Title + Heading 1/2/3 applied by meaning; Navigation pane shows a correct outline
Automatic TOC A real, updatable table of contents built from headings β€” not typed by hand
Cover, sections, headers/footers, page numbers Cover page present; body paginated; header/footer and page numbers correct
Footnotes At least one footnote, auto-numbered and correctly anchored
Presentation Visuals An image with text wrapping + alt text, and a table with a header row (optionally SmartArt/chart)
Consistent theme One coherent theme; switching themes restyles the whole doc cleanly (the theme test passes)
Accessible & exported Accessibility Checker clean; exported as a tagged PDF that reproduces the document faithfully

πŸŽ“ If every row is "yes"…

…then you have built a complete, polished, structured, accessible document β€” the exact thing this course promised on day one, and a genuinely professional deliverable. That's not a beginner's document. That's the work of someone who understands Word.

🎯 Project: Your Capstone Document

This is the big one. Build one complete document from blank page to exported PDF, following the four-step flow and grading it against the rubric above. Use the through-line document from your very first Word Plan (Lesson 1.1) if you can β€” finishing the exact thing you set out to build is the most satisfying possible ending.

πŸ‹οΈ Build a complete, polished, structured document

Objective: Produce a multi-page project report (or professional portfolio document) that passes every line of the rubric, and export it as a tagged, accessible PDF.

Instructions (about 60–75 minutes):

  1. (15 min) Content: Start blank. Draft the full text in Normal style β€” title, sections, subsections, a paragraph or two under each. No formatting yet.
  2. (15 min) Structure: Apply Title + Heading 1/2/3; check the Navigation pane; add a cover page and an automatic TOC; add section break, header/footer, and page numbers; insert at least one footnote.
  3. (15 min) Presentation: Insert an image with text wrapping and alt text, a table with a header row, and optionally a chart or SmartArt with alt text; apply a consistent Design theme (web: adjust Styles/colors); update the TOC.
  4. (10 min) Finish: Run Editor; run Review > Check Accessibility and fix everything to "No issues found" (then confirm your headings in the Navigation pane β€” the checker doesn't catch everything); export a tagged PDF and open it to verify.
  5. (5 min, optional) Share: Save to OneDrive, turn on Track Changes, and share it with someone for feedback.
  6. (5 min) Grade: Go through the rubric line by line. Fix any "no" before you call it done.
πŸ’‘ Hint β€” the build order at a glance
CAPSTONE BUILD ORDER

CONTENT
  [ ] Draft all text in Normal style β€” no formatting

STRUCTURE
  [ ] Title style on the title
  [ ] Heading 1 / 2 / 3 by meaning (check Navigation pane)
  [ ] Insert > Cover Page
  [ ] References > Table of Contents (automatic)
  [ ] Layout > Breaks (section) ; Header/Footer ; Page Numbers
  [ ] References > Insert Footnote (at least one)

PRESENTATION
  [ ] Insert image β†’ set wrapping β†’ ADD ALT TEXT
  [ ] Insert table β†’ header row
  [ ] (optional) Chart or SmartArt β†’ alt text
  [ ] Design > Themes β†’ one consistent theme
      (web: modify Heading/Normal styles' fonts & colors)
  [ ] References > Update Table

FINISH
  [ ] Home > Editor (spelling/grammar/clarity)
  [ ] Review > Check Accessibility β†’ "No issues found"
  [ ] File > Export β†’ tagged PDF β†’ open & verify
  [ ] (optional) OneDrive + Track Changes + Share
  [ ] Grade against the rubric β€” fix every "no"

Work top to bottom and resist jumping ahead. The order is the whole trick β€” it's what makes the polish almost effortless.

βœ… Project Completion Checklist

  • Content drafted first in Normal, then styled β€” not hand-formatted as you typed
  • Full Style hierarchy applied; Navigation pane shows a correct outline
  • Cover page, automatic TOC, sections, header/footer, page numbers, and a footnote all present
  • An image (with wrapping + alt text) and a table (with header row); optionally SmartArt/chart
  • One consistent theme applied; the theme test passes
  • Accessibility Checker clean and a tagged PDF exported and verified
  • You graded it against the rubric and fixed every "no"

🎯 Quick Quiz

Question 1: What's the correct order to build the capstone document?

Question 2: You switch themes on the Design tab (or, on the web, change the Heading and Normal styles' fonts) and one block of text refuses to change. What does that tell you?

Best Practices for the Capstone (and Every Document After)

βœ… Do's

  • Build in layers, in order. Content, then structure, then presentation, then finish. It's faster and it's how professionals work.
  • Style by meaning. Title, Heading 1/2/3, body β€” so the TOC, navigation, theme, and accessibility all "just work."
  • Add alt text as you insert visuals, not as an afterthought at the end.
  • Use the theme test to verify your structure is genuinely sound before you finish.
  • Grade against the rubric before you send. Catch your own gaps first.

❌ Don'ts

  • Don't hand-format headings or type a table of contents. After this whole course, you know better β€” let Styles do it.
  • Don't skip the accessibility check just because it "looks fine" β€” looking fine and being usable for everyone aren't the same.
  • Don't export an untagged PDF when you've done the work to make the document accessible.
  • Don't try to perfect the content and the layout at the same time. Layers, in order.

πŸ’‘ Pro Tips

  • Save your finished document as a template (Lesson 6.1) so your next report starts from this polished structure instead of a blank page.
  • Keep the ten-step table from this lesson somewhere handy β€” it's a reusable recipe for every serious document you'll ever build.

πŸ““ Learning Journal

Keep a learning journal as you work through this course β€” a separate document, a note, or even a second Word file right beside the one you're building. After each lesson, take a few minutes to write down:

  • Key concepts you learned
  • Techniques that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try in your own documents
  • Your progress and feelings about learning this β€” including where your confidence grew

✍️ This lesson's prompt (your final entry): Look back at your very first journal entry from Lesson 1.1 β€” your honest starting attitude toward Word, and what "documents I'm proud of" would let you do. How does it feel to read it now, having built a complete, polished, structured document? What's the single most valuable thing you learned in this course, and what's the next real document you're going to build with it? Then give yourself credit β€” you finished.

πŸ“ Lesson Summary & Congratulations

πŸŽ“ Key Takeaways

  • A great document is built in layers, in order: Content β†’ Structure β†’ Presentation β†’ Finish. That order is the whole course in one sentence.
  • The Style hierarchy (Title, Heading 1/2/3, body) is the backbone: it powers the Navigation pane, an automatic TOC, one-click theming, and accessibility all at once.
  • Structure means a cover page, an automatic table of contents, sections, headers/footers, page numbers, and footnotes β€” all self-maintaining because you built by meaning.
  • Presentation β€” visuals with wrapping and alt text, a table, optional SmartArt/chart, and a consistent theme β€” flows from that structure, so polish is nearly effortless.
  • Finish with an accessibility check and a tagged PDF export (optionally share via OneDrive with Track Changes), and grade the result against the rubric.

πŸŽ‰ What You've Accomplished

You started this course at a blank page, unsure whether Word was worth the trouble. You end it having built a complete, polished, professionally structured, accessible document β€” the exact thing Lesson 1.1 promised. Along the way you internalized the one idea that changes everything: format by meaning, not by hand. That skill will save you time on every report, application, and letter you ever write β€” and it transfers to Google Docs and any word processor you meet. You didn't just learn Word. You learned how documents work. That's real, durable, professional capability, and you earned it.

❓ Common Questions at This Stage

My capstone isn't perfect. Did I still "finish" the course?

Absolutely. No real document is ever perfect, and the goal was never perfection β€” it was building a complete, structured document using the whole toolkit. If you drafted content, applied real Styles, built an automatic TOC, added visuals with alt text, themed it, and exported an accessible PDF, you've done exactly what a professional does. Polish improves with every document; the method is what you've mastered.

Where should I go from here to keep improving?

Build real documents β€” that's where fluency comes from. Turn your capstone into a template so your next one starts strong. Revisit any lesson whose skill felt shaky. And explore the sibling courses below: the concepts you learned here transfer directly to Google Docs and to the other Microsoft 365 apps.

Do I need the paid desktop app or Copilot to keep using these skills?

No. Nearly everything in this course β€” Styles, headings, TOC, sections, visuals, accessibility, PDF export β€” works in free Word for the web with a Microsoft account. The desktop app and Microsoft 365 add power and offline use, and Copilot is an optional paid accelerator, but the core professional skills you built are free to keep using forever.

🎊 Congratulations β€” You Finished the Course!

That's all twenty-four lessons. Take a moment β€” this was a real body of work, and you saw it through. If you'd like to keep building your Microsoft 365 and document skills, here's where to go next:

Most of all: keep practicing. Skills fade without use and sharpen with it. Build your next real document this week β€” a report, a rΓ©sumΓ©, a letter β€” using the ten-step recipe from this lesson. The gap between "learned it" and "owns it" is a handful of real documents, and you're already most of the way there.

πŸ“š Additional Resources

🌟 Congratulations from Ray

You did it. From a blank page and an honest question β€” "is Word worth it?" β€” to a polished, structured, accessible document you'd proudly send anyone. That journey is the whole point, and you walked every step of it. Be proud: you don't just use Word now, you understand it β€” and that understanding travels with you to every document and every tool you'll ever touch. Now go build something real. πŸŽ‰πŸ“