Skip to main content

📁 Lesson 7.3: Project — A Project Hub Tying Docs, Sheets & Slides Together

This is the Module 7 capstone project — the lesson where every skill in this course, and the whole Google Workspace, comes together in one place. You'll build a project hub: a single shared folder holding a Doc, a Sheet, and a Slides deck, all tied together by a linked "index" Doc so anyone can find everything from one page. This is the moment Drive stops being a place to store files and becomes the command center where real work happens.

📚 What You'll Learn

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

  • Design a project hub folder that holds a Doc, a Sheet, a Slides deck, and reference files
  • See how Docs, Sheets & Slides all live in Drive and connect into one project
  • Build a hub index Doc that links to every file using file links and smart chips
  • Share the hub with a team so everyone works from one current place
  • Make the hub findable by search and synced across devices
  • Tie your Drive skills to the sibling Docs, Sheets & Slides courses

⏱️ Estimated Time: 65 minutes

🎯 Project: Build a real project hub folder containing a Doc, a Sheet, and a Slides deck, plus a linked index Doc that references each of them — shared with your team, findable by search, and synced.

In This Lesson

🎯 What a Project Hub Is

Think of any real project you've been part of — planning a trip, launching a small business, organizing an event, writing a report. It always involves several kinds of files at once: written notes and a brief, a spreadsheet to track numbers or tasks, a presentation to show others, and a pile of reference material. Scattered across email, downloads, and three people's laptops, that mix is chaos. Gathered into one place, it's a project hub.

A project hub is simply one folder that holds everything for one project — every file type, every collaborator, one home. It's the natural conclusion of everything this course has taught: you store the files in it, organize them under one roof, find them from one spot, share the whole folder at once, and let it sync to everyone's devices. Store → Organize → Find → Share → Sync, all serving a single goal.

The magic of a hub is that it makes a project legible. A newcomer opens one folder and sees the whole shape of the work. A collaborator always knows where the current version lives. Nobody asks "can you re-send me the deck?" because the deck is right there, in the hub, current. This is what people mean when they say "everything's in the project folder" — and it's a small superpower for getting real work done.

🧠 Why this is the Module 7 capstone

Every earlier lesson taught one stage or one skill. A project hub uses all of them at once, and it's where Drive's real purpose finally clicks: it's not a storage locker, it's the home base that ties your Docs, Sheets, Slides, and files into one coherent piece of work. Build one and you understand Drive at a level most people never reach.

🏛️ The Three Pillars: Doc, Sheet & Slides

Almost every project rests on three kinds of Workspace file, each doing a job the others can't. Together they cover words, numbers, and story — and because all three save automatically into Drive, your hub folder gathers them effortlessly.

File Its job in the project Made with New →
📝 A Doc The brief and the notes — the words: plan, decisions, meeting notes, the narrative of the project Google Docs
📊 A Sheet The tracker or budget — the numbers: tasks, costs, dates, anything that lives in rows and columns Google Sheets
📽️ A Slides deck The presentation — the story you show others: the pitch, the update, the summary Google Slides
📎 Reference files Supporting material — PDFs, images, uploads, links you didn't create but need Upload / drag in

Here's the beautiful part, and the through-line of this whole course: when you click New → Google Docs from inside your hub folder, the new Doc is born in that folder. Same for the Sheet and the deck. You don't create files somewhere and then hunt them down to move them in — you create them where they belong. Drive is the home base; the apps are just different ways of working on what lives inside it.

💡 Create files inside the folder

Open your hub folder first, then use the New button (or right-click → new file). The file lands directly in the folder — no moving required. This one habit prevents the classic "I made a Doc but can't find it" moment, because you never lose track of where a file was born.

If you've taken the sibling Docs, Sheets, or Slides courses in this series, this is where they all come home: the skills you built there produce the files, and Drive is where those files live, connect, and get shared. This lesson is the glue.

🔗 The Index Doc — Links & Smart Chips

A folder full of files is good; a folder with a front door is better. The heart of a project hub is a single Google Doc — call it the index, the hub, or the project home — that links to every other file. Instead of scanning a folder listing, anyone opens the index and clicks straight to what they need. It's the table of contents for the whole project.

