Skip to content

Instantly share code, notes, and snippets.

View lrknaff's full-sized avatar

Lacey Knaff lrknaff

View GitHub Profile
@lrknaff
lrknaff / 1608-FE_module-1_goals_LaceyKnaff.md
Created August 16, 2016 04:47
My Goals - 1608 FE - Lacey Knaff

###My Goals

####Professional Development

  1. Be able to speak confidently and knowledgeably to other developers about code
  2. Improve my public speaking skills
  3. Work towards breaking down communication barriers between design and development

####At Turing

  1. Find ways to be involved in the Turing community and seek out other avenues of involvement through meetup groups etc
  2. Learn how to write efficient, clean code that utizlizes best practices
@lrknaff
lrknaff / 160824_cssLayoutChallenge_1608.md
Last active August 28, 2016 23:43
CSS Layout Challenge 1608FE
Challenge 1

In this challenge I wrapped block 2 and 3 in there one div so that I could move them to the right of the page by using float right and float left on block 1(to keep on left side of page). In order to get block 2 and 3 inline in the right order I used floats again (float left for block 2 and float right for block3). And then I put in a margin-right of 5px to create space between the block 2 and 3.

Challenge 1

--

Challenge 2
@lrknaff
lrknaff / lacey-knaff_accessibility_m2.md
Last active October 3, 2016 17:17
Accessibility Commitments

###Accessibility Commitments

#####In my next projects I can focus on these things for accessibility:

  • Utilizing Chrome extensions (Vox & Axe) to make sure that my applications are accessible to people of all disabilities.
  • Making my applications have a clear path to usability and there is no confusion on how the application can be used by utilizing white space and clear visual heirarchy.
  • Adhering to AA standards for text size, color contrast and readablity and ease of use for people using screen readers.
@lrknaff
lrknaff / proper-git-messages.md
Created October 31, 2016 15:29
Proper Git Messages

#Git Commits - Best Practices ####Git commit messages are the most important part of a commit, because it's the only place that captures what was changed, and why.

###Rules:

  • should be short (because the git comment log doesn't have a lot of space to view copy)
  • should be able to sum up the commit in the headline
  • be useful
  • avoid editorialzing and writing useless messages
  • include the issue or bug number if it's a commit fixing a bug

Date: [02/14/2017]

Between us [Plum Street, Ltd.] and you [Lacey Knaff].

Summary:

In short; neither of us will share any confidential information about each-other, by any means, with anyone else.

What’s confidential information?

@lrknaff
lrknaff / 0_reuse_code.js
Created September 1, 2017 15:35
Here are some things you can do with Gists in GistBox.
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console