Domain Studio, and a Module Studio for every type

Four releases between 11 and 13 September. Domains and modules get the studio that paths got in v1.2.0-beta.15.

Domain Studio

A domain’s page now uses the same three-pane shell as Path Studio. The Journey lens lists the domain’s paths in the order a learner walks them, each as a card with its cover, level, module count and hours. The Analysis lens rolls up each path’s own findings, one row per path. Create and edit share one drawer with an overview tab and a content tab, and the domain cover you design there is now saved. It used to be thrown away on submit. A path you create from a domain belongs to that domain from the start.

Module Studio

The module editor is rebuilt around seven families of module types (document, sections, media, external, questions, prompt and sets), with a generic fallback. It has content, learning and preview lenses, readiness chips, and a quality radar that compares the module with the ideal for its type. The assistant keeps one conversation per module.

Definitions on tagged concepts

Authors can tag a phrase in a module with a concept. A learner who hovers over it, focuses it or taps it sees a small card with the concept’s name, type and one-line definition.

Large paths and whole turns

On a path with more than 40 modules, “organize into stages” now runs as a server job that assigns 40 modules at a time and reports its progress. Before, the model had to write one card with an assignment for every module, and on paths with hundreds of modules it often never finished. When a copilot turn proposes two or more changes, “Apply all” runs them in order and stops at the first failure.

Also in this release

Added

• A pane switcher for Domain Studio on narrow screens.
• Relationship generation between the concepts of a single module.

Changed

• Arabic headings in the studio docks are no longer letter-spaced.

Fixed

• People were signed out about an hour into a session. The dozen or so refreshes a page load fired now collapse into one, and a failed refresh clears the session only when the refresh token has expired. In a forced-expiry test, sign-outs went from 1 in 3 runs to 0 in 16.
• Path Studio numbered rows 1, 5, 9, 13 on a four-stage path when the stages loaded after the modules.
• A module body with an unknown mark rendered blank for learners.
• [server] A learner could enroll in an unpublished path.
• [server] Feature flags added after the first seed never reached the staging flags page.