| Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
* use descriptive docs btn naming
* rename `btn-bd-yellow` to `btn-bd-download`
* sort state vars
* sort state vars
* info, warning, danger
* rename btn-bd-purple
* rename `.btn-bd-purple` to `.btn-bd-primary`
* align docs color variables
* generate $bd-purple-light color
* with http://razorltd.github.io/sasscolourfunctioncalculator/
* allow overide of docs variables
|
|
- rename .btn-bs to .btn-bd-purple
- abstract yellow masthead button into .btn-bd-yellow and use it the new
docs navbar
|
|
|