Educational Resource Sharing Among Teachers
Share educational resources among teachers and educators. Build collaborative libraries of lesson plans, worksheets, and multimedia content.
Teachers share resources through four main channels: open repositories like OER Commons and CK-12 (Creative Commons licensed, free to remix), commercial marketplaces like Teachers Pay Teachers (TpT has 7 million teachers and 4 million resources, typical price $2 to $10), district-internal Google Drive or OneDrive folders, and direct person-to-person sharing by email, messaging, or encrypted link. The right channel depends on licensing, file size, audience, and how much control you want. A one-off 500 MB video for a grade-level team doesn't need a marketplace listing, just a link that expires next Friday.
Open Educational Resources and Creative Commons
OER Commons hosts 75,000+ items under CC BY, CC BY-SA, or CC BY-NC licenses. CK-12 focuses on K-12 STEM with remixable FlexBooks. OpenStax College produces full textbooks (Biology 2e, College Physics) free under CC BY, used by 65% of US degree-granting institutions. MERLOT is the university-level equivalent. When you remix or adapt, attribution matters — CC BY requires credit to the original author, title, source, and license, typically formatted as "Fractions Lesson by Sarah Kim, CC BY 4.0". Track your adaptations in a simple spreadsheet so your year-end sharing to colleagues keeps the chain intact.
District-Internal Libraries with SSO
A typical district sets up a shared Google Drive or Microsoft SharePoint library per grade level or department. Instead of one teacher emailing a lesson plan to eight colleagues, the resource lives in a shared folder with per-user access controlled by the district's Google Workspace for Education or Microsoft 365 Education tenant. Clever and ClassLink handle SSO rostering for 90%+ of US K-12 districts. Version history in Google Docs lets any teacher roll back when a colleague's edit wrecks the printable. For larger assets — 500 MB video clips, .mp4 lecture recordings — link out to Drive rather than trying to email attachments.
Marketplace Economics and Licensing
Teachers Pay Teachers pays sellers 60% on standard resources, 80% on premium membership sales. A popular 5th-grade fractions bundle at $8 selling 2,000 copies a year nets $9,600 to the author. TpT's license grants buyers "non-transferable single-classroom use" — a team of five teachers technically needs five licenses, which most buyers ignore but some districts enforce via central purchasing. Etsy has an education category with similar dynamics. For district bulk purchases, negotiate a site license directly with the creator rather than buying individual licenses; a $500 building license beats asking each teacher to expense $8.
Large Multimedia Files: Video, Audio, and Interactive
A classroom-filmed demonstration video at 1080p runs 500 MB to 2 GB for a 45-minute lesson. A narrated Keynote or PowerPoint with embedded audio hits 200 MB to 1 GB. H5P interactive content (drag-and-drop, hotspots, branching scenarios) stays small but needs a host — WordPress plugin, Moodle module, or H5P.com at $39 per month for small districts. For files above email attachment limits (25 MB on Gmail, 20 MB on Outlook free tier), upload to Google Drive and share the link, drop into the district SharePoint, or send through an encrypted transfer service like HexaTransfer, SwissTransfer, or WeTransfer for short-term one-off shares.
Respecting Student Work in Shared Resources
A lesson plan that includes photos of student work needs parental consent under FERPA and state student privacy laws. Pixelate faces, scrub names from worksheets, and remove any identifiers from handwriting samples before posting. Directory information (name, grade level) released under FERPA's directory-info provision still requires an annual opt-out notice. Some states — California (AB 1584, SOPIPA), New York (Ed Law 2-d), Illinois (SOPPA) — tighten the rules further with detailed vendor contracts required for any service touching student data. The simplest rule: if you wouldn't post it to your public Twitter, don't post it in a resource sharing site either.
Version Control for Lesson Plans
Lesson plans evolve year over year. The "fractions unit v3.2" you used last fall probably differs from v3.4 a colleague picked up. Dropbox's 30-day version history covers most accidental changes; Google Drive keeps unlimited versions on .gdoc files, 100 versions on non-Google formats. For teams collaborating across districts, a Git repo with plain markdown or plaintext lesson plans gives clean diffs and blame — overkill for most but essential for large curriculum projects like EngageNY or Illustrative Mathematics. Tag releases per academic year (2025-2026, 2026-2027) so district curriculum coordinators know what's current.
Sharing Across Districts and States
Cross-district sharing — a teacher in Texas giving a lesson to a colleague in Oregon — usually just means pasting a Google Drive link or emailing a PDF. For state-vetted materials, consortia like EdReports rate open curricula against standards; the @cast AEM (Accessible Educational Materials) Center tracks accessibility. If the resource includes copyrighted images (a Getty photo used under fair use in your classroom), stripping those before public sharing avoids DMCA takedowns — CC-licensed replacements from Pixabay, Unsplash, or Wikimedia Commons work for most subjects. When a colleague in another state asks for your AP Chemistry exam review, a 72-hour encrypted link avoids the "forward this to everyone" ripple.
Protecting Your Own Work
You wrote the lessons. They're copyrighted to you (or to the district, depending on your employment contract — check for "work made for hire" language). If you're selling on TpT, reserve rights with a clear license statement. If you're sharing with colleagues informally, a Creative Commons license (CC BY-NC-SA is common for teacher-to-teacher: attribute, non-commercial, share-alike) prevents your lesson showing up for sale on someone else's TpT store. For resources you don't want distributed beyond your team, a watermark with your name plus a short-expiry encrypted link keeps the payload inside the intended circle.
Try it at hexatransfer.com — free, no account, 10 GB max. When the grade-level team needs your 3 GB end-of-year project bundle by Friday, a single encrypted link beats eight Dropbox invites.
Send large files securely with end-to-end encryption
Transfer files up to 10 GB for free with end-to-end encryption. No account required. Your files are encrypted in your browser before upload — no one else can read them.
Send a file