📝 Lesson 8.3: Capstone — Build a Complete, Polished, Structured Document

The Brief & the Plan

Remember the "Document Plan" you wrote way back in Lesson 1.1? This is where it grows up. A capstone isn't a drill — it's a genuine document you'll actually use. The single biggest predictor of a great result is the same as it was on day one: choose something real.

Pick a substantial document that fits one of these shapes:

• A full report — a research summary, a project report, an analysis with findings and recommendations.
• A guide or handbook — a how-to, an onboarding doc, a study guide, a policy or reference manual.
• A portfolio — a showcase of your work, a case-study collection, a creative or professional portfolio.
• A polished proposal — a business, grant, event, or project proposal built to persuade.

Then plan before you type. A little outlining now saves a lot of thrashing later:

1. Name the goal and the reader. One sentence: "This document helps [audience] to [do what]." Everything else serves that.
2. Sketch the sections. List the major headings (your Heading 1s), and under each, the sub-points (your Heading 2s). Aim for real depth — enough that a table of contents is genuinely useful.
3. Note the visuals. Where would an image, a table, or a drawing make a point clearer? Mark those spots now.
4. Decide the collaboration. Who could give you feedback? Even one reviewer makes the collaboration step real.

That's the whole capstone in five moves — the same arc as this course itself. Plan, structure, polish, collaborate, finalize. Notice it's just Content → Structure → Presentation with collaboration and delivery wrapped around it — the model you've carried since Lesson 1.1, now second nature.

Structure & Content

Build the skeleton first, then hang the words on it. This is the opposite of how most people start (they type and decorate as they go), and it's exactly why your document will come out cleaner.

Apply heading styles as you outline

Turn your outline into real structure. Mark each major section as Heading 1 and its subsections as Heading 2 / Heading 3 — using the styles menu or shortcuts like Ctrl+Alt+1 and Ctrl+Alt+2, not manual big-and-bold. This is the through-line of the entire course (Module 3): headings are structure, and structure powers everything downstream — the outline, the TOC, accessibility, and navigation.

Write and assemble the content

Now fill in the words. Don't aim for perfect on the first pass — get the substance down under each heading, then revise. If you have AI help available (Lesson 8.1), it's fine to use it to beat the blank page or rewrite a clumsy paragraph — just verify every fact and make the words your own. Lean on the document outline (the side panel) to jump around and keep your bearings as it grows.

Insert an automatic table of contents

Once your headings are in place, add the payoff: Insert > Table of contents (Lesson 3.2). Because you used real heading styles, Docs builds a live, clickable TOC automatically — and you can refresh it as your headings change. This one moment is the clearest proof of why structure matters: you get professional navigation for free, purely because you marked your headings properly.

⚠️ Important Note: The TOC reflects your headings, not your intentions. If a section doesn't appear, it's almost always because it was hand-formatted (big/bold) instead of given a real heading style. Fix the style and refresh the TOC. This is the single most common structure mistake — and now you know exactly how to spot and fix it.

Visuals & Polish

With structure and content in place, make it look as good as it reads. Polish is where a solid document becomes a portfolio piece — and it's mostly about consistency and small, deliberate touches.

Images, tables, and drawings — with captions and alt text

Add the visuals you planned. For each one:

• Insert images, tables, or a drawing (Insert > Drawing) where they clarify a point — from Module 4.
• Caption it so readers know what they're looking at (a short line beneath: "Figure 1: ...").
• Add alt text to every image and drawing (Lesson 8.2) so it's accessible — describe what it shows and why it's there.
• Give data tables header rows so they read well and stay accessible.

Consistent styling

