Pathmaker

TemplatesDigital Ownership: Files, Systems, and Control
beginner
Technical Systems
analytical

Digital Ownership: Files, Systems, and Control

A foundational technology literacy class that teaches students what files are, how folders function as systems, how naming affects retrieval, and how to maintain control over digital work over time.

5 weeks
3 hrs/week
15 total hours
1 learners

About This Course

This class is not about teaching apps. It is about helping students understand what files are, how folders function as systems, how naming affects retrieval, and how to maintain control over digital work over time.

Designed for homeschoolers, childhood educators, parents, and mixed-age learners from upper elementary through middle school—and adaptable for older students and adults. By the end, students have a working file and folder system they understand and can maintain.

What You'll Learn

  • 1
    Understand what a file is and how different file types work
  • 2
    Distinguish between files and the apps used to open them
  • 3
    Build a folder structure as an intentional organizational system
  • 4
    Apply consistent naming conventions to support retrieval
  • 5
    Understand local storage, cloud storage, and backup basics
  • 6
    Create and explain a personal file organization system

Week by Week

1

What Is a File?

Before you can organize anything, you need to understand what you're organizing. This week introduces files as the basic unit of digital storage—what they are, what they contain, and how they differ from the tools used to open them.

Explore this week's curriculum

Key concepts

File: A named container that holds a specific kind of information—a document, image, audio clip, or other data—stored on a device or server.

File Type / Extension: The suffix at the end of a filename (like .pdf, .jpg, .docx) that tells the system what kind of data the file contains and which programs can open it.

File vs App: A file stores information. An app is a program that opens, reads, or edits certain kinds of files. They are separate things.

File Size: How much space a file takes up, measured in bytes, kilobytes, megabytes, or gigabytes. Different file types have very different sizes.

Studio activities

File Type Inventory

Explore a folder on a device and list at least 10 files. For each, record the name, extension, approximate size, and what program opens it.

  1. Navigate to a folder with mixed content
  2. Enable file extensions if they are hidden
  3. List 10 files with name, extension, size, and app
  4. Group your list by file type
  5. Note which types you had never thought about before
Success criteria

A completed inventory showing understanding of file types and their relationship to apps

Reflection

  • What surprised you about how many different file types exist?
  • What would happen if file types didn't exist?

Study guidance

  • Look at actual files on a device—open a folder and examine extensions before doing any activity
  • Emphasize the file vs app distinction early—it clears up a lot of confusion students carry

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

What is the difference between a file and the app you use to open it?

Why does a file need a type or extension?

What kinds of files do you already create or use?

What surprised you about how many different file types exist?

What would happen if file types didn't exist?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

3 hrs
2

Folders as Systems

A folder is not just a storage bin—it is a decision about structure. This week students learn how folder hierarchies work and begin building their own intentional system.

Explore this week's curriculum

Key concepts

Folder / Directory: A container that holds files and other folders, creating a hierarchy of organization.

Hierarchy: A nested structure where folders contain subfolders, creating levels from broad to specific.

Root Level: The top of a folder hierarchy—the broadest category before you go deeper.

Nesting: Placing folders inside folders to add specificity—e.g., School > Science > Lab Reports.

Studio activities

Folder Map on Paper

Design a folder structure for a school year or a home project on paper before touching a computer. Map it as a tree diagram.

  1. Choose a real area of your life with files (school, creative work, family projects)
  2. Draw a top-level folder name
  3. Branch out into 3-5 subfolders
  4. Add a second level of subfolders where needed
  5. Label each folder with what it would contain
Success criteria

A completed folder tree diagram that makes logical sense and could actually be used

Reflection

  • How is a folder structure like a physical filing system—and how is it different?
  • What would break down if your folder structure was just one level deep?

Study guidance

  • Draw folder structures on paper before creating them digitally—it makes the hierarchy concrete
  • A good structure is shallow and wide at the top, specific deeper down

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

What's the difference between dumping files into one folder and building a real system?

How do you decide what deserves its own folder?

What makes a folder structure easy to use versus confusing?

How is a folder structure like a physical filing system—and how is it different?

What would break down if your folder structure was just one level deep?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

3 hrs
3

Naming and Retrieval

A file named 'document3' is nearly useless six months later. This week students learn why naming matters, what makes a good name, and how to create simple conventions that make files findable.

Explore this week's curriculum

Key concepts

Naming Convention: A consistent rule or format for naming files—making them scannable, sortable, and retrievable.

Date Prefix: Starting a filename with the date (YYYY-MM-DD) so files sort chronologically automatically.

