A look inside Ranger of the Realms
The Making
of an Episode
I built a system to carry each episode through production. It gathers the lore, drafts the script, generates the images, and puts it all together. At every step, it brings the choices back to me: what to make, how to tell it, which images are right, what is ready to publish. Here is how it works.
Making things with AI is a charged subject right now, and more so when it touches a writer as loved as Tolkien. I think that is fair. This channel began as a way to bring together two things I care about: Tolkien's world, and the craft of building systems. I use these tools openly, and I am still learning where they help and where the work has to be mine. What follows is honestly how an episode gets made.
It is just me, running the channel with a system I keep building and refining as I go. Two things have held steady the whole time. I make the decisions, about what to cover and whether a piece is good enough to publish. And the system keeps improving, because every episode teaches it something I fold back in.
What follows is the path an idea takes here, from a passing interest to a finished episode.
Seven steps from a spark of interest to a published episode. The system runs each one; I review at every step, and nothing goes out until I approve it. The node that glows is mine. Every finished episode feeds back into the next.
Stills from recent episodes.
From idea to episode
The path an episode takes
The same shape repeats at every step. The system does the production work and lays a decision in front of me.
Where it begins
It usually starts with my own curiosity. The deeper I get into Tolkien, the more threads I want to pull, and those are what fill the backlog. The system adds to it: each week it scans what people are discussing across YouTube, Reddit, and the web, and surfaces ideas I might have missed. More data points, not marching orders.
I decide what is genuinely worth making, and often it is simply something I want to understand better.
The angle
A researcher goes back to the primary sources, the Silmarillion, The Lord of the Rings, Unfinished Tales, the History of Middle-earth, the Letters, and returns with quotes, a timeline, and the themes, each tied to where it came from.
I decide the angle: the one question the episode is really about, and the line it opens on.
The script
The script is drafted in four passes so it does not circle back on itself, then read again for the habits writers fall into. The system flags them. It does not quietly rewrite them.
I decide what stays, what is cut, and what gets written again.
The look
For every scene the system writes a prompt and generates the image. To keep the world consistent, each recurring subject is pinned to a locked reference I approved, and every image is checked against a visual canon I keep.
I decide on each one. I look at every image, count the figures when a scene calls for a set number, watch for a hand with too many fingers, and send back the ones that miss.
Voice and assembly
The script is read aloud in one steady voice, mixed with music, and cut together so each image lands on the words it belongs to.
I decide whether the timing and the tone are right, or send a section back.
The final say
The system proposes titles and thumbnails, each with a short case for why it might work.
I decide. I pick the title and the thumbnail, then watch the finished episode start to finish and make the last call: publish it, send it back, or scrap it. Nothing goes out on its own.
Where I make the calls
The Production Hub
All of those decisions come together in one place: a control room I built. It does not act on its own. It gathers everything waiting on me, lays out the options, and waits.
Thumbnail · 3 variants · click one to choose
ChosenThe approval view. The video and its chapters, the thumbnails the system drafted, and one button. I watch, I choose, I approve. Or I send it back.
The same room holds the images waiting for review, the schedule to arrange, and the comments readers have left, each one already paired with a reply drafted in my voice for me to edit, send, or skip. When a reader catches a detail, I go back to the script before I answer. The system surfaces the decision. It never makes it for me.
At a glance
Channel pulse · week ending 2026-05-23
The home view. How the channel is doing the moment I open it, drawn from its own analytics.
Consistency
The same world, every time
A channel like this lives or dies on consistency. The same Gandalf has to look like the same Gandalf in his fifth appearance and his fiftieth.
So before the system illustrates anyone, it reaches for a reference. I have built a library of 140+ locked reference images, a set for every recurring character, being, place, object, and creature. When a scene calls for the One Ring, the Balrog, or the white city of Minas Tirith, that reference is attached to the generation. It fixes who or what the subject is.
On top of the references sits a set of rules I keep, most of them learned the hard way. Elves are beardless. A council of the Valar shows exactly fourteen. The Silmarils sit set into Morgoth's iron crown, and never float above it. A Balrog carries its horns. When an image breaks a rule, I write down why, and the rule gets sharper so it cannot happen again.
It keeps getting better
Every episode teaches the next one
The system that made the last episode is not the one that will make the next.
It catches itself repeating
Read back across enough episodes and the patterns show. Every script was opening the same way. The writing kept reaching for the same reflective beat, ten times in one episode. Once I see it, the system gets fresh patterns to rotate through and a cap on the old ones.
Mistakes become rules
The Silmarils drawn floating above the crown. A Balrog that came out looking like a goat. Each one I catch gets written down with the reason it was wrong, and that note hardens into a rule the next batch has to follow.
I read it back, on purpose
Once a month I go back over the last ten episodes and decide what to sharpen. The system's own instructions get edited. What worked is kept, what did not is cut.
Small corrections, each week. Constant improvement.
The rest of it
Around the episodes
An atlas of Arda
Alongside the episodes I have been building an atlas: hand-styled, interactive maps of Middle-earth across its ages, from the Years of the Lamps to the end of the Third Age.
Explore the atlas →
This website
The site you are reading builds and publishes itself from the same records that run everything else. New episodes, notes, and pages appear without anyone touching HTML.
Under the hood
The machinery
Not the point of the page, but for anyone curious about the depth of it. The system has grown into a fair amount of deliberate engineering.
And the tools it runs on
- Claude Codeorchestrates the whole pipeline
- Geminigenerates the illustrations
- ElevenLabsreads the narration aloud
- Whispertimes the words to the picture
- FFmpegassembles and encodes the episode
- YouTube APIuploads, schedules, and tracks
- Grok and Redditsurface what people are discussing
- Cloudflareserves this site
The tools will keep changing. What starts every episode stays the same: something about this world I want to understand.