How to Build Your Own Student Work Archive

A step-by-step guide from OWL Celebrates Learning for schools that want to build their own archive of student work.

Why build an archive of student work

A public archive turns student work that would otherwise sit in a drawer, a hard drive or one family's fridge into something the whole community can see, return to and learn from. OWL Celebrates Learning is Open World Learning Community's archive: one WordPress site that holds more than a decade of documentaries, briefing books, magazines, calendars, playbills, art galleries and History Day projects.

An archive like this does four jobs at once:

Honors the work. Students make better work when they know it will have a real audience, and seeing it published tells them it mattered.
Shows what is possible. New students and teachers can see the bar set by the classes before them. Models of strong work are one of the most powerful teaching tools a school has.
Tells the school's story. Families, prospective families, district leaders, funders and visitors can see what learning at the school actually produces, not just read a description of it.
Preserves memory. Projects run for years and teachers move on. Without a home, the 2019 briefing book or the 2022 documentaries can disappear when a laptop is replaced or an account is closed.

Who this guide is for

This guide is for a teacher, coach or school leader who wants to start a similar site for their own school, without a web team or a budget. It walks through the steps OWL used, in the order you will need them, with the decisions and conventions that kept the site consistent as it grew. Each step ends with a short checklist.

Before you start

Settle four things before you build anything: who owns the site, how much time it takes, what you are allowed to publish, and who supports it.

Name an owner

An archive needs one person who keeps it going. At OWL, one teacher runs the site and colleagues send work to him. Collaborators are welcome, but a single owner keeps the style consistent and makes sure nothing falls through the cracks. If several people will post, decide who has final say on titles, tags and what goes live.

Plan the time

The heaviest lift is the first catch-up, when years of old work get gathered and posted. After that, the site runs on a predictable yearly rhythm: most projects finish in late spring, a few in the fall, so posting comes in bursts. A typical new post (gather the file, write a short description, tag it, check it) takes 20 to 45 minutes. A large gallery or a batch of videos takes longer.

Get permission and protect students

This is the step not to skip. Before you publish anything:

Check your district's media policy. Most districts collect an opt-out or release form each year. Know who has opted out of having their work or image shared online, and check that list before each post.
Use first names only. OWL credits students by first name only, adding a last initial only when two students in the same project share a first name ("Clara B." and "Clara R."). Never publish full names, ages, birthdays, home towns or contact details of students.
Look inside the work, not just at it. Magazines, memoirs and documentaries can contain full names, personal stories, faces and family details. Read or watch the whole piece before posting it.
Respect a student's current name. Students change names. If a student now goes by a different name, update the credit when you learn about it.
Ask before posting someone else's upload. If a video lives on another teacher's channel, link to or embed it rather than downloading and re-uploading it.
Adults can be named in full. Teachers, guest experts and partner organizations are usually happy to be credited by name.

Build support

Tell your principal and colleagues what you are doing and why, and ask them to send finished work your way. The archive grows much faster when teachers think of it as the natural home for their projects. A short note in the staff email each spring ("send me your final PDFs and videos") goes a long way.

Checklist

☐ One person named as owner of the site
☐ District media policy and opt-out list checked
☐ First-names-only rule agreed
☐ Principal informed and supportive
☐ Colleagues asked to send finished work

Step 1: Set up the site

OWL's archive runs on WordPress with its own domain name, a simple blog-style theme and a handful of plugins. You can be up and running in an afternoon.

Choose a platform

WordPress is a good fit for an archive because every piece of work becomes a post with a date, a category and tags, which is exactly how people want to browse student work. It handles PDFs, images and embedded videos well, and it is free and widely supported.

Option	Good for	Trade-offs
WordPress on a web host (what OWL uses)	Full control, any plugin, your own domain	You keep plugins and WordPress updated
WordPress.com	Less upkeep; updates handled for you	Some plugins need a paid plan
Google Sites	Quick start inside a school Google account	Weak tagging and search; hard to grow past a few dozen pages

Get a domain name

A short, memorable address makes the site easy to share on flyers, in emails and at events. OWL uses owlcelebrateslearning.com. Choose a name that will still make sense in ten years and that is about the school's work, not one teacher. Renew it automatically so it never lapses: a lapsed domain can be bought by someone else.

Pick a theme

Choose a clean theme with:

