Skip to content

Commit 05a108b

Browse files
mdoXhmikosR
andcommitted
Document some basic code conventions for us (#32778)
Co-authored-by: XhmikosR <[email protected]>
1 parent ec1d745 commit 05a108b

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

site/content/docs/4.5/extend/approach.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,3 +75,11 @@ Specifically regarding custom CSS, utilities can help combat increasing file siz
7575
## Flexible HTML
7676

7777
While not always possible, we strive to avoid being overly dogmatic in our HTML requirements for components. Thus, we focus on single classes in our CSS selectors and try to avoid immediate children selectors (`>`). This gives you more flexibility in your implementation and helps keep our CSS simpler and less specific.
78+
79+
## Code conventions
80+
81+
[Code Guide](https://codeguide.co/) (from Bootstrap co-creator, @mdo) documents how we write our HTML and CSS across Bootstrap. It specifices guidelines for general formatting, common sense defaults, property and attribute orders, and more.
82+
83+
We use [Stylelint](https://stylelint.io/) to enforce these standards and more in our Sass/CSS. [Our custom Stylelint config](https://github.com/twbs/stylelint-config-twbs-bootstrap) is open source and available for others to use and extend.
84+
85+
We use [vnu-jar](https://www.npmjs.com/package/vnu-jar) to enforce standard and semantic HTML, as well as detecting common errors.

0 commit comments

Comments
 (0)