ai/
The CMS Already Knew How

Andrei Bespamiatnov
Author
The slow path was the retyping
Course content does not start in the CMS. It starts in spreadsheets, outlines, and the heads of people who already know the material. Then someone retypes it.
Every question, term, category, and reference is entered by hand, then linked by hand. The links are the expensive part. The CMS stores ids, so a person looks up each bank, each category, each term, and attaches it one row at a time. Onboarding a course this way is measured in months.
The system was not missing. The typing was.
What changed today
An author can hand that slice to an assistant.
The assistant signs in as that author, stays inside one update batch, and creates the unpublished rows through the screens the CMS already has. Products, courses, banks, questions, terms. When the slice is saved, a person opens that batch in the CMS and publishes it there. Learners see nothing until a person says so.
That boundary matters. The assistant prepares the content. A person still decides that it is ready.
It was a small move
We did not build a second CMS.
The screens were already there. The saves were already there. The publish step was already there, and it still belongs to a person. The new part is that the person who has the content can drive those screens through an assistant, instead of retyping them.
That is why it landed in a day, not in a program. The hard months were never a missing platform. They were the distance between the person who knows the course and the forms that record it.
The people who own the content felt it first
Ingestion is the gate in front of every new course. If an author can bring a course in as a conversation instead of a season of retyping, onboarding gets shorter by months, not by a nicer form.
The business felt that the same day. The people who live with the retyping asked for the next course before the proof of concept had a second name. The same path can later carry the admin work that sits around a course. That is later. Today is content.
What I am proud of
A proof of concept, used on the real CMS, by the people who own the content. I am proud of the work, and proud that the business recognized it the same day.
We did not invent a new place to put courses. We let the people who have them use the place we already had.