A sidebar (or footer area) for search, recent posts and a tag list
Large, readable text and good spacing
A layout that works on phones, since many families will visit on one
Featured image support, so posts can show a cover in lists

Resist heavy designs. The student work should be the most colorful thing on the page.

Install a few essential plugins

Keep the plugin list short: every plugin is something to update.

Plugin	What it does at OWL
PDF Embedder	Shows PDFs (magazines, briefing books, calendars) as a flip-through viewer right in the post
Jetpack	Site stats, security, and a connection to WordPress.com tools
An SEO plugin (OWL uses All in One SEO)	Clean titles and descriptions in search results and link previews

Deactivate and remove plugins you don't use. When the dashboard warns about a security vulnerability, update the plugin right away.

Set the basics

Site title and tagline: OWL's homepage reads "Celebrating High-Quality Student Work at OWL."
Permalinks: set them to use the post name, so addresses read like /2027-phenology-calendar/ instead of /?p=630.
Comments: turn them off, or moderate every one. A student work archive rarely needs open comments.
Admin accounts: give each person who posts their own account, never a shared password, and use strong passwords.

Checklist

☐ Platform chosen and site created
☐ Domain registered, set to auto-renew
☐ Theme with sidebar and phone-friendly layout
☐ PDF viewer plugin installed
☐ Permalinks set to post name
☐ Comments off or moderated

Step 2: Plan the structure

Decide your categories, tags and naming rules before the first post, and write them down. Consistency is what lets a visitor find every Phenology Calendar or every 8th-grade project with one click, and it is much harder to fix after 100 posts.

Categories: what kind of work it is

Give every post exactly one category describing the form of the work. Keep the list short. OWL uses four:

Category	What goes in it	Examples
Publications	Anything printed or bound: magazines, books, calendars, briefing books, playbills, newspapers	Justice Magazine, Phenology Calendar, Senate Expedition briefing books
Documentaries	Student-made films	River Documentaries, History Day documentaries
Podcasts	Audio projects	Student podcast series
Artifacts	Physical or visual work shown through photos	Art galleries, History Day exhibits, models

Tags: who made it, when, and in what subject

Tags let a post belong to several groups at once. OWL tags every post on three axes, plus a few special tags:

Year: 2019, 2022, 2026 and so on. Pick one rule and stick to it, such as the year the work was finished or published.
Grade: 6th Grade through 12th Grade. Add every grade that took part (a senior course gets both 11th Grade and 12th Grade).
Subject: ELA, Math, Science, Art, Theatre, Music, Spanish. Interdisciplinary work gets every subject involved.
Program or competition: NHD for National History Day, so a whole competition history can be browsed in one place.

Only create a new tag when you expect to use it again. Check the existing list first so you don't end up with both "Theater" and "Theatre."

Naming conventions

Write these down and follow them every time. OWL's rules:

Item	Pattern	Example
Post title	Year + project name, then a subtitle after a dash	2026 Justice Magazine – Justice to Me
Series post title	Year + project + part number and theme	2022 River Documentaries Part 5 – Miscellaneous
Recurring post title	Same name every year so they line up	2025 Senate Expedition, 2026 Senate Expedition
Uploaded file name	Year-Project-Name-Subtitle, hyphens, no spaces	2026-Survival-Journal-The-Road-to-Survival.pdf
Gallery image file	year-project-firstname	2027-calendar-art-abir.jpg
Credit inside a post	First name: title of the piece	Luci: Steamboats
YouTube video title	Title by first name – collection	Steamboats by Luci – 2022 River Documentaries

Rename files before you upload them. Names like "8th magazine to be printed.pdf" or "proof 3 final again.pdf" make the Media Library hard to search and show up in links.

Post dates

Date each post to when the work came out, not the day you posted it. A playbill is dated to opening night and a calendar to its release. That way the site reads as a true timeline, and old work slots into place even when you add it years later.

Checklist

☐ Categories chosen (keep it to about four)
☐ Year, grade and subject tags created
☐ Naming rules written down and shared with anyone who posts
☐ Rule chosen for which year a project belongs to

Step 3: Gather the work

Start with an inventory of what exists and where it lives, then collect the files in one place. Most of the work is already out there; it is just scattered.

Where student work hides

