edx-pattern-library
Advanced tools
The (working) UI library and Front End Styleguide for edX/Open edX applications and sites.
This library contains the following:
The code in this repository is licensed the Apache 2.0 license unless otherwise noted. Please see the LICENSE file for details.
Using the edX Pattern Library source code in a project current requires:
Also, the Pattern Library currently relies on the following thrd party libraries:
| Library | Version | Purpose |
|---|---|---|
| Bourbon | 4.2.6 | basic sass/CSS utilities |
| bi-app-sass | latest | right-to-left/left-to-right directional support for layouts |
| breakpoint-sass | 2.6.1 | CSS breakpoint/media-query management |
| susy | 2.2.9 | Grid configuration and utilities |
| A Font Garde | 0.1.6 | A set of reliable (nay, bulletproof) patterns for icon fonts. |
The UX Pattern Library has its own living documentation site at http://ux.edx.org. Additionally, we have many styleguides and how-to wiki documents in the Github repository.
To work on the code of the documentation site portion of this repo, you'll need recent versions of the following things installed on your local machine.
| Library | Version | Purpose |
|---|---|---|
| Bundler | 1.10 | Used to install jekyll and its dependencies |
| Node.js | 0.12.x or 4.0.x | Third-party dependency package management |
| GulpJS + other gulp-based packages | 3.9.0 | Task runner for build process |
The Pattern Library is managed through Jekyll, a static website generator, so you'll need to install that.
Mac Users
We use a Ruby gem called Bundler to install Jekyll, as that allows us to track the version of Jekyll running on github pages easily.
We assume you have ruby 2.0.0 or later installed. If you don't, an easy way to do that is to use RVM.
With that out of the way, next step is to install bundler, and then to use that to install Jekyll:
$ gem install bundler
$ bundle install
Windows users
Windows users have a bit more work to do, but luckily @juthilo has provided some instructions with his Run Jekyll on Windows guide.
You may also need to install Pygments, the Python syntax highlighter for code snippets that plays nicely with Jekyll (which we use to highlight Front End source code). Read more about this in the Jekyll docs.
The npm command-line tool is bundled with Node.js. If you have it installed, then you already have npm too. If not, go download Node.js.
From the directory you've checked out this repo into locally, run:
npm install
This runs through all dependencies listed in package.json and downloads them to
a node_modules folder in your project directory.
NOTE: You may need to run this more than just once (if encountering errors when running the gulp command) as new dependencies may have been added.
To run the version of gulp installed local to the project, in the root of your this project, run:
./node_modules/.bin/gulp
To view the Pattern Library locally (and to watch for any local changes to
content/assets), run the default gulp task with:
gulp
This will run the default gulp task defined in gulpfile.js, which includes the general local development set-up task (build-development) and file/asset watching (watch).
After running the default task, your local instance of the Pattern Library can be viewable at http://localhost:3000. There are additional views:
http://localhost:3000/examples/**/* - where full page examples and demos are kepthttp://localhost:3000/patterns/**/* - permalinks for individually documented pattern library patternsWhen developing changes or new work within the PLDOC, please make sure to:
pattern-library) unedited (or edit in a separate branch/commit)gulp build-production, which will optimize any checked in production assets (styles, images, and scripts), if you've added or heavily edited new PLDOC assets.If you add or edit any patterns in this repo (found in _src/pattern-library/) or change any package-centric settings (e.g. package.json or bower.json), please do the following:
The UX Pattern Library is meant to be a starting UI Framework to support edX and Open edX applications and sites. To start using the UX Pattern Library in an edX/Open edX app, please follow these steps:
You'll need to download Node.js in order to use either of the UXPL packages.
Next, you'll want to add the edx-pattern-library registered package as a dependency for your project and install it all at once. You have a few options for what package manager to do that through:
In your project's main directory, you'll need to create a package.json file that will manage locally installed npm packages. To create a package.json run:
$ npm init
You'll be walked through some basic settings for your project's package. See also npm's documentation on setting up a package.
Next, you'll want to add the edx-pattern-library registered package as a dependency for your project and install it all at once.
$ npm install edx-pattern-library --save
See also, npm's documentation on installing/saving dependencies.
After instaling Node.js, you can install Bower, a package manager we use to download and maintain many of our vendor and external library refereces.
To install Bower globally:
npm install -g bower
Next, you'll want to add the edx-pattern-library registered package as a
bower dependency and install it all at once.
bower install edx-pattern-library --save
NOTE: Bower recommends initializing your project as a bower project in order to manage third party dependencies such as the edx-pattern-library bower package. Bower explains how to do that well with bower.json.
You can use the edX UX Pattern Library as a static CSS base alongside other CSS files. To do so add a reference in the <head> of your app's HTML
<link rel="stylesheet" href="[path to your package manager (npm or bower) or manually managed assets]/edx-pattern-library-ltr.min.css" />
NOTE: The node package manager (npm) package comes with several variations of compiled CSS, including:
*-ltr or *-rtl suffix.NOTE: This way of using the edX UX Pattern Library is currently in beta is not as widely tested as the Sass method (described below). If you find bugs/issues, please log them.
You can also use the edX UX Pattern Library as part of your CSS's Sass compilation (our preferred method). To do so,
just import all utilities (see the utilities directory) and what components (see the components directory) you want.
All components and utilities can be imported by default by importing the _edx-pattern-library.scss partial. See the expanded/simplified example below taken from main-ltr.scss and the _build.scss compilation of the edX Pattern Library's Documentation Site:
// ------------------------------
// edX Pattern Library Site: Main Style Compile - LTR
// About: Sass compile for the edX Pattern Library Site. This does not contain styles for other edX products/experiences (e.g. account/onboarding).
// ------------------------------
// #CONFIG - layout direction
// ------------------------------
@import 'ltr'; // LTR-specifc settings and utilities
// ------------------------------
// #CONFIG
// ------------------------------
@import 'config';
// ------------------------------
// #LIB
// ------------------------------
@import 'lib'; // third party libraries
@import '../../../pattern-library/sass/edx-pattern-library'; // UXPL
// ------------------------------
// #EXTENSIONS
// ------------------------------
@import 'utilities';
@import 'components';
@import 'layouts';
@import 'views';
@import 'overrides';
NOTE: Since both libSass and RubySass lack a way to pass in variables/configuration into their @import {file} method, each app is responsible for 1) storing any npm-based dependencies, including the edx-pattern-library, in the best directory structure for that app's set up and 2) creating a _lib.scss partial to import all third party library dependencies from that structure for the Pattern Library to use (see above example).
NOTE: We support right-to-left and left-to-right-based layouts. View more details on what configuration and utilities are needed alongside the UXPL
See the UX Pattern Library Files + Application Files guidelines and example style compile for more examples, details on how to use partials, and general background.
If you'd like to customize what to import, you can manually import specific elements from the edx-pattern-library package. Here's an example of customizing the default import demo above:
// ------------------------------
// edX Pattern Library Site: Main Style Compile - LTR
// About: **Customized** Sass compile for the edX Pattern Library Site. This does not contain styles for other edX products/experiences (e.g. account/onboarding). Any styles defined in the partials contained here should be prefixed with ".pldoc-" to avoid cascade/run-off into the element stylings.
// ------------------------------
// #CONFIG - layout direction
// ------------------------------
@import 'ltr'; // LTR-specifc settings and utilities
// ------------------------------
// #CONFIG
// ------------------------------
@import 'config';
// ------------------------------
// #LIB
// ------------------------------
@import 'lib'; // third party libraries
// use UXPL's buttons, headings, copy, grid, and layouts
@import '{path to edx-pattern-library package}/pattern-library/sass/patterns/buttons';
@import '{path to edx-pattern-library package}/pattern-library/sass/patterns/headings';
@import '{path to edx-pattern-library package}/pattern-library/sass/patterns/copy';
@import '{path to edx-pattern-library package}/pattern-library/sass/patterns/grid';
@import '{path to edx-pattern-library package}/pattern-library/sass/patterns/layouts';
// ------------------------------
// #EXTENSIONS
// ------------------------------
@import 'utilities';
@import 'components';
@import 'layouts';
@import 'views';
@import 'overrides';
There are a few places you can start to explore configuring aspects of the UX
Pattern Library for your purposes. You can find many configurations and base
settings in src/sass/utilities/_variables.scss and can override/customize
those in your application's utilities.scss partial (they'll be used
throughout the rest of the compile).
NOTE: The code and design contained in the library has not been tested for use alongside other UI Frameworks such as Bootstrap or Foundation.
NOTE: The source code of the Pattern Library does not include any local or production-focused Sass/Front End tooling. It's expected that your app/site has its own Sass compiler (preferrably LibSass).
Contributions are very welcome. The easiest way is to fork this repo, and then make a pull request from your fork. The first time you make a pull request, you may be asked to sign a Contributor Agreement.
Please refer to our [contributor guidelines](https://github.com/edx/edx- platform/blob/master/CONTRIBUTING.rst) in the main edx-platform repo for important additional information.
There are a few additional details alongside our general guidelines to keep in mind contributing to the UX Pattern Library:
If you're looking to suggest an idea or you're thinking about developing a feature, start a discussion by visiting the Open edX JIRA site and create a new "Issue" by selecting the "Create" button at the top of the page. Choose the project "UX Pattern Library" and the issue type "New Feature" or "Improvement" (you may first need to create a free JIRA account).
If you notice an issue or a bug with the Pattern Library, we would love ot hear about it! Follow the above instructions on logging a new UX Pattern Library JIRA issue and then assign the issue type of "Bug" to your issue. An edX UX Team member will then take it from there and triage your bug.
Conversely, if you want to help resolve any known bugs/issues, which are tracked in JIRA, you can create a free JIRA account and then comment on the ticket to indicate that you are working on it. Don't hesitate to ask clarifying questions on the ticket as needed, too, if anything is unclear.
For code contributions, please open up a pull request! PRs will get OSPR tickets assigned to them, as mentioned in the above contributing guidelines.
An edX UX Team member will be working with you on any pull requests you make. They will be evaulating your pull request from a design point of view as well as from a Front End Development perspective. Other team members as well as UI/Front End Developers may also lend a hand.
The Pattern library source code doesn't currently leverage the Open edX test suite nor are there any automated tests configured for this codebase currently.
In addition to the general contributor documentation, any contributions should meet specific Front End Development requirements, including the guidelines and principles listed in:
FAQs
The (working) Visual, UI, and Front End Styleguide for edX Apps
The npm package edx-pattern-library receives a total of 70 weekly downloads. As such, edx-pattern-library popularity was classified as not popular.
We found that edx-pattern-library demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 11 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
Security News
Research
A malicious npm campaign is targeting Ethereum developers by impersonating Hardhat plugins and the Nomic Foundation, stealing sensitive data like private keys.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.