We are making Briar usable for everyone.
The Briar style guide is based on Bootstrap, an open-source toolkit for developing with HTML, CSS, and JS. We are currently on v4.1.0.
To improve the Briar style guide, you can clone the repo and modify the content.
This style guide has been built using Hugo. Hugo is one of the most popular open-source static site generators. You can build this yourself by installing Hugo.
Reuse in a project
The components used in the Briar Style Guide are created with portability in mind. This means they can be reused elsewhere without having to reinvent the wheel.
The easiest way to do this is to download the scss style (components.scss) and import it in your project with bootstrap included.
If you want to use SASS you can download the complete archive for the styleguide. SASS is a CSS extension The scss folder under assets contains all the sass files. Since we use bootstrap, we only add a few styles without modifying bootstrap core or defining new elements whenever possible. language.
Use the Briar Style Guide
This package includes .scss filesVisit Repo
If you an interested in contributing to our design system, the first step is ensuring that an issue exists in our issue tracker. There are many applications that an issue can have, including:
- Submitting feature proposals
- Asking questions
- Reporting bugs and malfunctions
- Obtaining support
- Enhancing code implementations
If you were unable to find a related issue in our issue tracker, begin by creating a new one. Creating an issue for each change allows us to easily track all proposals in one place. For changes that affect visual designs or user experiences, it can be helpful to include a mockup.
If your proposal involves a new guideline or UX paradigm, ping a UX reviewer or maintainer to review and provide feedback.
If your proposal involves a change to the frontend implementation, ping a frontend reviewer or maintainer to review and provide feedback.
Contribute a merge request
To make changes within our Design System, follow these instructions:
- Choose an issue to work on. If one does not exist, please review the contribution guidelines regarding creating a new one. This opens the conversation and allows feedback to happen early, preventing risks such as duplicated or unnecessary work. It can be helpful to comment in the issue to verify that no one is working on it and that the issue is still relevant.
- Fork this project.
- Make changes reflecting the issue you’ve chosen to work on.
- Create a merge request. The earlier you open a merge request, the sooner you can get feedback. You can mark it as a Work in Progress to signal that you’re not done yet.
- Get your merge request approved. If your changes involved a new guideline or UX paradigm, then ping a UX reviewer or maintainer to approve your changes. If your changes involve an update to frontend implementation, ping a frontend reviewer or maintainer to approve. Some merge requests will require both a UX and frontend approver.
- Get your changes merged! After the necessary approvals have been added, a UX or frontend maintainer can then merge your merge request. 🙌