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
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.

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.

A Real Scenario

Imagine.

The Spark

Your designer spots a stunning web interaction. Your learning designer sees exactly how it could bring a story to life in a piece of digital learning. An initial concept is built as part of the design document, and it looks incredible.

The Conversation

You float the idea with your client. They love it. Then comes the question: "It needs to be SCORM conformant and work on our LMS." The idea is sound. The experience works. The client is bought in.

The Question

What now?

Freedom handles it

Components track completion individually. Pages track completion. The course tracks completion, just like any authoring tool. Responsive from mobile to widescreen. AA accessible. Themed to the designer's original vision. SCORM conformant from day one.

The Difference

A unique interaction, previously only possible on a website, is now part of a digital learning course. No compromise. No workarounds. No "we can't do that in Storyline."

The Outcome
→ The production team are proud of what they shipped
→ The client is amazed
→ Learners actually engage with the story
→ The LMS is happy, everything is reportable
Validation

The problem is real.
The client is ready.

"

We know exactly what we want our learning to look and feel like. The authoring tools just can't get there. mindboost. understands that gap better than anyone, and Freedom is the answer we've been waiting for.

Z

Zoe Yard

L&D Manager, BaxterStorey

Named Client

BaxterStorey, UK hospitality group, 35,000+ employees, is actively supportive of a co-created Freedom course as Phase 2 validation.

The Ceiling Moment

BaxterStorey briefed a visually ambitious course. The interaction design was signed off. Storyline couldn't build it. The brief became the proof of concept for Freedom.

Pipeline

Two further conversations in progress with enterprise L&D teams exploring framework licensing. Details available on request.

Why Now

The tools haven't changed.
The team has.

Storyline launched in 2012. Adapt in 2013. Rise in 2017. Evolve and Kwantic followed. The design ceiling has been there for over a decade, and every new entrant has inherited it. What's changed is what a small, expert studio can now build and maintain.

AI-assisted development, Claude Code, multi-agent workflows, generative asset pipelines, means a four-person team can now design, build, test, and maintain a production-grade learning framework that would have required a VC-backed engineering team five years ago. The window to build Freedom is now.

Then

Building a custom SCORM framework required a full engineering team, years of development, and significant capital. Only large vendors could attempt it.

Now

Claude Code architects components. Vite handles the build pipeline. A multi-agent studio ships in days what used to take months. The barrier to entry has collapsed, for us first.

The Opportunity

The market hasn't caught up. Enterprise L&D is still buying Storyline licences. The premium alternative doesn't exist yet. Freedom can be that alternative, built now, before the window closes.

Competitor Landscape

Every tool hits the same ceiling.

Feature Storyline Rise Adapt Evolve Kwantic Freedom
Custom visual design ⚠️
Template only
 ❌
Fixed blocks
 ⚠️
Theme limited
 ⚠️
Block-based
 ⚠️
AI content only
 ✅
No ceiling
3D / WebGL / Shaders ❌ ❌ ❌ ❌ ❌ ✅
Git-native workflow ❌ ❌ ✅
Partial
 ❌ ❌ ✅
AI-assisted build ❌ ❌ ❌ ❌ ⚠️
Content only
 ✅
SCORM 1.2 + 2004 ✅ ✅ ✅ ✅ ✅ ✅
Growing component moat ❌ ❌ ❌ ❌ ❌ ✅
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.

Architecture

How it fits together

Seven layers, four kinds — the spine every element inherits, the limbs that plug in, the mirror that reviews it, and the seal that secures it. All driven by one course.json.

Course Definition

course.json

Menu, pages, components, extensions, theme, surfaces, localisation, completion rules, SCORM version. Single source of truth.

The spine · inherited by every element
Framework

Shell · Router · SCORM

Menu, pages, nav bar. SCORM 1.2 / 2004 / xAPI to any LMS. Full design surface, no locked templates.

Tracking

Reactive core

event → state → rules → effect. Declarative when→then rules over dotted state. The only layer that talks to the LMS.

Design

Tokens · surfaces · motion

The component design system. Themeable to any brand — colour, image, video, animation on any surface.

The limbs · plug into the spine
Component

[Any Component]

A Web Component in the content flow — one learning interaction. Knows nothing about SCORM, the shell, or other components.

Extension

[Any Extension]

Enhances a course — assessment, bookmarking, hints, glossary. Plugs into the spine; never content itself.

The mirror
Review

On the running course

Pinned comments anchored to elements, not Word docs. The QA gates, exercised on the live build.

The seal · wraps & secures every layer
Security & Assurance

Static · no PII · no phone-home · runs in your LMS sandbox. Self-hosted & CSP-locked, signed builds, CI scanning, SBOM. Cyber Essentials today → ISO 27001 next — the evidence a corporate IT review needs.

Phase 1, Component Library

The moat grows
with every project.

Every project adds a component to Freedom's library. Phase 1 rebuilds proven components from the Adapt contrib library, cgkineo, and Nacho Cinalli's catalogue, production-tested, accessible, and SCORM-compliant from day one.

Same component. Different world.
Owen designs a visual concept in Figma, colours, typography, motion, tone. Same code. Entirely different experience.
# Create a new course
mb create baxterstoreys-neurodiversity
# Build + package for LMS
mb package --scorm 1.2
Phase 1, Example Components
Rebuilt on Freedom architecture from proven Adapt ecosystems
🃏

Card Carousel

3D arc fan, key facts & stats

📖

Narrative

Stepped image + text panels

🪗

Accordion

Expandable sections & FAQs

🔍

Hotspot

Tap-to-discover on image

✅

MCQ / Matching

Core question types, themed

📶

Steps Graphic

Timelines & workflows

👆

Swiper Slider

Touch-first swipeable cards

➕

Phase 2 & beyond

