background preloader

Webmaster front end dev

Facebook Twitter

Free PSDs of popular Web Interfaces. Catch common usability problems before user testing. · Swatch you doing? Learn CSS Layout. 960 Grid System. Progressive jpegs: a new best practice. Bandwidth-wise, images are hogs.

Progressive jpegs: a new best practice

They are the largest average web site payload (62%), and they are most often the content bottleneck. When images arrive, they come tripping onto the page, pushing other elements around and triggering a clumsy repaint. They come “chop chop chop chop chop down” or you get nothing until suddenly “boom!” Out of nowhere there it is. We all know what I’m talking about when I say “chop chop down” and “boom” and it makes us a little bit sick, because we sense how much time we’ve lost of our precious, short lives, waiting for pictures to download.

A missed opportunity Photos are the main culprit when it comes to slow rendering. Web-optimized photos are jpegs, and jpegs come in two flavors: baseline and progressive. Progressive jpegs are better because they are faster. Experimenting locally with a throttled bandwidth, an 80K progressive jpeg beats a 5K baseline jpeg (the same image, downsized) to the page in Firefox on Windows. Reality Check #1 Reality Check #2. Modpagespeed - Apache module for rewriting web pages to reduce latency and bandwidth. Most popular AJAX loading GIF and APNG spinners. ICSI Certificate Notary. Wait, Chrome Dev Tools could do THAT? Chrome Devtools Cheatsheet. Opening Devtools ◊ To access the DevTools, on any web page or app in Google Chrome you can use one of these options: Open the Chrome menu at the top-right of your browser window, then select Tools > Developer Tools.

Chrome Devtools Cheatsheet

Right-click on any page element and select Inspect Element. To open up the General Settings dialog type ? Or F1 when the Developer Tools window is open. All Panels Elements Panel ◊ Right-clicking an element you can: Force element psuedo states: (:active, :hover, :focus, :visited) Set breakpoints on the elements: (Subtree modifications, Attribute modification, Node removal) Clear console Styles Sidebar ◊ Emulate an element's pseudo state (:active, :hover, :focus, :visited) Add new style selectors Network Panel ◊ Understanding the information displayed within each column Sources Panel ◊ Don't pause on exceptions Pause on All exceptions (including those caught within try/catch blocks) Pause on uncaught exceptions (usually the one you want) Exceptions Timeline Panel ◊ Cool Sites. TinyPNG – Compress PNG images while preserving alpha transparency.

Dat-gui - A lightweight controller library for JavaScript. A lightweight graphical user interface for changing variables in JavaScript.

dat-gui - A lightweight controller library for JavaScript.

Get started with dat.GUI by reading the tutorial at Packaged Builds The easiest way to use dat.GUI in your code is by using the built source at build/dat.gui.min.js. These built JavaScript files bundle all the necessary dependencies to run dat.GUI. In your head tag, include the following code: Using dat.GUI with require.js Internally, dat.GUI uses require.js to handle dependency management. Then, in path/to/main.js: require([ 'path/to/gui/module/GUI'], function(GUI) { // No namespace necessary var gui = new GUI(); Directory Contents build: Concatenated source code. src: Modular code in require.js format. Building your own dat.GUI In the terminal, enter the following: $ cd utils$ node build_gui.js This will create a namespaced, unminified build of dat.GUI at build/dat.gui.js To export minified source using Closure Compiler, open utils/build_gui.js and set the minify parameter to true. Dat.GUI. 33 fantastic Chrome extensions.

Twitter Bootstrap. Themes for Twitter Bootstrap - WrapBootstrap. 10 points I always keep in mind while designing.