FieldNote 002

Craig pixel avatar Computer pixel avatar
Project Title
UDL 3.0 Planning Dashboard
Project Type
Educational Tool / Interactive Dashboard
Terrain
Professional Learning / Early Career Teachers
Toolchain
HTML, CSS, JavaScript, AI Agent, GitHub Pages
Time to Prototype
~1 focused working session
Record
Dialogue distilled into strategic phases

The Result

Public link: https://craigwrenasmir.github.io/UDL-Dashboard/

Screenshot of the UDL 3.0 Planning Dashboard showing the top-down classroom view

The Goal

The UDL 3.0 guidelines created by CAST are a powerful framework for inclusive lesson design. They are regularly incorporated into early career Australian teacher training. It would be useful to have a practical dashboard that these educators could sit down with and think through a lesson in dialogue with a mentor.

The goal was to turn the UDL domains into an accessible, interactive planning dashboard that felt informative and useful. I also wanted the dashboard to produce an output that educators could copy into their lesson plans or other planning documents (like a Google Doc). Then, I thought, "You know what might be fun and useful? If the output also mapped onto a visual classroom environment". So, that's what we did :)

Conversation Strategy

  1. Define the audience first: early career Australian teachers and those interested in learning more about UDL. The tool doesn't replace educators using the UDL Guidelines or accessing the CAST website, it's just a way of thinking the elements through, preferably in conversation with a mentor at university or in a school.
  2. Get a working tool before refining it: request the full dashboard structure first, then iterate on language, spelling, and labelling as separate passes.
  3. Think about what could be unique and fun: I knew I wanted a classroom view as part of the output, and it's nice to have these sort of 'joy' elements when creating tools.
  4. Describe the vision before asking for code: for the classroom view, have the design conversation first — agree on zone mapping, interaction model, and visual style — then build.
  5. Publish early, refine continuously: push to GitHub Pages before the tool is finished so every iteration can be seen and shared as a live link.

Dialogue Excerpt

Infrastructure Notes

File Structure: two-file app — index.html for the full dashboard, udl-guidelines-summaries.js for all popover content — kept separate for safe editing.
Draft Persistence: planning notes auto-save to browser localStorage so teachers can return to a lesson in progress without losing work.
Hosting: GitHub Pages for public delivery, shareable link from day one.
Deployment Workflow: local edits, commit, push to main, automatic Pages refresh within minutes.
Asset Management: avatar images and any screenshots stored in assets/ folder inside the repo — no external dependencies.
Maintenance Pattern: summaries and guideline labels live in a single JS file — language updates never require touching the dashboard logic.

Reusable Pattern

You could use this pattern to…

Back to Home →