Finished result
The task
Bring chapters, guided activities, labs, and navigation into one learning environment for BITM 330. This is a bigger project, and it is still going. Agents help with the content and the software. I design the learning sequence and review every change.
Starting materials
- Chapter and lab source files, figures, learning activities, and a course outline.
- A reader interface with chapter and section navigation.
- Account and course-access requirements.
- A repeatable build and deployment process.
How the project is assembled
Organize the learning content
Draft and review the course materials in the working folders. The current generator supports chapter HTML and Markdown sources, selected through chapter metadata. The content is kept separate from how the reader looks.
Bring reviewed sources into version control
GitHub stores the project source and change history. Review proposed changes before they become part of a published version. The courseware repository is not linked from this demonstration.
Assemble the reader data and interface
Build scripts assemble the source content and metadata for the reader. The current interface uses React and TypeScript, with Vite for the application build. Generated content is rebuilt from its sources.
Connect account access
Supabase supports authentication and course-access data. The application checks access separately from how it displays a chapter. Account controls require their own verification when the interface changes.
Build, preview, and deploy
The Vercel configuration runs the full build and serves its output at the custom domain. The configuration also includes a protected-content API route. Review a preview and check key reading and access paths before promoting a change.
Make small, reviewable improvements
Give the agent one small task, the files it needs, what should happen, and how to check it. Review the change, then do the next one. The whole platform was built this way.
View and copy the prompt
Inspect the current courseware source and build configuration. Map the content files, reader interface, authentication and access checks, and deployment process. Propose one small improvement to chapter navigation. Identify the source files it would affect, how to preview it, and how to verify existing navigation and access behavior. Do not edit generated data directly, change authentication rules, deploy, or expose private repository links. Save a plan before implementing anything.
What each component contributes
| Component | Role in this project |
|---|---|
| Google Drive | Working materials, drafts, and teaching assets |
| GitHub | Source files, reviewed revisions, and change history |
| React + TypeScript | Reader interface and navigation |
| Vite and content scripts | Assemble content and build the application |
| Supabase | Authentication and course-access data |
| Vercel | Build, hosting, and the configured API route |
This description was checked against current package, generator, deployment, and access-code files. Some older README descriptions refer to a prototype and are not used as evidence of current behavior.
Try one small change
Choose one navigation improvement and write a plan using the prompt above. During the session, use the completed public site as a tour. No accounts, access rules, or live course content need to change.
Files and resources
What carries over is the routine: organize the sources, make one small change, review it, publish.