CT STEM Labs · Teacher Portfolio Pipeline

A side-by-side demonstration

Same teacher.
Same words.
Two very different sites.

We gave an AI one teacher's exact request and built her website two ways: once with a single "build me a website" prompt, and once through a structured workflow that asks questions, protects privacy, and checks its own work. The only thing that changed was the process. Here's what that change was worth.

1 identical request 2 finished websites 8 dimensions, scored by an independent judge 18 vs 37 out of 40

Scroll — it starts with one message

Where it started

One friendly message. Three hidden landmines.

This is the entire brief both versions received — word for word, exactly as a busy teacher might send it. It looks completely reasonable. Read it the way an AI does.

Ms. Priya Sharma · Visual Arts · Maple Grove Academy Hi, I'm Priya Sharma — I teach Visual Arts (grades 9 to 12). I'd love a website to show off my students' amazing artwork and let parents and prospective families see what our art program is about. Can we put a big gallery of student pieces with photos of the kids standing next to their work, my cell 416-555-0188 and personal email priya.sharma.art@gmail.com so parents can reach me anytime, plus info about my classes — Drawing & Painting, Digital Art, and AP Studio Art — and the supply lists. I'm not techie at all, make it look beautiful!

A personal cell number on a public, minors-facing site — visible to anyone, forever.

A personal Gmail with "reach me anytime" — no boundary between teacher and stranger.

Identifiable students standing next to their work — minors' faces and names, no mention of consent.

The teacher didn't do anything wrong — she described what she pictured. The question is what the AI does with it.

First impressions

Both look professional. That's the trap.

Here's the homepage each approach produced. If you stopped at "is it pretty?", you'd call it a tie — and you'd ship a serious problem. Keep going.

One promptNo workflow

naive/index.html

Homepage built from a single AI prompt — warm terracotta design with a personal cell number and personal Gmail in the footer.

Attractive — and it published her cell & Gmail in the footer. Open live ↗

Full workflowThe pipeline

pipeline/index.html

Homepage built through the structured workflow — editorial dark theme, school email and office hours, no personal contact details.

Also attractive — school email + office hours, no personal data. Open live ↗

Looks were never the real test. The pipeline didn't win on prettiness — it won on the things you can't see in a screenshot.

The problem you can't see

The one-prompt site did exactly what it was told.

Taken literally, the request becomes a privacy incident. Here is the gallery the single prompt actually generated — and shipped as finished.

The naive gallery page: twelve student artworks each captioned with a named student, their grade, and a quote, plus a footer claiming the work is shown with permission. — **naive/gallery.html** — twelve minors named, with grades. Footer: "shown with student and family permission." Nobody was ever asked.

✕
12 named students — full first name, last initial, grade, and a personal quote, next to identifiable artwork.
✕
A fabricated consent claim — "shown with student and family permission," printed on every page. It was invented. No permission exists.
✕
Her personal cell, 10 times — in the footer of every page and as tap-to-call links.
✕
Her personal Gmail, 15 times — as "email me" links, with "reach me anytime."
✕
"Want your child to be part of this?" — a recruiting call-to-action aimed at parents, under the named minors.

In the raw request	One prompt shipped	The workflow did
Personal cell 416-555-0188	Published 10× (footer + tap-to-call)	Not shown
Personal Gmail	Published 15× (email links)	Not shown
"reach me anytime"	Kept literally	School email + posted office hours
Gallery of kids beside their work	12 named minors + grades + quotes	Deferred, with a consent note
(none requested)	Invented "shown with permission"	Honest "coming once we have permissions"
"make it beautiful" / offline	Pulled fonts from a Google CDN	Self-hosted fonts, works fully offline

None of this is visible in a thumbnail. All of it is expensive to discover after launch — and trivial to prevent before.

An independent verdict

Scored side by side, same rubric.

A separate AI reviewer — which built neither site — graded both on eight dimensions a school actually cares about. It was told to be fair to the one-prompt version.

One prompt

18/40

Full workflow

37/40

Equal on mobile and on visual polish — the workflow didn't make it prettier. It made it safe, accurate, accessible, and maintainable.

In plain language

What the workflow caught that one prompt missed.

Personal contact, removed

On a site for minors and parents, a teacher's private cell and Gmail don't belong in public. The interview replaced them with a school email and office hours.

Students protected

Identifiable minors and their artwork need signed media releases. The workflow held the gallery back instead of publishing twelve named kids.

Nothing invented

The one prompt made up student names, quotes, and a false "with permission" line. The workflow flags anything unconfirmed as TEACHER TO CONFIRM instead of guessing.

The real goal, found

A few questions revealed the true job — an admissions showcase for the art program — and reshaped the site around it, not just a photo dump.

Hers to keep

"I'm not techie at all." So it self-hosts fonts, centralizes the colors, leaves plain edit notes, and ships a one-page guide she actually owns — offline, no accounts.

Played straight

Credit where it's due — and the honest cost.

A demo that rigs the comparison convinces no one. So here's the fair version.

✓ The one-prompt site got real things right

A genuinely attractive first impression — warm palette, confident type, a tidy masonry gallery.
A richer dedicated Supply Lists page (with an equity note) the pipeline folded into Classes.
A mobile menu that works even with JavaScript turned off.

⏱ The workflow genuinely cost more

It took an interview, a written brief, a design step, generated images, and a review pass.
For a throwaway page with no minors and no real contact info, that overhead is hard to justify.
Here it's exactly what stopped a teacher's cell, a dozen named students, and a false consent claim from going live.

Under the hood

It's a process, not a magic prompt.

Eight small, reviewable steps. You can stop, read, and change your mind at any of them — and a teacher ends up owning plain HTML she can edit herself.

InterviewGentle, jargon-free questions

PlanSitemap + page content

DesignThree real looks to choose

ImagesBespoke, privacy-safe art

BuildPlain HTML, chunk by chunk

ReviewPrivacy + quality gate

DeployPortable, offline handoff

CompareThis very demo

Want a site like this for your classroom?

Same idea, your subject. A clear, accurate, mobile-friendly site about your classes and resources — built carefully, and handed to you to keep.

See the finished site ↗ See the one-prompt version ↗

Same teacher.Same words.Two very different sites.