Teachers' computers and Google Drives. Final PDFs, InDesign exports, video files and photos. Ask for the version that was printed, not a draft.
Desktop folders from past years. OWL's catch-up turned up whole folders of old publications, such as playbills, magazines and a 2019 river book.
Printed copies. Calendars, books and posters can be scanned if the digital file is gone.
Physical art. Artwork behind a publication (OWL's Minnesota species drawings behind each Phenology Calendar) can be scanned as a full set, not just the pieces that made it into print.
YouTube channels and old shared drives. Videos may already be online under a former teacher's or student's account.
Competition and partner sites. National History Day websites and other hosted projects can expire. Save a copy or screenshots while they still work.
The school's own website. Some collections, like OWL's student newspaper archive, already live there. Link to them instead of duplicating them.

Keep a running to-do list

A shared list of missing pieces keeps the catch-up moving and gives colleagues something concrete to help with. Group items so they are easy to scan. OWL's list included items like:

Find videos of four placing History Day documentaries (2012, 2014, 2016, 2020)
Get photos of History Day exhibits
Find missing graduation years for older projects
Republish two History Day websites whose hosted pages now show "Under Construction"
Find the 2026 Phenology Calendar
Collect this year's River Documentaries, Senate Expedition and magazines from colleagues

Ask colleagues in a way that works

Ask for specific items ("the final PDF of this year's Justice Magazine") rather than "anything you have."
Ask right after a project ends, while the files are fresh, usually in late May or June.
Ask who made what. Credits are much easier to get from the teacher in June than to piece together years later.
Thank people publicly: send them the link when their students' work goes live.

Organize files as they arrive

Keep one folder per collection (for example, "Publications 2025 and before" or "Fall 2026 MN Species Scans"). Leave originals untouched and make a separate "to upload" folder with renamed, resized copies.

Checklist

☐ Inventory of known projects by year
☐ Shared to-do list of missing pieces
☐ Colleagues asked for specific final files and credits
☐ One folder per collection, originals kept untouched

Step 4: Prepare the files

Every file should be renamed, the right size and right side up before it reaches the site. Fixing these after upload takes far longer and leaves clutter behind.

PDFs (publications, books, calendars, playbills)

Use the final version. Look for the file that went to the printer. Check the cover and last page to be sure it isn't a proof with missing pages.
Rename it following your naming pattern before uploading.
Watch the size. Most hosts limit uploads to somewhere between 32 MB and 128 MB. A 20 to 30 MB magazine is fine. A very large file (OWL had a 77 MB comic book) is slow to load on phones: export a smaller "web" version or compress it first.
Read it through for anything that shouldn't be public (see the privacy rules in Before you start).

Images (artwork, photos, scans)

Resize to about 1,600 pixels on the longest side and save as JPEG at about 80% quality. That keeps each image near 300 KB, sharp on any screen, and quick to load. A full-resolution scan can be 2,500 x 3,400 pixels and 3 MB.
Turn every image upright. Scanners often save artwork sideways or upside down, and the file carries no flag saying which way is up. Look at each one. With a batch of scans, check thumbnails side by side, then zoom in on any you're unsure of. For abstract pieces, ask the art teacher.
Rename each file with the year, project and the student's first name (2027-calendar-art-abir.jpg).
Fix problems before uploading. WordPress can rotate an image after upload, but it saves a new "-edited" copy and leaves the original behind, which you then have to delete.
Write alt text for every image, such as "Abir's drawing of a snow bunting." Screen readers need it, and it helps search engines.

Videos (documentaries, performances, podcasts with video)

Don't upload video files to WordPress. They are huge, slow down the site, and quickly use up storage. Instead:

Create a YouTube channel owned by the school or the program, not by a single teacher's personal account, so the videos stay if that teacher leaves.
Upload each video and set it to Unlisted. Unlisted videos play anywhere you embed them but don't appear in YouTube search, so students' work isn't exposed to the wider internet.
Title each video consistently, for example "Steamboats by Luci – 2022 River Documentaries."
Put each collection in its own playlist, such as "2022 River Documentaries."
Turn off comments.
Paste the YouTube link into the WordPress post, where it becomes a playable embed.

Before saving a title in YouTube Studio, check that the video showing in the editor is the one you meant to rename. When you rename many videos in a row, the upload screen can still be showing the previous video.

Checklist

☐ Final, print-ready PDFs, renamed and under the upload limit
☐ Images resized, upright and renamed
☐ Alt text written for images
☐ Videos on a school-owned YouTube channel, unlisted, titled and in playlists

Step 5: Write and publish posts

Every post follows the same short pattern: what the work is, how students made it, who made it, the work itself, and links to related work. Three or four paragraphs is plenty; the student work is the main event.

Anatomy of a post

Opening paragraph: what and who. Name the project, the grade or class, the year and the driving question. "Each year, OWL's seventh graders explore the question 'What makes a community thrive or suffer?' through Fall Fieldwork."
The process. Two or three sentences on what students actually did: the fieldwork, the reading, the drafts, the experts they met, the audience they presented to. This is what makes the post useful to other teachers.
Credits. Name the teachers and partners in full. Credit student teams by first name and role: "Anna and Rain handled the design and layout, Greta was chief proofreader." Thank funders and partners (a PTO, a grant, a GoFundMe, a nature center).
The work. A lead-in line ("Read the full journal below.") followed by the PDF viewer, video, or gallery.
Related links. Point to other years of the same project and to related projects: "You can also read the 2024 Survival Guide and the 2026 Survival Journal."

The best source for steps 1 to 3 is the work itself. Most publications open with a teacher's foreword that explains the project and thanks the student team. Pull your description from it.

A fill-in template

[Project name] is [what it is] by [your school]'s [grade or class], [Class of / year]. [The driving question or purpose of the project.]

[What students did: fieldwork, reading, research, drafts, audience. Two or three sentences.]

[Student team by first name and role.] [Teachers and partners by full name.] [Thanks to funders.]

Read the full [book / magazine / calendar] below.

[PDF viewer / video / gallery]

You can also see [link to other years] and [link to related project].

Before you hit Publish

Category: exactly one.
Tags: year, every grade involved, every subject involved, and any program tag.
Date: set to when the work came out.
Excerpt: one sentence that describes the work for lists and link previews, such as "AP Language students' 50 essays about survival, from rip currents and house fires to mental health and family, illustrated and designed by a student editing team."
Featured image: the cover or a strong piece of art, if your theme shows one in lists.
Names: student first names only, spelled correctly, with initials where two share a name.
Preview: open the draft preview, check that the PDF viewer or video loads, click every link, and read it on a phone.
Subscribers: if the site emails new posts to subscribers, decide whether a backdated post should go out as an email.

Link old and new both ways

When you publish a new year of a recurring project, update the older posts so they link forward to it as well. Visitors often land on an old post from a search, and a link to the newest edition keeps them moving through the archive. Add the new year to any "Previous editions" list.

Checklist

☐ Opening, process and credits paragraphs written
☐ Work embedded and loading in preview
☐ Category, tags, date and excerpt set
☐ Links added to and from other years
☐ Checked on a phone

Step 6: Recipes for common kinds of work

Different kinds of work need slightly different posts. These are the patterns OWL settled on.

Publications: magazines, books, calendars, playbills

One post per publication, with the PDF shown in a flip-through viewer (PDF Embedder) so visitors can read without downloading.
Name recurring publications the same way every year so they line up: 2024 Justice Magazine, 2026 Justice Magazine.
If a publication changed names over the years (OWL's 8th-grade magazine was Our View in 2022, Reflections in 2023 and the Justice Magazine after), keep the subtitle and link all editions together.
Playbills: credit the director and production team in full, and the student editors and designers by first name.

A newspaper or other serial with many issues

For something like a monthly student newspaper, one evergreen page works better than a post per issue. OWL's Purple Press page has:

A short description of the paper.
A "Read the latest issue" button, updated each month.
A list of recent issues grouped by volume (school year), newest first.
A link to the complete archive on the school's website.
How to subscribe or support the paper.

An issue worth highlighting can also get its own post that links back to the page.

Art galleries

When a publication shows only some of the art, a gallery of every student's piece is a powerful companion. OWL's Phenology Calendars each feature 12 drawings, and a separate gallery post shows all 70 or so.

Use the gallery block with 3 or 4 columns, each image linked to its full-size file.
Caption each piece with the first name and title or subject: "Abir: Snow bunting." When the subjects aren't known, use first names alone.
Write alt text for every image.
Link the gallery and its publication to each other.
Expect to fix a few rotations after posting. Ask the art teacher or students to look the gallery over.

Video collections: documentaries and performances

Group large collections into several posts by theme. OWL's 2022 River Documentaries span five posts: Flooding and Droughts, Invasive Species, Milling, Pollution, and Miscellaneous.
Put a navigation line at the top of each part linking to all the others.
Label each video with a bold line above it in the form "Students: Title," such as "Lauren and Sophie: Slavery on the Mississippi."
Keep the same title on YouTube so the two match.

Projects with a public audience: civic presentations, exhibitions

OWL's Senate Expedition, where students present research on the state budget to lawmakers at the Capitol, gets a fuller post each year:

The final product (the briefing book) in a PDF viewer.
A side-by-side comparison of an early draft and a later draft, which shows growth through revision better than any description.
The posters or exhibit materials.
Photos of the event, without close-up faces of students who have opted out.
One "journey" post that explains the whole project start to finish, which every later year links to.

Competitions: History Day and similar

Tag every entry with the competition (NHD) so the whole history can be browsed together.
Include the year, category (paper, exhibit, website, documentary, performance), division and any placement or award.
Save hosted websites before they expire. A screenshot tour or a PDF export is better than a dead link.

Checklist

☐ Recurring publications named consistently and linked across years
☐ Serials on one evergreen page
☐ Galleries captioned, with alt text, linked to their publication
☐ Video collections split by theme with navigation between parts
☐ Competition entries tagged with year, category and placement

Step 7: Help visitors find the work

Visitors arrive with different questions: a parent wants their child's class, a teacher wants every History Day project, a visitor wants the newest work. Give each of them a one-click path.

The main menu

Put your categories in the top menu (Publications, Documentaries, Podcasts, Artifacts). Each one opens a page listing every post of that kind, newest first, with no extra work from you.

The sidebar

OWL's sidebar has three parts:

Search, for visitors looking for a name or topic.
Recent posts, showing the newest three so returning visitors see what's new.
Browse by tag, a list of every tag (years, grades and subjects). One click shows, for example, all 7th-grade work or everything from 2022. WordPress's tag cloud block does this; set it to show every tag at one size so it reads as a tidy list.

Before you change the sidebar or any shared template, note what was in it so you can put it back.

The homepage

A clear title that says what the site is. OWL's reads "Celebrating High-Quality Student Work at OWL."
The newest posts first, with excerpts and featured images.
Optionally, a short welcome paragraph and links to the biggest collections.

Pages worth adding

About: what the school is, why the archive exists, and how to contact the site owner.
For teachers: how colleagues can send work, what format to send it in, and the deadlines each year.
How to build your own: a guide like this one, for other schools.

Checklist

☐ Categories in the main menu
☐ Sidebar with search, recent posts and a tag list
☐ Homepage title that says what the site is
☐ About page with a contact

Step 8: Keep it healthy

After the catch-up, an archive needs a few hours a month, in a predictable yearly rhythm, plus a careful check now and then.

The yearly rhythm

When	What to do
Fall (Sept–Nov)	Post fall projects (fieldwork, fall plays). Ask new staff to send work. Check plugins and renewals.
Winter (Dec–Feb)	Post winter performances and calendars. Update serials such as the newspaper each month.
Spring (Mar–May)	Remind colleagues that final files and credits are due. Post competitions and civic presentations as they happen.
End of year (late May–June)	The big push: magazines, books, documentaries and galleries. Link each new edition to the older ones.
Summer	Run a full site check, clean up the Media Library, and work through the to-do list of missing pieces.

The full site check

Do this once a year, and before you share the site with anyone important.

☐ Every PDF viewer loads (a deleted or renamed file breaks the post without warning)
☐ Every video plays (videos on other people's channels can vanish)
☐ Links between posts work, and outside links still go somewhere
☐ Homepage, menu and sidebar look right on a phone
☐ No student full names or opted-out students
☐ WordPress, theme and plugins updated; no security warnings
☐ Domain and hosting set to auto-renew, with a current payment method

Clean up the Media Library

Old uploads pile up: rotated copies, renamed duplicates, abandoned drafts. Before deleting anything, confirm it isn't used in a post. Search for the file name across the site, and delete only the versions nothing uses. After a cleanup, open the affected posts to confirm every image still loads.

Fix things quickly

Corrections build trust. When a student's name changes, a credit is wrong or a drawing is upside down, fix it as soon as you hear about it, in the post and in any matching YouTube title. If a family asks for something to come down, take it down first and talk second.

Back it up

Turn on automatic backups through your host or Jetpack, and keep your original files (the folders from Step 3) somewhere safe, such as a school shared drive. If the site ever had to be rebuilt, the originals and your naming rules are what you'd need.

Plan for the next owner

Keep the login details, hosting account, domain registration and YouTube channel under school-controlled accounts, and write down where everything lives. An archive that depends on one person's personal accounts can disappear the day that person leaves.

Using an AI assistant

An AI assistant with access to your site and a folder of student work can do most of the building, posting and upkeep, which makes the archive far easier to start and to keep going. Much of OWL’s catch-up, including this guide, was done this way, with a teacher directing the work and approving each step.

What an assistant can do

Process the files. Read every PDF to find titles, years, forewords and credits; spot duplicates already on the site; rename, resize and rotate images.
Write the posts. Draft descriptions from each publication’s own foreword, and set tags, dates, excerpts, alt text and links between editions.
Build the bigger pieces. Galleries with captions, video collections split into themed parts, evergreen pages like a newspaper archive.
Keep things healthy. Run site checks, confirm every PDF viewer and image loads, clean up the Media Library, and keep a running to-do list.

What stays with a person

Accounts and money. Buying the domain and hosting, creating accounts, and signing in.
Privacy decisions. Checking the opt-out list and deciding what is appropriate to publish. An assistant can flag full names or sensitive content, but a person who knows the students makes the call.
Facts that aren’t in the files. Who made an untitled documentary, or which species a drawing shows, has to come from a teacher or student.
Approval and a final look. Review drafts before they go live, and check visual calls such as which way a drawing faces.

Why it helps the archive last

The biggest risk to a student work archive is that it depends on one busy person. When that person runs out of time or moves on, posting stops and the site slowly goes stale. An assistant lowers that risk in three ways:

Less time per post. Posting a year’s work becomes an afternoon instead of weeks of evenings, so it actually gets done each June.
Consistency without memory. Given your naming rules, tags and post pattern (Step 2 and Step 5), an assistant follows them every time, so the site stays consistent even when a new teacher takes over.
An easier handoff. A new owner doesn’t need to learn WordPress first. With the guide, the folders of originals and an assistant, they can pick up where the last person left off.

To make the most of it, keep your conventions written down, keep originals in organized folders, and keep the to-do list current. Those are what let anyone, with or without an assistant, carry the work forward.

Share it, and learn from others

An archive only matters if people visit it. Share it widely, and borrow ideas from schools that have done this well.

Get the word out

Link the archive from the school website and the weekly family email.
Send families a direct link when their child's class work goes up.
Share it with district leaders, partner organizations and funders, especially the post that features the project they supported.
Show it at open houses, exhibitions of learning and staff meetings, and use it with students as a source of models.
Send it to the networks your school belongs to. OWL shared its archive with EL Education.

Other archives worth exploring

High Tech High student work: a long-running project archive across a network of 16 schools.
XP Trust shop: a network of schools in England that sells student-created books and books about student work.
Four Rivers Charter Public School gallery of student work: a single school's gallery.

Lessons learned at OWL

Decide conventions early. Titles, tags and file names are easy to set at the start and tedious to fix across 100 posts.
Collect credits when the work is fresh. Finding out who made one documentary years later can take weeks of emails.
Keep originals untouched. Rename, resize and rotate copies, never the only file.
Own the accounts. Videos on a retired teacher's channel or a project on an expired competition site can't be moved without them.
Read before you publish. Student writing can hold names and personal details that belong offline.
Tie the years together. Links between editions turn a pile of posts into a story of how a project grew.
The work speaks for itself. Keep descriptions short and let the student work fill the page.

Quick-start checklist

☐ Owner named, principal on board, privacy rules agreed
☐ Site, domain, theme and PDF viewer set up
☐ Categories, tags and naming rules written down
☐ Inventory and to-do list of work started
☐ First five posts published from your strongest recent projects
☐ Menu and sidebar set up for browsing
☐ Colleagues told how to send work
☐ Yearly check on the calendar