📝 Lesson 7.2: Project — A Résumé & a Newsletter (Designed Documents)

Structure vs Design — a Different Kind of Build

A report and a résumé are both documents, but you build them with a different mindset. A report is read in order, top to bottom, so structure rules: headings, an outline, a TOC. A résumé or a newsletter is scanned — the eye jumps around looking for the interesting bits — so layout rules: where things sit on the page, how aligned they are, how much breathing room surrounds them.

That doesn't throw away the Content → Structure → Presentation model — it just leans harder on the Presentation layer. You still write your content first and give it light structure, but now you spend real effort on arrangement: columns, alignment, images that sit beside text, and the deliberate use of empty space. The good news is that the tools are ones you've already met — tables, tab stops, images, and section breaks — used with a designer's intent.

Read that diagram as your recipe for the day: pick the document type, reach for the right layout tools, apply a few design principles, and finish with a polished page you can reuse. We'll do it twice — once for a tight, professional résumé, once for a lively, multi-column newsletter.

Step 1 — The Résumé: Layout with Tables or Tabs

A résumé's job is to present your experience so a busy reader can scan it in seconds. That means tidy alignment above all — dates that line up, sections that are easy to find, nothing ragged. You have two honest starting points.

Start from a template or from scratch

Docs offers résumé templates in the template gallery (from the Docs home screen, or File > New > From template gallery). A template gives you a head start on layout you then customize. Starting from scratch gives you full control and a better understanding of how the layout works. Either is fine — we'll teach the from-scratch mechanics so a template never mystifies you.

Align with a table (recommended)

The cleanest way to align a résumé is an invisible table. Insert a two-column table (Insert > Table): put labels or dates in the narrow left column and details in the wide right column. Then remove the borders so the grid disappears (select the table, then set the border width to 0 pt in the table/border options). The result: everything lines up perfectly, but the reader sees only clean columns of text, no visible lines. This is the pro trick behind most tidy résumés — you're borrowing the table skills from Lesson 4.2 for alignment, not for data.

Align with tab stops (the lightweight alternative)

For simpler layouts, tab stops on the ruler let you push text to precise positions — for example, a job title on the left and its dates flush right on the same line. Click the ruler to place a tab stop (including a right-aligned tab for those flush-right dates), then press Tab to jump to it. Tabs keep the document lighter than a table and are perfect when you only need a few aligned points.

Step 2 — Résumé Polish & the ATS Reality

A one-page résumé is a discipline: every line has to earn its place. Polish it by tightening these three things.

• Spacing. Consistent gaps between sections do more for readability than any font choice. Adjust once via Format > Line & paragraph spacing and keep it even throughout.
• Alignment. Dates flush right, bullets indented the same amount, section headings starting at the same left edge. Ragged alignment is what makes an amateur résumé look amateur.
• One-page discipline. If you're spilling onto page two, cut words before you shrink fonts. Tighter writing beats tiny text every time.

Step 3 — The Newsletter: Masthead & Columns

Now for something more playful. A newsletter — for a club, a team, a class, a family — is where you get to design freely, because no ATS is going to scan it. We'll build the classic two-column layout.

Create the masthead

The masthead is the big title banner across the top ("The Weekly Bulletin", "Team Notes", etc.). Give it a large Title style, maybe a subtitle with the date and issue number, and keep it full width — the masthead spans the whole page even though the articles below will be in columns. A thin horizontal line beneath it (Insert > Horizontal line) neatly separates the banner from the body.

Split the body into two columns

Here's the key layout move. You want the masthead to stay one column while the articles below flow into two. That's exactly what section breaks are for. Place your cursor just below the masthead and insert a section break (Insert > Break > Section break (continuous)). Everything after the break is now an independent section whose column count you can set separately.

With the cursor in that new section, open Format > Columns and choose two columns (you can set the spacing between them and even add a line between). Your article text now flows down the left column and continues into the right — just like a real newspaper. Text automatically balances and reflows as you edit, which is the whole point of columns over hand-made layouts.

Add wrapped images and a pull quote

Insert an image within a column and set its text wrapping to Wrap text so the article flows neatly around it, rather than the "In line" wrapping we preferred for the report's figure. A little margin around the image keeps it from crowding the words.

A pull quote — a short, striking line lifted from the article and shown large — draws the eye and breaks up gray text. Create one with a single-cell table or a text box, give it a larger italic font, and let the surrounding text wrap around it. It's the visual equivalent of a highlighter.

