LessonUp Studio
Beginner workshop - templates, files, and sharing what works
LessonUp Studio
Beginner workshop - templates, files, and sharing what works
Aim of the session: everyone leaves having made one lesson, reused one template, and knowing where the team's shared templates live. Image credit: Marvin Meyer / Unsplash
Before we start
Have these two installed and open:
Claude - Claude Desktop or Claude Code, signed in
LessonUp Studio - opened at least once, signed in to LessonUp
The Getting started screen in Studio shows a checklist. Everything on it should be green.
Walk the room before starting. The checklist reports whether Claude Code is installed, whether the studio's plugin is current, and whether anything has called the studio's tools yet.
Optional but worth it: the Lessonup mcp plugin (Customize > Discover in Claude), which brings search_images for rights-free photos. Image credit: Rodeo Project Management Software / Unsplash
How do you make most of your lessons today?
From scratch in the editor
By copying an old lesson
From a colleague's lesson
I mostly present, others build
This item has no instructions
What Studio is
Studio turns a folder of files into LessonUp lessons.
You ask Claude for a lesson, Claude writes the file
The Studio window shows it as slides while you work
When it is right, you push it to your LessonUp library
The window is a preview. The file is the lesson.
This item has no instructions
Everything is just a file
A lesson is one text file
A template library is one text file
Instructions for Claude are a text file - CLAUDE.md
A house style is a notes file next to the lessons
A skill is a folder with a text file in it
Open the workfolder in Finder next to the Studio window, so people see the files and the slides at the same time. Open one lesson file in a text editor to show it is readable. Image credit: Richard Heinen / Unsplash
Why that matters
Files you can read
Files you can move
Copy, back up, email, or put them in a shared folder - like any document.
Open any lesson and see exactly what is on each slide. Nothing is hidden in a database.
This item has no instructions
Templates
A slide with its layout, colors and fixed parts already in place.
Define it once
Each slide fills in only what changes
The rest stays the same, everywhere
Image credit: Tómas Rekstad / Unsplash
One template, many slides
Title goes here
Chapter
the template
layout, colors, band, chip
The Rhine
Chapter 1
The Danube
Chapter 2
The Thames
Chapter 3
each slide fills in only the title and the chip
Left is the definition: it never shows as a slide itself. Right are three slides built from it. They only say what differs - the title and the chip. Change the band color in the template and all three change with it.
Why templates are powerful
One change, everywhere
A whole series looks like one product. Logos, footers and colors never drift.
Consistent
Redraw the logo in the template library and every lesson in the series changes with it.
Real example in the workfolder: the rijksmuseum folder. One house-style library, several lessons built on it. The studygo folder is another one.
You fix the logo in a template library. What happens to the lessons that use it?
Nothing - you have to fix every lesson yourself
Only new lessons get the new logo
Every lesson that uses the library shows the new logo
They pick it up in Studio straight away. Lessons already pushed to LessonUp change once they are pushed again.
Good templates come from good lessons
You do not have to design templates up front.
Take a lesson that already looks great
Ask Claude to turn it into a template library
Build the next lessons from that library
Studio has a documentation page for this - Building a Template Library.
Because it is a file, it can be shared
Put the good stuff in a shared Google Drive folder and everyone gets it:
Templates - the libraries that already look right
Skills - repeatable recipes, like "make a quiz from this chapter"
Example lessons - to start from
Drive keeps it in sync. Improve it once, the whole team has it.
Google Drive for desktop puts the shared folder on your disk like any other folder, so Studio and Claude can read it. Point Studio's workfolder at it, or at a folder inside it, from the settings (the cog at the bottom of the sidebar).
One folder, the whole team
Shared Google Drive folder
Template libraries
House styles
Skills
Example lessons
You
Claude + Studio
Colleague
Claude + Studio
Colleague
Claude + Studio
sync
LessonUp
push
improve it once - the whole team has it
The shared folder holds what makes lessons good: templates, house styles, skills and examples. Everyone's Claude reads the same folder, so everyone's lessons start from the same place.
Each person still pushes to their own LessonUp library. The folder is shared, the lessons are not - which is why you Duplicate before you start from a shared lesson.
Working with CLAUDE.md
Long - in a file of its own
Every Claude starts by reading it
Studio owns the top part and rewrites it
Your rules go below the line - write them, or ask Claude to add them
Only what every lesson needs
A house style, the rules of one series
Keep it in its own file, next to the lessons
Point at it from CLAUDE.md with one line
Claude reads it only when it is needed.
Short - in CLAUDE.md
Example of a rule below the line: "We write in Dutch and use the Light theme."
Example of a pointer: "For Rijksmuseum lessons, read rijksmuseum/rijksmuseum-huisstijl.md first." That house style is long and only matters for one series - in CLAUDE.md, every Claude would read it before every lesson.
Open the workfolder's CLAUDE.md and show the line, then ask Claude live to add a rule below it.
What to share
Picture names must be unique across the folder
Start from a shared lesson with Duplicate, never copy the file
Watch out
Template libraries
House-style notes
Skills
Example lessons to start from
Share
This item has no instructions
Why Duplicate and not copy?
Every lesson file carries its own id - the one lesson in LessonUp it belongs to.
A copied file still points at the original lesson
Pushing it updates someone else's lesson, or is refused
Duplicate gives the copy an id of its own
This item has no instructions
How to duplicate a lesson
In Studio
Open the lesson you want to start from
Press Duplicate, top right, next to Save
Studio opens the copy, called <name> copy, next to the original
Or ask Claude: "Duplicate the Night Watch lesson and call it Van Gogh"
Starting from a documentation example? Use as starter lesson does the same.
Show it live on one of the rijksmuseum lessons.
The copy lands in the same folder as the original. If that is the shared Drive folder, move it into your own folder afterwards. Moving a file is fine; only copying brings the old id along.
Already copied a file by hand? Delete every id line in it (the lesson's and each slide's), then ask Claude to lint it. That gives it fresh ids.
Put the Studio loop in the right order
Claude runs lint, validate and render itself when it works in the workfolder. The point is to know they happen, and to ask for them when something looks off.
The Studio loop
ask
you, in plain words
write
Claude writes the file
lint
the shape
validate
the conversion
render
what it really looks like
push
to your library
look here, every time
and again, until it looks right
The answer to the sorting question, drawn out.
Stop at render. Lint and validate read the file; render shows what it becomes - text running over an edge, a question nobody can read, a slide that is too full. That is where the quality comes from, and Claude goes round this loop by itself until it looks right.
Exercise 1 - your first lesson
In Studio, open the documentation and pick roman-empire
Press Use as starter lesson
Ask Claude to rewrite it for a subject you teach
Watch the Studio window update as Claude works
Ask Claude to push it to your library
About 15 minutes. Check everyone can see their lesson in LessonUp before moving on. Image credit: Daniel Thomas / Unsplash
Exercise 2 - make it a template
Duplicate your lesson from exercise 1, and work in the copy
Pick the slide you like best
Ask Claude to turn it into a template
Ask for three new slides that use it
Change one color in the template and watch all three follow
About 15 minutes. People who finish early can ask Claude to move the template into its own library file. Image credit: Annie Spratt / Unsplash
What should go in our team's shared Studio folder?
Collect the answers - they are the to-do list for the shared Drive folder after the workshop.
Take this home
The file is the lesson, the window is a preview
Templates keep a series consistent, and one change updates them all
Files can be shared - templates, house styles and skills sync through Google Drive
Start from someone else's lesson with Duplicate
This item has no instructions