267.Front-end Policy

Front-end Policy
"CSS stands for Cascading Style Sheets, CSS describes how HTML elements are to be displayed on screen, paper, or in other media, CSS saves a lot of work. It can control the layout of multiple web pages all at once, External stylesheets are stored in CSS files"
Nowadays we have been working global as 267, it has become a necessity to create globally accepted standards in our departments.
CSS (Cascading Style Sheets), Javascript, front-end working policy and standards are listed in this blog.
1-) : When creating classes, the globally accepted language must be used. (Today english)
2-) : Bootstrap should'nt be overridden. It should only be extend with new classes.
3-) : Scaffolding must be in accordance with the bootstrap standards. (Using the container, row etc. grid elements correctly)
4-) : Inline should'nt be written unless JavaScript is compulsory.
5-) : Not use Inline css.
6-) : Singular form elements must use the same class (not written with different classes), buttons, input elements, etc.
7-) : Class names .title, .success, .selected, .active, .creditcard etc. Should not be used at the top level.
8-) : The special JS code blocks explain what it does and how it works with comment lines.
9-) : At the end of the work, no error should be seen when looking through the browser console.
10-) : Icons in visual naming should be meaningful like .icon-filename.svg, for background images .bg-267.jpg
11-) : Grouping of related blocks by section.
12-) : The code should be explained in general with the description lines. Repeating list items under the HTML main sections (section) must have start and end description lines like <! - /. content -> for all of them.
13-) : The given classes must be descriptive of the work done on that part and must continue in the same way as the base classes in the child element classes.