issues
search
Clicksco
/
Front-End
Organisation Front End Documentation & Tooling
http://docs.clicksco.com/frontend
2
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Templating Engine
#85
BenjaminRCooper
opened
10 years ago
0
Task Runner & Automation Tooling
#84
BenjaminRCooper
opened
10 years ago
0
When writing selectors which are using BEM, you MUST use the syntax provided in Sass 3.3
#83
BenjaminRCooper
closed
10 years ago
4
You SHOULD group related classes together in your Markup
#82
BenjaminRCooper
closed
10 years ago
6
Inconsistencies and comments
#81
jausions
closed
10 years ago
2
Unit fallback for properties with multiple values.
#80
ampersarnie
closed
10 years ago
6
Update helper mixins to placeholders where no arguments are passed to save on rendering selectors before extending
#79
timgale
closed
10 years ago
0
You MUST have all content visible to both user and assistive technology when JavaScript is not available
#78
BenjaminRCooper
closed
10 years ago
3
You MUST use the correct helper class when you want to hide content
#77
BenjaminRCooper
closed
10 years ago
3
You SHOULD use WAI-ARIA roles within your main structural elements
#76
BenjaminRCooper
closed
10 years ago
3
You MUST provide alt tag values when adding an image element
#75
BenjaminRCooper
closed
10 years ago
3
When you store JQuery wrapped objects within variables, you SHOULD prefix the variable name with a dollar sign
#74
BenjaminRCooper
closed
10 years ago
6
If you would like to communicate a certain piece of code which you feel needs a refactor, back to fellow maintainers, you MUST add a comment prefixed with "REFACTOR REQUIRED"
#73
BenjaminRCooper
closed
10 years ago
9
You SHOULD comment any functionality using the format defined by JSDoc
#72
BenjaminRCooper
closed
10 years ago
6
When doing any DOM manipulation or lookup, you SHOULD cache the necessary DOM element
#71
BenjaminRCooper
closed
10 years ago
7
If you want to have private properties contained in your objects, you SHOULD prefix them with an underscore
#70
BenjaminRCooper
closed
10 years ago
6
If you are to create get/set methods within your Behaviour, you SHOULD prefix your method with the relevant action
#69
BenjaminRCooper
closed
10 years ago
5
When naming custom properties and methods in your Behaviour, you MUST be descriptive.
#68
BenjaminRCooper
closed
10 years ago
6
When testing equality you SHOULD use boolean conversion
#67
BenjaminRCooper
closed
10 years ago
12
You MUST use the strict equality operator when type coercion would impact functionality
#66
BenjaminRCooper
closed
10 years ago
7
If you require to call a function before it is assigned, you MUST use a function declaration
#65
BenjaminRCooper
closed
10 years ago
2
You MUST always assign variables at the top of their scope
#64
BenjaminRCooper
closed
10 years ago
4
You MUST always use the var keyword when declaring variables
#63
BenjaminRCooper
closed
10 years ago
5
You SHOULD always use one var statement when declaring multiple variables
#62
BenjaminRCooper
closed
10 years ago
7
You SHOULD name any constructors which you create using Pascal Case
#61
BenjaminRCooper
closed
10 years ago
4
You MUST name your Behavior properties and methods using Camel Case
#60
BenjaminRCooper
closed
10 years ago
12
Add editorcofig file
#59
lewismorris
closed
10 years ago
2
Variables, Mixins and Functions MUST be stored within their own partial file
#58
lewismorris
closed
10 years ago
12
All variables MUST be grouped together within the _vars file based on their purpose
#57
BenjaminRCooper
closed
11 years ago
2
All variables SHOULD be named so they explicitly display there aesthetic or purpose back to the developer without any confusion
#56
BenjaminRCooper
closed
11 years ago
12
When nesting your styles, you MUST add additional space, above and below your nested declaration
#55
BenjaminRCooper
closed
11 years ago
4
You MUST place @extend statements at the top of your declaration block
#54
BenjaminRCooper
closed
11 years ago
5
Added a base HTML file and removed banner options from Gruntfile
#53
BenjaminRCooper
closed
10 years ago
17
Boilerplate - SCSS Implementation
#52
BenjaminRCooper
closed
10 years ago
0
You MUST NOT use browser hacks to get around a certain unsupported feature or inconsistency
#51
BenjaminRCooper
closed
11 years ago
1
When implementing a polyfill, you MUST use the classes provided by Modernizr
#50
BenjaminRCooper
closed
11 years ago
2
If you are too add properties whilst debugging, you SHOULD outdent these properties.
#49
BenjaminRCooper
closed
11 years ago
5
You SHOULD always remove code first before adding any additional properties
#48
BenjaminRCooper
closed
11 years ago
1
You MUST use @extend when working with module to inherit from the base element
#47
BenjaminRCooper
opened
11 years ago
19
You MUST NOT go any deeper than 3 levels within your SCSS declarations
#46
BenjaminRCooper
closed
11 years ago
6
You SHOULD store values which are referenced numerous times within variables
#45
BenjaminRCooper
closed
11 years ago
4
Use of CSS Grids
#44
lewismorris
closed
10 years ago
13
What type of projects do we require?
#43
BenjaminRCooper
opened
11 years ago
2
You SHOULD include comments which communicate a specific feature or decision back to your team
#42
BenjaminRCooper
closed
11 years ago
0
You SHOULD use relative units to size as much as your UI as possible.
#41
BenjaminRCooper
closed
11 years ago
1
You SHOULD write your comments in the format specified via the StyleDocco website
#40
BenjaminRCooper
closed
10 years ago
11
You MUST seperate selectors out on to multiple lines if a declaration block is shared
#39
BenjaminRCooper
closed
11 years ago
4
You SHOULD cluster all properties within your declarations based on relationship e.g. spacing, typography
#38
BenjaminRCooper
closed
11 years ago
6
Add in jshint, concat, uglify, imagemin, autoprefixer, cssmin
#37
markgoodyear
closed
11 years ago
4
You SHOULD name all of your classes so they are sensible and are not specific to the content
#36
BenjaminRCooper
closed
11 years ago
8
Next