Version Suffix: Adding v1, v2, or _final to track iterations without overwriting previous work.

Retrievability: The ability to find a file later without remembering exactly where you put it.

Studio activities

The Rename Exercise

Take 10 poorly named files and rename them using a clear, consistent convention. Document your before-and-after names and explain the rules you used.

  1. Find 10 files with unclear names
  2. Draft a naming convention: what info should every name include?
  3. Rename each file using your convention
  4. Document before and after names in a simple table
  5. Write 3-sentence explanation of your naming rules
Success criteria

10 renamed files with a written explanation of the naming system applied

Reflection

  • What would happen if everyone on a shared project named files differently?
  • When is a longer filename better? When is shorter better?

Study guidance

  • Have students rename 10 of their own poorly-named files as a hands-on exercise
  • Date prefixes in YYYY-MM-DD format sort correctly in any file browser automatically

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

What makes a filename actually useful a year from now?

When would you use a date prefix? When would you use a version number?

What's wrong with names like 'final,' 'new,' or 'untitled'?

What would happen if everyone on a shared project named files differently?

When is a longer filename better? When is shorter better?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

3 hrs
4

Storage, Cloud, and Backup

Where does a file actually live? This week students learn the difference between local storage and cloud storage, understand what backup means and why it matters, and think clearly about what happens when files are lost.

Explore this week's curriculum

Key concepts

Local Storage: Files saved on a physical device—a hard drive, SSD, or USB. Only accessible from that device unless moved.

Cloud Storage: Files saved on remote servers and accessible via internet connection from multiple devices.

Sync vs Backup: Syncing mirrors files across devices in real time. Backup creates a separate, independent copy for recovery.

The 3-2-1 Rule: A backup principle: keep 3 copies of important data, on 2 different media types, with 1 stored offsite or in the cloud.

Studio activities

Storage Map

Draw a map of where your files currently live. Mark which are local-only, which sync to cloud, and which have actual backups. Identify any gaps.

  1. List the devices you regularly use
  2. For each device, identify where files are stored
  3. Note which services sync files to cloud (if any)
  4. Identify 3 important files or folders and trace where each copy lives
  5. Mark gaps where important work has no backup
Success criteria

A completed storage map with gaps and backup status clearly identified

Reflection

  • What is the difference between 'it's in the cloud' and 'it's backed up'?
  • What would a reasonable backup habit look like for you personally?

Study guidance

  • Have students map where their most important files actually live right now—most will not know
  • Use the question 'what would you lose if this device broke today?' as a motivating prompt

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

What is the difference between a file being synced and a file being backed up?

Why would you want a copy of a file somewhere other than where you normally work?

What files would be most devastating to lose? Are those protected?

What is the difference between 'it's in the cloud' and 'it's backed up'?

What would a reasonable backup habit look like for you personally?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

3 hrs
5

Build Your System

Everything from the previous four weeks comes together. Students create, refine, and explain a working file and folder system they can actually use going forward.

Explore this week's curriculum

Key concepts

System: A set of organized parts that work together reliably to accomplish a goal.

Maintenance: The ongoing practice of keeping a system working—filing new items, removing outdated ones, updating names.

Usability: Whether a system is easy enough to use consistently. The best system is the one you'll actually maintain.

Studio activities

Personal File System Build

Build a complete, working folder structure for your actual digital files. Apply a naming convention throughout. Write a short explanation of how your system works.

  1. Review your folder map from Week 2 and refine it
  2. Create the folder structure on an actual device
  3. Move or rename at least 20 existing files into the system
  4. Apply your naming convention from Week 3
  5. Write a 1-page explanation: structure, naming rules, storage locations, backup plan
Success criteria

A working folder system with renamed files and a written explanation of how it functions

Reflection

  • What is the hardest part of maintaining a file system over time?
  • If someone else needed to find a file in your system, could they? Why or why not?

Study guidance

  • This week is about building something real—push students to work with their actual files, not hypothetical ones
  • A system that is a bit imperfect and gets used is better than a perfect one that gets abandoned

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

Walk me through your file system—how would someone else find a specific file in it?

What would make this system break down over time? How do you prevent that?

What would you change about it in 3 months?

What is the hardest part of maintaining a file system over time?

If someone else needed to find a file in your system, could they? Why or why not?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

3 hrs

Topics Covered

technology
digital literacy
files
organization
homeschool
systems
ownership
education

More in This Track

Ready to begin?

Start your personalized curriculum today — free to try, no credit card needed.