Materials trapped in the LMS disappear when the semester ends. The static HTML + private link shape lets a lesson live where the educator chooses, not where the institution provides.
The teacher builds a great unit on data visualization for the spring semester. Interactive examples, embedded video walkthroughs, a chart-comparison exercise the students click through, a methodology appendix with citations. The whole thing lives in Canvas.
The semester ends. Students lose Canvas access in 90 days. The teacher's portfolio includes a link to the unit; the link asks for Canvas login when followed from outside. Two semesters later the teacher wants to update the unit with refreshed examples; Canvas's editor doesn't support the workflow they prefer; the export is messy.
The unit was correct. The container made it fragile.
Four properties that recur across most educator workflows:
The LMS handles property 1 well. Properties 2-4 are usually awkward fits.
LMS (Canvas / Moodle / Blackboard / Google Classroom). Designed for the institution's grade-attached workflow — assignments, submissions, discussion threads, grade book, attendance. Strong for during-semester interactions; weak after the semester closes and the access permissions expire.
Notion / Notion for Education. Works well as a working document — the educator edits, students view, the page lives indefinitely on the Notion subdomain (or on a custom domain for paid plans). Trade-off: the URL reads as Notion, the page UI competes for attention, fine-grained visibility per page is limited.
Personal academic site (WordPress on the .edu domain, etc.). Strong for ongoing publishing — papers, course pages, news. Heavier setup; the institution's IT often involved; the workflow assumes regular updating.
Static HTML at a private link. Designed for one-page deliverables; the lesson as a single HTML file lives at a stable URL chosen by the educator. Survives the semester end; references cleanly from a portfolio; per-document searchable opt-in handles the selective public-visibility case.
For most educators, the practical shape is: LMS for the live semester (graded interactions, attendance, discussions), private-link static HTML for the persistent reference version that lives across semesters and is portfolio-referenceable.
For an educator already building lesson materials in any of the common tools:
The lesson file ends up as one HTML page in the 100KB-2MB range (text-heavy lessons land small; image-heavy or video-heavy lessons go larger). The file uploads to the private-link host once; updates happen by re-uploading at the same URL.
The private-link shape doesn't mean "students must log in." For most educator use cases, the access shape is:
For the cases where the institution requires authenticated access (graded assignments, student-data-attached content), the LMS remains the right shape — the private link is for the materials themselves, not for graded interactions.
Try the shape with one lesson — drop the HTML, send the URL to a colleague, walk through how the material reads outside the LMS. Free, no card, 7-day self-destruct on the anonymous tier (upgrade to permanent before sharing with a real class).
A few materials per term usually want to be public — a guest-lecture handout, an open course resource, a conference talk supplement, a piece the educator wants in their portfolio. The private-link host's per-document searchable opt-in handles this:
This is the shape the tiers are sized for: the free tier opts one document into searchable, Solo raises it to five, and Studio is unlimited. For most educators with mostly-private materials and one or two public exceptions per term, the free tier's single searchable — or Solo's five if a term runs busier — is enough.
A specific advantage worth naming: when an educator moves between institutions, the LMS material doesn't move with them. The Canvas units from the old institution stay in the old Canvas; the Moodle pages from the new institution start empty.
A private-link host is institution-agnostic. The lesson materials at the educator's chosen URL move with them — across semester, institution, country. The educator's portfolio link points at the same URL regardless of where they're teaching.
For educators who change roles or institutions across their career, this is the structural property that makes the static-HTML pattern worth the setup overhead.
Solo plan ($4.99/mo) keeps lesson URLs permanent (no self-destruct). Studio plan ($14.99/mo) adds custom domain so URLs read as the educator's own surface, plus unlimited searchable opt-in for materials meant to be public. The password layer for restricted-access material is available on every account, free.
The static-HTML + private-link shape doesn't replace:
The right framing: the private-link static HTML is for the lesson materials themselves — the part of teaching the educator owns, that should outlive the semester, and that should be referenceable from anywhere the educator chooses. For the parts that genuinely need institutional infrastructure (grades, paid enrollment, peer review), different shapes fit.
"Client portal" is one word covering two very different jobs. One of them needs software with logins and permissions. The other one is four links in an email, and buying the first when you needed the second is how a solo practice ends up administering a system nobody logs into.
You have one finished case study but the portfolio site isn't live yet. Here's how to send that single piece as a private link — without pushing a half-built site or flattening it into a doc.
Freebies, drafts, little tools — as a creator you keep needing a link that reaches specific people and nowhere else. A working guide to private share links for the three things creators send most.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.