Add scss devtools
parent
1b807bd6f3
commit
746afe0f60
|
@ -12,7 +12,7 @@
|
|||
<var:if condition = "hideFrame" const:negate = "YES"
|
||||
>
|
||||
<html const:xmlns = "http://www.w3.org/1999/xhtml"
|
||||
xml:lang = "en" const:lang = "en">
|
||||
xml:lang = "en" const:lang = "en" class="">
|
||||
<head>
|
||||
<title>
|
||||
<var:string value = "title" />
|
||||
|
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because one or more lines are too long
|
@ -0,0 +1,24 @@
|
|||
///
|
||||
//
|
||||
// @filename _devtools.scss
|
||||
//
|
||||
// NOT FOR PRODUCTION
|
||||
// Add some utilties when the class "dev" is append to html
|
||||
//
|
||||
|
||||
html.dev {
|
||||
// displays a grid-columns transparent guide
|
||||
&.guide::after {
|
||||
display: block;
|
||||
position: absolute;
|
||||
top: 0;
|
||||
left: 0;
|
||||
background-image: linear-gradient(90deg,rgba(0, 255, 255, 0.10) 0, rgba(0, 255, 255, 0.10) 80%, rgba(0, 0, 0, 0.0) 80%);
|
||||
background-size: (8 * $baseline-grid) (8 * $baseline-grid);
|
||||
background-repeat-x: repeat;
|
||||
width: 100%;
|
||||
height: 100%;
|
||||
content: " ";
|
||||
z-index: 1000;
|
||||
}
|
||||
}
|
|
@ -1,15 +1,15 @@
|
|||
/**
|
||||
*
|
||||
* This is the shame file (http://csswizardry.com/2013/04/shame-css/)
|
||||
* RULES
|
||||
* 1. If it’s a hack, it goes in shame.css.
|
||||
* 2. Document all hacks fully:
|
||||
* 1. What part of the codebase does it relate to?
|
||||
* 2. Why was this needed?
|
||||
* 3. How does this fix it?
|
||||
* 4. How might you fix it properly, given more time?
|
||||
* 3. Do not blame the developer; if they explained why they had to do it
|
||||
* then their reasons are probably (hopefully) valid.
|
||||
* 4. Try and clean shame.css up when you have some down time.
|
||||
* Even better, get a tech-debt story in which you can dedicate actual sprint time to it.
|
||||
*/
|
||||
///
|
||||
//
|
||||
// This is the shame file (http://csswizardry.com/2013/04/shame-css/)
|
||||
// RULES
|
||||
// 1. If it’s a hack, it goes in shame.css.
|
||||
// 2. Document all hacks fully:
|
||||
// 1. What part of the codebase does it relate to?
|
||||
// 2. Why was this needed?
|
||||
// 3. How does this fix it?
|
||||
// 4. How might you fix it properly, given more time?
|
||||
// 3. Do not blame the developer; if they explained why they had to do it
|
||||
// then their reasons are probably (hopefully) valid.
|
||||
// 4. Try and clean shame.css up when you have some down time.
|
||||
// Even better, get a tech-debt story in which you can dedicate actual sprint time to it.
|
||||
//
|
||||
|
|
|
@ -58,3 +58,7 @@
|
|||
|
||||
// Make sure this is last to override anything else
|
||||
@import 'shame';
|
||||
|
||||
// dev-tools - NOT FOR PRODUCTION
|
||||
// ------------------------------------------------------------------------------
|
||||
@import 'devtools';
|
Loading…
Reference in New Issue