How Time-Weaver Was Built
One person. AI as the builder. Six thousand years.
I'm not a programmer. I'm a sales guy who wanted to see history laid out on one thread.
I wanted a timeline where you could watch the Book of Mormon unfold next to ancient Greece, see the Crusades against the rise of the Mongols, and zoom from 4000 BC down to a single week in AD 33. Nothing out there did it the way I pictured it. So I built it. Or more precisely, I described it, and AI built it with me.
The process
Every piece of this site came out of a conversation. I described what I wanted in plain English. The AI wrote the code, I looked at the result, and we went back and forth until it matched the picture in my head. The parchment timeline, the zoom that goes from millennia to months, the overlay system, the event research and writing. All of it.
When something broke, I described the symptom and the AI found the cause. When the history was wrong, we audited it: three independent review passes checked dates, removed duplicates, and tightened more than a thousand event descriptions.
The whole thing runs on a simple web host. No team. No budget. Evenings and weekends.
Why it matters
Five years ago this site would have taken a development team months and cost tens of thousands of dollars. I built it in conversations, the same way you'd describe a kitchen remodel to a contractor.
If a non-technical sales guy can build this, what could you build?
That question became a second project. I now help other non-technical people learn to work with AI the same way at Achievementoring.com. Not theory. The exact process that built the site you're looking at.
About the timeline itself
Events span from the dawn of recorded history to the present day, organized into 49 overlays you can mix freely: world regions, military history, political history, religious history, and scripture timelines. Every event was researched and written with AI assistance, then audited for accuracy. Found an error anyway? History is big. I'd genuinely like to know.