July 30, 2026
Action Items
- Add Process to the current posts (e.g., how-to, what platforms used, specific prompts)
- Video tutorials also work.
- prompt design > vibe coding > html, js, css code package vs. standalone html > github page URL > embed WordPress
- In the Learning Outcomes – Simple Matrix, add description of LOs, rather than using LO# only.
- Add Reflections section to the end, addressing:
- Rough time estimates (e.g., 2 hours, 2 days)
- Cost and tips (e.g., token limit, environmental cost, offline LM, Copliot for UBC faculty)
- Conversation/ vibe coding, rather than single prompt
- Accessibility/Alt-text/interactive features
- Print version generation
- *Napkin AI
- *Notebook LM – popular tool for visualization; but generated images may need careful implementation. (image too crowded; AI-feel; should be meaningful; UDL aligned)
- Case study: Good example vs. Bad example
- *AI-generated presentation that walks through syllabus (Gamma.app)
- (Optiona) AI policy
- clear statement
- how to indicate relevant AI policy for each tasks? (recent trends, tags)
Overall Structure (Refined)
- By Component
- Course Schedule
- Learning Outcomes
- Reading List
- By Tool
- Napkin AI
- Notebook LM
- Claude/ChatGPT (create project studio with prompt embedded or app)
- Gamma/Google Vids (For AI-generated presentation)
- By Case
- Good example
- Bad example (key consideration, tips, pet peeves)
Next Step
- Schedule next meeting with Natasha in mid-August