Pathway Creation

Overview

Pathway Creation covers the tools used to define and publish programs — structured sequences of courses that lead to a credential. On Open edX, programs are authored primarily through the course-discovery service admin and program authoring tools. Programs group courses into a defined learning path with its own branding, prerequisites, and credential outcome.

Split from v1.0. This file was created in v1.1 by splitting Course & Pathway Creation (archived). Individual course authoring is covered in Course Creation.

Current State (2026)

• Program authoring: Programs (sequences of courses) created and managed via Django admin in course-discovery, or through the frontend-app-publisher MFE
• Program types: MicroMasters, Professional Certificate, XSeries, MicroBachelors — defined by program type configuration in course-discovery
• Learner Pathway XBlock: An in-course XBlock (xblock-learner-pathway) allows embedding pathway information within course content
• Program metadata: Program title, description, banner, courses, prerequisites, and pacing type stored in course-discovery
• Credential integration: Program completion triggers credential issuance via the credentials service

Architecture

• course-discovery: Canonical backend for program/pathway data; stores program structures, types, and course memberships
• frontend-app-publisher: Publisher MFE for course and program metadata editing (primarily for edX.org publishing workflows)
• xblock-learner-pathway: XBlock for embedding pathway navigation inside course content
• credentials integration: course-discovery communicates with credentials to confirm program enrollment and completion requirements
• LMS integration: edx-platform reads program data from course-discovery to display program context on course pages

Relevant Repositories

Repository	Role in This Feature	Activity Level	Notes
openedx/course-discovery	Program/pathway data model and admin	High	Canonical pathway backend
openedx/frontend-app-publisher	Publisher MFE for program metadata editing	Medium	Used in edX.org publishing workflow
openedx/xblock-learner-pathway	XBlock for pathway display in course content	Low	Embedded pathway navigation
openedx/credentials	Program credential issuance and tracking	High	Completion verification
openedx/openedx-platform	Reads program data for learner context	High	Consumer of course-discovery

Recent Changes

• Program authoring workflows primarily admin-driven; no dedicated authoring MFE for self-service deployments

History

Origin

• Year introduced: ~2013–2014 (programs introduced as edX expanded beyond individual MOOCs to structured learning tracks)
• Initial implementation: Program data initially managed in edx-platform; later extracted to course-discovery as the program catalog grew
• Context: Programs (XSeries, then MicroMasters, Professional Certificates) were a strategic product to provide structured credentials beyond individual courses

Key Milestones

Year	Milestone	Teams / People Involved
~2013–2014	XSeries programs introduced	Unknown
~2015–2016	MicroMasters program type introduced	Unknown
~2016–2017	Program data migrated to course-discovery	Unknown
~2019–2020	Professional Certificate and MicroBachelors added	Unknown

People Who Shaped This Area

• Engineering: Unknown — open question for interview
• Product: Unknown — open question for interview
• Design: Unknown — open question for interview

Open Questions

• [ ] When were programs first introduced and what was the original product motivation?
• [ ] Why is program authoring primarily done through Django admin rather than a dedicated authoring UI?
• [ ] What is the relationship between course-discovery programs and the credentials service?
• [ ] How does the Learner Pathway XBlock relate to the program structure in course-discovery?
• [ ] Is there a self-service pathway authoring tool in the roadmap?