Frontend Tooling @ Madison+ UX 2014

Slides accompanying the Frontend Tooling workshop given by Adam Simpson and Ethan Muller at Madison+ UX 2014.

Transcript

1. WELCOME
3. Who we are
4. Who are you?
5. http://bit.ly/madison-ux- frontend-tooling
6. BUILD RIGHT: FRONTEND TOOLING PATH OF PAIN
7. BUILD RIGHT: FRONTEND TOOLING TRADITIONAL PAIN
8. PATH OF PAIN Traditional Painful Flow DESIGNER FRONTEND BUILDING LAUNCH! DEV A DEV C “DONE!” THIS PART SUCKS LAST SEC CHANGES
10. PAIN POINTS
11. ENLIGHTENMENT
12. PAIN POINTS
13. ENLIGHTENMENT
14. The traditional web development workflow is fraught with variance, isolation, and errors. Modern frontend tooling provides solutions for most of these issues.
15. COMPUTERS SOFTWARE DEV FRONT END DEV
16. CS FRONT END DEV SOURCE CONTROL DRY PRINCIPLES JAVASCRIPT
17. “There’s a new set of baseline skills required in order to be successful as a front-end developer, and developers who don’t meet this baseline are going to start feeling more and more left behind…” ! —rmurphey.com/blog/2012/04/12/a-baseline- for-front-end-developers/
18. BUILD RIGHT: FRONTEND TOOLING WHERE ARE WE HEADED?
19. Source Control
20. Static Design Tools
21. Local Servers
22. Deployment
23. Preprocessing
24. Editors
25. Development Tools
26. Device Testing
27. Productivity
28. github.com/sparkbox/ br-frontend-demo
29. PRODUCTIVITY BUILD RIGHT: FRONTEND TOOLING
30. LAYING THE GROUNDWORK A Case For Laziness
31. Laziness: the programmer’s mantra
32. DRY Don’t Repeat Yourself
33. Productivity is about net gain.
34. LAYING THE GROUNDWORK Getting Into The Command Line
35. Should a frontend dev learn to use the CLI?
36. Image: nasa.gov Launch a rocket without a control center?
37. Image: flickr.com/photos/library_of_congress/ Fight a fire without an oxygen tank?
38. Do it. It’s the “way in” to your computer
39. If you're only comfortable with GUI interfaces, you're always going to be stuck relying on a translator.
40. bit.ly/br-tooling-links
41. You'll take a few steps backward in productivity when you begin. There's a net gain here, though.
42. PRODUCTIVITY PAIN POINTS And Their Solutions
43. MOUSE CLICKS Using the pointer is usually cumbersome.
44. alfredapp.com Type everything.
45. Alfred Workflows
47. kapeli.com/dash Quick access to docs.
49. vimium.github.io Internet with your keyboard.
51. Touch typing. Practice typing without looking. Looking at your keyboard is a crutch. bullettrain.com
52. DOCUMENT SAVING, RETRIEVING & ORGANIZING
53. daringfireball.net/projects/markdown/ Markdown and the plain text workflow
54. Markdown
55. Markdown
56. Github —’s Markdown!
57. Github —’s Markdown!
58. brettterpstra.com/projects/nvalt nvAlt: Quick access to text entry
60. EXCESSIVE TYPING
61. smilesoftware.com/ TextExpander TextExpander: speedy text snippets
62. Shortcuts within the terminal: aliases and bash scripts
63. alias c="clear" ~/.bashrc or ~/.zshrc
64. alias go="cd ~/Documents/Projects ; ls" ~/.bashrc or ~/.zshrc
65. Your /dotfiles repo
66. Other People's Dotfiles (OPD) dotfiles.github.io github.com/asimpson/dotfiles
67. DISTRACTION
68. Syntax highlighting
69. Achieving focus: Obsessive singularity
72. manytricks.com/moom Moom: quick screen resizing
74. Achieving focus: The desktop of evil
75. Achieving focus: Hide your dock
76. Achieving focus: Do not disturb
77. THE INTERNET IS A DEEP BLACK HOLE
 The thing we build can also keep us from doing notable work
