| # Installing Packages in Sublime Text 2 | |
| Installing packages in Sublime Text 2 is a great way to take advantage of plethora of pre-built tools developed by the community, ranging from themes that customize the look of your editor to support for different language styles, such as for Jade. | |
| In order to take advantage of all of the wonderful packages out there, the first step is to install Package Control. So let's do that now. | |
| 1. Open the console in Sublime by clicking *View* in the menu bar, then *Show Console*. | |
|  |
Installing packages in Sublime Text 2 is a great way to take advantage of plethora of pre-built tools developed by the community, ranging from themes that customize the look of your editor to support for different language styles, such as for Jade.
In order to take advantage of all of the wonderful packages out there, the first step is to install Package Control. So let's do that now.
Open the console in Sublime by clicking View in the menu bar, then Show Console.
| #Graceful Degredation or Progressive Enhancement? | |
| ## Graceful Degredation | |
| The general belief on support for browsers used to be to take advantage of the newest browser features as they were released. Utlizing the newest browser features can be fun and exciting, but it can create a large problem. What happens to all of the users of your website that are on older browsers that cannot support the new features you introduce? They may have a very "poor but passable" experience, but it is not a big deal. Who really cares? This is graceful degredation. | |
| ## Progressive Enhancement | |
| There is a new belief in town now -- progressive enhancement. The basic idea of this is to not even think about the browser, only the content. Start with your base content written in semantinc HTML, and once that is set, add on presentation in the form of CSS. After this is done, snap on interactivity in the form of Javascript. By separating your development process into this three-step process, stop worrying about browser compatibility |
| #Graceful Degredation or Progressive Enhancement? | |
| ## Graceful Degredation | |
| The general belief on support for browsers used to be to take advantage of the newest browser features as they were released. Utlizing the newest browser features can be fun and exciting, but it can create a large problem. What happens to all of the users of your website that are on older browsers that cannot support the new features you introduce? They may have a very "poor but passable" experience, but it is not a big deal. Who really cares? This is graceful degredation. | |
| ## Progressive Enhancement | |
| There is a new belief in town now -- progressive enhancement. The basic idea of this is to not even think about the browser, only the content. Start with your base content written in semantinc HTML, and once that is set, add on presentation in the form of CSS. After this is done, snap on interactivity in the form of Javascript. By separating your development process into this three-step process, stop worrying about browser compatibility |
| // ---- | |
| // Sass (v3.3.4) | |
| // Compass (v1.0.0.alpha.18) | |
| // Bourbon (v) | |
| // ---- | |
| @import "bourbon/bourbon"; | |
| .block { | |
| width: calc(50% - #{em(200)}); |
