0e920ce3f4
With the current docs directory setup, I'm making too many mistakes and have to manually address path changes and directory moves on deploy. This makes for a frustrating experience developing locally and shipping releases. With this PR, we're basically back to the same setup from v3—duplicating the dist directory into our docs directory. Not the most ideal, but very straightforward for me as the release manager.
3.0 KiB
| layout | title | description | group | toc |
|---|---|---|---|---|
| docs | Brand guidelines | Documentation and examples for Bootstrap's logo and brand usage guidelines. | about | true |
Have a need for Bootstrap's brand resources? Great! We have only a few guidelines we follow, and in turn ask you to follow as well. These guidelines were inspired by MailChimp's Brand Assets.
Mark and logo
Use either the Bootstrap mark (a capital B) or the standard logo (just Bootstrap). It should always appear in San Francisco Display Semibold. Do not use the Twitter bird in association with Bootstrap.
Download mark
Download the Bootstrap mark in one of three styles, each available as an SVG file. Right click, Save as.
Name
The project and framework should always be referred to as Bootstrap. No Twitter before it, no capital s, and no abbreviations except for one, a capital B.
Colors
Our docs and branding use a handful of primary colors to differentiate what is Bootstrap from what is in Bootstrap. In other words, if it's purple, it's representative of Bootstrap.