There are two lovely ways to add those links, both of which keep everything connected:

  • Paste a file link. Open a file, copy its link (Share → Copy link, or the address bar), and paste it into the index Doc. Google usually offers to turn a pasted Drive link into a tidy smart chip — a little labeled token showing the file's name and icon rather than a long raw URL.
  • Insert with @ (smart chips). In the Doc, type @ and start typing a file's name. Docs suggests matching files from your Drive; pick one and it drops in as a smart chip that links straight to it. Hover a chip and you get a preview without leaving the page.

Smart chips are the connective tissue of Workspace — a small feature that makes a hub feel alive. Because a chip points to the real file in Drive, it's always current: update the Sheet and the chip in your index still opens the latest version. No copies, no stale links, no "which one is right?"

Here's the shape you're building — one hub folder, the three pillar files plus references inside it, and an index Doc whose links reach every one of them:

graph TD HUB["📂 Project Hub
(shared folder)"] --> IDX["🏠 Index Doc
links to everything"] HUB --> DOC["📝 Brief / Notes
(Doc)"] HUB --> SHEET["📊 Tracker / Budget
(Sheet)"] HUB --> SLIDES["📽️ Presentation
(Slides)"] HUB --> REF["📎 Reference files"] IDX -.->|"smart chip"| DOC IDX -.->|"smart chip"| SHEET IDX -.->|"smart chip"| SLIDES IDX -.->|"link"| REF

Notice the two kinds of arrow: solid ones show what physically lives in the folder, dotted ones show the index Doc's links reaching out to each file. The folder holds; the index connects. Together they make one navigable project.

👥 Sharing the Hub as One Unit

Here's where a hub pays off beautifully: you share the folder once, and everyone gets access to everything inside it — the Doc, the Sheet, the deck, the references, and any file you add later. Access flows down from the folder, so you manage one thing instead of chasing permissions on a dozen files. This is the shared-space skill from the last lesson, applied to a whole project.

Everything you learned in Lesson 7.2 applies directly:

  • Share the folder, not individual files. Right-click the hub folder → Share, add your teammates by email, and everything inside inherits the access.
  • Choose roles deliberately. The core team who build the project are Editors; reviewers who weigh in are Commenters; anyone who just needs to see it is a Viewer.
  • Point people at the index. Tell collaborators "open the Index Doc first" — it's the front door that orients everyone, just like a Start Here doc for the project.
  • Run the quick security review. Confirm general access is Restricted unless the project is genuinely meant to be public. A hub often holds a budget or plan you don't want wandering off.

✅ Pro Tip

Because a new file created inside the hub folder inherits the folder's sharing automatically, your teammates can see it the moment you make it — no re-sharing, no "can you give me access?" That inheritance is the quiet reason hubs feel so smooth: set the sharing once at the folder, and the whole project just works for everyone.

🔍 Findable by Search, Synced Everywhere

A hub you can't find fast, or can't reach from your phone, only does half its job. The last two stages of the model — Find and Sync — make the hub effortless to live with.

Findable

Give the hub folder and its files a consistent, searchable name — a shared project prefix works wonders. If everything starts with the project name (for example Spring Fundraiser - Brief, Spring Fundraiser - Budget, Spring Fundraiser - Deck), a single search for "Spring Fundraiser" surfaces the whole project at once. Star the hub folder so it sits in your Starred view, and you're one click from the project anytime. Drive's search can also filter by type — search the project name and filter to Spreadsheets to jump straight to the tracker.

Synced

Because the hub lives in Drive, it's automatically everywhere you sign in — the web, the mobile app, and, if you use Drive for desktop, right in your computer's file system. Edit the budget on your laptop, and the version on your phone updates too. Mark the hub's key files available offline if you'll need it on a plane or a patchy connection, and it travels with you. One hub, every device, always current.

💡 A searchable name is a free superpower

The single easiest thing you can do to make a project findable forever is to name its files with a shared prefix. It costs nothing at creation time and turns every future search into a one-word job. This is the naming convention from Lesson 7.1, aimed at a whole project instead of a single file.

🌐 The Whole Workspace, One Home Base

Step back and look at what a project hub really demonstrates. A Doc, a Sheet, and a Slides deck are three different apps — but they aren't three different places. They all save into Drive, live in the same folder, share the same permissions, and link to each other through the index. Drive is the home base; the apps are windows onto files that all live in the same house.

This is the idea the whole course has been building toward, and it's why organizing Drive well organizes your entire Google life at once. When you keep the hub tidy, you're keeping the Doc, the Sheet, the deck, and the references tidy in one move. When you share the hub, you share all of them. When you find the hub, you've found everything. One home base, and everything that matters flows through it.

📖 The through-line, complete

Store → Organize → Find → Share → Sync — you've now done all five, together, in service of one real project. You stored three file types by creating them in the folder, organized them under one roof with a searchable naming scheme, made them findable by name and by star, shared the whole hub with controlled roles, and let it sync to every device. That's the entire course, expressed in one folder. Drive was never just storage; it's the connected home base for everything you do.

⚠️ Important Note: Menus, the exact wording of "smart chips," and where the New button sits will shift as Google updates Workspace. Don't memorize positions — hold onto the ideas: files are born in the folder, the index links to the real files, sharing flows down from the folder, and a good name makes everything findable. Those ideas outlast any redesign.

🎯 Project: Build Your Project Hub

Time for the Module 7 capstone build. Pick a real project — however small — that actually needs words, numbers, and a bit of presentation: an event, a trip, a side hustle, a class project, a family plan. Open drive.google.com and build the hub for real.

🏋️ Build a project hub that ties everything together

Objective: One shared hub folder containing a Doc, a Sheet, and a Slides deck, plus a linked index Doc that references each — shared with at least one person, findable by search, and synced.

Instructions (about 50 minutes):

  1. (4 min) Create a hub folder named for your project (for example "Spring Fundraiser"). Star it so it's easy to reach.
  2. (12 min) Inside the folder, use New to create the three pillars: a Doc (brief / notes), a Sheet (tracker / budget), and a Slides deck (presentation). Put a line or two of real content in each so they're not empty.
  3. (4 min) Add at least one reference file — upload a PDF or image, or drag one in.
  4. (3 min) Name all files with a shared project prefix so one search finds the whole project.
  5. (10 min) Create an Index Doc at the top of the folder. In it, link to the Doc, the Sheet, the Slides deck, and the reference — using the @ smart-chip menu or by pasting file links. Add a sentence describing each.
  6. (6 min) Share the hub folder with at least one person, choosing a deliberate role (Editor / Commenter / Viewer), and point them to the Index Doc first.
  7. (4 min) Run the quick security review: general access = Restricted unless the project is truly public; roles correct; nothing sensitive over-shared.
  8. (4 min) Confirm it's synced — open the hub on your phone (or mark its key files available offline) to see the same files everywhere.
💡 Hint — a starter Index Doc
[Project Name] — Project Hub

Welcome! This is the home base for [project]. Everything lives in
this folder. Open the linked files below to jump straight in.

📝 Brief & Notes        @[Project] - Brief
   The plan, decisions, and meeting notes.

📊 Tracker / Budget      @[Project] - Budget
   Tasks, costs, and dates. Editors keep this current.

📽️ Presentation          @[Project] - Deck
   The story we show others.

📎 Reference             [paste link to the PDF / image]
   Supporting material.

Team & norms
- Editors: [names]   Commenters: [names]
- Name new files "[Project] - ..." so search finds them
- Add your own files here; ask before moving others'

The @ entries become smart chips that link to the real files. Keep the index short — it's a front door, not a report.

✅ Project Completion Checklist

  • A starred hub folder named for your project exists
  • Inside it: a Doc, a Sheet, and a Slides deck, each created in the folder and holding real content
  • At least one reference file is in the folder
  • All files share a project-name prefix, so one search surfaces the whole project
  • An Index Doc links to the Doc, Sheet, Slides, and reference using smart chips or file links
  • The hub folder is shared with at least one person at a deliberately chosen role
  • The security review is clean (general access Restricted unless truly public)
  • You confirmed the hub syncs — same files on another device or key files marked available offline

🎯 Quick Quiz

Question 1: Why is it best to create your Doc, Sheet, and Slides deck from inside the hub folder?

Question 2: In your Index Doc, why is a smart chip (or file link) better than pasting a copy of each file's contents?

Best Practices for Project Hubs

✅ Do's

  • Create files inside the hub folder. They're born in place and inherit its sharing — no hunting, no re-sharing.
  • Make the Index Doc the front door. Link to everything with smart chips and point every collaborator there first.
  • Use a shared name prefix. One project word in every filename makes the whole hub findable in one search.

❌ Don'ts

  • Don't paste copies into the index. Link to the real files with chips so nothing goes stale.
  • Don't share files one by one. Share the folder once and let access flow down to everything inside.
  • Don't skip the security review. A hub often holds a budget or plan — confirm it isn't accidentally public.

💡 Pro Tips

  • Type @ in a Doc to drop in a smart chip that links straight to any file in your Drive.
  • Star the hub folder so the whole project is one click away from your Starred view.

📓 Learning Journal

Keep a learning journal as you work through this course — a separate document, a note, or a Google Doc right in the Drive you're organizing. 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 Drive
  • Your progress and feelings about learning this — including where your confidence grew

✍️ This lesson's prompt: Now that you've built a hub where a Doc, a Sheet, and a Slides deck all live in one shared folder, has your picture of Drive changed? Describe a real project in your life that would run more smoothly as a hub. Which piece felt most powerful — creating files inside the folder, the index with smart chips, or sharing everything at once — and why? Consider saving this entry inside the hub you just built.

📝 Lesson Summary

🎓 Key Takeaways

  • A project hub is one shared folder holding everything for a project — a Doc (words), a Sheet (numbers), a Slides deck (story), and reference files — so a whole project has one home.
  • Create files inside the hub folder so they're born there and inherit its sharing; because Docs, Sheets, and Slides all save into Drive, the folder gathers them effortlessly.
  • An Index Doc with smart chips (type @) or file links is the front door — it points to the real, always-current files rather than stale copies.
  • Share the folder once and access flows to everything inside; a shared name prefix makes the whole project findable in one search, and Drive keeps it synced everywhere.

🎉 What You've Accomplished

You built a project hub — the Module 7 capstone, and a preview of the course capstone in Lesson 8.3. In one folder you gathered a Doc, a Sheet, a Slides deck, and references; tied them together with a linked index; shared the lot with controlled roles; made it findable by name; and confirmed it syncs everywhere. You used all five stages of Store → Organize → Find → Share → Sync at once, and you saw Drive for what it truly is: the connected home base that ties the entire Google Workspace into one coherent piece of work.

❓ Common Questions at This Stage

What exactly is a "smart chip"?

A smart chip is a small, labeled link inside a Doc that points to another file, person, date, or item — shown as a tidy token with a name and icon instead of a long URL. Type @ in a Doc and start typing a file's name to insert one. Because it links to the real file in Drive, hovering shows a preview and clicking opens the current version. Wording and exact behavior evolve, so if the menu looks different, the idea is the same: a live link to a real file.

Do I need the Docs, Sheets, and Slides courses to make a hub?

Not at all — a hub works with even simple files. But this lesson is exactly where those sibling courses connect: they teach you to build powerful Docs, Sheets, and Slides, and this course shows you where those files live, how they link, and how to share them as one project. If you've taken them, the hub is the satisfying payoff; if not, you're perfectly set up to use them.

What happens to my index links if I rename or move a file?

Smart chips and Drive file links point to the file itself, not to its name or location, so renaming or moving a file within your Drive keeps the link working — it still opens the same real file. The main things that break a link are deleting the file or a collaborator losing access. Because you shared the whole hub folder at once, access stays consistent, and the links keep pointing at current versions.

🔭 Looking Ahead

In the next lesson — Lesson 8.1: Versioning, Recovery & the Trash — Getting Files Back — we turn to the safety net under everything you've built. You'll learn how version history lets you roll back an edit, how the trash gives you a grace period to recover deleted files, and how to get a file back when you thought it was gone — the peace of mind that makes it safe to organize fearlessly.

✅ Before the Next Lesson

  • Finish your project hub — three pillar files, a reference, a linked Index Doc, shared and synced
  • Confirm one search for the project name surfaces the whole hub
  • Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

You just built the thing this whole course was pointing at — a hub where words, numbers, and story live together, shared and findable, all in one home base. That's Drive at its most powerful, and now it's a skill you own. One safety net left to learn, and your Drive will be truly trustworthy. 📁