RapidFire Content Engine
The editor LearnDash never had.
LearnDash supplies the tree and the completion rules, then leaves the content to whichever editor the site has — which is why so many LearnDash sites are Elementor sites. The Content Engine is the part that fills the tree.
What it adds
Everything that is about a
course rather than a document.
It sits on top of the editor and runs over a provider interface. LearnDash is the first implementation.
The course tree, with outline numbers
Product, module, tree, step — one workspace with no page reload between them. The tree paints without loading a body, because reading ease is cached in post meta and the checker is cached by content hash.
Proposed beside Live, paragraph by paragraph
Paragraphs are matched by stable block id, never by ordinal, so a proposal stays aligned even when the shape changes. Accept one paragraph or all of them. Publish takes only what changed, and writes one revision per touched step.
Whole-module checks
Score, check and save an entire module in one pass. Every button states its scope — Check this step, Check all 15 steps, Save step, Save every changed step — so nothing wider ever happens by accident.
Import a module from a document
Drop in a marked-up Word or PDF strawman. RapidFire reads the breakers, shows you the parsed tree with word counts and warnings, and creates the lessons, topics and quizzes as drafts only after you approve the review.
Import
Your strawman is
already the outline.
Most courses start life in Word. Mark the breakers, drop the file in, and review what RapidFire read before anything is written.
| Marker | What it does |
|---|---|
[MODULE] | Module title. One per document — becomes the course. |
[META] | Optional key/value pairs: audience, voice, reading-ease target. |
[LESSON] | Starts lesson 1, 2, 3 … Becomes a LearnDash lesson post. |
[TOPIC] | Belongs to the lesson above it. Becomes a topic post. |
[QUIZ] | Belongs to the lesson above it. Becomes a quiz shell. |
[SUMMARY] | One line, used as the item excerpt. |
[OBJECTIVES] | Followed by one objective per line or bullet. |
[END] | Optional. Anything after it is ignored. |
[MODULE] Laboratory Safety Essentials[META] audience: Key Stage 4[LESSON] Working safely in the lab[SUMMARY] Why lab rules exist.Every practical begins with arisk assessment.[TOPIC] Personal protective equipmentGoggles, lab coat and gloves.[QUIZ] Lesson 1 check[END]— parsed ————————————————✓ 2 lessons ✓ 4 topics ✓ 1 quiz! 1 to check (no body text)Nothing is written until you approve.
Heading 1 / 2 / 3 styles work too, if you prefer styles to markers. Bold, italic, links, lists and tables are kept. An item with no body text imports as an empty draft and is flagged.
Build
Stage 6Build a course from a brief,
a framework and your sources.
Instructional design is the constraint, not the model. The outline is shaped by a framework, and it refuses shapes that do not hold together.
Alignment by construction
Every objective maps to an assessment and to the activities that teach it. The outline refuses a lesson with no objective, and an objective with no assessment.
Scaffold by default
A model asked for a concentration or a statutory duty invents confident wrong ones, so the default output is a scaffold. Source-derived steps come first and cite their source.
Rollback as a unit
Forty posts are created in one operation and stamped, so the whole build can be removed in one. A build that goes wrong does not leave debris in your course.
Frameworks: CLEAPSS, ADDIE, Bloom and Gagné at Stage 6, with Backward Design, Merrill's First Principles, SAM and Kirkpatrick to follow. The framework shapes the outline; it does not write the content.
The category
Completion is a proxy.
A grade is a proxy.
Performance is the thing itself.
The corporate system asks whether a person can do the job safely. The academic system asks whether a person has learned something. Both settle for a proxy, and the proxy is exactly what fails at the boundary between them.
Both track the course. Neither tracks the learner.
In the corporate world, tracking is whatever the content package chose to report: if the package reports only completed, that is all there will ever be. In the academic world, tracking is the gradebook — an administrative record of marks that cannot say what was demonstrated and cannot be recomputed.
That is why a person's record restarts every time their life changes category.
In RapidFire, the evidence model is the content model.
Every active assessment block declares what evidence it produces as a condition of existing, so content cannot be authored without its evidence being authored with it. How far a signal may be trusted is computed from how the block is configured, not claimed by its author.
Passive content emits nothing at all, deliberately. Reading a page is not instrumented. This is a performance record, not surveillance.
There is no "and then we added analytics." The thing that produces the evidence is the thing the author was already writing.
Stated honestly, in the present tense. The architecture is specified in full. The emitter, the evidence ledger and the assessment block set are not yet built. Interactive tiles and xAPI-shaped statements arrive at Stage 8. The claim above is a claim about the design, and about what the product is being built to do.
Host independence
The engine knows no LMS,
and the editor knows no host.
The editor core is handed a five-part host interface. The Content Engine is handed a provider. WordPress and LearnDash are one implementation of each.
WordPress and LearnDash, today
Content lives in post_content as HTML. The tree, the steps and the completion rules stay LearnDash's.
SCORM and LTI
PlannedPackage a course as SCORM 1.2 or 2004 and launch it over LTI 1.3. Clean stored HTML is already the input those importers need.
Why this matters commercially. Content authored in a builder's JSON does not move platforms. Content stored as HTML with a small documented dialect moves unchanged. What survives a platform change also survives a theme change, a builder change and a plugin's deactivation.
The engine that fills the tree.
The Content Engine requires the Editor. One price per site, per year.