78. THE PRODUCTIVITY MINDSET
79. Drip, drip, drip ‣ Productivity boosts happen in tiny increments ‣ Could I automate this?
80. Productivity Strain: ! Embrace small strains for huge productivity gains over time
81. Productivity Strain COMFY OUCH! RADICAL IMPROVEMENT
82. Productivity Strain ‣ The best time to create a shortcut for an obtuse task is the moment you imagine that it could be faster. ‣ It’s probably billable time.
83. Simple example: ! TYPE ALL OF YOUR CODE
85. Your productivity hacks?
86. DEMO
87. TEXT EDITORS BUILD RIGHT: FRONTEND TOOLING
88. Which editor do you use?
89. WHY CAN’T WE ALL JUST GET ALONG?
91. Do Editors Matter? ‣ 90% of editor arguments are lighthearted ‣ Your editor preference barely effects the rest of your team ‣ Fighting over editors is almost useless. There are better battles to fight.
92. HOWEVER
93. You spend almost all of your time in your editor.
94. Your editor preference changes the way you think.
95. THE PATH OF PAIN
96. TEXT EDITORS A few signs you need a better editor: 1. Your editor is writing code for you
97. TEXT EDITORS A few signs you need a better editor: 2. You’re doing lots of clicking
98. TEXT EDITORS A few signs you need a better editor: 3. You’re repeating yourself—a lot!
99. TEXT EDITORS A few signs you need a better editor: 4. You’ve hit a ceiling, and you can’t go higher.
100. THE CASE FOR THE PLAIN TEXT EDITOR
101. Technically, all you need to code is an app that will accept text:
102. Writing all your code in TextEdit.app would be pretty painful, though! ‣ Lots of typing! ‣ No project tree ‣ No syntax highlighting ‣ Sad and depressed
103. IDE? Integrated Development Environment
104. This is the part you actually need
105. Choosing a great text editor removes abstraction between your brain and your code.
106. IDE’s ‣Slow development time ‣Messy code ‣Unskillful developers
107. “Dreamweaver was attempting to be helpful, but the moment it reformatted my code, I threw a fit. YOU TOUCHED MY CODE. Dreamweaver never recovered from that horrendous first impression.” http://randsinrepose.com/
108. Enter the simple, powerful text editor
109. Here’s what to look for: ‣ are you comfortable in it? ‣ can it do what you need? ‣ is it writing code for you?
110. THE CURRENT STATE OF EDITORS
111. Editors on the market: ‣ Sublime Text ‣ Vim ‣ TextMate ‣ BBedit ‣ Coda ‣ Emacs ‣ Espresso
112. Editors you should actually consider: ‣ Sublime Text ‣ Vim
113. Seriously, you guys. Vim Sublime Text sublimetext.com vim.org
114. “I don’t think of BBedit as a commitment. It simply continues to be the best choice.” —bit.ly/editor-rage
115. bit.ly/br-tooling-links
116. Why Sublime? ‣low barrier of entry sublimetext.com/
117. Why Sublime? ‣highly extensible
118. Why Sublime? ‣highly extensible sublime.wbond.net/installation
120. A few essential Sublime packages: Many more: sublime.wbond.net/ ‣ SideBarEnhancements ‣ AdvancedNewFile ‣ Emmet
121. Why Sublime? ‣killer features Go to Anything: ⌘+P
123. Why Sublime? ‣killer features Command Palette: ⌘+Shift+P
125. Why Sublime? ‣ recent rise in popularity ‣ compared to Coda or Espresso, it’s fast & close to the code ‣ Vintage mode for Vim key bindings ‣ hint: you should use Sublime
126. Why Vim?
127. Why Vim? ‣ fast ‣ mouseless! ‣ text objects and motions ‣ dot command ‣ configurable (vimrc, vundle) ‣ super old
128. …the fact that, yes, people still use an editor that is over 20 years old […], and those people number in the hundreds of thousands, perhaps they might be
 onto something. csswizardry.com/2014/06/vim-for-people-who-think- things-like-vim-are-weird-and-hard/
129. Why Vim? ‣ high skill ceiling ‣ popular (vimbits.com) ‣ Runs in a terminal ‣ everywhere (any platform, ssh, other people’s machines) ‣ fun, in a weird way
130. Runners-up panic.com/coda/ macrabbit.com/espresso/
131. THE RABID CASH MACHINE
132. TEXT EDITORS MATTER. GET FOAMY.
133. Editor Cults ‣ Get cultic about your editor ‣ As you're making your case, you'll have to nerd out on your editor. ‣ This is where real learning happens!
134. Seething, rabid coding machine
135. There’s only one thing more important than your editor. The code it helps you write.
136. While you're nerding out on your editor, your coworkers are raking in cash for the boss.
137. THE RABID CASH MACHINE He’s using Sublime
138. $ $
139. BUILD RIGHT: FRONTEND TOOLING SOURCE CONTROL
140. THE PATH OF PAIN Life without Source Control
141. Let’s build something!
145. Manually look for changes
147. Collaboration + Data Integrity
148. What about you?
149. UH… WHAT’S SOURCE CONTROL?
150. TERMS
151. Push Server Computer
152. Pull Server Computer
153. Commit ⌘ S +
154. Branch Master New Branch
155. Master New Branch Merge
156. Conflict !@#$
157. Branching is a huge feature.
158. Git supports rapid branching and merging [...] A core assumption in Git is that a change will be merged more often than it is written, as it is passed around various reviewers. Branches in git are very lightweight. http://marc.info/?l=linux- kernel&m=111288700902396
159. Go Branch Crazy
160. DEFINING SOURCE CONTROL Source Control gives you: ‣ The ability to collaborate with others on a single codebase ‣ Manage any conflicts that collaboration brings ‣ The ability to move code around in time.
161. Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later http://git-scm.com/book/en/Getting-Started-About- Version-Control
162. Local v. Centralized
163. Both of these solutions suffer from having the change data stored in a single place.
164. Distributed: A third option arises!
165. Git is a DVCS
166. We use Git because it allows effortless branching, it's blazing fast, and it's extremely reliable
167. “[In making Git] Take CVS as an example of what not to do; if in doubt, make the exact opposite decision." Torvalds http://en.wikipedia.org/wiki/Git_(software)
169. bit.ly/br-tooling-links
170. QUITE THE COUPLE
172. INTRO TO USING GIT
173. Grab the GitHub App ! http://mac.github.com http://windows.github.com
174. DEMO
175. BUILD RIGHT: FRONTEND TOOLING DESIGN TOOLS
176. VERSION CONTROL FOR DESIGNERS!
177. Static or Hybrid?
179. bit.ly/br-tooling-links
180. THE STATIC COMBATANTS
182. PAIN POINTS
183. PHOTOSHOP
184. Photoshop is the most widely used, and most well known. http://bradfrostweb.com/blog/post/the-post-psd-era/
186. Multiple Files v. Layer Comps
187. Layer Comps
188. Photoshop Drawbacks
189. ILLUSTRATOR
191. Illustrator Drawbacks
192. SKETCH
194. Sketch Cons
195. NO WINNERS
196. Reality is that design should be happening in all phases of a project.
197. Know your tools, use the right one for the task at hand.
198. Thoughts? Your Experience?
199. DEMO
200. BROWSER DEVELOPER TOOLS BUILD RIGHT: FRONTEND TOOLING
201. THE PATH OF PAIN Dev Tools Edition
202. We don’t know how good we have it ‣ Alerts to debug JavaScript alert("JavaScript is loaded!");
203. We don’t know how good we have it ‣ Blindly switching between editor and browser
204. Humble beginnings ‣ 2006: Firebug ‣ 2007: IE Developer toolbar (IE6 and IE7) ‣ 2009: IE8 Developer tools
205. Firebug: a tool is born
206. “When you hit the ‘Inspect’ button, mousing around the page will reveal the source of the element under your cursor ‘in real time’. Having the source instantly expand to reveal what what you touch is quite fun - it gives one the sensation of panning for gold.” ! —Joe Hewitt, creator of Firebug http://joehewitt.com/2006/03/15/firebug-a-love-story
208. Now, dev tools are a key part of our workflow, and more powerful than ever.
209. YOUR BROWSER IS A DESIGN TOOL
210. Our designs have started far away from code…
211. …but we’re slowly moving closer to the code.
212. styletil.es “Style Tiles are similar to the paint chips and fabric swatches an interior designer gets approval on before designing a room”
213. …until we’re almost right on top of the code.
214. sparkbox.github.io/style-prototype/ “…allow[s] a client to get a visual summary of a site’s design direction without creating multiple Photoshop comps or fully developing HTML pages.
215. demo.pattern-lab.info/ Atoms can also include more abstract elements like color palettes, fonts and even more invisible aspects of an interface like animations.
216. Our deliverable? Websites. The sooner we get to the code, the closer we are to shipping.
217. Image: “You best solve problems using tools you are fluent with.” 
 —@bencallahan fluency
218. Modern browser developer tools are incredibly sophisticated. ! Fluency is possible.
219. We should shift the bulk of our time toward the environment where our final deliverable will live.
220. Is this… really less complex?
221. A FRIENDLY BEGINNER’S GUIDE What can the dev tools do for me?
222. ⌘ + OPT + I! or right-click, “Inspect Element” How do I view source?
223. The ideal inspector layout for RWD work
224. The ideal inspector layout for RWD work
225. The ideal inspector layout for RWD work
226. Elements Tab
227. Network Tab
228. Sources Tab
229. DEV TOOLS MASTERY It can do that?!
230. Know this one thing!
231. The Settings Pane
232. Resources: loaded documents
233. Resources: local storage
234. Resources: cookies
235. Audit panel
236. Audit panel
237. Dev tools plugins
238. 3rd Party Dev Tool Plugins ‣ Grunt devtools ‣ Ember Inspector ‣ RailsPanel ‣ You name it!
239. bit.ly/br-tooling-links
240. DEMO
241. PREPROCESSING BUILD RIGHT: FRONTEND TOOLING
242. “I’m doing just fine, thank-you.”
243. SEMANTIC SHIFT “the evolution of word usage — usually to the point that the modern meaning is radically different from the original usage” —http://en.wikipedia.org/wiki/Semantic_change
244. Usage of words, 1850 to 2014 —books.google.com/ngrams/
245. AWFUL inspiring wonder or truly terrible?
246. FANTASTIC existing only in the imagination or marvelous, wonderful?
247. MOUSE small gray rodent with a long tail or a plastic device used to navigate on a computer screen
248. Languages have always evolved.
249. Why should we expect anything less from computer languages? ‣ Incredible complexity ‣ Rapid change in hardware ‣ Rapid change in software
250. Embrace “semantic shift” in your workflow if it tends toward efficiency.
251. THE PATH OF PAIN Our languages are flawed ‣ HTML is redundant. ‣ CSS is “flat”. ‣ JavaScript is verbose.
252. Preprocessors let us live in a fantasy world where we create the languages we want.
253. What is a preprocessor, exactly?
254. User friendly language PREPROCESSOR Compiled language
255. Language optimized for humans PREPROCESSOR Language optimized for browsers
256. What, exactly? ‣ Preprocessors are a way to write code in a friendly language. ‣ The code then gets processed into something that browsers can understand.
257. CSS PREPROCESSORS
259. Preprocessing: CSS ‣ Less: lesscss.org/ ‣ Stylus: learnboost.github.io/stylus/ ‣ Sass: sass-lang.com/
260. Less CSS .unstyled-link {! text-decoration: none;! }! ! .toollist-item {! .border-radius(5px);! background-color: #7b81d1;! ! a {! &:extend(.unstyled-link);! color: #000;! }! }! .toollist-item {! -webkit-border-radius: 5px;! -moz-border-radius: 5px;! border-radius: 5px;! background-color: #7b81d1;! }! ! .toollist-item a {! text-decoration: none; ! color: #000;! }!
261. .toollist-item {! -webkit-border-radius: 5px;! -moz-border-radius: 5px;! border-radius: 5px;! background-color: #7b81d1;! }! ! .toollist-item a {! text-decoration: none; ! color: #000;! }! Stylus CSS .unstyled-link! text-decoration none! ! .toollist-item! border-radius 5px! background-color #7b81d1! ! a! @extend .unstyled-link! color #000!
262. .unstyled-link {! text-decoration: none;! }! ! .toollist-item {! @include border-radius(5px);! background-color: #7b81d1;! ! a {! @extend %unstyled-link;! color: #000;! }! }! Sass CSS .toollist-item {! -webkit-border-radius: 5px;! -moz-border-radius: 5px;! border-radius: 5px;! background-color: #7b81d1;! }! ! .toollist-item a {! text-decoration: none; ! color: #000;! }!
263. PREPROCESSING: CSS Which one? ‣ nesting ‣ variables ‣ mixins / functions ‣ extends ‣ math ‣ including
264. PREPROCESSING: CSS We use Sass ‣ Widely used ‣ Personal preference ‣ Shipped with Rails ‣ Not much else
265. Let’s take a look at some Sass.
266. $primary-color: #cb592c;! $no-mq-support: false;!
267. @mixin sb-media($query) {! @if $no-mq-support{! @if $query < $serve-to-nomq-max-width{! @content;! }! } @else {! @media ( 'min-width:' + $query ) {! @content;! }! }! }
268. gem install sass! ! sass-lang.com
269. PREPROCESSING: CSS Sass: The Ecosystem ‣ Compass ‣ Bourbon ‣ Scut
270. gem install compass! ! compass-style.org
271. DEMO
272. JAVASCRIPT PREPROCESSORS
273. Preprocessing: JavaScript
274. var number, summaryMarkup;! ! number = 3 + 2;! ! summaryMarkup = "<div class=\"content\">\n <p> \n Foo: " + number + "\n </p>\n</div>";! JS
275. number = 3+2! ! summaryMarkup = """! <div class="content">! <p>! Foo: #{number}! </p>! </div>! """! Coffee
276. Preprocessors let us live in a fantasy world where we create the languages we want.
277. sudo npm install -g coffee-script! ! coffeescript.org
278. DEMO
279. HTML PREPROCESSORS
280. jade-lang.com
281. haml.info
282. We don’t use HTML preprocessing at Sparkbox
283. Emmet emmet.io/
285. LET’S PULL IT ALL TOGETHER
287. How do we compile preprocessed code?
288. bit.ly/br-tooling-links
289. incident57.com/codekit/
290. http://alphapixels.com/prepros/
291. Honorable mentions: ‣ Less.app ‣ Scout app ‣ Compass.app
292. Is there a better way?
293. Ruby Node SASS, Compass Grunt packages Bundler NPM Grunt
294. Grunt: a taskrunner gruntjs.com/
295. npm install -g grunt-cli
296. Grunt does all the things! ‣ Process CSS ‣ Process CoffeeScript ‣ Process HTML ‣ Reload a page when code changes ‣ Minify code ‣ So much more
297. Grunt is a JavaScript task runner that can automate dozens of repetitive tasks.
298. It's just JavaScript. (actually Node)
299. Grunt: Open source. Just files.
300. module.exports = function(grunt) {! ! // Project configuration.! grunt.initConfig({! pkg: grunt.file.readJSON('package.json'),! uglify: {! options: {! banner: '/*! <%= pkg.name %> <%=grunt.template.today("yyyy- ! ! ! mm-dd") %> */\n'! },! build: {! src: 'src/<%= pkg.name %>.js',! dest: 'build/<%= pkg.name %>.min.js'! }! }! });! ! // Load the plugin that provides the "uglify" task.! grunt.loadNpmTasks('grunt-contrib-uglify');! ! // Default task(s).! grunt.registerTask('default', ['uglify']);! }; Everything lives in Gruntfile.js
301. DEMO
302. Bower: a frontend package manager bower.io/
303. npm install -g bower
304. What is Bower? ‣ Pull down almost any JS library via the command line ‣ Not checking dependancies into the repp ‣ Use Grunt to manipulate the libraries once Bower pulls them down
305. bower install jquery
306. “Bower runs over Git, and is package-agnostic.” —http://bower.io
307. bower install git@github.com:sparkbox/Custom-Selectbox.git
308. {! "name": "br-demo",! "version": "0.1.0",! "dependencies": {! "jquery": "1.9.1",! "js-md5": "~1.1.0",! "d3": "3.4.2",! "bootstrap": "2.3.2"! }! } Everything lives in bower.json
309. DEMO
310. The holy grail: modular markup
311. This is a simple page, right?
313. Many repeating elements
314. This is our final preprocessor pain point
315. Handlebars + Assemble: powerful, modular markup
316. Handlebars ‣ Basic templating without a CMS ‣ Brings automation power to markup (100’s of helpers) ‣ Reduce repetition
317. Assemble ‣ Light static site generator ‣ Organize your layouts into manageable chunks ‣ Separate data from markup
318. Notice the repetition?
319. _tool-list-item.hbs <div class="tool-list-item" style="background-color: {{color}}">! <div class="tool-list-item--container">! <div class="tool-list-item--title">{{title}}</div>! <div class="tool-list-item--entry"><a href="{{entry-anchor}}" title="{{entry}}">{{entry}}</a></div>! {{#if notes}}! <div class="tool-list-item--expander js-trigger-tool-list">! <span class="icon-plus tool-list-item--expander-icon">! <a href="#" title="Read more">Read more</a>! </span>! </div>! {{/if}}! </div>! ! {{#if notes}}! <div class="tool-list-item--dropdown js-list-dropdown">! <div class="tool-list-item--dropdown-content wysiwyg">! {{#markdown}}{{notes}}{{/markdown}}! </div>! </div>! {{/if}}! </div>! Let’s write that once.
320. _tool-list.hbs {{#each tool-list }}! {{> _tool-list-item }}! {{/each}}! Then use handlebars to automate it
321. _tool-list-item.scss .tool-list-item {! @extend %clearfix;! overflow: hidden;! padding: 3em 1em;! position: relative;! }! Now our Sass can mirror this partial
322. DEMO
323. Questions?
324. BUILD RIGHT: FRONTEND TOOLING LOCAL SERVERS
325. […] what matters is if you can test any changes to your code fast enough. http://programmers.stackexchange.com/questions/ 139187/web-development-no-local-server-workflow
326. Working via Remote Server ‣ Slows development time ‣ Opens up production vulnerabilities ‣ Increases downtime
327. Working Locally ‣ Websites/apps load instantly ‣ Work offline ‣ Allows existing live sites to be up and functioning normally. ‣ Catch errors before they get to staging or production.
328. Remember DVCS?
329. OPTIONS
330. bit.ly/br-tooling-links
331. Packages
332. Roll Your Own
333. Vagrant ‣ Creates a VM to exactly replicate a production environment. ‣ Vagrant’s config can be checked into source control to replicate the environment across a team.
334. Try a number of solutions to find one that fits your project, your team, and your workflow
335. Your Local server of choice? Questions?
336. DEVICE TESTING BUILD RIGHT: FRONTEND TOOLING
337. GET YOUR HANDS DIRTY
338. Community Device Lab Start one?
339. Company Device Lab Start one?
341. Getting Started ‣ Android mobile device ‣ iOS mobile device (iPod Touch works great) ‣ A tablet: iPad Mini, Kindle Fire, or Google Nexus
342. Poor man’s device lab! —Image source: http://www.flickr.com/photos/21241102@N00/3908708670/
343. VIRTUALIZATION
344. Desktop OS virtualization allows developers to run alternate operating systems for testing purposes.
345. parallels.com virtualbox.org
346. bit.ly/br-tooling-links
347. But what about licensing?
348. LICENSING.
349. modern.ie
350. Every major IE and it’s needed OS
351. One-command install: ! github.com/xdissent/ievms
352. browserstack.com Simulated VMs in your browser
353. VIRTUALIZATION Mobile Device Emulation ‣ iOS simulation with Xcode’s iOS Simulator ‣ Android simulation with Google’s Android Emulator
354. We default to using physical devices if possible, VM’s for IE, and Browserstack for everything else.
355. SYNCHRONIZED TESTING SOFTWARE
356. 3RD PARTY SOFTWARE 3rd party synchronized testing software ‣ Adobe Edge Inspect ‣ Ghostlab
357. Adobe Edge Inspect iOS & Android app Chrome Browser Extension 3RD PARTY SOFTWARE
358. Adobe Edge Inspect 3RD PARTY SOFTWARE
359. Adobe Edge inspect works great, but limited in devices. Included in CC membership. 3RD PARTY SOFTWARE
360. Ghostlab 3RD PARTY SOFTWARE
361. Ghostlab Mac & Windows application 3RD PARTY SOFTWARE
362. Ghostlab Hosts your site on a local server 3RD PARTY SOFTWARE
363. Ghostlab Point any device on your network to that server 3RD PARTY SOFTWARE
364. Ghostlab Inspector on host device 3RD PARTY SOFTWARE
365. Ghostlab is fast, almost unlimited in devices. $49.99 for license. 3RD PARTY SOFTWARE
366. ACCESSIBILITY TESTING
367. Don’t overlook accessibility testing. Consider it a part of your job.
368. VoiceOver on OS X System Preferences > Accessibility
369. VoiceOver on iOS ! Preferences > General > Accessibility
370. Sim Daltonism Mac App Store
371. iconfactory.com/software/xscope XScope
372. BUILD RIGHT: FRONTEND TOOLING AUTOMATED DEPLOYMENT
373. A Major Point of Vulnerability
374. STOP FTPing ALL THE FILES
375. “Own your deployments from beginning to end.” !
376. Services
377. bit.ly/br-tooling-links
379. Roll Your Own
380. Mina
381. Features ‣ Fast! ‣ Uses Rake ‣ Boils down to a single Bash script
382. Downsides ‣ Doesn’t support more complex configurations
383. require 'mina/git'! ! set :repository, 'git://...'! set :env_config, YAML.load_file('./config/env.yml')! set :environment, ENV['on'] || env_config.fetch('default')! ! desc 'Sets up Mina to deploy to the requested environment'! task :environment do! env_config.fetch(environment).each do |key, value|! set key.to_sym, value.to_s! end! end! ! task :setup => :environment do! end! ! desc "Deploys the current version to the server."! task :deploy => :environment do! deploy do! invoke :'git:clone'! invoke :'deploy:link_shared_paths'! ! to :launch do! end! end! end desc "Deploys the current version to the server."! task :deploy => :environment do! deploy do! invoke :'git:clone'! invoke :'deploy:link_shared_paths'! ! to :launch do! end! end! end deploy.rb
384. staging:! domain: staging.example.com! deploy_to: /var/www/staging_site! branch: master! ssh_options: "-A"! ! production:! domain: example.com! deploy_to: /var/www/site! branch: production! ssh_options: "-A"! ! default: staging environments.yml
385. Capistrano
386. Features ‣ Deploys to multiple environments out of the box. ‣ Ruby syntax
387. Downsides ‣ Slower than Mina ‣ More complex ‣ 2.x is buggy
388. Questions?
389. THANK-YOU!