edu-demo-builder

To build interactive educational demos, copy a base HTML template to your output location and start editing. This workflow enforces a phase-driven process, guiding you from initial visual planning to final usability validation with reproducible outputs.

A documentation-first approach for educational visualizations captures design decisions and rationale in an agent_approach.md file before coding. This ensures explicit UX design logic, consistent outcomes, and reviewer-ready artifacts across generations.

Yes, the template orchestrator supports iterating educational demo layouts across generations. By copying base templates into structured generation directories, you preserve previous versions while refining visuals and validating usability.

No external dependencies are required to start designing educational demos. You only need to copy the provided base HTML template to your local output directory and begin editing the visualizations directly.

The best way to document design decisions when refining educational demos is maintaining an agent_approach.md file. This captures your explicit design rationale and validation steps, ensuring reproducible, reviewer-ready artifacts.

The phase-driven workflow for educational demo generation requires strict adherence to copying base templates and documenting decisions. Skipping phases or bypassing the documentation-first approach breaks reproducibility and compromises reviewer-ready outputs.