A clearer entry point
Removed redundant lesson teasers and rebuilt the homepage around orientation, module discovery, and a confident place to start.

Making a developer-oriented course more approachable without losing the concepts that make it useful.
UX / CONTENT STRATEGY / AGENT DIRECTION
VIEW THE COURSETHE PROJECT
The original course offered a practical introduction to agents, tools, context, and web-building workflows. It worked—but it assumed the learner already felt at home around developer language and interfaces.
I redesigned the course for true beginners and non-coders. My role combined UX and content strategy, visual design, instructional thinking, and direction of Codex as an analysis and implementation partner.
Removed redundant lesson teasers and rebuilt the homepage around orientation, module discovery, and a confident place to start.
Reworked definitions, prompts, and lesson framing so beginners could understand agents without flattening the technical ideas.
Unified editorial reading surfaces with dark workbench patterns for simulations, quizzes, traces, and technical examples.
Used scoped changes, protected originals, targeted agent reviews, validation checks, and written handoffs to keep the work reviewable.
BEFORE / AFTER
Homepage
The redesign replaces a passive, centered introduction with an editorial hero, clearer course framing, and a more direct path into the module system.
Module page
Typography, spacing, callouts, and technical surfaces were reorganized to help new learners distinguish explanation from action.
Simulation
The simulation was reframed as a focused workbench: clearer steps, stronger contrast, and less decorative noise around the core interaction.
Quiz pattern
Quiz components gained a consistent dark treatment, more readable code-heavy prompts, and clearer feedback states.
HUMAN × AGENT
Define scope, protect originals, and tell the agent what it may inspect or change.
Use targeted read-only reviews for redundancy, readability, typography, and risk.
Review findings, reject noise, and choose the design response that serves the learner.
Make scoped edits, preview in browser, inspect behavior, and document the result.
ONE CONCRETE EXAMPLE ↓
Scan the homepage for content that repeats material already taught in the modules.
Lesson teasers made the homepage behave like a second, shallower version of the course.
Remove the teasers and refocus the page on orientation, module discovery, and a clear place to begin.
A simpler entry path with less cognitive load and a more confident first impression.
THE RECEIPTS
REUSABLE ACROSS PROJECTS
FROM DOCUMENTATION TO A WORKING TOOL
Instead of leaving the style guide as a project-specific reference, I translated its typography, color, spacing, and component rules into instructions an agent could load and apply in future projects. This made the system portable and repeatable—while keeping final design decisions and quality control in human hands.
WHAT I LEARNED
01Clear constraints make agent-assisted work safer, easier to review, and easier to continue.
02Beginner-friendly design is often an act of subtraction—not simplification for its own sake.
03Local fixes protect a pilot, but repeated patterns should eventually become shared components.
04AI can surface options and problems. The designer still decides what matters to the learner.
SEE THE WORK IN CONTEXT
Explore both versions to see how the redesign changed the course’s structure, language, and learning experience—not just its visual style.
01 / REDESIGNED COURSE
See the beginner-focused course as it exists now, including its revised lessons, interactive tools, visual system, and clearer paths through technical ideas.
EXPLORE THE REDESIGN02 / ORIGINAL COURSE
Open the original course to compare the earlier structure and presentation directly with the redesign decisions documented in this case study.
VIEW THE ORIGINAL