Step 4 — Design Principles That Never Fail

These four principles are the difference between "made in a word processor" and "looks designed." They apply to the résumé, the newsletter, and honestly every document you'll ever make.

Notice that styles are how you enforce most of this without effort. When your headings and body text come from styles rather than hand-formatting, consistency is automatic — change the style once and the whole document stays in step. That's the same lesson from the report project, wearing a designer's hat: structure isn't the enemy of design, it's what keeps design consistent.

⚠️ Important Note: When in doubt, do less. The single most common design mistake is too much — too many fonts, too many colors, too many boxes and lines. A calm, consistent, well-aligned page with plenty of whitespace almost always beats a busy one. Restraint reads as confidence.

Step 5 — Reuse: Save Each as a Template

You just did real design work — don't do it twice. The professional move is to turn each finished document into a reusable template so your next résumé update or newsletter issue starts with the layout, styles, and spacing already in place.

The simple, universal method: copy the file

The approach that works on every account is to keep a clean "master" version and make a copy for each real use. From the file, use File > Make a copy, name the copy (e.g. "Résumé — 2026 application" or "Newsletter — March issue"), and edit the copy while your master stays pristine. To make a truly blank template, strip out the specific content and leave the structure and placeholder text ("[Your headline here]"), then copy that each time.

The template gallery (Workspace accounts)

If you use Docs through a Google Workspace (work or school) account, your organization may let you submit documents to a shared template gallery so a whole team can reuse the same résumé or newsletter design. This isn't available on every account — free personal accounts use the copy-a-file method above — so check what your account offers rather than assuming. Either way, the goal is the same: design once, reuse forever.

🎯 Project: Build Both Designed Documents

Two builds, one lesson. You'll produce a clean one-page résumé and a two-column newsletter, then save each as a reusable template. Use your real information for the résumé (or a fictional persona if you'd rather) and any topic you like for the newsletter — a club update, a project recap, a family bulletin.

RÉSUMÉ (borderless 2-column table for alignment)
+-----------+--------------------------------------+
| 2022-Now  | Job Title, Company                   |
|           | - Achievement one                    |
|           | - Achievement two                    |
+-----------+--------------------------------------+
| 2019-2022 | Previous Title, Company              |
+-----------+--------------------------------------+
Then: select table > set border width to 0 pt so lines vanish.

NEWSLETTER
[ MASTHEAD - full width, big Title, date/issue ]
------------------ horizontal line ------------------
--- section break here ---
[ two columns via Format > Columns ]
Article 1 heading        |  Article 2 heading
body text flows down and |  continues into the
across the columns...    |  second column...
        [ image, Wrap text ]   [ pull quote ]

Best Practices for Designed Documents

✅ Do's

• Use borderless tables for alignment. They're the cleanest way to line up a résumé — invisible grid, perfectly aligned text.
• Use section breaks for mixed layouts. Full-width masthead plus two-column body is a section break away.
• Keep a plain résumé version. One for people, one for the machines that scan applications.
• Enforce consistency with styles. Design that lives in styles stays consistent for free.

❌ Don'ts

• Don't over-decorate. Five fonts and a rainbow of colors read as noise. Restraint looks professional.
• Don't rely on a heavily designed résumé for online applications. The ATS may mangle it; upload the plain version there.
• Don't crowd the page. Whitespace is doing real work — resist the urge to fill every inch.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built two very different documents in one sitting and made both look intentional — a scannable one-page résumé and a lively two-column newsletter. You learned the pro tricks (borderless tables for alignment, section breaks for mixed column layouts, text wrapping around images) and, just as importantly, the honest real-world caveat about ATS parsing. You now know that good design isn't talent — it's a few principles applied with restraint. And you saved your work as templates, so you'll never start from scratch again.

❓ Common Questions at This Stage

🔭 Looking Ahead

Next — Lesson 7.3: Project — A Reusable Meeting-Notes System — we take the "design once, reuse forever" idea all the way. You'll build a meeting-notes system a team would actually adopt, using building blocks, smart chips, checkboxes, and templates, then wire it into a real collaboration workflow.

✅ Before the Next Lesson

• Finish both documents and run through the completion checklist
• Confirm you saved a reusable master copy of each
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• docs.google.com — open the app
• Google Docs Help Center (Google Support)
• Add or delete columns in a document (Google Support)