Skip to content
This repository was archived by the owner on Dec 11, 2021. It is now read-only.

Initial files and initial demo styles added #144

Closed

Conversation

nashvail
Copy link
Contributor

@nashvail nashvail commented Mar 9, 2016

For issue 10 : #10


@import
"dist/chassis",
"functions",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

empty file, remove this and the file for now, add later when there is something to do in functions file

@rohmulan
Copy link
Contributor

rohmulan commented Mar 9, 2016

@nashvail all your styles are direct css. Use some variables to make it easier to modify ur styles.
Also discuss this sometime in a chassis meeting.

input[type=email],
input[type=search],
input[type=password] {
font-family: "Source Sans Pro";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should pull from a variable font, and we currently do not use "Source Sans Pro" anywhere

Removed empty files,variables for colors, autoprefixr to  handle vendor prefixes
@nashvail
Copy link
Contributor Author

nashvail commented Mar 9, 2016

Sorry for so many inconsistencies, just getting familiar with the code base. Hope the latest commit is compatible

@sfrisk
Copy link
Contributor

sfrisk commented Mar 9, 2016

@nashvail Looks like you're currently a few commits behind master, and you have some conflicts with master that need resolving. If you merge in master, you can look at the code for how we did buttons, to get an idea for how we expect variables to be used. As it is, I'm not sure using $primary makes sense for the hover state for these inputs.

screen shot 2016-03-09 at 1 48 30 pm

input[type=password] {
border-radius: 2px;
border: 1px solid map-get($text, light);
box-shadow: inset 0 1px 3px rgba(0,0,0,.24);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Variable

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working exactly on that, wasn't aware of the way variables are used. Looking at the button example gave the idea.

@rohmulan
Copy link
Contributor

@nashvail please go through existing code to see how we declare varibles and where and when we do it.
add a file in scss/variables for your input variables and use them in your scss. Things like box shadow should be variables making them easy to modify.

}( this, function( chassis ) {

chassis.input = {
"ui-input-shadows": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove the "ui-" bit

<input type="text" placeholder="Name">
<input type="email" placeholder="Email">
<input type="password" placeholder="Password">
<input type="text" placeholder="Locaiton" value="Earth" readonly disabled>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo for the word "Location"

@sfrisk
Copy link
Contributor

sfrisk commented Apr 26, 2016

Could you please address the additional form elements in #6

<div class="demo_container">
<h1>CSS Chassis</h1>
<div class="demo_container__inputs">
<input type="text" placeholder="Name">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Demos with inputs should show labels associated with them to help enforce best practices, since placeholders should not be used as a label

@nashvail nashvail closed this May 31, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants