mindboost. Internal 2026

Freedom

A modern way to create emotion-led learning with zero design constraints. Build anything. Ship everywhere.

github.com/mindboost-studio freedom.mindboost.dev
mindboost.
01 / 15
The Problem

Every authoring tool has a visual ceiling.

Storyline. Rise. Adapt. They all impose a template. The ceiling is the product.

01

Template prison

Every course looks like it was made by the same tool, because it was. Design freedom ends at the theme editor.

02

Web design is unreachable

Scroll animations, 3D components, shader effects, particle morphs — none of it is possible inside an authoring tool. The gap between Awwwards and Storyline is enormous.

03

No studio workflow

Authoring tools were built for one person. mindboost. works as a multi-agent studio. There's no git workflow, no component library, no separation of design and build.

04

The moat evaporates

When everyone uses the same tool, nobody has a point of difference. Premium pricing requires premium output. Authoring tools can't get there.

mindboost.
02 / 15
The Solution

Design freedom.
Zero SCORM compromise.

Freedom is a modern learning framework that utilises SCORM. Any interaction you can build for the web, you can build as a Freedom component, and it drops into any course, and works on any LMS, with full completion tracking.

The framework handles SCORM. The component handles the experience. Perfect for modern learners.

🎨

Any design, any component

We spot inspiration from web interactions. We then build it as a Freedom component. It drops into any course. That's the model.

📦

SCORM without compromise

Components know nothing about SCORM. The framework handles all tracking, suspend data, and LMS communication — transparently.

🎭

Every course, a different visual world

The same component looks completely different in every course. Owen defines the visual concept in Figma — colours, typography, motion, tone. The course theme is applied via CSS tokens. The component stays the same. The experience is entirely new.

🔌

Plug-and-play components

Each component is self-contained. Drop it in, configure it via JSON, done. No coupling to the course structure.

⚡

Modern build tooling

Vite, ES modules, no Grunt, no Backbone. Fast builds, hot reload, tree-shaking. A developer experience that doesn't feel like 2013.

🔀

Git-native studio workflow

Every course in source control. Component library grows with every project. Full diff, branch, review — the way code should be built.

mindboost.
03 / 15
Architecture

How it fits together

Three clean layers. The framework, the component, and the course. Each knows only what it needs to.

Course Definition

course.json

Sections, component references, completion rules, SCORM version. The single source of truth for a course.

↓
Framework Core

Shell + Router

Section layout, navigation, progress bar, completion overlay.

Framework Core

SCORM Layer

Pipwerks wrapper. Tracks completion. Saves suspend data. Speaks to any LMS.

Framework Core

Component Bus

postMessage protocol. lc:ready → lc:init → lc:progress → lc:complete.

↓
Component

[Any Component]

Sandboxed iframe. Knows nothing about SCORM.

Component

[Any Component]

Three.js hero, scroll scene, shader reveal — anything.

Component

[Any Component]

Branching scenario, hotspot, reflection prompt.

mindboost.
04 / 15
Component Library

The moat grows with every project.

Every project adds a component to the Freedom library. We find the inspiration. We build the component. It's production-tested, responsive, accessible, and SCORM-compliant from day one — ready to drop into the next course.

Same component. Different world.
Owen designs a visual concept in Figma for each course — colours, typography, motion, tone. That concept is applied as a course theme. Same code. Entirely different experience.
# Install the CLI
npm install -g @mindboost/freedom-cli

# Create a new course
mb create baxterstoreys-neurodiversity

# Build + package for LMS
mb package --scorm 1.2
Component Catalogue
🃏

Card Carousel

3D arc fan — key facts, stats, learning points

🎭

Branching Scenario

Decision-based narrative, emotion-led choices

🔍

Hotspot Reveal

Tap-to-discover on image or illustration

📊

Data Story

Animated stats and charts that build on scroll

🪞

Reflection Prompt

Timed journalling with save and revisit

🎬

Video Scene

Fullscreen video with chapter markers and interaction locks

✨

Scroll Hero

GSAP scroll-driven cinematic section intro

🌐

Particle Morph

Three.js particle system — full Awwwards tier

➕

+ Any web interaction

If it runs in a browser, it's a valid component

mindboost.
05 / 15
Why Freedom

Six reasons this changes everything

01

No visual ceiling

If it can be designed, it can be a Freedom component. The design ambition is limited only by our creativity and output — not the tool.

02

Real competitive moat

A growing library of production-tested, accessible, responsive, SCORM-compliant components. Built on real client work. No competitor can replicate this in two years.

03

Studio-grade workflow

Git-native. Component-isolated. JSON-configured. Built for a multi-agent team, not a solo instructional designer with a drag-and-drop tool.

04

Client review built in

Clients get a token-protected preview link. They pin comments directly on words, assets, and components. Issues are tracked, resolved, and closed before a single SCORM zip is packaged.

05

Fast course builds

mb create → mb dev → mb package. A new course scaffolds in seconds. Component drops into JSON in minutes. No GUI, no waiting.

06

Localisation as standard

Course content is a locale map from day one. Export XLIFF. Translate. Import. Package once for all languages — or as a separate SCORM per locale. RTL included, not retrofitted.

mindboost.
06 / 15
Define · Design · Develop · Deliver

From design doc to deployed SCORM

📝

Design Doc & Script

Learning objectives, content structure and script defined

Lily Define
🎨

Design

Visual design in Figma and Claude Design

Owen Design
⚙️

Component Build

Freedom component built to design spec in Claude Code

Stu Develop
📋

Course Build

Components wired, script uploaded, assets added, theme applied in Claude Cowork

Everyone Develop
🧪

QA & Testing

Testing script created, SCORM validation, multi-device & accessibility testing in Claude Cowork

Everyone Develop
💬

Client Review

Pinned comments on words, assets, components via review link

Client Deliver
🚀

Package + Deliver

mb package → SCORM zip → client LMS upload

Stu + Caleb Deliver
New Component
Owen spots and designs it → Stu builds it → everyone tests it → available in every course
mindboost.
07 / 15
Content & Asset Pipeline

Lily writes.
Owen designs.
Two commands assemble.

Lily never touches JSON. Owen never manually wires assets. Course build is two CLI commands — copy and assets land in exactly the right component fields automatically.

# Lily's copy → course.json
mb content-import content-template.docx

# Owen's assets → course.json
mb asset-import design-handoff/ --manifest asset-manifest.json
Course fully assembled. No manual JSON editing. mb dev → review in browser.
How it works
📝 Lily — Content Template

mb content-template generates a Word doc from course.json. Every field is labelled — card stats, body copy, CTA text, reflection prompts. Lily fills in the boxes. The importer maps every word back to the correct component field.

🎨 Owen — Asset Manifest

Owen exports assets from Figma and fills an asset-manifest.json — a simple file mapping each image, SVG, Lottie, or font to its exact component and field. The importer wires everything and writes the client theme CSS tokens automatically.

🔁 Iteration is instant

Copy needs rework? Lily edits the Word doc. Run mb content-import again. New assets from Owen? Run mb asset-import again. No manual JSON. No hunting for the right field.

✅ Word doc = client sign-off

The content template is the audit trail. Send it to the client for copy approval before a single component is rendered. Signed-off copy goes straight into the course. No transcription errors.

mindboost.
08 / 15
Localisation

One course.
Every language.

Develop once in en-GB. Translate the strings file. Package as a single multilingual SCORM with a language picker — or separate SCORM per language. Components never know which language they're running in.

# Export for translation
mb export-strings --output strings.xliff
mb import-strings fr.xliff

# Single SCORM with picker · or separate per language
mb package --lang all
mb package --lang en-GB,fr,de,ar
Single SCORM
Language picker on launch. One upload. One completion record.
Multi SCORM
Separate zip per language. Standard LMS enrolment model.
How it works
📄 Industry-standard XLIFF

Works with SDL Trados, memoQ, Phrase, DeepL Pro. Send the file. Get it back. Import it. No custom format.

🧩 Components are locale-agnostic

Shell resolves locale and passes already-translated strings via lc:init. Components receive plain strings. Zero locale logic inside a component.

↔️ RTL supported

Shell injects dir="rtl" for Arabic, Hebrew, Persian. Components mirror layout via CSS selectors. Built in from day one.

🖼️ Localised assets

Owen flags locale-specific assets in the manifest. Base asset used as fallback — only provide variants where the visual actually differs.

mindboost.
09 / 15
Deliver · Client Review

Build fast.
Show the client.
Amend before you ship.

A shareable review link gives the client a live preview of the course. They click anywhere — on a word, an asset, a button — and leave a pinned comment at that exact point. Like Vimeo Review, but for learning.

# Launch review preview
mb serve --review

# Share with client (token-protected, no login)
mb review-link --expires 7d
Closed loop
Review comment → one click → issue in tracker → assigned to team → resolved → comment auto-marked done. Nothing falls through the cracks.
Two tools. One workflow.
💬 Client Review Tool review.mindboost.dev

Client gets a token link. No login. Course renders in preview mode. Click any word, asset, or component — a numbered pin drops at that exact position. Leave a comment. mindboost. team sees everything in real time.

🐛 Issue Tracker ops.mindboost.dev/issues

Lightweight Trac-style tracker. Issues have ID, status, priority, assignee, course, component, source. Filter by course or team member. One click from a review comment creates an issue. Issue resolved → comment auto-closed.

📋 Review flow
1 Send review link after QA passes
2 Client pins comments directly on course content
3 Triage comments → create issues → assign to team
4 Team resolves → issues close → client sees green ticks on their pins
5 All comments resolved → SCORM packaged and delivered
mindboost.
10 / 15
Commercial Potential

