/
Open edX Shared Design Collateral

Open edX Shared Design Collateral

Overview

The Open edX Shared Design Collateral is the collection of Figma files for the Open edX platform's design infrastructure. It includes the Paragon Design System and product area files. This space documents the various Figma files, and how to use the files based on your use case.

What's in this Space?

Figma Instance Structure

Figma Instance Structure: Teams, Projects, Files

Defines the full Figma hierarchy (workspace, teams, projects, and files) including the Paragon Design System, Product / App Libraries (Authoring, Instructor, Learner, Mobile, etc.), Published Release Files, and Connected Projects for external providers. Also covers the release cycle: live files are updated continuously and duplicated into release files at each platform release.

Potential gap in this documentation / upcoming question: should we add additional documentation on Figma file preferred structure across projects or for particular projects (e.g. workflows, components, page use, branching, etc.) in this Confluence documentation, or should that live within Figma projects / managed by working groups?

Access Control & Licensing

Access Control and Licensing covers who can access files and how licenses are managed.

Contribution Workflow

Contribution Workflow:

Describes the two paths for landing design changes: Funded Contributions (FCs) and Community Contributions. Outlines the full lifecycle from intake through branch creation, working-group review, maintainer review, merge, and release cut. Covers branch naming conventions, principles (live files as source of truth, all-or-nothing merges), and how to preserve exploration work in archive files.

  • Guide to Major/FC Design Contributions: Step-by-step onboarding for FC designers: CC approval, license allocation, branch setup, working in Figma, archiving explorations, close-out and merge, and connected-project handoff.

  • Guide to Community Contributions: Guidance for contributors outside an FC, covering both users with an active license seat (branch the live file) and paths for those without an active seat to contribute either through a design maintainer or a liaison at their org.

  • Design Maintainers: Responsibilities of design maintainers: triaging proposals, reviewing branches, performing copy-in merges for unseated contributors, managing archive files, and post-merge housekeeping.