leobauza / browncoat Goto Github PK

This includes:

1. Reorganize the folders (see gettoknowgaming)
2. EM based media queries (investigate more) More Info Here

1. Add .l class.
2. Tweak javascript that automatically adds this as well.

• Currently there are non-elements in the elements category

When using .row or .span in the documentation for other modules they are highlighted. Add specific classes for showing the highlights.

set a default library order....wash does part of this by having all the varialbes...but something like the base-lib needs to be the first thing being output.

Wraith was broken when we moved the docs into their own folder. Wraith should also be set up to document the app as well as the docs.

When trying to reorganize things, everything turns into a nightmare because all my paths are set one way...figure out how to address this.

when no kaylee exists input[type="text"] elements don't take their height seriously...wtf?

quickspan is using the wrong values inside the mixin.

Add .-doc to label and box on documentation templates so they can be styled independently of actual app styles.

• Set a maximum height for code samples
• Allow horizontal scrollbar for code samples

none: if you look inside kaylee you will see that this is wrapped in a function "createLibArrays()" the plan here is to write something that can dynamically create the array with some information river writes into the creation of all the library arrays. Right now I can't even imagine what that looks like or how to accomplish this. update: that wont be there pretty soon...

//some old code .....??? do magic and spit out an array i can use for each library instead of having multiple?
function createLibArrays() {    
    $libArr = array(
        //lib name => lib path
        "core" => "../libs/core-lib/core-firefly.less",
        "btn" => "../libs/btn-lib/btn-firefly.less",
        "callout" => "../libs/callouts-lib/callouts-firefly.less",
        "modal" => "../libs/modal-lib/modal-firefly.less",
    );
    return $libArr;
}
$serenityArr = createLibArrays( something here that helps make this array from something generic so i can make multiple of these );
$washArr = createLibArrays( something here that helps make this array from something generic so i can make multiple of these );

Should typography be broken away from blocks (ie. h1-h2 be in _typography.scss and header-footer be in _reset.scss or _divisions.scss)

Add these:

• .esllintrc.json
  • trailing coma on objects
  • no semicolons
  • other stuff...
• .nvmrc
• .editorconfig

1. EMs based media queries SAMPLE
2. Organize folders

Look into height calculation....if the width is variable it doubles the height for some reason? So the modalHeight option is useless.

Having all modules live inside of boxes is a problem for 2 reasons.

1. Tags will be affected downstream ie. the .box p style will be applied to .box .card p (which is undesirable)
2. Media queries are inaccurate

Add the .l class to the last ".span" manually rather than letting the script do it? This relates to the form.

Make note in documentation about best practice for this. It is only done to support IE8 and below.

If this is always supposed to run locally...do permissions really matter at all?

• Remove xmp tags from documentation since they are deprecated

No need for separate folders, let the data files and code samples files live next to each other. Adjust the calls from the docs app to target a single folder and two different files.

kaylee needs to contain a message that it has been written by river...and a way to fill out all previously checked stuff.

• Some kind of modal pop up to run serenity/firefly wipes?
• Modal has buttons to take you away to your project.
• Refresh the CSS somehow upon landing without a page refresh?
• fetch css from the server maybe?

Bottom margin that is...Figure out if setting a width in percentages in IE7 for some reason does this.

Wiping doesn't work unless a kaylee file exists... prob because it sets the paths to serenity and stuff so it has to fall back on default kaylee or something...

This was expected. Either:
a. Find a way to support it
b. Drop support for IE seven for some elements

if b make sure to mention it in the docs.

addslashses for title description and author in a way that works...

• Minify js/css and optimize in any other way
• Run tests
• Make sure docs scss isn't compiled into application css

Legends don't seem to be too cross browser friendly?

• JS section lacking .jshint documentation.
• Look into ESHint (?)

Document how to edit .json and .md files to generate/edit/add documentation.

Currently says:

Default (Angular.js)
a website description

how embarrassing...