These are the Kickstarter Engineering and Data role definitions for both teams.
Styleguides courtesy [@codylindley](https://twitter.com/codylindley) & [@mundizzle](https://twitter.com/mundizzle) | |
- [http://demo.patternlab.io](http://demo.patternlab.io) | |
- [http://www.yelp.com/styleguide](http://www.yelp.com/styleguide) | |
- [http://patterns.alistapart.com](http://patterns.alistapart.com) | |
- [http://ux.mailchimp.com/patterns](http://ux.mailchimp.com/patterns) | |
- [http://www.starbucks.com/static/reference/styleguide/](http://www.starbucks.com/static/reference/styleguide/) | |
[*Original Tweet](https://twitter.com/jdsharp/status/519958518112075776) |
#CSS FLEXBOX
Summary of : http://la-cascade.ghost.io/flexbox-guide-complet/
display: flex | inline-flex;
This is a ServiceWorker template to turn small github pages into offline ready app.
Whenever I make small tools & toys, I create github repo and make a demo page using github pages (like this one).
Often these "apps" are just an index.html
file with all the nessesary CSS and JavaScript in it (or maybe 2-3 html/css/js
files). I wanted to cache these files so that I can access my tools offline as well.
Make sure your github pages have HTTPS enforced, you can check Settings > GitHub Pages > Enforce HTTPS
of your repository.
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent
elem.clientLeft
,elem.clientTop
,elem.clientWidth
,elem.clientHeight
elem.getClientRects()
,elem.getBoundingClientRect()
Set up your environment carefully: It's important to have one canonical source of truth per environment, per platform. (i.e. iOS Development, iOS Testflight, iOS Production, ditto Android.) Every time you build, your config should propagate values from one input source (per platform) to either Java/JavaScript or Objective-C/JavaScript. Here's what we did for Android and here's what we did for iOS. I don't doubt that you can do better. Please do better. But you can't say that we didn't have one canonical source of truth that worked very simply and effectively throughout the development process.
Don't wait until the end to develop Android and iOS concurrently: Even if you're not actively focusing on both platforms, don't assume that "RN is cross platform… we can develop iOS and flip the Android switch when we'r
http://www.dennyferra.com/setting-up-a-front-end-development-environment/ |
{ | |
env: { | |
es6: true | |
}, | |
parserOptions: { | |
sourceType: 'module', | |
ecmaVersion: 6, | |
ecmaFeatures: { | |
modules: true, | |
experimentalObjectRestSpread: true |
node_modules/** | |
dist/** | |
reports/** |