The component library is the business.

Open-source frameworks win on community. Premium component libraries win on quality. Freedom can be both — the framework builds trust; the components generate revenue.

Every course mindboost. builds on Freedom is a live proof-of-concept. That's a sales asset no competitor can replicate.

Option A — Recommended

Open core + Premium components

Free framework, paid component packs. Studios pay for Awwwards-tier components they can't build themselves.

Option B

Studio licences

Monthly access to the full component library. Recurring revenue, low support overhead.

Option C

Enterprise white-label

In-house L&D teams licence Freedom with the mindboost. library. Higher price, fewer customers — fits the existing ICP.

Option D — Long game

SaaS authoring layer

A GUI on top of course.json. The authoring tool for studios who care about design. Highest ceiling, most build effort.

mindboost.
11 / 15
What happens next

Build it for ourselves first.
Then sell it to the world.

Freedom starts as the tool that lets mindboost. build learning no authoring tool can match. That proof-of-concept becomes the product.

1

Green-light Phase 1

Amanda briefs Stu on the Freedom infrastructure build. Repo created at mindboost-studio/freedom.

2

Confirm the target course

BaxterStorey Neurodiversity as Phase 2 proof-of-concept — first real course built on Freedom.

3

Brief Owen

Owen designs the full visual world for the Neurodiversity course in Figma.

mindboost.
12 / 15
Honest Answers

Is this really
achievable?

Yes. Every layer is built on proven patterns. postMessage, pipwerks SCORM, Vite, sandboxed iframes — all running in production at scale today. The architecture isn't experimental. The ambition is.

Three non-negotiables on every brief
📱 Mobile-first — 375px upward, always
♿ Accessibility in the manifest — screenReaderText, reducedMotionFallback, keyboardPath
⚡ Performance tier — light / medium / heavy; heavy = auto lazy-load
Frequently Asked
Can any Awwwards design become a component?
Yes — with one filter. Every component needs a mobile strategy and reduced-motion fallback. Owen designs both from the start. A particle morph at 1440px needs rethinking at 375px, not just scaling.
Will it work on corporate LMS platforms?
SCORM 1.2 and 2004 both supported. Tested on the client's actual LMS before delivery — not just SCORM Cloud. SCORM Cloud ≠ Moodle ≠ Cornerstone.
How long does a new component take to build?
Simple (text, hotspot): 2–3 days. Medium (carousel, branching): 1–2 weeks. Complex (3D, shaders): 2–4 weeks. Production-tested, accessible, and mobile-first before it enters the library.
How does a client review the course before delivery?
They get a token-protected preview link — no login needed. They click any word, asset, or component and leave a pinned comment. Comments feed directly into the issue tracker. Every pin gets resolved before packaging.
What happens when Freedom components become outdated?
Components are versioned in the library. A course pins to a specific component version — it never breaks when the library updates. Courses can opt in to upgrades explicitly, just like an npm dependency.
mindboost.
13 / 15
Now

Phase 1
Infrastructure

3–4 weeks · Stu
✓

Core framework — section-slot layout, component bus, SCORM layer

✓

mb CLI — create, dev, build, package commands

✓

Card Carousel ported as first Freedom component

✓

Theme system — CSS token set, client overrides

✓

GitHub — private repo at mindboost-studio/freedom

✓

Docs site — freedom.mindboost.dev, Cloudflare Pages

✓

SCORM Cloud validated — example course passes

A developer can clone, create a course, and ship a valid SCORM zip in 15 minutes.
Next

Phase 2
First Real Course

6–8 weeks · Full team
→

BaxterStorey Neurodiversity — first client course built on Freedom

→

Component 2 + 3 — branching scenario + hotspot reveal

→

LXD integration — Lily's content structure flows into course.json

→

Client LMS test — validated on BaxterStorey's actual LMS

→

Accessibility audit — full WAI-AA pass on all components

→

Client Review Tool — mb serve --review; pinned comments on live preview

→

Issue Tracker — ops.mindboost.dev/issues; comments → issues → resolved closed loop

A real client course, delivered on Freedom, signed off by Caleb and the client.
Future

Phase 3
Commercialise

12+ months
→

Open-source the core — MIT licence, public repo, community builds

→

Premium component packs — 3D, motion, assessment — sold to other studios

→

Studio licences — other agencies pay to access the component library

→

Enterprise tier — white-label for in-house L&D teams (your existing ICP)

→

Authoring layer — optional GUI on top of course.json for non-technical users

Freedom becomes a product. The component library is the moat. mindboost. is the studio behind it.
mindboost.
14 / 15
mindboost. · Freedom Framework

mindboost. build for the learner.
Others build for the tool.

Other authoring tools gave us structure. Freedom gives us possibilities.

∞
Component designs
1
Framework to build them
0
Authoring tool constraints
mindboost.
mindboost.
15 / 15