Welcome!

When to Use the Advanced Path

This path is not offered as a general option. Before the Creation Tools existed, a video project was built entirely by hand: a folder structure in a GitHub repository, a toc.yml file, Markdown slide content, and optional custom styling. It still works, but only as a special case that the Lupo team sets up for you on request. If nobody has set one up for you, the pages in this section don't apply — use the Creation Tools and the course builder instead.

TL;DR; The advanced path is kept for the hand-authored projects that already exist, and for the rare case where the Lupo team agrees a new one is the right fit. It isn't a more powerful hidden mode — it's the older mechanism the Creation Tools were built on top of.

Before you start

Nothing — this page is just the map of what the advanced section covers. Everything in it assumes a project the Lupo team has already provisioned for you; you can't create one yourself from inside the product.

When it's the right fit

You already have a project structured this way and are maintaining or extending it, rather than starting fresh.
Your team keeps course source under version control and the Lupo team has agreed to set up a repository-backed project for you — a toc.yml and a folder of Markdown files behave like ordinary text files.

When it isn't

If you're starting a new course from nothing, the Creation Tools turn a PowerPoint into a narrated video, and the course builder covers modules, lessons, activities, quizzes and SCORM — without writing a single line of YAML or Markdown. Nothing here is faster than that, and nothing here is something you can switch on for yourself.

What this section covers

toc.yml reference — every key the file accepts, its type, its default, and what it does.
Authoring in Markdown — the syntax a hand-authored project's slide content is written in.
Styling and themes — customizing how a hand-authored project looks.

Where to go next

toc.yml reference