Branching, GSAP, Media Sync

The Team

Built by people who've lived the problem.

C

Caleb Foster

Founder

25+ years in L&D. Former Head of Learning Technology at Compass Group and Whitbread (FTSE 100). LPI Certified Performance Consultant. Founded mindboost. to solve the problems he lived inside enterprise learning.

S

Stuart Nicholls

Lead Developer

Senior eLearning developer with over two decades of experience at Kineo, MakeReal, and mindboost. Deep expertise in SCORM, Adapt framework internals, and modern JavaScript tooling.

O

Owen Worts

Creative Director

15+ years in UX/UI and digital learning design. Former Senior Solutions Art Director at Kineo. BA Digital Media, University of Brighton. Designs the visual world Freedom makes possible.

L

Lily Winslow

Learning Experience Designer

10+ years in instructional design and LMS architecture. Formerly Lead Learning Designer at Kineo. Designs the content pipeline and learning architecture Freedom courses are built on.

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
We spot and design it → we build it → everyone tests it → available in every course
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.

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.

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
Risk & Mitigation

We've thought about what could go wrong.

Every R&D project carries uncertainty. Freedom is built on proven architectural patterns, Web Components, pipwerks SCORM, Vite, which reduces technical risk significantly. The risks that remain are manageable, and we have planned for them.

LMS compatibility

Validate on client LMS before delivery, not just SCORM Cloud. SCORM 1.2 as baseline, the most universally supported standard.

Component build time

AI-assisted development compresses build cycles. Conservative timelines built into the budget to absorb overruns.

AI tooling cost variance

Tooling budget modelled at upper range to avoid surprises during heavy development phases.

Market adoption

BaxterStorey validation reduces adoption risk. Freedom is built on real client briefs, not speculative features. The library compounds regardless of pace.

Accessibility compliance

WAI-AA is a Phase 1 non-negotiable. Every component ships with screenReaderText, reducedMotionFallback, and keyboardPath defined from day one.

Key person dependency

All components are git-native, fully documented, and JSON-configured. Architecture is designed to be transferable, not locked to any individual.

Our process. Our standards. Our non-negotiables.

How We Build

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

Three non-negotiables on every brief
📱 Mobile-first, 320px upward, always
♿ Accessibility in the manifest, screenReaderText, reducedMotionFallback, keyboardPath
⚡ Performance tier, light / medium / heavy; heavy = auto lazy-load
Frequently Asked
Component scope
Any design that can be built in pure CSS/JS ships as a component. We scope complexity at the design stage, not the build stage.
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.
Why not just use Adapt?
Adapt is a great framework, Freedom was inspired by it. But Adapt has a visual ceiling. The menu is a template. Blocks are fixed units. You can push it hard and still feel the walls. Freedom has no walls. That's the only difference that matters.
Who maintains the components?
mindboost. owns and maintains the library. Every component built on a client project enters the library and is available on the next. The library grows with every course. That's the compounding advantage.
Now

Phase 1
Infrastructure

Infrastructure

✓

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

✓

Course shell, the menu is a launchpad, not a template. Home page, navigation & course pages are full design surfaces, Owen-designed, fully custom, as visually ambitious as any component.

✓

Background layer system, images, video, animation or canvas backgrounds on the shell, any page, any component, or any region. Applied anywhere. Inherited or overridden. No constraints.

✓

Theme system, a simple design system every layer hooks into: shell, menu, pages, components and extensions all inherit client colours, typography, motion and spacing from a single token file. One override. Infinite looks.

✓

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

✓

Accessibility audit, full WAI-AA pass on all components

✓

Multi-device, mobile-first 320px→desktop, touch targets, performance tiers

✓

SCORM 1.2 + 2004 validated, example course passes on SCORM Cloud

Tooling

✓

mb CLI, create, dev, build, package commands

Components

✓

Component library, first learning components built on Freedom (in-flow Web Components, light DOM, in-process events)

✓

Extension framework, 13 battle-tested shell-level extensions: Assessment, Bookmarking, Close, Hint, Home, Language Picker, Navigation Logo, Page Incomplete Prompt, Page Level Progress, Resources, Spoor, Tutor. Outside the content flow. Fully themeable.

✓

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

✓

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

Next

Phase 2
First Real Course

→

Client course, first client course built on Freedom

→

Client LMS test, validated on client's actual LMS

→

Additional components & extensions, expanded library plus new extensions driven by client requirements

→

xAPI support, mb package --xapi for LRS-enabled clients

→

Translation & localisation, XLIFF workflow, RTL support, multi-language SCORM output

→

Additional enhancements & extensions, framework improvements driven by real course build

What Success Looks Like

Month 6. What exists.

Stable Framework

A production-ready framework to build any course from, section-slot layout, component bus, SCORM layer, shell, and full CLI tooling.Phase 1 complete → first client course delivered → commercial viability proven

Learning Components

A Phase 1 component library, card carousel, narrative, hotspot, MCQ, accordion, steps graphic, swiper slider, production-tested and accessible.

Extensions & Translation

13 shell-level extensions shipped. XLIFF localisation workflow live, export, translate, import, package. RTL supported from day one.

mb

CLI Shipped

create · dev · package · content-import · asset-import. A new course scaffolds in seconds. Components wire in minutes. No GUI, no waiting.

£0

Licence Dependency

No Storyline. No Rise. No per-seat licence. Freedom is owned infrastructure, the cost base improves with every course we ship.

∞

The Moat

Every component built for a client is available on the next brief. The library compounds. No competitor can replicate 6 months of production-tested work overnight.

mindboost. · Freedom Framework

We build for the learner.
Everyone else builds for the tool.

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

∞
Component designs
1
Framework to rule them
0
Design constraints
mindboost.
1 / 20
⤓ PDF