A design system for Mozilla websites.
Перейти к файлу
Reem H 9b4015aaf6
fixed broken link (#794)
2022-06-10 10:05:18 -07:00
.github Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
bin Add build command for deploying the docs (Issue #746) (#756) 2021-12-15 07:57:02 -08:00
docs Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
gulpfile.js Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
src fixed broken link (#794) 2022-06-10 10:05:18 -07:00
tests Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
.editorconfig Add article and sidebar menu organisms and main/sidebar template 2018-05-04 16:20:42 +01:00
.eslintignore Move CSS/JS linting to NPM scripts (Fixes #745) (#747) 2021-12-07 17:25:37 -08:00
.eslintrc.js Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
.gitignore Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
.gitlab-ci.yml Rename master to main in gitlab-ci.yml 2021-09-14 14:56:14 -04:00
.nvmrc Move CSS/JS linting to NPM scripts (Fixes #745) (#747) 2021-12-07 17:25:37 -08:00
.stylelintrc.json Move CSS/JS linting to NPM scripts (Fixes #745) (#747) 2021-12-07 17:25:37 -08:00
CHANGELOG.md Bump version to 16.0.1 2022-05-06 10:33:46 -07:00
CODE_OF_CONDUCT.md Add Mozilla Code of Conduct file 2019-03-30 15:24:04 +00:00
LICENSE Initial commit 2018-02-21 11:31:08 -08:00
README.md [fix #447] Implement brand themes (#609) 2020-11-17 13:39:43 -08:00
netlify.toml Add some dependencies for Netlify deployment 2018-02-21 15:45:41 -05:00
package-lock.json Bump moment from 2.29.1 to 2.29.2 (#777) 2022-04-20 14:12:19 -07:00
package.json Bump version to 16.0.1 2022-05-06 10:33:46 -07:00
webpack.build.config.js Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00
webpack.static.config.js Add Webpack config for package publishing (Fixes #746) (#754) 2021-12-14 15:26:49 -08:00

README.md

Protocol

Protocol is a design system for Mozilla and Firefox websites. It establishes a common design language, provides reusable coded components, and outlines high level guidelines for content and accessibility.

https://protocol.mozilla.org/

Protocol is still an evolving project. Currently its used primarily by the Mozilla Marketing Websites team as the front-end for www.mozilla.org. The long term goal is to provide a robust, unified design system that anyone at Mozilla can use to build an on-brand website.

If youre interested in using Protocol on your project, let us know and we can help you. You can find us in #protocol-design-system on Mozillas Slack (for Mozillians) or in #protocol-design-system on Matrix (open to the public). Also feel free to file an issue on GitHub.

Current npm package version. Total downloads on npm. Pull requests welcome!

Getting Started

Protocol is built on the Node.js platform and published to NPM, so be sure to have both installed before proceeding.

Installation

To use Protocol in your website you can install the core package directly from NPM:

npm install @mozilla-protocol/core --save

Alternatively, you can also download the latest release from GitHub.

Usage

Once installed, the relevant CSS and JS files will be available in your project under ./node_modules/@mozilla-protocol/core/.

The core CSS file is bundled as protocol.css, which contains styling for things such as basic elements and typography. Component and layout CSS is bundled as protocol-components.scss for convenience.

Note: The original source (.scss) files are also included in the published package. You may want to consider compiling your own CSS to include only what you need for each page of your website, in order to further optimize for performance.

Building From Source

To build Protocol from source including the documentation site, you can clone the repo from GitHub:

$ git clone https://github.com/mozilla/protocol.git
$ cd protocol
$ npm start

Running npm start will install dependencies, build your toolkit, and start the development server at http://localhost:3000.

Further Documentation