Gutenberg v2.0 is built around one major addition: Courses. Courses are a new way to organise material for self-paced learning, alongside the existing event model for scheduled, instructor-led delivery. The change reaches well beyond a new /courses page. It affects the home page, the sidebar, material navigation, progress tracking, admin workflows, and event editing.
Courses and self-paced learning
Previously, Gutenberg could act as a static repository for a variety of teaching material but organised this taught material mainly through events. v2.0 introduces courses as a separate self-paced model.
Courses now have their own catalogue, detail pages, enrolment flow, progress tracking, completion state, filtering, and grouped editing model. Learners can browse what is available, enrol in the courses they want, and work through material at their own pace.
Active learning context across the app
The introduction of Courses has necessitated a shift in how the application handles learning context. This has resulted in a new home page, highlighting enrolled courses and events, and a new EventSwitcher component in the sidebar that lets users switch between their active course and active event contexts. That context is used across:
- course cards and course pages
- event flows
- the sidebar
- material page hints and navigation
Default courses and sync tooling
This release also introduces a default course catalog based on the HPC-universe material. Admins can review and sync those defaults into the database directly from the courses page by clicking the Sync default courses button.
When updates to default courses are made in the future, the sync button will present a clear diff, including grouped material changes broken out per material group, so these changes can be reviewed. Courses can also be imported and exported as JSON, which makes it easier to move curated course structures between instances or edit them outside the application.
Streamlined editing for courses and events
Course editing now happens around grouped material on a single page. Event editing follows the same direction:
- event groups are edited inline on the main event page
- material can be added, removed, and reordered without separate group-edit navigation
- new events can be created either blank or from a course blueprint
This gives courses and events a more consistent editing model than the earlier event-only setup, and it removes a lot of awkward navigation while authoring.
Better material navigation and progress surfaces
Material pages can now reflect course and event structure more directly:
- course-aware material hints
- event-aware, course-aware, and dependency aware previous/next links
- return-to-course behavior at the end of a course sequence
- improved home-page course surfaces and progress fetching
Admins can also see summary stats for courses and events, including enrolment and completion counts, in-progress numbers, progress summaries, and per-course or per-event detail pages.
Events
Events remain the model for scheduled, instructor-led delivery, but they have been reworked to fit more naturally alongside courses.
New events can now be created either blank or from a course blueprint, and event editing has moved toward the same grouped, inline model used by courses.
Gutenberg 2.0 is less of an event-only teaching tool and more of a general platform for working with authored learning material in different ways. Courses are brand new in v2.0, but much of the release is about making the rest of the application fit that addition properly.
For the detailed release summary, see the changelog.