| <!doctype html> | |
| <html> | |
| <head> | |
| <!-- Run in full-screen mode. --> | |
| <meta name="apple-mobile-web-app-capable" content="yes"> | |
| <!-- Make the status bar black with white text. --> | |
| <meta name="apple-mobile-web-app-status-bar-style" content="black"> |
| /** | |
| * Example of using an angular provider to build an api service. | |
| * @author Jeremy Elbourn ([email protected]) | |
| */ | |
| /** Namespace for the application. */ | |
| var app = {}; | |
| /******************************************************************************/ |
pwd Shows the full path of the current directory
ls Lists all the files in the current directory
ls -al Lists all files and information
ls –alR Lists all files and information in all subdirectories
ls -alR | more Same as ls –alR, pausing when screen becomes full
ls -alR > filename.txt Same as ls –alR, outputs the results to a file
ls *.html Lists all files ending with .html
cd [directory name] Changes to a new directory
| /* | |
| * This decorates Handlebars.js with the ability to load | |
| * templates from an external source, with light caching. | |
| * | |
| * To render a template, pass a closure that will receive the | |
| * template as a function parameter, eg, | |
| * T.render('templateName', function(t) { | |
| * $('#somediv').html( t() ); | |
| * }); | |
| * Source: https://github.com/wycats/handlebars.js/issues/82 |
| /** A simple Node.js script to instantly serve | |
| * Processing source code as Processing.js :) | |
| * | |
| * This is an enhanced version which pre-procs | |
| * the code, so each of the clients does not | |
| * have to translate the PDE Java code into | |
| * PJS. The server will re-load the file only | |
| * if it has changed, in the first version | |
| * that had been reloaded on each GET request! | |
| * |
| <!DOCTYPE html> | |
| <!-- Helpful things to keep in your <head/> | |
| // Brian Blakely, 360i | |
| // http://twitter.com/brianblakely/ | |
| --> | |
| <head> | |
| <!-- IE10 Plug-in setting | |
| Including this tag will force plug-in-less "Metro IE10" to prompt the user to open the URL in "Desktop IE10" which supports plug-ins. |
by Dale Sande
CSS has had a long and sordid past. A developer never sets out with the goal of making a complete and total mess of things. Their intention is not to build something that is practically illegible, impractical to maintain and is limited in scale. But somehow, this is where many inevitably end up. Luckily, all is not lost. With some simple strategies, organizational methods and out-of-the box tools, we can really help get that junk-drawer inline.
For many of us getting started with Sass, at one time or another have created a junk-drawer of files. For most, this was a rookie mistake, but for others, this is a continuing issue with our architecture and file management techniques. Sass doesn't come with any real rules for file management so developers are pretty much left to their own devices.
CSS started out with very simple intentions, but as [tableless web design][1.1] began to really take a foothold, o
| --- | |
| - :colors_4: | |
| - "#EAABA3" | |
| - "#CE4232" | |
| - "#473332" | |
| - "#C6AB60" | |
| :colors_5: | |
| - "#CE4232" | |
| - "#7A937F" | |
| - "#473332" |
| 'use strict'; | |
| module.exports = function(grunt) { | |
| function readOptionalJSON(filepath) { | |
| var data = {}; | |
| try { | |
| data = grunt.file.readJSON(filepath); | |
| grunt.log.write('Reading data from ' + filepath + '...').ok(); | |
| } catch(e) {} |
| config.init({ | |
| meta: { | |
| title: 'Premier Dental Implant Practices', | |
| name: "Christopher Webb", | |
| homepage: 'http://conspirator.co', | |
| twitter: 'conspirator', | |
| banner: '/* \n' + | |
| ' * \tAuthor:\t\t{{meta.name}}\n' + | |
| ' * \tWebsite:\t{{meta.homepage}}\n' + | |
| ' * \tTwitter:\thttp://twitter.com/{{meta.twitter}}\n' + |