DocC content types: are interactive tutorials supported?

[mobilemind]

Are interactive tutorials supported? See https://www.swift.org/documentation/docc/tutorial-syntax

I tried adding one I know of and it didn't work when I added the viewing URL.

Here's some sample documentation that I also found on GitHub in DocC… https://github.com/simonbs/Runestone/tree/main/Sources/Runestone/Documentation.docc

The example above includes tutorials so maybe that could be a test case??

[mobilemind]

OK, I threw it at Claude which came back to me indicating…

The real blocker: tutorial render-nodes aren't modeled

The content itself is reachable — https://it-training.apple.com/support/index/index.json is a standard, public DocC index, and every page has a standard render-node endpoint under /support/data/…json. The custom HTML template is only the human-facing renderer; the underlying archive is intact. (Note: you have to add the archive root https://it-training.apple.com/support/, not the viewing URL …/support/tutorials/course/ — DocB appends index/index.json to whatever you paste, so the viewing URL 404s.)

The blocker is that every page is DocC Tutorials content, whose JSON schema is fundamentally different from the documentation/symbol schema DocB renders. Confirmed against the live JSON:

Page	kind	Body lives in…
/tutorials/course (root)	overview	top-level sections: hero, volume → chapters
sup010 (a lesson)	article	top-level sections: hero, articleBody, callToAction

DocB's Article model has no sections field — it renders from primaryContentSections / abstract / topicSections, none of which exist in these payloads. So even though the JSON decodes (metadata and references are present), the page renders blank. The Framework model likewise has no volume / chapter / hero / tasks.

Individual tutorials (kind: project) go further, adding section kinds like tasks → steps (code + media + runtime preview) and assessments — the multiple-choice quizzes that make them "interactive." None of these are modeled or rendered in DocCKit today.

Separately, DocBCore currently forwards any link containing tutorials to the system browser on purpose (ContentView.swift:153-157), so even once rendering exists, that routing would need to change for tutorial links to open in-app.

[mobilemind]

And follow-up—

What it would take to support this?

This is a real feature epic in DocCKit, not a config tweak:

1. New models in DocCKit for tutorial render-nodes: kind: overview|project (+ the article-with-sections variant), decoding hero, volume/chapter, articleBody, tasks/steps, assessments, callToAction.
2. New renderers: e.g. DocCTutorialOverviewView and DocCTutorialView, step-by-step layout, media, and interactive assessment UI/state.
3. Routing change in DocBCore: stop force-forwarding tutorials URLs to Safari (ContentView.swift:155) once in-app rendering exists.
4. Onboarding nicety: accept/derive the archive root so users can paste the natural viewing URL. Search/sidebar already work — these nodes are in index/index.json (overview/article/groupMarker), so they'd flow in automatically once renderable.