ForgeLessons From Localization to Lesson Authoring
Adam Kane and Miguel Whitney trace the problem behind ForgeLessons, demonstrate the localization workspace, and define the next layer of authoring tools.
September 9, 2026 · Adam Kane + Miguel Whitney Fireflies duration: 118.05 min · 1,740 transcript sentences Focused product walkthrough: approximately 29:02–42:01
Google Sheets remains the source of truth for lesson content consumed by Unity. ForgeLessons provides the working interface, identifies changed source text, and is intended to add structured authoring and supporting material without creating another competing script.
This is meeting evidence, not a current-state product audit. Demonstrated controls, agreed direction and future requests are distinguished below.
01 / THE PROBLEM
One Script, Too Many Copies
Miguel describes writing lessons in Word and copying their text into Google Sheets. When English text changes without a corresponding localization update, the versions diverge. Without a reliable change list, he has to revisit translations across entire lessons.
Transcript 29:39–31:37 ↗Recording capture · 30:50 video time · Google Sheets source text and localized columns shown during the discussion.
Why this matters: The problem is not simply generating translations faster. It is knowing which source strings changed, what remains trustworthy, and which rows need attention.
02 / DEMONSTRATED WORKSPACE
Make Changed Source Text Visible
Miguel says the tool detects changes in the sheet and identifies out-of-sync content. Adam asks for an out-of-sync filter; the screen shows a Source changed filter alongside missing translations, reviewed-and-locked strings and formula/protected rows.
Transcript 31:41–33:19 ↗Recording capture · 33:10 video time · The Source changed filter is visible in the localization workspace.
Visible in the Recording
Lesson navigation, English source strings, target translations, review actions, localization actions, and tabs for proposals, batches, history, context and glossary.
Not Proven by a Screenshot
The frame proves these controls were displayed. It does not independently establish backend correctness, safe write behavior or successful localization across every sheet.
03 / AUTHORING DIRECTION
Projects → Lessons → Steps
Miguel proposes expanding the tool to create projects and lessons, add or reorder steps, and work with his Unity-side tool. Adam requests a shared glossary so the project, lesson and step vocabulary stays consistent.
Both explicitly confirm Google Sheets as the source of truth. Unity already loads lesson information from Sheets. Future authoring in the web interface should update that same source.
Supporting Data
Programmer notes can live in a database such as Supabase, associated with a row or step identifier. Images are requested, but their final storage location is left open; Adam says not to store them in GitHub.
Miguel describes Jonathan adding a step during an on-site machine walkthrough and dictating notes directly into it. This is a requested workflow, not a demonstrated transcription feature. The notes would help the author write the actual lesson text afterward.
Translation boundary: Only lesson text is to be localized—not internal notes. Miguel names Portuguese, Spanish and French as the current languages and asks for the ability to support other languages in the future.
Transcript 39:53–40:37 ↗Recording capture · 40:25 video time · The target-locale menu shows Portuguese · Brazil, Español · Latin America and Français · Canada.
Adam requests an Admin page for supported languages and service-connection health, including Google Sheets and other integrations. These are requirements raised in the meeting, not verified delivered features.
Keep Google Sheets canonical for Unity-facing content.
Surface changed-source rows rather than treating every translation as stale.
Keep internal notes distinct from localized lesson text.
Develop toward projects, lessons and editable steps.
Still Needs Implementation or Verification
Authoring and safe write-back behavior.
Stable row/step identity for database enrichment.
Image storage choice and upload workflow.
On-site audio capture and transcription.
Admin language controls and service-health checks.
Production deployment and end-to-end QA.
The broader call also covers repository separation and developer setup. These highlights deliberately omit account setup, credentials, private desktop material and unrelated conversation.
06 / SOURCE CONTEXT
Genuinely Related Meetings
DIRECT PRECURSOR DEMO
Following: John Deere Phase 2 Sprint Planning
2026-09-08 · 491 sentences fetched
Miguel demonstrates the Unity lesson voice-over tool and the Google Sheets localization workspace one day before the ForgeLessons walkthrough. The team confirms a single master source, discusses script editing and programmer notes, and calls for retranslating only changed English source text to prevent drift.
14:16–20:40 · Unity lesson voice-over generation and language previews
23:56–28:16 · Localization workspace demo; Google Sheets API, authoring plans and canonical source
28:25–29:50 · Changed-source tracking and machine-specific glossary consistency
Adam Kane and Scott LaForge discuss structured lesson-script automation: lessons with child steps, source transcripts, storyboard outputs and editable data. This is relevant design history, not proof of the same ForgeLessons application or a direct code predecessor.
14:03–15:26 · Lesson/step structure and storyboard output requirements
18:59–24:30 · Structured authoring data and source transcript associations
Searches covered product spelling variants and transcript terms including ForgeLesson, Forge Lessons, Forage lessons, localization workspace, localization tool, lesson tool, lesson content and lesson generation. Full transcripts were fetched for selected candidates. Routine lesson QA, generic lesson-builder sales talk, unrelated Miguel meetings and partner-only meetings are not used as product evidence.
Images are actual frames recovered from the Fireflies recording, not recreated UI and not original screenshot attachments. Each frame is cropped from the 1280 × 720 recording to 1030 × 550, removing browser chrome and participant tiles. No generative retouching was used. Capture times refer to the downloaded video; citations refer to the transcript, whose total duration differs from the video. Links open the source meeting; timestamps are reading guides, not verified deep-link seeking.
Recording duration measured with ffprobe: 7,035.043 seconds. Transcript duration reported by Fireflies: 118.050003 minutes. No synchronization correction has been assumed.