Consistency is what reads as "professional." Use the same heading styles throughout (don't hand-tweak one heading to look different), keep fonts and spacing uniform, and align your images and captions the same way every time. If you want a custom look, change the style once and let every matching element update — the styles-over-hand-formatting habit from Module 2 (Lesson 2.3), paying off at scale.

Headers, footers, and page numbers

Add a header or footer with the document title and page numbers (Insert > Page numbers) — essential for anything printed or long (Module 3). Consider a cover or title page: a clean title, your name, and a date, set apart from the body. Where it genuinely helps — a newsletter-style layout, say — sections and columns are available too, and smart chips can add polish (a date chip, a person chip) where useful.

Collaborate & Refine

A document improves when someone else's eyes touch it. This step turns your solo draft into a refined piece — and it exercises the collaboration muscles from Module 5.

Share for comments or suggestions

Share your document with at least one reviewer (a friend, classmate, or colleague), granting them Comment or Suggesting access. Ask a specific question — "Is the structure clear? Does the intro land?" — rather than a vague "thoughts?" Reviewers in Suggesting mode propose edits you can accept or reject; comments start conversations you can resolve. If no one's available, be your own reviewer: read it aloud, or leave yourself comments where something feels off.

Incorporate feedback

Work through comments and suggestions deliberately. Accept the good edits, reply to or resolve comments as you address them, and don't be afraid to push back on suggestions that don't fit — it's your document. This back-and-forth is exactly how real documents get better in the world.

Use version history

As you make big changes, lean on version history (Module 5): it records your progress and lets you roll back if a revision goes wrong. Name a version at a milestone ("First complete draft") so you can always return to it. This is your safety net — it's the reason you can revise boldly without fear of breaking anything. You genuinely cannot lose your work.

Finalize & Celebrate

The last stretch: make it reachable, and then step back and take it in. This is Lesson 8.2 put to work on your best document.

Run the accessibility check

Do a final accessibility pass (Lesson 8.2): real heading styles throughout, alt text on every image, meaningful link text (no "click here"), strong contrast, table header rows. Docs has no built-in checker, so work through that checklist deliberately (or use a checker add-on if you've vetted one) to catch anything you missed. This ensures your portfolio piece works for everyone.

Export and (optionally) publish

Produce the deliverables (File > Download): a PDF for a frozen, shareable, printable copy, and a .docx if anyone needs to edit in Word — and open each one to verify it survived the trip. If it's meant for a broad public audience and contains nothing sensitive, you might also Publish to web. Keep the Google Doc as your living master; the exports are snapshots for specific audiences.

Step back

Now open your finished document and read it start to finish. Cover page, table of contents, clean headings, captioned and accessible visuals, footnotes, page numbers, incorporated feedback, exported cleanly. You built that. A few months ago, some of this might have felt out of reach. Now it's a document you can hand to anyone.

🎯 Project: The Capstone Build (~90 minutes)

Here's your full build. Work through it in order — plan, structure, visuals, collaborate, finalize — and give yourself the time; this is the real thing. If you already have a strong Module 7 document, you may elevate it into your capstone rather than starting completely fresh. Either way, the goal is one complete, polished, structured document you're proud of.

My Capstone

Type: report / guide / portfolio / proposal
Goal: This document helps ______ to ______.

Structure (headings)
- Cover / title page
- 1. ______  (Heading 1)
    - 1a. ______ (Heading 2)
- 2. ______
- 3. ______
- (TOC inserted after headings exist)

Visuals planned
- Figure 1: ______  (caption + alt text)
- Table 1: ______   (header row)

Polish
- [ ] Cover page   [ ] Page numbers
- [ ] Header/footer [ ] Footnotes (if citing)
- [ ] Consistent styles throughout

Collaborate
- Reviewer: ______  Access: Comment / Suggesting
- Version named "Ready for review"
- Version named "Feedback incorporated"

Finalize
- [ ] Accessibility check passed
- [ ] PDF exported and opened
- [ ] .docx exported and opened
- [ ] (Optional) sanitized copy published to web

Best Practices for the Capstone

✅ Do's

• Choose something real — a document you'll actually use makes every step meaningful.
• Structure before content, content before polish — the Content → Structure → Presentation arc.
• Let the TOC and outline guide you — read them as an X-ray of your document's logic.
• Name versions at milestones so you can revise boldly and see your progress.

❌ Don'ts

• Don't hand-format headings — real styles power the TOC, outline, and accessibility.
• Don't over-decorate — restraint reads as more professional than busyness.
• Don't skip the accessibility check or the export verification — those are what make it truly finished.
• Don't chase perfect — chase complete, then keep improving it for real use.

📓 Learning Journal

📝 Lesson Summary & Course Close

🎉 What You've Accomplished

You built a complete, polished, structured document from a blank page — and in doing so, you demonstrated nearly every skill this course set out to teach. More than that: you've become someone who reaches for structure instead of fighting formatting, who thinks in layers, who collaborates and ships. That's not a trick you learned; it's a way of working you now own.

❓ Common Questions at This Stage

🔭 Looking Ahead

This is the end of the lessons — but the start of using them. There's no Lesson 9; from here, the "next lesson" is the real document on your plate. Take everything you've built and put it to work: the next thing you write will be cleaner, faster, and more professional than anything you'd have made before this course.

✅ Before You Close the Course

• Finish and save your capstone document — keep it; you'll reuse and update it
• Write your final Learning Journal entry, re-reading your first one
• Bookmark the lessons you'll want to reference again (TOC, styles, sharing, export)
• Pick the next real document you'll build with these skills

📚 Additional Resources

• docs.google.com — go build your next document
• Google Docs Help Center (Google Support)
• Google Docs on Google Workspace — overview