Page tree
Skip to end of metadata
Go to start of metadata


Starting in mid-January 2016, the FedX team has been constituted to speed the development and integration of the UX Pattern Library and the edX UI Toolkit. See this wiki page for details: Initial rollout plan for the UI Toolkit and Pattern Library. Our primary goal is to publish the first public release of the edX Pattern Library and to enable its usage in both the edx-platform as well as in other edX repositories. In addition, we are releasing the edX UI Toolkit which is a JavaScript library for shared utilities and components.

Why are we doing this now? Multiple teams are developing edX features across tens (maybe hundreds) of repositories, which means that the styling, utilities and components in the edX platform cannot be used. These two new libraries will provide consistency and code reuse as we scale, as well as providing responsive implementations that are mobile-ready.

What are these two libraries?

  • edX Pattern Library - the UX Pattern Library is a collection of user interface elements that can be easily plugged together to build new pages and interfaces. The library defines how each pattern looks visually, how it behaves from an interaction point of view, and it includes SASS to style each pattern.
  • edX UI Toolkit - the UI Toolkit provides components for the more complex patterns (e.g. paginated lists, tab switching), both as a means to speed up development and to ensure that they meet edX’s standard for quality, theming, accessibility, and internationalization.

Along with developing and releasing these two libraries, we will be updating the edx-platform to consume them. This will require the long awaited updates to our JavaScript libraries (JQuery, Backbone, Underscore etc), as well as allowing us to evaluate the usage of newer front end technologies such as WebPack, EcmaScript 2015 (through Babel), and React.

Note that converting all of our web applications and views to use these new libraries is a massive undertaking so we will be taking an incremental approach starting initially with new features.

Team Members

See Also


Project Status

Sprint Names

Sprints are named after single word rock bands, in alphabetical order. Some ideas:

  • anthrax/abc/air/a-Ha/alt-J/avicii
  • belly/biosphere/blur/bauhaus/blondie/baroness
  • can/chvrches/coil/carcass/clutch
  • devo/doves/danzig/deadmau5
  • evanescence/elastica/emf/eurythmics/entombed
  • feist/funkadelic
  • garbage/gorillaz/ghost
  • hole/HAIM
  • interpol/isis
  • james/japan/journey
  • kiss/kajagoogoo/kvelertak
  • lush/l7/loop
  • motörhead/metallica
  • nirvana/neurosis
  • oasis/orbital/outkast
  • paramore/pixies/phish/primus
  • queen/queensrÿche
  • radiohead/r.e.m./ride/rush/rammstein
  • sepultura/slayer/slowdive/soundgarden/spiritualized/stereolab
  • tricky/tycho/testament
  • u2/ultravox/underworld/UFO
  • visage/vader
  • weezer/wham!/wilco/wildhearts
  • xtc
  • yazoo/yes/yppah
  • zoroaster/ZOM/zeke/zebrahead


  • No labels


  1. How to get involved i FedX Team?

    1. Hi Rizky. Thanks for your interest in the FedX initiative. In what ways would you like to contribute? Have you contributed to the Open edX code base previously? If not, a good place to start would be to pick up some "byte-sized" bugs and submit pull requests for them. See our guide to contributing for more details:

  2. Hello FedX team, I  would like to contribute in documentation if any.


    1. Thanks, Ashay. The front end developer documentation is produced from this GitHub repository:

      We would love PRs against this repo to add more documentation. Feel free to just create a PR with documentation that you'd like to see added. For more details on that process, see:

      Thanks again!