Demo

diff --git a/.editorconfig b/.editorconfig new file mode 100644 index 00000000..7faa7966 --- /dev/null +++ b/.editorconfig @@ -0,0 +1,15 @@ +# This file is for unifying the coding style for different editors and IDEs +# editorconfig.org + +root = true + +[*] +end_of_line = lf +charset = utf-8 +trim_trailing_whitespace = true +insert_final_newline = true +indent_style = tab + +[*.{json,yml}] +indent_style = space +indent_size = 2 diff --git a/.gitignore b/.gitignore index c8e4ed6f..633f1bde 100644 --- a/.gitignore +++ b/.gitignore @@ -1,7 +1,3 @@ -vendor -tmp/* -tmp -config.json -node_modules/ -dist/ -.DS_Store +/dist/ +/node_modules/ +config.js* diff --git a/.mailmap b/.mailmap new file mode 100644 index 00000000..ffb1b476 --- /dev/null +++ b/.mailmap @@ -0,0 +1,16 @@ +Addy Osmani +Clément Partiot +Corey Frang +Douglas Calhoun +Eddie Monge +Eran Weissenstern +Eugene Nikolaev +Garrett Johnson <=> +Herwin Weststrate +John K. Paul +Luís Soares +Radu Oprita +Rebecca Murphey +Scott Murphy +Steven Hauser +Youssef Boulkaid diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bdaba76f..97125d06 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,11 +1,3 @@ ---- -title: Contributing -customFields: - - - key: "is_chapter" - value: 0 ---- - Depending on your level of experience with some of the workflows common to many open source projects, e.g. git/GitHub, the command line, and setting up a local development environment, contributing to this site may be a breeze or come with a bit of a learning curve. If you fit into the former group, great! Jump ahead to learn how to get started. But if you think you're part of the second group, and have had trouble participating in open source because of a lack of comfort with the tools, **you're still welcome**! Beyond providing a resource for learning jQuery, a major goal of this site is to provide an encouraging environment for you to develop these skills, while still making a contribution that matters. Many people think that the only way to get involved with a programming project like jQuery is to solve intricate bugs that require a nuanced understanding of the codebase, or to propose enhancements that may or may not be in scope with the development team's plans. The fact is that there's way more: improving documentation, working on web properties, and supporting other users are crucial aspects where more help is always needed. If you're willing to share your time and expertise to help other developers, we're willing to [help you get up to speed with the tools](#getting-help) you'll need. @@ -22,7 +14,7 @@ Of course, we'll also give you credit for your work! The **Contributors** sectio ### Content -The content in this site is maintained in [this GitHub repository](https://github.com/jquery/learn.jquery.com) as a collection of [Markdown](http://daringfireball.net/projects/markdown/) files in the `page` directory. The order in which chapters and articles are presented is controlled by the [order.yml](https://github.com/jquery/learn.jquery.com/blob/master/order.yml) file. +The content in this site is maintained in [this GitHub repository](https://github.com/jquery/learn.jquery.com) as a collection of [Markdown](http://daringfireball.net/projects/markdown/) files in the `page` directory. The order in which chapters and articles are presented is controlled by the [order.json](https://github.com/jquery/learn.jquery.com/blob/master/order.json) file. ### Design @@ -73,17 +65,13 @@ For more advice on managing your fork and submitting pull requests to the jQuery ### Adding a New Article 1. Add the file to the right folder in the `page` folder. -2. Add the slug name (the filename without the extension) to the desired location in `order.yml` +2. Add the slug name (the filename without the extension) to the desired location in `order.json` 3. Run `grunt` 4. You should now be able to navigate to the file. ### Formatting Articles -Yes! Take a look at our [style guide](http://learn.jquery.com/style-guide) for more information on authoring and formatting conventions. - -## How Will My Contribution Be Acknowledged? - -We will build the attribution of an article based on the git commit logs and present this information on the site. +Yes! Take a look at our [style guide](http://learn.jquery.com/style-guide/) for more information on authoring and formatting conventions.

Getting Help

@@ -91,6 +79,6 @@ If you're struggling to get any part of the site working properly, or have any q The best place to get help is on [IRC](http://en.wikipedia.org/wiki/Internet_Relay_Chat), in the `#jquery-content` channel on [Freenode](http://freenode.net). If you're unfamiliar with IRC, you can use the [webchat gateway](http://webchat.freenode.net/). -In addition, the jQuery Content Team holds a [public, weekly meetings](http://jquery.org/meeting) on Freenode, at 1PM Eastern time in the `#jquery-meeting` channel. +In addition, the jQuery Content Team holds a [public, biweekly meeting](http://jquery.org/meeting) on Wednesday, at 1PM Eastern time in the `#jquery-meeting` channel on Freenode. If IRC is not your thing, but you still want or need to get in touch, please use the site's [GitHub repo](https://github.com/jquery/learn.jquery.com) or send us an e-mail to `content at jquery dot org`. diff --git a/Gruntfile.js b/Gruntfile.js new file mode 100644 index 00000000..bc7c615b --- /dev/null +++ b/Gruntfile.js @@ -0,0 +1,61 @@ +var jqueryContent = require( "grunt-jquery-content" ); + +module.exports = function( grunt ) { + +grunt.loadNpmTasks( "grunt-jquery-content" ); + +grunt.initConfig({ + "build-posts": { + page: "page/**" + }, + "build-resources": { + all: "resources/**" + }, + wordpress: (function() { + var config = require( "./config" ); + config.dir = "dist/wordpress"; + return config; + })() +}); + +function getOrderMap() { + var map = {}, + index = 0; + + function walk( items, prefix ) { + items.forEach(function( item ) { + if ( typeof item === "object" ) { + var page = Object.keys( item )[ 0 ]; + map[ prefix + page ] = ++index; + walk( item[ page ], prefix + page + "/" ); + } else { + map[ prefix + item ] = ++index; + } + }); + } + + walk( require( "./order" ), "" ); + + return map; +} + +jqueryContent.postPreprocessors.page = (function() { + var orderMap = getOrderMap(); + + return function( post, postPath, callback ) { + var slug = postPath.replace( /^.+?\/(.+)\.\w+$/, "$1" ), + menuOrder = orderMap[ slug ]; + + if ( menuOrder ) { + post.menuOrder = menuOrder; + } + + callback( null, post ); + }; +})(); + +grunt.registerTask( "build", [ "build-posts", "build-resources" ] ); + +grunt.registerTask( "deploy", [ "wordpress-deploy", "deploy-redirects" ] ); + +}; diff --git a/LICENSE-MIT.txt b/LICENSE.txt similarity index 63% rename from LICENSE-MIT.txt rename to LICENSE.txt index e664703e..5bbeec51 100644 --- a/LICENSE-MIT.txt +++ b/LICENSE.txt @@ -1,8 +1,13 @@ -Copyright (c) 2013 jQuery Foundation, http://jquery.org/ +Copyright jQuery Foundation and other contributors, https://jquery.org/ This software consists of voluntary contributions made by many individuals. For exact contribution history, see the revision history -and logs, available at http://github.com/jquery/learn.jquery.com +available at https://github.com/jquery/learn.jquery.com + +The following license applies to all parts of this software except as +documented below: + +==== Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the @@ -22,3 +27,18 @@ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +==== + +Copyright and related rights for sample code are waived via CC0. Sample +code is defined as all source code displayed within the prose of the +documentation. + +CC0: http://creativecommons.org/publicdomain/zero/1.0/ + +==== + +All files located in the node_modules directory are externally +maintained libraries used by this software which have their own +licenses; we recommend you read them, as their terms may differ from the +terms above. diff --git a/README.md b/README.md old mode 100755 new mode 100644 index 868f777a..cbfec1e1 --- a/README.md +++ b/README.md @@ -1,7 +1,6 @@ # The jQuery Learning Site -* Primary Domain: [http://learn.jquery.com](http://learn.jquery.com) -* Staging Domain: [http://stage.learn.jquery.com](http://stage.learn.jquery.com) +This site aims to be an authoritative educational resource for those wishing to learn how to use jQuery. From beginners, to more advanced users. It's being driven by the jQuery community. ## About @@ -10,41 +9,38 @@ The goal of this site is twofold: 1. To serve as a central, trustworthy, narrative compendium of information about how to use jQuery and JavaScript. 2. To remain a timely, vibrant, and community-driven reference with a relatively low barrier to contribution. -Much of the initial content - and spirit - comes from [jQuery Fundamentals](http://jqfundamentals.com/legacy), an open-source book about jQuery, originally written by [Rebecca Murphey](http://www.rmurphey.com/) and released in 2010. In 2011, Rebecca [bequeathed the book](http://rmurphey.com/blog/2011/03/17/the-future-of-jquery-fundamentals-and-a-confession/) unto the jQuery Foundation to serve as the basis for this site. +Much of the initial content - and spirit - comes from [jQuery Fundamentals](http://jqfundamentals.com/legacy), an open-source book about jQuery, originally written by [Rebecca Murphey](http://www.rmurphey.com/) and released in 2010. In 2011, Rebecca [bequeathed the book](http://rmurphey.com/blog/2011/03/17/the-future-of-jquery-fundamentals-and-a-confession/) unto the jQuery Foundation to serve as the basis for this site. The book was split up into individual sections, whch we iterated on and improved over several months. Early on we wanted to ensure we covered as many relevant topics as possible and reached out to writers in the community to give us permission to integrate some of their blog posts as well. ## How This Site Works This site's core content consists of [Markdown](http://daringfireball.net/projects/markdown/) files. The template that controls the site's appearance is a [child theme](https://github.com/jquery/jquery-wp-content/tree/master/themes/learn.jquery.com) of [jquery-wp-content](https://github.com/jquery/jquery-wp-content), and any issues with the presentation should be directed to [that repository](https://github.com/jquery/jquery-wp-content). + ### Site Organization All of the content lives inside of the subdirectories of the `page` directory. Each of these subdirectories is considered a **chapter**, and contains one or more **articles**, and there is also a top level file that corresponds to each chapter, which contains the chapter's human-readable title and an overview, which will appear on the chapter's landing page. -The [`order.yml`](https://github.com/jquery/learn.jquery.com/blob/master/order.yml) file controls the order that chapters and articles appear in the site. +The [`order.json`](https://github.com/jquery/learn.jquery.com/blob/master/order.json) file controls the order that chapters and articles appear in the site. -### YAML Conventions +### Front Matter -Each of the articles on the site has some YAML "Front Matter" that contains metadata. All articles should include the following: +Each of the articles on the site has some JSON "Front Matter" that contains metadata. All articles should include the following: -* `title` - The title of the article as it will appear in the site. If it contains special characters, put the string in quotes. +* `title` - The title of the article as it will appear in the site. -`title: "jQuery Event Extensions"` +`"title": "jQuery Event Extensions"` * `level` - The approximate level of jQuery experience required to find the article useful. Options: `beginner`, `intermediate`, or `advanced`. -`level: advanced` +`"level": "advanced"` -## Building & Working Locally +## Building and Deploying -As this site is part of the jQuery network of sites, its presentation is controlled by [jquery-wp-content](https://github.com/jquery/jquery-wp-content). To preview the site locally, first follow the [instructions there](https://github.com/jquery/jquery-wp-content) to set up a local version of the jQuery WordPress network. Then, clone this repo and run the following steps (node.js required). +To build and deploy your changes for previewing in a [`jquery-wp-content`](https://github.com/jquery/jquery-wp-content) instance, follow the [workflow instructions](http://contribute.jquery.org/web-sites/#workflow) from our documentation on [contributing to jQuery Foundation web sites](http://contribute.jquery.org/web-sites/). -1. `npm install` -2. `cp config-sample.json config.json` -3. Edit config.json to use the username and password for your local WordPress network -4. `grunt` ## How Can I Help? diff --git a/config-sample.json b/config-sample.json deleted file mode 100644 index e1ad4f6b..00000000 --- a/config-sample.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "url": "vagrant.learn.jquery.com", - "username": "admin", - "password": "sample" -} diff --git a/eslint.config.js b/eslint.config.js new file mode 100644 index 00000000..dcf8f70f --- /dev/null +++ b/eslint.config.js @@ -0,0 +1,18 @@ +const jqueryConfig = require( "eslint-config-jquery" ); +const globals = require( "globals" ); + +module.exports = [ + { + ignores: [ "dist" ] + }, + + { + files: [ "eslint.config.js", "Gruntfile.js" ], + languageOptions: { + globals: { + ...globals.node + } + }, + rules: jqueryConfig.rules + } +]; diff --git a/grunt.js b/grunt.js deleted file mode 100644 index ce00cd2b..00000000 --- a/grunt.js +++ /dev/null @@ -1,205 +0,0 @@ -var yaml = require( "js-yaml" ), - config = require("./config.json"); - -module.exports = function( grunt ) { - -"use strict"; - -grunt.loadNpmTasks( "grunt-clean" ); -grunt.loadNpmTasks( "grunt-html" ); -grunt.loadNpmTasks( "grunt-wordpress" ); -grunt.loadNpmTasks( "grunt-jquery-content" ); -grunt.loadNpmTasks( "grunt-check-modules" ); - -grunt.initConfig({ - clean: { - wordpress: "dist/" - }, - htmllint: { - resources: "resources/*.html" - }, - jshint: { - options: { - undef: true, - node: true - } - }, - lint: { - grunt: "grunt.js" - }, - watch: { - pages: { - files: "page/**", - tasks: "deploy" - } - }, - "build-pages": { - all: grunt.file.expandFiles( "page/**" ) - }, - "build-resources": { - all: grunt.file.expandFiles( "resources/**/*" ) - }, - wordpress: grunt.utils._.extend({ - dir: "dist/wordpress", - order: "order.yml" - }, grunt.file.readJSON( "config.json" ) ) -}); - - - -// Process a YAML order file and return an object of page slugs and their ordinal indices -grunt.registerHelper( "read-order", function( orderFile ) { - var order, - map = {}, - index = 0; - - try { - order = yaml.load( grunt.file.read( orderFile ) ); - } catch( error ) { - grunt.warn( "Invalid order file: " + orderFile ); - return null; - } - - - function flatten( item, folder ) { - var title, - path = folder ? [ folder ] : []; - - if ( grunt.utils._.isObject( item ) ) { - title = Object.keys( item )[ 0 ]; - path.push( title ); - path = path.join( "/" ); - map[ path ] = ++index; - - item[ title ].forEach(function( item ) { - flatten( item, path ); - }); - } else { - path.push( item ); - map[ path.join( "/" ) ] = ++index; - } - } - order.forEach(function( item ) { - flatten( item ); - }); - return map; -}); - -grunt.registerHelper( "contributor-attribution", function( post, fileName, fn ) { - var contribs = [], - _ = grunt.utils._, - parseRE = /^(.*)<(.*)>$/; // could certainly be better. - - // Read contributors from git file information - grunt.utils.spawn({ - cmd: "git", - args: [ - "log", - "--follow", // Trace history through file rename operations - "--diff-filter=AM", // Only consider "Add" and "Modify" operations - "--format=%aN <%aE>", - fileName - ] - }, function( err, result ) { - if ( err ) { - grunt.verbose.error(); - grunt.log.error( err ); - return; - } - // make unique. - contribs = _.uniq( result.stdout.split( /\r?\n/g ) ); - - // make object { name: 'name', email: 'email@address.com' } - contribs.forEach(function(str, idx) { - var m = parseRE.exec(str); - if ( m ) { - contribs[idx] = { name: m[1].trim(), email: m[2] }; - } - else { - contribs[idx] = { name: str }; - } - }); - - // Alphabetize by 'last name' (relatively crude) - contribs = _.sortBy( contribs, function(a) { - return a.name.split(' ').pop().toLowerCase(); - }); - - // Handle "legacy" content - content authored outside of the learn site - // and attributed with metadata in the file, - // push those contributors to the front of the list - if ( post.attribution ) { - post.attribution.forEach(function(str, idx) { - var contrib, m; - - // Handling specifically for articles originally from jQuery Fundamentals - if (str == "jQuery Fundamentals") { - contribs.unshift({ - name: str, - // Use the jQuery Gravatar - email: "github@jquery.com", - source: post.source - }); - } else { - m = parseRE.exec(str); - if ( m ) { - contrib = { name: m[1].trim(), email: m[2] }; - } - else { - contrib = { name: str }; - } - if ( post.source ) { - contrib.source = post.source; - } - contribs.unshift( contrib ); - } - }); - } - - if ( post.customFields ) { - post.customFields.push({ - key: "contributors", - value: JSON.stringify( contribs ) - }); - - } else { - post.customFields = [{ - key: "contributors", - value: JSON.stringify( contribs ) - }]; - } - - fn(); - }); - -}); - -grunt.registerHelper( "build-pages-preprocess", (function() { - var orderMap = grunt.helper( "read-order", "order.yml" ); - - return function( post, fileName, done ) { - grunt.utils.async.series([ - function applyOrder( fn ) { - var slug = fileName.replace( /^.+?\/(.+)\.\w+$/, "$1" ), - menuOrder = orderMap[ slug ]; - if ( menuOrder ) { - post.menuOrder = menuOrder; - } - fn(); - }, - - function applyContribs( fn ) { - grunt.helper( "contributor-attribution", post, fileName, fn ); - } - ], done ); - }; -})()); - -grunt.registerTask( "default", "wordpress-deploy" ); -grunt.registerTask( "build-wordpress", "check-modules clean lint build-pages build-resources"); -grunt.registerTask( "deploy", "wordpress-deploy" ); - -}; - - - diff --git a/order.json b/order.json new file mode 100644 index 00000000..2b38e2c8 --- /dev/null +++ b/order.json @@ -0,0 +1,137 @@ +[ + "index", + "about", + "contributing", + { + "about-jquery": [ + "how-jquery-works", + "additional-support" + ] + }, + { + "using-jquery-core": [ + "dollar-object-vs-function", + "document-ready", + "avoid-conflicts-other-libraries", + "attributes", + "selecting-elements", + "working-with-selections", + "manipulating-elements", + "jquery-object", + "traversing", + "css-styling-dimensions", + "data-methods", + "utility-methods", + "iterating", + "understanding-index", + { + "faq": [ + "how-do-i-select-an-item-using-class-or-id", + "how-do-i-select-elements-when-i-already-have-a-dom-element", + "how-do-i-test-whether-an-element-has-a-particular-class", + "how-do-i-test-whether-an-element-exists", + "how-do-i-determine-the-state-of-a-toggled-element", + "how-do-i-select-an-element-by-an-id-that-has-characters-used-in-css-notation", + "how-do-i-disable-enable-a-form-element", + "how-do-i-check-uncheck-a-checkbox-input-or-radio-button", + "how-do-i-get-the-text-value-of-a-selected-option", + "how-do-i-replace-text-from-the-3rd-element-of-a-list-of-10-items", + "how-do-i-pull-a-native-dom-element-from-a-jquery-object" + ] + } + ] + }, + { + "events": [ + "event-basics", + "event-helpers", + "introduction-to-events", + "handling-events", + "inside-event-handling-function", + "event-delegation", + "triggering-event-handlers", + "history-of-events", + "introduction-to-custom-events", + "event-extensions" + ] + }, + { + "effects": [ + "intro-to-effects", + "custom-effects", + "queue-and-dequeue-explained" + ] + }, + { + "ajax": [ + "key-concepts", + "jquery-ajax-methods", + "ajax-and-forms", + "working-with-jsonp", + "ajax-events" + ] + }, + { + "plugins": [ + "finding-evaluating-plugins", + "basic-plugin-creation", + "publishing-plugins", + "advanced-plugin-concepts" + ] + }, + { + "performance": [ + "append-outside-loop", + "cache-loop-length", + "detach-elements-before-work-with-them", + "dont-act-on-absent-elements", + "optimize-selectors", + "use-stylesheets-for-changing-css", + "read-the-source" + ] + }, + { + "code-organization": [ + "concepts", + "beware-anonymous-functions", + "dont-repeat-yourself", + "feature-browser-detection", + { + "deferreds": [ + "about-deferreds", + "jquery-deferreds", + "examples" + ] + } + ] + }, + { + "jquery-ui": [ + "getting-started", + "how-jquery-ui-works", + "theming", + "themeroller", + { + "widget-factory": [ + "why-use-the-widget-factory", + "how-to-use-the-widget-factory", + "widget-method-invocation", + "extending-widgets", + "classes-option" + ] + }, + { + "environments": [ + "amd", + "bower" + ] + } + ] + }, + { + "jquery-mobile": [ + "getting-started", + "theme-roller" + ] + } +] diff --git a/order.yml b/order.yml deleted file mode 100644 index a004754b..00000000 --- a/order.yml +++ /dev/null @@ -1,109 +0,0 @@ -- index -- about -- contributing -- about-jquery: - - how-jquery-works - - additional-support -- javascript-101: - - getting-started - - running-code - - syntax-basics - - types - - operators - - conditional-code - - loops - - reserved-words - - arrays - - objects - - functions - - testing-type - - this-keyword - - scope - - closures -- using-jquery-core: - - dollar-object-vs-function - - document-ready - - avoid-conflicts-other-libraries - - attributes - - selecting-elements - - working-with-selections - - manipulating-elements - - jquery-object - - traversing - - css-styling-dimensions - - data-methods - - utility-methods - - iterating - - understanding-index - - faq: - - how-do-i-select-an-item-using-class-or-id - - how-do-i-select-elements-when-i-already-have-a-dom-element - - how-do-i-test-whether-an-element-has-a-particular-class - - how-do-i-test-whether-an-element-exists - - how-do-i-determine-the-state-of-a-toggled-element - - how-do-i-select-an-element-by-an-id-that-has-characters-used-in-css-notation - - how-do-i-disable-enable-a-form-element - - how-do-i-check-uncheck-a-checkbox-input-or-radio-button - - how-do-i-get-the-text-value-of-a-selected-option - - how-do-i-replace-text-from-the-3rd-element-of-a-list-of-10-items - - how-do-i-pull-a-native-dom-element-from-a-jquery-object -- events: - - event-basics - - event-helpers - - introduction-to-events - - handling-events - - inside-event-handling-function - - event-delegation - - triggering-event-handlers - - history-of-events - - introduction-to-custom-events - - event-extensions -- effects: - - intro-to-effects - - custom-effects - - queue-and-dequeue-explained - - uses-of-queue-and-dequeue -- ajax: - - key-concepts - - jquery-ajax-methods - - ajax-and-forms - - working-with-jsonp - - ajax-events -- plugins: - - finding-evaluating-plugins - - basic-plugin-creation - - advanced-plugin-concepts - - stateful-plugins-with-widget-factory -- performance: - - append-outside-loop - - cache-loop-length - - detach-elements-before-work-with-them - - dont-act-on-absent-elements - - optimize-selectors - - use-stylesheets-for-changing-css - - read-the-source -- code-organization: - - concepts - - beware-anonymous-functions - - dont-repeat-yourself - - feature-browser-detection - - deferreds: - - about-deferreds - - jquery-deferreds - - examples -- jquery-ui: - - getting-started - - how-jquery-ui-works - - theming: - - themeroller - - api - - write-a-theme - - widget-factory: - - why-use-the-widget-factory - - how-to-use-the-widget-factory - - environments: - - amd - - bower -- jquery-mobile: - - getting-started - - theme-roller diff --git a/package-lock.json b/package-lock.json new file mode 100644 index 00000000..8871b1ed --- /dev/null +++ b/package-lock.json @@ -0,0 +1,2249 @@ +{ + "name": "learn.jquery.com", + "version": "0.6.31", + "lockfileVersion": 3, + "requires": true, + "packages": { + "": { + "name": "learn.jquery.com", + "version": "0.6.31", + "dependencies": { + "grunt": "1.6.1", + "grunt-jquery-content": "3.3.1" + }, + "devDependencies": { + "eslint": "^9.0.0", + "eslint-config-jquery": "^3.0.2", + "globals": "^15.0.0" + } + }, + "node_modules/@aashutoshrathi/word-wrap": { + "version": "1.2.6", + "resolved": "https://registry.npmjs.org/@aashutoshrathi/word-wrap/-/word-wrap-1.2.6.tgz", + "integrity": "sha512-1Yjs2SvM8TflER/OD3cOjhWWOZb58A2t7wpE2S9XfBYTiIl+XFhQG2bjy4Pu1I+EAlCNUzRDYDdFwFYUKvXcIA==", + "dev": true, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/@eslint-community/eslint-utils": { + "version": "4.4.0", + "resolved": "https://registry.npmjs.org/@eslint-community/eslint-utils/-/eslint-utils-4.4.0.tgz", + "integrity": "sha512-1/sA4dwrzBAyeUoQ6oxahHKmrZvsnLCg4RfxW3ZFGGmQkSNQPFNLV9CUEFQP1x9EYXHTo5p6xdhZM1Ne9p/AfA==", + "dev": true, + "dependencies": { + "eslint-visitor-keys": "^3.3.0" + }, + "engines": { + "node": "^12.22.0 || ^14.17.0 || >=16.0.0" + }, + "peerDependencies": { + "eslint": "^6.0.0 || ^7.0.0 || >=8.0.0" + } + }, + "node_modules/@eslint-community/eslint-utils/node_modules/eslint-visitor-keys": { + "version": "3.4.3", + "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz", + "integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==", + "dev": true, + "engines": { + "node": "^12.22.0 || ^14.17.0 || >=16.0.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" + } + }, + "node_modules/@eslint-community/regexpp": { + "version": "4.10.0", + "resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.10.0.tgz", + "integrity": "sha512-Cu96Sd2By9mCNTx2iyKOmq10v22jUVQv0lQnlGNy16oE9589yE+QADPbrMGCkA51cKZSg3Pu/aTJVTGfL/qjUA==", + "dev": true, + "engines": { + "node": "^12.0.0 || ^14.0.0 || >=16.0.0" + } + }, + "node_modules/@eslint/eslintrc": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-3.0.2.tgz", + "integrity": "sha512-wV19ZEGEMAC1eHgrS7UQPqsdEiCIbTKTasEfcXAigzoXICcqZSjBZEHlZwNVvKg6UBCjSlos84XiLqsRJnIcIg==", + "dev": true, + "dependencies": { + "ajv": "^6.12.4", + "debug": "^4.3.2", + "espree": "^10.0.1", + "globals": "^14.0.0", + "ignore": "^5.2.0", + "import-fresh": "^3.2.1", + "js-yaml": "^4.1.0", + "minimatch": "^3.1.2", + "strip-json-comments": "^3.1.1" + }, + "engines": { + "node": "^18.18.0 || ^20.9.0 || >=21.1.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" + } + }, + "node_modules/@eslint/eslintrc/node_modules/argparse": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz", + "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==", + "dev": true + }, + "node_modules/@eslint/eslintrc/node_modules/globals": { + "version": "14.0.0", + "resolved": "https://registry.npmjs.org/globals/-/globals-14.0.0.tgz", + "integrity": "sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==", + "dev": true, + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/@eslint/eslintrc/node_modules/js-yaml": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz", + "integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==", + "dev": true, + "dependencies": { + "argparse": "^2.0.1" + }, + "bin": { + "js-yaml": "bin/js-yaml.js" + } + }, + "node_modules/@eslint/eslintrc/node_modules/minimatch": { + "version": "3.1.2", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", + "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", + "dev": true, + "dependencies": { + "brace-expansion": "^1.1.7" + }, + "engines": { + "node": "*" + } + }, + "node_modules/@eslint/js": { + "version": "9.0.0", + "resolved": "https://registry.npmjs.org/@eslint/js/-/js-9.0.0.tgz", + "integrity": "sha512-RThY/MnKrhubF6+s1JflwUjPEsnCEmYCWwqa/aRISKWNXGZ9epUwft4bUMM35SdKF9xvBrLydAM1RDHd1Z//ZQ==", + "dev": true, + "engines": { + "node": "^18.18.0 || ^20.9.0 || >=21.1.0" + } + }, + "node_modules/@humanwhocodes/config-array": { + "version": "0.12.3", + "resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.12.3.tgz", + "integrity": "sha512-jsNnTBlMWuTpDkeE3on7+dWJi0D6fdDfeANj/w7MpS8ztROCoLvIO2nG0CcFj+E4k8j4QrSTh4Oryi3i2G669g==", + "dev": true, + "dependencies": { + "@humanwhocodes/object-schema": "^2.0.3", + "debug": "^4.3.1", + "minimatch": "^3.0.5" + }, + "engines": { + "node": ">=10.10.0" + } + }, + "node_modules/@humanwhocodes/module-importer": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz", + "integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==", + "dev": true, + "engines": { + "node": ">=12.22" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/nzakas" + } + }, + "node_modules/@humanwhocodes/object-schema": { + "version": "2.0.3", + "resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-2.0.3.tgz", + "integrity": "sha512-93zYdMES/c1D69yZiKDBj0V24vqNzB/koF26KPaagAfd3P/4gUlh3Dys5ogAK+Exi9QyzlD8x/08Zt7wIKcDcA==", + "dev": true + }, + "node_modules/@nodelib/fs.scandir": { + "version": "2.1.5", + "resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz", + "integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==", + "dev": true, + "dependencies": { + "@nodelib/fs.stat": "2.0.5", + "run-parallel": "^1.1.9" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/@nodelib/fs.stat": { + "version": "2.0.5", + "resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz", + "integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==", + "dev": true, + "engines": { + "node": ">= 8" + } + }, + "node_modules/@nodelib/fs.walk": { + "version": "1.2.8", + "resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz", + "integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==", + "dev": true, + "dependencies": { + "@nodelib/fs.scandir": "2.1.5", + "fastq": "^1.6.0" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/abbrev": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.1.1.tgz", + "integrity": "sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==" + }, + "node_modules/acorn": { + "version": "8.11.3", + "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.11.3.tgz", + "integrity": "sha512-Y9rRfJG5jcKOE0CLisYbojUjIrIEE7AGMzA/Sm4BslANhbS+cDMpgBdcPT91oJ7OuJ9hYJBx59RjbhxVnrF8Xg==", + "dev": true, + "bin": { + "acorn": "bin/acorn" + }, + "engines": { + "node": ">=0.4.0" + } + }, + "node_modules/acorn-jsx": { + "version": "5.3.2", + "resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz", + "integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==", + "dev": true, + "peerDependencies": { + "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0" + } + }, + "node_modules/ajv": { + "version": "6.12.6", + "resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz", + "integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==", + "dev": true, + "dependencies": { + "fast-deep-equal": "^3.1.1", + "fast-json-stable-stringify": "^2.0.0", + "json-schema-traverse": "^0.4.1", + "uri-js": "^4.2.2" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/epoberezkin" + } + }, + "node_modules/ansi-regex": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", + "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/ansi-styles": { + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz", + "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==", + "dependencies": { + "color-convert": "^2.0.1" + }, + "engines": { + "node": ">=8" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/argparse": { + "version": "1.0.10", + "resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz", + "integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==", + "dependencies": { + "sprintf-js": "~1.0.2" + } + }, + "node_modules/array-each": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/array-each/-/array-each-1.0.1.tgz", + "integrity": "sha512-zHjL5SZa68hkKHBFBK6DJCTtr9sfTCPCaph/L7tMSLcTFgy+zX7E+6q5UArbtOtMBCtxdICpfTCspRse+ywyXA==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/array-slice": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/array-slice/-/array-slice-1.1.0.tgz", + "integrity": "sha512-B1qMD3RBP7O8o0H2KbrXDyB0IccejMF15+87Lvlor12ONPRHP6gTjXMNkt/d3ZuOGbAe66hFmaCfECI24Ufp6w==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/async": { + "version": "0.9.2", + "resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz", + "integrity": "sha512-l6ToIJIotphWahxxHyzK9bnLR6kM4jJIIgLShZeqLY7iboHoGkdgFl7W2/Ivi4SkMJYGKqW8vSuk0uKUj6qsSw==" + }, + "node_modules/balanced-match": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz", + "integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==" + }, + "node_modules/boolbase": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz", + "integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==" + }, + "node_modules/brace-expansion": { + "version": "1.1.11", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", + "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==", + "dependencies": { + "balanced-match": "^1.0.0", + "concat-map": "0.0.1" + } + }, + "node_modules/braces": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz", + "integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==", + "dependencies": { + "fill-range": "^7.0.1" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/callsites": { + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz", + "integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==", + "dev": true, + "engines": { + "node": ">=6" + } + }, + "node_modules/chalk": { + "version": "4.1.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz", + "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==", + "dependencies": { + "ansi-styles": "^4.1.0", + "supports-color": "^7.1.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/chalk?sponsor=1" + } + }, + "node_modules/cheerio": { + "version": "1.0.0-rc.12", + "resolved": "https://registry.npmjs.org/cheerio/-/cheerio-1.0.0-rc.12.tgz", + "integrity": "sha512-VqR8m68vM46BNnuZ5NtnGBKIE/DfN0cRIzg9n40EIq9NOv90ayxLBXA8fXC5gquFRGJSTRqBq25Jt2ECLR431Q==", + "dependencies": { + "cheerio-select": "^2.1.0", + "dom-serializer": "^2.0.0", + "domhandler": "^5.0.3", + "domutils": "^3.0.1", + "htmlparser2": "^8.0.1", + "parse5": "^7.0.0", + "parse5-htmlparser2-tree-adapter": "^7.0.0" + }, + "engines": { + "node": ">= 6" + }, + "funding": { + "url": "https://github.com/cheeriojs/cheerio?sponsor=1" + } + }, + "node_modules/cheerio-select": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/cheerio-select/-/cheerio-select-2.1.0.tgz", + "integrity": "sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==", + "dependencies": { + "boolbase": "^1.0.0", + "css-select": "^5.1.0", + "css-what": "^6.1.0", + "domelementtype": "^2.3.0", + "domhandler": "^5.0.3", + "domutils": "^3.0.1" + }, + "funding": { + "url": "https://github.com/sponsors/fb55" + } + }, + "node_modules/color-convert": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz", + "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==", + "dependencies": { + "color-name": "~1.1.4" + }, + "engines": { + "node": ">=7.0.0" + } + }, + "node_modules/color-name": { + "version": "1.1.4", + "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz", + "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==" + }, + "node_modules/colors": { + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/colors/-/colors-1.1.2.tgz", + "integrity": "sha512-ENwblkFQpqqia6b++zLD/KUWafYlVY/UNnAp7oz7LY7E924wmpye416wBOmvv/HMWzl8gL1kJlfvId/1Dg176w==", + "engines": { + "node": ">=0.1.90" + } + }, + "node_modules/concat-map": { + "version": "0.0.1", + "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz", + "integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==" + }, + "node_modules/cross-spawn": { + "version": "7.0.3", + "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz", + "integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==", + "dev": true, + "dependencies": { + "path-key": "^3.1.0", + "shebang-command": "^2.0.0", + "which": "^2.0.1" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/cross-spawn/node_modules/isexe": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", + "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==", + "dev": true + }, + "node_modules/cross-spawn/node_modules/which": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz", + "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==", + "dev": true, + "dependencies": { + "isexe": "^2.0.0" + }, + "bin": { + "node-which": "bin/node-which" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/css-select": { + "version": "5.1.0", + "resolved": "https://registry.npmjs.org/css-select/-/css-select-5.1.0.tgz", + "integrity": "sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==", + "dependencies": { + "boolbase": "^1.0.0", + "css-what": "^6.1.0", + "domhandler": "^5.0.2", + "domutils": "^3.0.1", + "nth-check": "^2.0.1" + }, + "funding": { + "url": "https://github.com/sponsors/fb55" + } + }, + "node_modules/css-what": { + "version": "6.1.0", + "resolved": "https://registry.npmjs.org/css-what/-/css-what-6.1.0.tgz", + "integrity": "sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw==", + "engines": { + "node": ">= 6" + }, + "funding": { + "url": "https://github.com/sponsors/fb55" + } + }, + "node_modules/dateformat": { + "version": "4.6.3", + "resolved": "https://registry.npmjs.org/dateformat/-/dateformat-4.6.3.tgz", + "integrity": "sha512-2P0p0pFGzHS5EMnhdxQi7aJN+iMheud0UhG4dlE1DLAlvL8JHjJJTX/CSm4JXwV0Ka5nGk3zC5mcb5bUQUxxMA==", + "engines": { + "node": "*" + } + }, + "node_modules/debug": { + "version": "4.3.4", + "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.4.tgz", + "integrity": "sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==", + "dev": true, + "dependencies": { + "ms": "2.1.2" + }, + "engines": { + "node": ">=6.0" + }, + "peerDependenciesMeta": { + "supports-color": { + "optional": true + } + } + }, + "node_modules/deep-is": { + "version": "0.1.4", + "resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz", + "integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==", + "dev": true + }, + "node_modules/detect-file": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/detect-file/-/detect-file-1.0.0.tgz", + "integrity": "sha512-DtCOLG98P007x7wiiOmfI0fi3eIKyWiLTGJ2MDnVi/E04lWGbf+JzrRHMm0rgIIZJGtHpKpbVgLWHrv8xXpc3Q==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/dom-serializer": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-2.0.0.tgz", + "integrity": "sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==", + "dependencies": { + "domelementtype": "^2.3.0", + "domhandler": "^5.0.2", + "entities": "^4.2.0" + }, + "funding": { + "url": "https://github.com/cheeriojs/dom-serializer?sponsor=1" + } + }, + "node_modules/domelementtype": { + "version": "2.3.0", + "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.3.0.tgz", + "integrity": "sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==", + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/fb55" + } + ] + }, + "node_modules/domhandler": { + "version": "5.0.3", + "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-5.0.3.tgz", + "integrity": "sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==", + "dependencies": { + "domelementtype": "^2.3.0" + }, + "engines": { + "node": ">= 4" + }, + "funding": { + "url": "https://github.com/fb55/domhandler?sponsor=1" + } + }, + "node_modules/domutils": { + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/domutils/-/domutils-3.1.0.tgz", + "integrity": "sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==", + "dependencies": { + "dom-serializer": "^2.0.0", + "domelementtype": "^2.3.0", + "domhandler": "^5.0.3" + }, + "funding": { + "url": "https://github.com/fb55/domutils?sponsor=1" + } + }, + "node_modules/entities": { + "version": "4.5.0", + "resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz", + "integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==", + "engines": { + "node": ">=0.12" + }, + "funding": { + "url": "https://github.com/fb55/entities?sponsor=1" + } + }, + "node_modules/escape-string-regexp": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz", + "integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==", + "dev": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/eslint": { + "version": "9.0.0", + "resolved": "https://registry.npmjs.org/eslint/-/eslint-9.0.0.tgz", + "integrity": "sha512-IMryZ5SudxzQvuod6rUdIUz29qFItWx281VhtFVc2Psy/ZhlCeD/5DT6lBIJ4H3G+iamGJoTln1v+QSuPw0p7Q==", + "dev": true, + "dependencies": { + "@eslint-community/eslint-utils": "^4.2.0", + "@eslint-community/regexpp": "^4.6.1", + "@eslint/eslintrc": "^3.0.2", + "@eslint/js": "9.0.0", + "@humanwhocodes/config-array": "^0.12.3", + "@humanwhocodes/module-importer": "^1.0.1", + "@nodelib/fs.walk": "^1.2.8", + "ajv": "^6.12.4", + "chalk": "^4.0.0", + "cross-spawn": "^7.0.2", + "debug": "^4.3.2", + "escape-string-regexp": "^4.0.0", + "eslint-scope": "^8.0.1", + "eslint-visitor-keys": "^4.0.0", + "espree": "^10.0.1", + "esquery": "^1.4.2", + "esutils": "^2.0.2", + "fast-deep-equal": "^3.1.3", + "file-entry-cache": "^8.0.0", + "find-up": "^5.0.0", + "glob-parent": "^6.0.2", + "graphemer": "^1.4.0", + "ignore": "^5.2.0", + "imurmurhash": "^0.1.4", + "is-glob": "^4.0.0", + "is-path-inside": "^3.0.3", + "json-stable-stringify-without-jsonify": "^1.0.1", + "levn": "^0.4.1", + "lodash.merge": "^4.6.2", + "minimatch": "^3.1.2", + "natural-compare": "^1.4.0", + "optionator": "^0.9.3", + "strip-ansi": "^6.0.1", + "text-table": "^0.2.0" + }, + "bin": { + "eslint": "bin/eslint.js" + }, + "engines": { + "node": "^18.18.0 || ^20.9.0 || >=21.1.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" + } + }, + "node_modules/eslint-config-jquery": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/eslint-config-jquery/-/eslint-config-jquery-3.0.2.tgz", + "integrity": "sha512-1CdP7AY5ZuhDGUXz+/b7FwhRnDoK0A1swz+2nZ+zpEYJ3EyV085AOAfpFJL2s+ioHDspNQEsGSsl9uUEm9/f/g==", + "dev": true + }, + "node_modules/eslint-scope": { + "version": "8.0.1", + "resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-8.0.1.tgz", + "integrity": "sha512-pL8XjgP4ZOmmwfFE8mEhSxA7ZY4C+LWyqjQ3o4yWkkmD0qcMT9kkW3zWHOczhWcjTSgqycYAgwSlXvZltv65og==", + "dev": true, + "dependencies": { + "esrecurse": "^4.3.0", + "estraverse": "^5.2.0" + }, + "engines": { + "node": "^18.18.0 || ^20.9.0 || >=21.1.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" + } + }, + "node_modules/eslint-visitor-keys": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-4.0.0.tgz", + "integrity": "sha512-OtIRv/2GyiF6o/d8K7MYKKbXrOUBIK6SfkIRM4Z0dY3w+LiQ0vy3F57m0Z71bjbyeiWFiHJ8brqnmE6H6/jEuw==", + "dev": true, + "engines": { + "node": "^18.18.0 || ^20.9.0 || >=21.1.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" + } + }, + "node_modules/eslint/node_modules/minimatch": { + "version": "3.1.2", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", + "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", + "dev": true, + "dependencies": { + "brace-expansion": "^1.1.7" + }, + "engines": { + "node": "*" + } + }, + "node_modules/espree": { + "version": "10.0.1", + "resolved": "https://registry.npmjs.org/espree/-/espree-10.0.1.tgz", + "integrity": "sha512-MWkrWZbJsL2UwnjxTX3gG8FneachS/Mwg7tdGXce011sJd5b0JG54vat5KHnfSBODZ3Wvzd2WnjxyzsRoVv+ww==", + "dev": true, + "dependencies": { + "acorn": "^8.11.3", + "acorn-jsx": "^5.3.2", + "eslint-visitor-keys": "^4.0.0" + }, + "engines": { + "node": "^18.18.0 || ^20.9.0 || >=21.1.0" + }, + "funding": { + "url": "https://opencollective.com/eslint" + } + }, + "node_modules/esprima": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz", + "integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==", + "bin": { + "esparse": "bin/esparse.js", + "esvalidate": "bin/esvalidate.js" + }, + "engines": { + "node": ">=4" + } + }, + "node_modules/esquery": { + "version": "1.5.0", + "resolved": "https://registry.npmjs.org/esquery/-/esquery-1.5.0.tgz", + "integrity": "sha512-YQLXUplAwJgCydQ78IMJywZCceoqk1oH01OERdSAJc/7U2AylwjhSCLDEtqwg811idIS/9fIU5GjG73IgjKMVg==", + "dev": true, + "dependencies": { + "estraverse": "^5.1.0" + }, + "engines": { + "node": ">=0.10" + } + }, + "node_modules/esrecurse": { + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz", + "integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==", + "dev": true, + "dependencies": { + "estraverse": "^5.2.0" + }, + "engines": { + "node": ">=4.0" + } + }, + "node_modules/estraverse": { + "version": "5.3.0", + "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz", + "integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==", + "dev": true, + "engines": { + "node": ">=4.0" + } + }, + "node_modules/esutils": { + "version": "2.0.3", + "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz", + "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==", + "dev": true, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/eventemitter2": { + "version": "0.4.14", + "resolved": "https://registry.npmjs.org/eventemitter2/-/eventemitter2-0.4.14.tgz", + "integrity": "sha512-K7J4xq5xAD5jHsGM5ReWXRTFa3JRGofHiMcVgQ8PRwgWxzjHpMWCIzsmyf60+mh8KLsqYPcjUMa0AC4hd6lPyQ==" + }, + "node_modules/exit": { + "version": "0.1.2", + "resolved": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz", + "integrity": "sha512-Zk/eNKV2zbjpKzrsQ+n1G6poVbErQxJ0LBOJXaKZ1EViLzH+hrLu9cdXI4zw9dBQJslwBEpbQ2P1oS7nDxs6jQ==", + "engines": { + "node": ">= 0.8.0" + } + }, + "node_modules/expand-tilde": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/expand-tilde/-/expand-tilde-2.0.2.tgz", + "integrity": "sha512-A5EmesHW6rfnZ9ysHQjPdJRni0SRar0tjtG5MNtm9n5TUvsYU8oozprtRD4AqHxcZWWlVuAmQo2nWKfN9oyjTw==", + "dependencies": { + "homedir-polyfill": "^1.0.1" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/extend": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/extend/-/extend-3.0.2.tgz", + "integrity": "sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==" + }, + "node_modules/fast-deep-equal": { + "version": "3.1.3", + "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", + "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==", + "dev": true + }, + "node_modules/fast-json-stable-stringify": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz", + "integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==", + "dev": true + }, + "node_modules/fast-levenshtein": { + "version": "2.0.6", + "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz", + "integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==", + "dev": true + }, + "node_modules/fastq": { + "version": "1.17.1", + "resolved": "https://registry.npmjs.org/fastq/-/fastq-1.17.1.tgz", + "integrity": "sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==", + "dev": true, + "dependencies": { + "reusify": "^1.0.4" + } + }, + "node_modules/file-entry-cache": { + "version": "8.0.0", + "resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-8.0.0.tgz", + "integrity": "sha512-XXTUwCvisa5oacNGRP9SfNtYBNAMi+RPwBFmblZEF7N7swHYQS6/Zfk7SRwx4D5j3CH211YNRco1DEMNVfZCnQ==", + "dev": true, + "dependencies": { + "flat-cache": "^4.0.0" + }, + "engines": { + "node": ">=16.0.0" + } + }, + "node_modules/fill-range": { + "version": "7.0.1", + "resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz", + "integrity": "sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==", + "dependencies": { + "to-regex-range": "^5.0.1" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/find-up": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz", + "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==", + "dev": true, + "dependencies": { + "locate-path": "^6.0.0", + "path-exists": "^4.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/findup-sync": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-5.0.0.tgz", + "integrity": "sha512-MzwXju70AuyflbgeOhzvQWAvvQdo1XL0A9bVvlXsYcFEBM87WR4OakL4OfZq+QRmr+duJubio+UtNQCPsVESzQ==", + "dependencies": { + "detect-file": "^1.0.0", + "is-glob": "^4.0.3", + "micromatch": "^4.0.4", + "resolve-dir": "^1.0.1" + }, + "engines": { + "node": ">= 10.13.0" + } + }, + "node_modules/fined": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/fined/-/fined-1.2.0.tgz", + "integrity": "sha512-ZYDqPLGxDkDhDZBjZBb+oD1+j0rA4E0pXY50eplAAOPg2N/gUBSSk5IM1/QhPfyVo19lJ+CvXpqfvk+b2p/8Ng==", + "dependencies": { + "expand-tilde": "^2.0.2", + "is-plain-object": "^2.0.3", + "object.defaults": "^1.1.0", + "object.pick": "^1.2.0", + "parse-filepath": "^1.0.1" + }, + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/flagged-respawn": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/flagged-respawn/-/flagged-respawn-1.0.1.tgz", + "integrity": "sha512-lNaHNVymajmk0OJMBn8fVUAU1BtDeKIqKoVhk4xAALB57aALg6b4W0MfJ/cUE0g9YBXy5XhSlPIpYIJ7HaY/3Q==", + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/flat-cache": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-4.0.1.tgz", + "integrity": "sha512-f7ccFPK3SXFHpx15UIGyRJ/FJQctuKZ0zVuN3frBo4HnK3cay9VEW0R6yPYFHC0AgqhukPzKjq22t5DmAyqGyw==", + "dev": true, + "dependencies": { + "flatted": "^3.2.9", + "keyv": "^4.5.4" + }, + "engines": { + "node": ">=16" + } + }, + "node_modules/flatted": { + "version": "3.3.1", + "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.3.1.tgz", + "integrity": "sha512-X8cqMLLie7KsNUDSdzeN8FYK9rEt4Dt67OsG/DNGnYTSDBG4uFAJFBnUeiV+zCVAvwFy56IjM9sH51jVaEhNxw==", + "dev": true + }, + "node_modules/for-in": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/for-in/-/for-in-1.0.2.tgz", + "integrity": "sha512-7EwmXrOjyL+ChxMhmG5lnW9MPt1aIeZEwKhQzoBUdTV0N3zuwWDZYVJatDvZ2OyzPUvdIAZDsCetk3coyMfcnQ==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/for-own": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/for-own/-/for-own-1.0.0.tgz", + "integrity": "sha512-0OABksIGrxKK8K4kynWkQ7y1zounQxP+CWnyclVwj81KW3vlLlGUx57DKGcP/LH216GzqnstnPocF16Nxs0Ycg==", + "dependencies": { + "for-in": "^1.0.1" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/fs.realpath": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz", + "integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==" + }, + "node_modules/function-bind": { + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz", + "integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==", + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/getobject": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/getobject/-/getobject-1.0.2.tgz", + "integrity": "sha512-2zblDBaFcb3rB4rF77XVnuINOE2h2k/OnqXAiy0IrTxUfV1iFp3la33oAQVY9pCpWU268WFYVt2t71hlMuLsOg==", + "engines": { + "node": ">=10" + } + }, + "node_modules/gilded-wordpress": { + "version": "1.0.7", + "resolved": "https://registry.npmjs.org/gilded-wordpress/-/gilded-wordpress-1.0.7.tgz", + "integrity": "sha512-w8g4jfs1TWywX2hZ4+LlzQoz2z/JRX/8S6OgelD3IUsNnGHxXQ1FgExoIqomwZVPAmxYs0vEu2BeA1Y4KciZlw==", + "dependencies": { + "async": "^0.9.0", + "wordpress": "^1.4.2" + } + }, + "node_modules/glob": { + "version": "7.1.7", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.1.7.tgz", + "integrity": "sha512-OvD9ENzPLbegENnYP5UUfJIirTg4+XwMWGaQfQTY0JenxNvvIKP3U3/tAQSPIu/lHxXYSZmpXlUHeqAIdKzBLQ==", + "dependencies": { + "fs.realpath": "^1.0.0", + "inflight": "^1.0.4", + "inherits": "2", + "minimatch": "^3.0.4", + "once": "^1.3.0", + "path-is-absolute": "^1.0.0" + }, + "engines": { + "node": "*" + }, + "funding": { + "url": "https://github.com/sponsors/isaacs" + } + }, + "node_modules/glob-parent": { + "version": "6.0.2", + "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz", + "integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==", + "dev": true, + "dependencies": { + "is-glob": "^4.0.3" + }, + "engines": { + "node": ">=10.13.0" + } + }, + "node_modules/global-modules": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/global-modules/-/global-modules-1.0.0.tgz", + "integrity": "sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==", + "dependencies": { + "global-prefix": "^1.0.1", + "is-windows": "^1.0.1", + "resolve-dir": "^1.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/global-prefix": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/global-prefix/-/global-prefix-1.0.2.tgz", + "integrity": "sha512-5lsx1NUDHtSjfg0eHlmYvZKv8/nVqX4ckFbM+FrGcQ+04KWcWFo9P5MxPZYSzUvyzmdTbI7Eix8Q4IbELDqzKg==", + "dependencies": { + "expand-tilde": "^2.0.2", + "homedir-polyfill": "^1.0.1", + "ini": "^1.3.4", + "is-windows": "^1.0.1", + "which": "^1.2.14" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/global-prefix/node_modules/isexe": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", + "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==" + }, + "node_modules/global-prefix/node_modules/which": { + "version": "1.3.1", + "resolved": "https://registry.npmjs.org/which/-/which-1.3.1.tgz", + "integrity": "sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==", + "dependencies": { + "isexe": "^2.0.0" + }, + "bin": { + "which": "bin/which" + } + }, + "node_modules/globals": { + "version": "15.0.0", + "resolved": "https://registry.npmjs.org/globals/-/globals-15.0.0.tgz", + "integrity": "sha512-m/C/yR4mjO6pXDTm9/R/SpYTAIyaUB4EOzcaaMEl7mds7Mshct9GfejiJNQGjHHbdMPey13Kpu4TMbYi9ex1pw==", + "dev": true, + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/graphemer": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/graphemer/-/graphemer-1.4.0.tgz", + "integrity": "sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==", + "dev": true + }, + "node_modules/grunt": { + "version": "1.6.1", + "resolved": "https://registry.npmjs.org/grunt/-/grunt-1.6.1.tgz", + "integrity": "sha512-/ABUy3gYWu5iBmrUSRBP97JLpQUm0GgVveDCp6t3yRNIoltIYw7rEj3g5y1o2PGPR2vfTRGa7WC/LZHLTXnEzA==", + "dependencies": { + "dateformat": "~4.6.2", + "eventemitter2": "~0.4.13", + "exit": "~0.1.2", + "findup-sync": "~5.0.0", + "glob": "~7.1.6", + "grunt-cli": "~1.4.3", + "grunt-known-options": "~2.0.0", + "grunt-legacy-log": "~3.0.0", + "grunt-legacy-util": "~2.0.1", + "iconv-lite": "~0.6.3", + "js-yaml": "~3.14.0", + "minimatch": "~3.0.4", + "nopt": "~3.0.6" + }, + "bin": { + "grunt": "bin/grunt" + }, + "engines": { + "node": ">=16" + } + }, + "node_modules/grunt-check-modules": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/grunt-check-modules/-/grunt-check-modules-1.1.0.tgz", + "integrity": "sha512-B0dWhmnqEZztfDbqEb5UWAI/9o0mmlRPEyJYdpitgr/W7i1893cq4hmN+Vw+xJEC/+A5vzmaaHfDZU3fO8JheQ==", + "engines": { + "node": ">=0.6.0" + }, + "peerDependencies": { + "grunt": ">=0.4.0" + } + }, + "node_modules/grunt-cli": { + "version": "1.4.3", + "resolved": "https://registry.npmjs.org/grunt-cli/-/grunt-cli-1.4.3.tgz", + "integrity": "sha512-9Dtx/AhVeB4LYzsViCjUQkd0Kw0McN2gYpdmGYKtE2a5Yt7v1Q+HYZVWhqXc/kGnxlMtqKDxSwotiGeFmkrCoQ==", + "dependencies": { + "grunt-known-options": "~2.0.0", + "interpret": "~1.1.0", + "liftup": "~3.0.1", + "nopt": "~4.0.1", + "v8flags": "~3.2.0" + }, + "bin": { + "grunt": "bin/grunt" + }, + "engines": { + "node": ">=10" + } + }, + "node_modules/grunt-cli/node_modules/nopt": { + "version": "4.0.3", + "resolved": "https://registry.npmjs.org/nopt/-/nopt-4.0.3.tgz", + "integrity": "sha512-CvaGwVMztSMJLOeXPrez7fyfObdZqNUK1cPAEzLHrTybIua9pMdmmPR5YwtfNftIOMv3DPUhFaxsZMNTQO20Kg==", + "dependencies": { + "abbrev": "1", + "osenv": "^0.1.4" + }, + "bin": { + "nopt": "bin/nopt.js" + } + }, + "node_modules/grunt-jquery-content": { + "version": "3.3.1", + "resolved": "https://registry.npmjs.org/grunt-jquery-content/-/grunt-jquery-content-3.3.1.tgz", + "integrity": "sha512-aK4DdMYkM+qjSyXkEswvlSTHqcWDfvKKjWveeDLK/dIM1Ok7iXGd1SwFuFp2ShO+rx9XEHToX3KC5+Gn2BwAug==", + "dependencies": { + "cheerio": "^1.0.0-rc.12", + "gilded-wordpress": "1.0.7", + "grunt-check-modules": "^1.1.0", + "he": "^1.2.0", + "highlight.js": "^10.7.2", + "marked": "^4.0.0", + "which": "^4.0.0", + "wordpress": "^1.4.1" + } + }, + "node_modules/grunt-known-options": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/grunt-known-options/-/grunt-known-options-2.0.0.tgz", + "integrity": "sha512-GD7cTz0I4SAede1/+pAbmJRG44zFLPipVtdL9o3vqx9IEyb7b4/Y3s7r6ofI3CchR5GvYJ+8buCSioDv5dQLiA==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/grunt-legacy-log": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/grunt-legacy-log/-/grunt-legacy-log-3.0.0.tgz", + "integrity": "sha512-GHZQzZmhyq0u3hr7aHW4qUH0xDzwp2YXldLPZTCjlOeGscAOWWPftZG3XioW8MasGp+OBRIu39LFx14SLjXRcA==", + "dependencies": { + "colors": "~1.1.2", + "grunt-legacy-log-utils": "~2.1.0", + "hooker": "~0.2.3", + "lodash": "~4.17.19" + }, + "engines": { + "node": ">= 0.10.0" + } + }, + "node_modules/grunt-legacy-log-utils": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/grunt-legacy-log-utils/-/grunt-legacy-log-utils-2.1.0.tgz", + "integrity": "sha512-lwquaPXJtKQk0rUM1IQAop5noEpwFqOXasVoedLeNzaibf/OPWjKYvvdqnEHNmU+0T0CaReAXIbGo747ZD+Aaw==", + "dependencies": { + "chalk": "~4.1.0", + "lodash": "~4.17.19" + }, + "engines": { + "node": ">=10" + } + }, + "node_modules/grunt-legacy-util": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/grunt-legacy-util/-/grunt-legacy-util-2.0.1.tgz", + "integrity": "sha512-2bQiD4fzXqX8rhNdXkAywCadeqiPiay0oQny77wA2F3WF4grPJXCvAcyoWUJV+po/b15glGkxuSiQCK299UC2w==", + "dependencies": { + "async": "~3.2.0", + "exit": "~0.1.2", + "getobject": "~1.0.0", + "hooker": "~0.2.3", + "lodash": "~4.17.21", + "underscore.string": "~3.3.5", + "which": "~2.0.2" + }, + "engines": { + "node": ">=10" + } + }, + "node_modules/grunt-legacy-util/node_modules/async": { + "version": "3.2.5", + "resolved": "https://registry.npmjs.org/async/-/async-3.2.5.tgz", + "integrity": "sha512-baNZyqaaLhyLVKm/DlvdW051MSgO6b8eVfIezl9E5PqWxFgzLm/wQntEW4zOytVburDEr0JlALEpdOFwvErLsg==" + }, + "node_modules/grunt-legacy-util/node_modules/isexe": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", + "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==" + }, + "node_modules/grunt-legacy-util/node_modules/which": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz", + "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==", + "dependencies": { + "isexe": "^2.0.0" + }, + "bin": { + "node-which": "bin/node-which" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/has-flag": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz", + "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==", + "engines": { + "node": ">=8" + } + }, + "node_modules/hasown": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.2.tgz", + "integrity": "sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==", + "dependencies": { + "function-bind": "^1.1.2" + }, + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/he": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/he/-/he-1.2.0.tgz", + "integrity": "sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==", + "bin": { + "he": "bin/he" + } + }, + "node_modules/highlight.js": { + "version": "10.7.3", + "resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-10.7.3.tgz", + "integrity": "sha512-tzcUFauisWKNHaRkN4Wjl/ZA07gENAjFl3J/c480dprkGTg5EQstgaNFqBfUqCq54kZRIEcreTsAgF/m2quD7A==", + "engines": { + "node": "*" + } + }, + "node_modules/homedir-polyfill": { + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/homedir-polyfill/-/homedir-polyfill-1.0.3.tgz", + "integrity": "sha512-eSmmWE5bZTK2Nou4g0AI3zZ9rswp7GRKoKXS1BLUkvPviOqs4YTN1djQIqrXy9k5gEtdLPy86JjRwsNM9tnDcA==", + "dependencies": { + "parse-passwd": "^1.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/hooker": { + "version": "0.2.3", + "resolved": "https://registry.npmjs.org/hooker/-/hooker-0.2.3.tgz", + "integrity": "sha512-t+UerCsQviSymAInD01Pw+Dn/usmz1sRO+3Zk1+lx8eg+WKpD2ulcwWqHHL0+aseRBr+3+vIhiG1K1JTwaIcTA==", + "engines": { + "node": "*" + } + }, + "node_modules/htmlparser2": { + "version": "8.0.2", + "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-8.0.2.tgz", + "integrity": "sha512-GYdjWKDkbRLkZ5geuHs5NY1puJ+PXwP7+fHPRz06Eirsb9ugf6d8kkXav6ADhcODhFFPMIXyxkxSuMf3D6NCFA==", + "funding": [ + "https://github.com/fb55/htmlparser2?sponsor=1", + { + "type": "github", + "url": "https://github.com/sponsors/fb55" + } + ], + "dependencies": { + "domelementtype": "^2.3.0", + "domhandler": "^5.0.3", + "domutils": "^3.0.1", + "entities": "^4.4.0" + } + }, + "node_modules/iconv-lite": { + "version": "0.6.3", + "resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.6.3.tgz", + "integrity": "sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==", + "dependencies": { + "safer-buffer": ">= 2.1.2 < 3.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/ignore": { + "version": "5.3.1", + "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.1.tgz", + "integrity": "sha512-5Fytz/IraMjqpwfd34ke28PTVMjZjJG2MPn5t7OE4eUCUNf8BAa7b5WUS9/Qvr6mwOQS7Mk6vdsMno5he+T8Xw==", + "dev": true, + "engines": { + "node": ">= 4" + } + }, + "node_modules/import-fresh": { + "version": "3.3.0", + "resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz", + "integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==", + "dev": true, + "dependencies": { + "parent-module": "^1.0.0", + "resolve-from": "^4.0.0" + }, + "engines": { + "node": ">=6" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/imurmurhash": { + "version": "0.1.4", + "resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz", + "integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==", + "dev": true, + "engines": { + "node": ">=0.8.19" + } + }, + "node_modules/inflight": { + "version": "1.0.6", + "resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz", + "integrity": "sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==", + "dependencies": { + "once": "^1.3.0", + "wrappy": "1" + } + }, + "node_modules/inherits": { + "version": "2.0.4", + "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz", + "integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==" + }, + "node_modules/ini": { + "version": "1.3.8", + "resolved": "https://registry.npmjs.org/ini/-/ini-1.3.8.tgz", + "integrity": "sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==" + }, + "node_modules/interpret": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/interpret/-/interpret-1.1.0.tgz", + "integrity": "sha512-CLM8SNMDu7C5psFCn6Wg/tgpj/bKAg7hc2gWqcuR9OD5Ft9PhBpIu8PLicPeis+xDd6YX2ncI8MCA64I9tftIA==" + }, + "node_modules/is-absolute": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/is-absolute/-/is-absolute-1.0.0.tgz", + "integrity": "sha512-dOWoqflvcydARa360Gvv18DZ/gRuHKi2NU/wU5X1ZFzdYfH29nkiNZsF3mp4OJ3H4yo9Mx8A/uAGNzpzPN3yBA==", + "dependencies": { + "is-relative": "^1.0.0", + "is-windows": "^1.0.1" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/is-core-module": { + "version": "2.13.1", + "resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.13.1.tgz", + "integrity": "sha512-hHrIjvZsftOsvKSn2TRYl63zvxsgE0K+0mYMoH6gD4omR5IWB2KynivBQczo3+wF1cCkjzvptnI9Q0sPU66ilw==", + "dependencies": { + "hasown": "^2.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/is-extglob": { + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz", + "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/is-glob": { + "version": "4.0.3", + "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz", + "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==", + "dependencies": { + "is-extglob": "^2.1.1" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/is-number": { + "version": "7.0.0", + "resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz", + "integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==", + "engines": { + "node": ">=0.12.0" + } + }, + "node_modules/is-path-inside": { + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-3.0.3.tgz", + "integrity": "sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/is-plain-object": { + "version": "2.0.4", + "resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-2.0.4.tgz", + "integrity": "sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==", + "dependencies": { + "isobject": "^3.0.1" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/is-relative": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/is-relative/-/is-relative-1.0.0.tgz", + "integrity": "sha512-Kw/ReK0iqwKeu0MITLFuj0jbPAmEiOsIwyIXvvbfa6QfmN9pkD1M+8pdk7Rl/dTKbH34/XBFMbgD4iMJhLQbGA==", + "dependencies": { + "is-unc-path": "^1.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/is-unc-path": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/is-unc-path/-/is-unc-path-1.0.0.tgz", + "integrity": "sha512-mrGpVd0fs7WWLfVsStvgF6iEJnbjDFZh9/emhRDcGWTduTfNHd9CHeUwH3gYIjdbwo4On6hunkztwOaAw0yllQ==", + "dependencies": { + "unc-path-regex": "^0.1.2" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/is-windows": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/is-windows/-/is-windows-1.0.2.tgz", + "integrity": "sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/isexe": { + "version": "3.1.1", + "resolved": "https://registry.npmjs.org/isexe/-/isexe-3.1.1.tgz", + "integrity": "sha512-LpB/54B+/2J5hqQ7imZHfdU31OlgQqx7ZicVlkm9kzg9/w8GKLEcFfJl/t7DCEDueOyBAD6zCCwTO6Fzs0NoEQ==", + "engines": { + "node": ">=16" + } + }, + "node_modules/isobject": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz", + "integrity": "sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/js-yaml": { + "version": "3.14.1", + "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.1.tgz", + "integrity": "sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==", + "dependencies": { + "argparse": "^1.0.7", + "esprima": "^4.0.0" + }, + "bin": { + "js-yaml": "bin/js-yaml.js" + } + }, + "node_modules/json-buffer": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.1.tgz", + "integrity": "sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==", + "dev": true + }, + "node_modules/json-schema-traverse": { + "version": "0.4.1", + "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz", + "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==", + "dev": true + }, + "node_modules/json-stable-stringify-without-jsonify": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz", + "integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==", + "dev": true + }, + "node_modules/keyv": { + "version": "4.5.4", + "resolved": "https://registry.npmjs.org/keyv/-/keyv-4.5.4.tgz", + "integrity": "sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==", + "dev": true, + "dependencies": { + "json-buffer": "3.0.1" + } + }, + "node_modules/kind-of": { + "version": "6.0.3", + "resolved": "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz", + "integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/levn": { + "version": "0.4.1", + "resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz", + "integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==", + "dev": true, + "dependencies": { + "prelude-ls": "^1.2.1", + "type-check": "~0.4.0" + }, + "engines": { + "node": ">= 0.8.0" + } + }, + "node_modules/liftup": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/liftup/-/liftup-3.0.1.tgz", + "integrity": "sha512-yRHaiQDizWSzoXk3APcA71eOI/UuhEkNN9DiW2Tt44mhYzX4joFoCZlxsSOF7RyeLlfqzFLQI1ngFq3ggMPhOw==", + "dependencies": { + "extend": "^3.0.2", + "findup-sync": "^4.0.0", + "fined": "^1.2.0", + "flagged-respawn": "^1.0.1", + "is-plain-object": "^2.0.4", + "object.map": "^1.0.1", + "rechoir": "^0.7.0", + "resolve": "^1.19.0" + }, + "engines": { + "node": ">=10" + } + }, + "node_modules/liftup/node_modules/findup-sync": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-4.0.0.tgz", + "integrity": "sha512-6jvvn/12IC4quLBL1KNokxC7wWTvYncaVUYSoxWw7YykPLuRrnv4qdHcSOywOI5RpkOVGeQRtWM8/q+G6W6qfQ==", + "dependencies": { + "detect-file": "^1.0.0", + "is-glob": "^4.0.0", + "micromatch": "^4.0.2", + "resolve-dir": "^1.0.1" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/locate-path": { + "version": "6.0.0", + "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz", + "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", + "dev": true, + "dependencies": { + "p-locate": "^5.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/lodash": { + "version": "4.17.21", + "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz", + "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==" + }, + "node_modules/lodash.merge": { + "version": "4.6.2", + "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz", + "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==", + "dev": true + }, + "node_modules/make-iterator": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/make-iterator/-/make-iterator-1.0.1.tgz", + "integrity": "sha512-pxiuXh0iVEq7VM7KMIhs5gxsfxCux2URptUQaXo4iZZJxBAzTPOLE2BumO5dbfVYq/hBJFBR/a1mFDmOx5AGmw==", + "dependencies": { + "kind-of": "^6.0.2" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/map-cache": { + "version": "0.2.2", + "resolved": "https://registry.npmjs.org/map-cache/-/map-cache-0.2.2.tgz", + "integrity": "sha512-8y/eV9QQZCiyn1SprXSrCmqJN0yNRATe+PO8ztwqrvrbdRLA3eYJF0yaR0YayLWkMbsQSKWS9N2gPcGEc4UsZg==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/marked": { + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/marked/-/marked-4.3.0.tgz", + "integrity": "sha512-PRsaiG84bK+AMvxziE/lCFss8juXjNaWzVbN5tXAm4XjeaS9NAHhop+PjQxz2A9h8Q4M/xGmzP8vqNwy6JeK0A==", + "bin": { + "marked": "bin/marked.js" + }, + "engines": { + "node": ">= 12" + } + }, + "node_modules/micromatch": { + "version": "4.0.5", + "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz", + "integrity": "sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==", + "dependencies": { + "braces": "^3.0.2", + "picomatch": "^2.3.1" + }, + "engines": { + "node": ">=8.6" + } + }, + "node_modules/minimatch": { + "version": "3.0.8", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.8.tgz", + "integrity": "sha512-6FsRAQsxQ61mw+qP1ZzbL9Bc78x2p5OqNgNpnoAFLTrX8n5Kxph0CsnhmKKNXTWjXqU5L0pGPR7hYk+XWZr60Q==", + "dependencies": { + "brace-expansion": "^1.1.7" + }, + "engines": { + "node": "*" + } + }, + "node_modules/ms": { + "version": "2.1.2", + "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz", + "integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==", + "dev": true + }, + "node_modules/natural-compare": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz", + "integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==", + "dev": true + }, + "node_modules/nopt": { + "version": "3.0.6", + "resolved": "https://registry.npmjs.org/nopt/-/nopt-3.0.6.tgz", + "integrity": "sha512-4GUt3kSEYmk4ITxzB/b9vaIDfUVWN/Ml1Fwl11IlnIG2iaJ9O6WXZ9SrYM9NLI8OCBieN2Y8SWC2oJV0RQ7qYg==", + "dependencies": { + "abbrev": "1" + }, + "bin": { + "nopt": "bin/nopt.js" + } + }, + "node_modules/nth-check": { + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.1.1.tgz", + "integrity": "sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==", + "dependencies": { + "boolbase": "^1.0.0" + }, + "funding": { + "url": "https://github.com/fb55/nth-check?sponsor=1" + } + }, + "node_modules/object.defaults": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/object.defaults/-/object.defaults-1.1.0.tgz", + "integrity": "sha512-c/K0mw/F11k4dEUBMW8naXUuBuhxRCfG7W+yFy8EcijU/rSmazOUd1XAEEe6bC0OuXY4HUKjTJv7xbxIMqdxrA==", + "dependencies": { + "array-each": "^1.0.1", + "array-slice": "^1.0.0", + "for-own": "^1.0.0", + "isobject": "^3.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/object.map": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/object.map/-/object.map-1.0.1.tgz", + "integrity": "sha512-3+mAJu2PLfnSVGHwIWubpOFLscJANBKuB/6A4CxBstc4aqwQY0FWcsppuy4jU5GSB95yES5JHSI+33AWuS4k6w==", + "dependencies": { + "for-own": "^1.0.0", + "make-iterator": "^1.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/object.pick": { + "version": "1.3.0", + "resolved": "https://registry.npmjs.org/object.pick/-/object.pick-1.3.0.tgz", + "integrity": "sha512-tqa/UMy/CCoYmj+H5qc07qvSL9dqcs/WZENZ1JbtWBlATP+iVOe778gE6MSijnyCnORzDuX6hU+LA4SZ09YjFQ==", + "dependencies": { + "isobject": "^3.0.1" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/once": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz", + "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==", + "dependencies": { + "wrappy": "1" + } + }, + "node_modules/optionator": { + "version": "0.9.3", + "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.3.tgz", + "integrity": "sha512-JjCoypp+jKn1ttEFExxhetCKeJt9zhAgAve5FXHixTvFDW/5aEktX9bufBKLRRMdU7bNtpLfcGu94B3cdEJgjg==", + "dev": true, + "dependencies": { + "@aashutoshrathi/word-wrap": "^1.2.3", + "deep-is": "^0.1.3", + "fast-levenshtein": "^2.0.6", + "levn": "^0.4.1", + "prelude-ls": "^1.2.1", + "type-check": "^0.4.0" + }, + "engines": { + "node": ">= 0.8.0" + } + }, + "node_modules/os-homedir": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.2.tgz", + "integrity": "sha512-B5JU3cabzk8c67mRRd3ECmROafjYMXbuzlwtqdM8IbS8ktlTix8aFGb2bAGKrSRIlnfKwovGUUr72JUPyOb6kQ==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/os-tmpdir": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.2.tgz", + "integrity": "sha512-D2FR03Vir7FIu45XBY20mTb+/ZSWB00sjU9jdQXt83gDrI4Ztz5Fs7/yy74g2N5SVQY4xY1qDr4rNddwYRVX0g==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/osenv": { + "version": "0.1.5", + "resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.5.tgz", + "integrity": "sha512-0CWcCECdMVc2Rw3U5w9ZjqX6ga6ubk1xDVKxtBQPK7wis/0F2r9T6k4ydGYhecl7YUBxBVxhL5oisPsNxAPe2g==", + "dependencies": { + "os-homedir": "^1.0.0", + "os-tmpdir": "^1.0.0" + } + }, + "node_modules/p-limit": { + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz", + "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==", + "dev": true, + "dependencies": { + "yocto-queue": "^0.1.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/p-locate": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz", + "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==", + "dev": true, + "dependencies": { + "p-limit": "^3.0.2" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/parent-module": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz", + "integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==", + "dev": true, + "dependencies": { + "callsites": "^3.0.0" + }, + "engines": { + "node": ">=6" + } + }, + "node_modules/parse-filepath": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/parse-filepath/-/parse-filepath-1.0.2.tgz", + "integrity": "sha512-FwdRXKCohSVeXqwtYonZTXtbGJKrn+HNyWDYVcp5yuJlesTwNH4rsmRZ+GrKAPJ5bLpRxESMeS+Rl0VCHRvB2Q==", + "dependencies": { + "is-absolute": "^1.0.0", + "map-cache": "^0.2.0", + "path-root": "^0.1.1" + }, + "engines": { + "node": ">=0.8" + } + }, + "node_modules/parse-passwd": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/parse-passwd/-/parse-passwd-1.0.0.tgz", + "integrity": "sha512-1Y1A//QUXEZK7YKz+rD9WydcE1+EuPr6ZBgKecAB8tmoW6UFv0NREVJe1p+jRxtThkcbbKkfwIbWJe/IeE6m2Q==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/parse5": { + "version": "7.1.2", + "resolved": "https://registry.npmjs.org/parse5/-/parse5-7.1.2.tgz", + "integrity": "sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==", + "dependencies": { + "entities": "^4.4.0" + }, + "funding": { + "url": "https://github.com/inikulin/parse5?sponsor=1" + } + }, + "node_modules/parse5-htmlparser2-tree-adapter": { + "version": "7.0.0", + "resolved": "https://registry.npmjs.org/parse5-htmlparser2-tree-adapter/-/parse5-htmlparser2-tree-adapter-7.0.0.tgz", + "integrity": "sha512-B77tOZrqqfUfnVcOrUvfdLbz4pu4RopLD/4vmu3HUPswwTA8OH0EMW9BlWR2B0RCoiZRAHEUu7IxeP1Pd1UU+g==", + "dependencies": { + "domhandler": "^5.0.2", + "parse5": "^7.0.0" + }, + "funding": { + "url": "https://github.com/inikulin/parse5?sponsor=1" + } + }, + "node_modules/path-exists": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz", + "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/path-is-absolute": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz", + "integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/path-key": { + "version": "3.1.1", + "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz", + "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/path-parse": { + "version": "1.0.7", + "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz", + "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==" + }, + "node_modules/path-root": { + "version": "0.1.1", + "resolved": "https://registry.npmjs.org/path-root/-/path-root-0.1.1.tgz", + "integrity": "sha512-QLcPegTHF11axjfojBIoDygmS2E3Lf+8+jI6wOVmNVenrKSo3mFdSGiIgdSHenczw3wPtlVMQaFVwGmM7BJdtg==", + "dependencies": { + "path-root-regex": "^0.1.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/path-root-regex": { + "version": "0.1.2", + "resolved": "https://registry.npmjs.org/path-root-regex/-/path-root-regex-0.1.2.tgz", + "integrity": "sha512-4GlJ6rZDhQZFE0DPVKh0e9jmZ5egZfxTkp7bcRDuPlJXbAwhxcl2dINPUAsjLdejqaLsCeg8axcLjIbvBjN4pQ==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/picomatch": { + "version": "2.3.1", + "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz", + "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==", + "engines": { + "node": ">=8.6" + }, + "funding": { + "url": "https://github.com/sponsors/jonschlinkert" + } + }, + "node_modules/prelude-ls": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz", + "integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==", + "dev": true, + "engines": { + "node": ">= 0.8.0" + } + }, + "node_modules/punycode": { + "version": "2.3.1", + "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.1.tgz", + "integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==", + "dev": true, + "engines": { + "node": ">=6" + } + }, + "node_modules/queue-microtask": { + "version": "1.2.3", + "resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz", + "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/feross" + }, + { + "type": "patreon", + "url": "https://www.patreon.com/feross" + }, + { + "type": "consulting", + "url": "https://feross.org/support" + } + ] + }, + "node_modules/rechoir": { + "version": "0.7.1", + "resolved": "https://registry.npmjs.org/rechoir/-/rechoir-0.7.1.tgz", + "integrity": "sha512-/njmZ8s1wVeR6pjTZ+0nCnv8SpZNRMT2D1RLOJQESlYFDBvwpTA4KWJpZ+sBJ4+vhjILRcK7JIFdGCdxEAAitg==", + "dependencies": { + "resolve": "^1.9.0" + }, + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/resolve": { + "version": "1.22.8", + "resolved": "https://registry.npmjs.org/resolve/-/resolve-1.22.8.tgz", + "integrity": "sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==", + "dependencies": { + "is-core-module": "^2.13.0", + "path-parse": "^1.0.7", + "supports-preserve-symlinks-flag": "^1.0.0" + }, + "bin": { + "resolve": "bin/resolve" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/resolve-dir": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/resolve-dir/-/resolve-dir-1.0.1.tgz", + "integrity": "sha512-R7uiTjECzvOsWSfdM0QKFNBVFcK27aHOUwdvK53BcW8zqnGdYp0Fbj82cy54+2A4P2tFM22J5kRfe1R+lM/1yg==", + "dependencies": { + "expand-tilde": "^2.0.0", + "global-modules": "^1.0.0" + }, + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/resolve-from": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz", + "integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==", + "dev": true, + "engines": { + "node": ">=4" + } + }, + "node_modules/reusify": { + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz", + "integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==", + "dev": true, + "engines": { + "iojs": ">=1.0.0", + "node": ">=0.10.0" + } + }, + "node_modules/run-parallel": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz", + "integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/feross" + }, + { + "type": "patreon", + "url": "https://www.patreon.com/feross" + }, + { + "type": "consulting", + "url": "https://feross.org/support" + } + ], + "dependencies": { + "queue-microtask": "^1.2.2" + } + }, + "node_modules/safer-buffer": { + "version": "2.1.2", + "resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz", + "integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==" + }, + "node_modules/sax": { + "version": "1.2.4", + "resolved": "https://registry.npmjs.org/sax/-/sax-1.2.4.tgz", + "integrity": "sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==" + }, + "node_modules/shebang-command": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz", + "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==", + "dev": true, + "dependencies": { + "shebang-regex": "^3.0.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/shebang-regex": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz", + "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/sprintf-js": { + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz", + "integrity": "sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==" + }, + "node_modules/strip-ansi": { + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", + "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", + "dev": true, + "dependencies": { + "ansi-regex": "^5.0.1" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/strip-json-comments": { + "version": "3.1.1", + "resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz", + "integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==", + "dev": true, + "engines": { + "node": ">=8" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/supports-color": { + "version": "7.2.0", + "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz", + "integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==", + "dependencies": { + "has-flag": "^4.0.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/supports-preserve-symlinks-flag": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz", + "integrity": "sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==", + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/text-table": { + "version": "0.2.0", + "resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz", + "integrity": "sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==", + "dev": true + }, + "node_modules/to-regex-range": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz", + "integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==", + "dependencies": { + "is-number": "^7.0.0" + }, + "engines": { + "node": ">=8.0" + } + }, + "node_modules/type-check": { + "version": "0.4.0", + "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz", + "integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==", + "dev": true, + "dependencies": { + "prelude-ls": "^1.2.1" + }, + "engines": { + "node": ">= 0.8.0" + } + }, + "node_modules/unc-path-regex": { + "version": "0.1.2", + "resolved": "https://registry.npmjs.org/unc-path-regex/-/unc-path-regex-0.1.2.tgz", + "integrity": "sha512-eXL4nmJT7oCpkZsHZUOJo8hcX3GbsiDOa0Qu9F646fi8dT3XuSVopVqAcEiVzSKKH7UoDti23wNX3qGFxcW5Qg==", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/underscore.string": { + "version": "3.3.6", + "resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.3.6.tgz", + "integrity": "sha512-VoC83HWXmCrF6rgkyxS9GHv8W9Q5nhMKho+OadDJGzL2oDYbYEppBaCMH6pFlwLeqj2QS+hhkw2kpXkSdD1JxQ==", + "dependencies": { + "sprintf-js": "^1.1.1", + "util-deprecate": "^1.0.2" + }, + "engines": { + "node": "*" + } + }, + "node_modules/underscore.string/node_modules/sprintf-js": { + "version": "1.1.3", + "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.1.3.tgz", + "integrity": "sha512-Oo+0REFV59/rz3gfJNKQiBlwfHaSESl1pcGyABQsnnIfWOFt6JNj5gCog2U6MLZ//IGYD+nA8nI+mTShREReaA==" + }, + "node_modules/uri-js": { + "version": "4.4.1", + "resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz", + "integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==", + "dev": true, + "dependencies": { + "punycode": "^2.1.0" + } + }, + "node_modules/util-deprecate": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz", + "integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==" + }, + "node_modules/v8flags": { + "version": "3.2.0", + "resolved": "https://registry.npmjs.org/v8flags/-/v8flags-3.2.0.tgz", + "integrity": "sha512-mH8etigqMfiGWdeXpaaqGfs6BndypxusHHcv2qSHyZkGEznCd/qAXCWWRzeowtL54147cktFOC4P5y+kl8d8Jg==", + "dependencies": { + "homedir-polyfill": "^1.0.1" + }, + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/which": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/which/-/which-4.0.0.tgz", + "integrity": "sha512-GlaYyEb07DPxYCKhKzplCWBJtvxZcZMrL+4UkrTSJHHPyZU4mYYTv3qaOe77H7EODLSSopAUFAc6W8U4yqvscg==", + "dependencies": { + "isexe": "^3.1.1" + }, + "bin": { + "node-which": "bin/which.js" + }, + "engines": { + "node": "^16.13.0 || >=18.0.0" + } + }, + "node_modules/wordpress": { + "version": "1.4.2", + "resolved": "https://registry.npmjs.org/wordpress/-/wordpress-1.4.2.tgz", + "integrity": "sha512-T+o+Af6pK7mhTz/rJEZk4PpSIyRMVhx6vZm6UsmrnlL8pVudhu1gWzn1n3wZXlcEZQz7I0AOkEvPQ5hu++L+qg==", + "dependencies": { + "xmlrpc": "1.3.2" + } + }, + "node_modules/wrappy": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz", + "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==" + }, + "node_modules/xmlbuilder": { + "version": "8.2.2", + "resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-8.2.2.tgz", + "integrity": "sha512-eKRAFz04jghooy8muekqzo8uCSVNeyRedbuJrp0fovbLIi7wlsYtdUn3vBAAPq2Y3/0xMz2WMEUQ8yhVVO9Stw==", + "engines": { + "node": ">=4.0" + } + }, + "node_modules/xmlrpc": { + "version": "1.3.2", + "resolved": "https://registry.npmjs.org/xmlrpc/-/xmlrpc-1.3.2.tgz", + "integrity": "sha512-jQf5gbrP6wvzN71fgkcPPkF4bF/Wyovd7Xdff8d6/ihxYmgETQYSuTc+Hl+tsh/jmgPLro/Aro48LMFlIyEKKQ==", + "dependencies": { + "sax": "1.2.x", + "xmlbuilder": "8.2.x" + }, + "engines": { + "node": ">=0.8", + "npm": ">=1.0.0" + } + }, + "node_modules/yocto-queue": { + "version": "0.1.0", + "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz", + "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==", + "dev": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + } + } +} diff --git a/package.json b/package.json index 1dadaf77..8ca5b6e7 100644 --- a/package.json +++ b/package.json @@ -1,32 +1,14 @@ { "name": "learn.jquery.com", - "title": "jQuery Learning Site", - "description": "jQuery Foundation site for learning jQuery and JavaScript", - "version": "0.3.20", - "homepage": "http://learn.jquery.com", - "author": { - "name": "jQuery Foundation (http://jquery.org/)" - }, - "repository": { - "type": "git", - "url": "git://github.com/jquery/learn.jquery.com.git" - }, - "bugs": { - "url": "https://github.com/jquery/learn.jquery.com/issues" - }, - "licenses": [ - { - "type": "MIT", - "url": "http://www.opensource.org/licenses/MIT" - } - ], + "private": true, + "version": "0.6.31", "dependencies": { - "grunt": "0.3.17", - "grunt-clean": "0.3.0", - "grunt-html": "0.1.1", - "grunt-wordpress": "1.0.7", - "grunt-jquery-content": "0.11.1", - "grunt-check-modules": "0.1.0", - "js-yaml": "2.0.1" + "grunt": "1.6.1", + "grunt-jquery-content": "3.3.1" + }, + "devDependencies": { + "eslint": "^9.0.0", + "eslint-config-jquery": "^3.0.2", + "globals": "^15.0.0" } } diff --git a/page/about-jquery.md b/page/about-jquery.md index 5814541c..1830bd4e 100644 --- a/page/about-jquery.md +++ b/page/about-jquery.md @@ -1,10 +1,14 @@ ---- -title: About jQuery -level: beginner -customFields: - - - key: "icon" - value: "certificate" ---- + Getting started with jQuery can be easy or challenging, depending on your experience with JavaScript, HTML, CSS, and programming concepts in general. In addition to these articles, you can read about the [history of jQuery](https://jquery.org/history/) and the [licensing terms](https://jquery.org/license/) that apply to jQuery projects. You can also [make a donation](https://jquery.org/donate/) to help the [jQuery team](https://jquery.org/team/) continue to improve jQuery. + +One important thing to know is that jQuery is just a __JavaScript library__. All the power of jQuery is accessed via JavaScript, so having a strong grasp of JavaScript is essential for understanding, structuring, and debugging your code. While working with jQuery regularly can, over time, improve your proficiency with JavaScript, it can be hard to get started writing jQuery without a working knowledge of JavaScript's built-in constructs and syntax. Therefore, if you're new to JavaScript, we recommend checking out the [JavaScript basics tutorial](https://developer.mozilla.org/en-US/Learn/Getting_started_with_the_web/JavaScript_basics) on the Mozilla Developer Network (MDN). diff --git a/page/about-jquery/additional-support.md b/page/about-jquery/additional-support.md index ec90ab81..9378b57f 100644 --- a/page/about-jquery/additional-support.md +++ b/page/about-jquery/additional-support.md @@ -1,6 +1,6 @@ ---- -title : Additional jQuery Support ---- + While we hope to cover most jQuery-related topics on this site, you may need additional or more immediate support. The following resources can prove useful. @@ -11,29 +11,29 @@ http://forum.jquery.com/ There are many subforums where you can discuss jQuery, ask questions, talk about JavaScript, or announce your plugins. * [Getting Started](http://forum.jquery.com/getting-started) - * This is the best place to post if you are brand new to jQuery and JavaScript. + * This is the best place to post if you are brand new to jQuery and JavaScript. * [Using jQuery](http://forum.jquery.com/using-jquery) - * This is the best place to post if you have general questions or concerns. - * If you've built a site that uses jQuery, or would like to announce a new plugin, this is the place to do it. + * This is the best place to post if you have general questions or concerns. + * If you've built a site that uses jQuery, or would like to announce a new plugin, this is the place to do it. * [Using jQuery Plugins](http://forum.jquery.com/using-jquery-plugins) - * If you are a plugin author or user and you wish to discuss specific plugins, plugin bugs, new features, or new plugins. + * If you are a plugin author or user and you wish to discuss specific plugins, plugin bugs, new features, or new plugins. * [Using jQuery UI](http://forum.jquery.com/using-jquery-ui) - * This is the place to discuss use of [jQuery UI](http://jqueryui.com/) Interactions, Widgets, and Effects + * This is the place to discuss use of [jQuery UI](http://jqueryui.com/) Interactions, Widgets, and Effects * [jQuery Mobile](http://forum.jquery.com/jquery-mobile) - * This is the place to discuss jQuery Mobile. + * This is the place to discuss jQuery Mobile. * [Developing jQuery Core](http://forum.jquery.com/developing-jquery-core) - * This forum centers around development of the jQuery library itself. - * Post here if you have questions about certain bugs, development with jQuery, features, or anything in the bug tracker or Git. + * This forum centers around development of the jQuery library itself. + * Post here if you have questions about certain bugs, development with jQuery, features, or anything in the bug tracker or Git. * [Developing jQuery Plugins](http://forum.jquery.com/developing-jquery-plugins) - * This forum covers development of jQuery plugins. + * This forum covers development of jQuery plugins. * [Developing jQuery UI](http://forum.jquery.com/developing-jquery-ui) - * This is the place to discuss development of [jQuery UI](http://jqueryui.com/) itself – including bugs, new plugins, and how you can help. - * All jQuery UI svn commits are posted to this list to facilitate feedback, discussion, and review. - * Also note that a lot of the development and planning of jQuery UI takes place on the [jQuery UI Development and Planning Wiki](http://wiki.jqueryui.com/). + * This is the place to discuss development of [jQuery UI](http://jqueryui.com/) itself – including bugs, new plugins, and how you can help. + * All jQuery UI svn commits are posted to this list to facilitate feedback, discussion, and review. + * Also note that a lot of the development and planning of jQuery UI takes place on the [jQuery UI Development and Planning Wiki](http://wiki.jqueryui.com/). * [Developing jQuery Mobile](http://forum.jquery.com/developing-jquery-mobile) - * This forum covers issues related to the development of jQuery Mobile. + * This forum covers issues related to the development of jQuery Mobile. * [QUnit and Testing](http://forum.jquery.com/qunit-and-testing) - * This is the place to discuss JavaScript testing in general and QUnit in particular + * This is the place to discuss JavaScript testing in general and QUnit in particular At the bottom of each of the forums is an RSS feed you can subscribe to. @@ -76,7 +76,7 @@ The IRC Channel is best if you need quick help with any of the following: If your problem is more in-depth, we may ask you to post to the mailing list, or the bug tracker, so that we can help you in a more-suitable environment. -####Connect info: +#### Connect info: **Server:** irc.freenode.net @@ -84,9 +84,9 @@ If your problem is more in-depth, we may ask you to post to the mailing list, or You can also connect at http://webchat.freenode.net/?channels=#jquery. -Additionally we have `#jquery-es` and `#jquery-de` if you want to speak your native language. +If you wish to post code snippets to the channel, you should use a paste site, like [jsfiddle.net](http://jsfiddle.net/) or [jsbin.com](http://jsbin.com/). -If you wish to post code snippets to the channel, you should use a paste site, like [jsfiddle.net](http://jsfiddle.net/) or [jsbin.com](http://jsbin.com/) +Additional info regarding jQuery's use of IRC can be found on [irc.jquery.org](http://irc.jquery.org). ### StackOverflow diff --git a/page/about-jquery/how-jquery-works.md b/page/about-jquery/how-jquery-works.md index 5b8dfa00..5314273e 100644 --- a/page/about-jquery/how-jquery-works.md +++ b/page/about-jquery/how-jquery-works.md @@ -1,7 +1,7 @@ ---- -title : How jQuery Works -level: beginner ---- + ### jQuery: The Basics @@ -11,7 +11,7 @@ This is a basic tutorial, designed to help you get started using jQuery. If you - + Demo @@ -28,6 +28,12 @@ This is a basic tutorial, designed to help you get started using jQuery. If you The `src` attribute in the ` Learning how and when to use jQuery is a different process for each and every web developer, depending largely on experience with the primary tools for front-end development (HTML, CSS, and JavaScript) and knowledge of general programming principles. Over the years developers of all stripes have come to rely on our [API documentation](http://api.jquery.com) for help figuring out how to do exactly what they need to do. However, API documentation alone cannot serve as a guide to solving problems and fostering a true understanding of web development. Over the years, an ecosystem of blog posts, books, support forums, and channels has grown to help cover the **hows** and **whys** of developing with jQuery, as well as explaining best practices, techniques, and workarounds for common problems. This type of documentation has been invaluable resource for millions of people, but the experience of navigating these waters can be frustrating as often as it is fulfilling, as developers struggle to identify trustworthy resources, determine whether what they're reading is actually up to date, and figure out those magical search keywords that are _just right_! -This site represents the jQuery Foundation's ongoing effort to consolidate and -curate this information in order to provide this crucial "narrative -documentation" to our community and serve the following goals: +This site represents the jQuery Foundation's ongoing effort to consolidate and curate this information in order to provide this crucial "narrative documentation" to our community and serve the following goals: 1. Provide our **users** with a digestible reference on all aspects of using jQuery, from the basics of getting started and performing common tasks to more advanced topics like approaches to structuring code and where jQuery fits into modern web application development. 2. Provide our **contributors** a central, open place to collaborate and provide a dependable, highly sharable resource that will improve our users' support experiences. 3. Foster an environment by which users are encouraged to become contributors and build the skills to help them work on jQuery – or any other open source project! -In order to achieve these goals, all of [this site's content is maintained publicly on GitHub](https://github.com/jquery/learn.jquery.com) and is licensed under the [MIT License](https://github.com/jquery/learn.jquery.com/blob/master/LICENSE-MIT.txt). To learn more about how the site works, take a look at our [contributing guide](/contributing/). +In order to achieve these goals, all of [this site's content is maintained publicly on GitHub](https://github.com/jquery/learn.jquery.com) and is licensed under the [MIT License](https://github.com/jquery/learn.jquery.com/blob/master/LICENSE.txt). To learn more about how the site works, take a look at our [contributing guide](/contributing/). ## History The jQuery Learning site has its roots in two primary places. -The first is Rebecca Murphey's [jQuery Fundamentals](http://jqfundamentals.com/legacy), a free, open source book on jQuery basics she originally released in 2010. Seeking a better home where the information could be both maintained going forward, and consumed in a more piecemeal fashion, Rebecca donated the content to the jQuery Foundation to form the basis of what was then an abstract idea for some sort of "learning center." +The first is Rebecca Murphey's _jQuery Fundamentals_ ([archive](https://web.archive.org/web/20151123192026/http://jqfundamentals.com/legacy/), [source](https://github.com/rmurphey/jqfundamentals)), a free, open source book on jQuery basics originally released in 2010. Seeking a better home where the information could be both maintained going forward, and consumed in a more piecemeal fashion, Rebecca donated the content to the jQuery Foundation to form the basis of what was then an abstract idea for some sort of "learning center." -The second is [docs.jquery.com](http://docs.jquery.com), that erstwhile chestnut still living out its final days before it will be shut down in early 2013. Since we've moved the API documentation for jQuery Core off that domain, we needed a place that could serve a similar need – documentation (that anyone can contribute to) that gets into the "how-to" and FAQs – without clumsy barriers to entry like finding the right person to set you up with a special wiki account and forcing all authoring into a `

`.
+The second is docs.jquery.com ([archive](https://web.archive.org/web/20121027123801/http://docs.jquery.com/Main%5FPage), [source](https://github.com/jquery/docs.jquery.com)), that erstwhile chestnut was home to all official documentation for jQuery Core, jQuery UI, and QUnit, as well as various community plugins, tutorials, and contribution guides. It was powered by MediaWiki and ran from 2006 to 2013. We moved official API documentation for jQuery to their own sites (that [anyone can contribute to](https://contribute.jquery.org/web-sites/#site-amp-repository-guide) via Git), but still needed a place for the the "how-to" guides and FAQs that was similarly open to contribution. Many of these pages live on in the jQuery Learning Center.
 
-<h2 id="beta">About the Beta</h2>
+## Contributing
 
-Though this resource will never truly be "done," the current version of this site should still be considered something of a preview. We still have a number of improvements we want to make to the content, user experience, and site build before we're ready to call it a "final release." At the same time, however, it's important for us to open the doors now so we can begin providing better docs to people who need them right away and spread the word about this effort. If you're interested in helping us reach the finish line, we invite you to please read more about how [you can get involved with contributing](/contributing/)!
+This project wouldn't have been possible without all our [awesome contributors](https://github.com/jquery/learn.jquery.com/graphs/contributors?type=a). If you feel like something on the site is open for improvements, you can contribute [on GitHub](https://github.com/jquery/learn.jquery.com). Feel free to check out [the contributing guide](contributing/) for more in-depth information.
diff --git a/page/ajax.md b/page/ajax.md
index 7f0cab3d..95315bb7 100644
--- a/page/ajax.md
+++ b/page/ajax.md
@@ -1,11 +1,13 @@
----
-title: Ajax
-level: beginner
-customFields:
- -
-    key: "icon"
-    value: "refresh"
----
+<script>{
+	"title": "Ajax",
+	"level": "beginner",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "refresh"
+		}
+	]
+}</script>
 
 Traditionally webpages required reloading to update their content. For web-based email this meant that users had to manually reload their inbox to check and see if they had new mail. This had huge drawbacks: it was slow and it required user input. When the user reloaded their inbox, the server had to reconstruct the entire web page and resend all of the HTML, CSS, JavaScript, as well as the user's email. This was hugely inefficient. Ideally, the server should only have to send the user's new messages, not the entire page. By 2003, all the major browsers solved this issue by adopting the XMLHttpRequest (XHR) object, allowing browsers to communicate with the server without requiring a page reload.
 
diff --git a/page/ajax/ajax-and-forms.md b/page/ajax/ajax-and-forms.md
index 8c5a946d..3c3c4d2a 100644
--- a/page/ajax/ajax-and-forms.md
+++ b/page/ajax/ajax-and-forms.md
@@ -1,10 +1,9 @@
----
-title: Ajax and Forms
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Ajax and Forms",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 jQuery's ajax capabilities can be especially useful when dealing with forms. There are several advantages, which can range from serialization, to simple client-side validation (e.g. "Sorry, that username is taken"), to [prefilters](http://api.jquery.com/jQuery.ajaxPrefilter/) (explained below), and even more!
 
@@ -18,7 +17,7 @@ The `.serialize()` method serializes a form's data into a query string. For the
 // Turning form data into a query string
 $( "#myForm" ).serialize();
 
-// creates a query string like this:
+// Creates a query string like this:
 // field_1=something&field2=somethingElse
 ```
 
@@ -28,7 +27,7 @@ While plain old serialization is great, sometimes your application would work be
 // Creating an array of objects containing form data
 $( "#myForm" ).serializeArray();
 
-// creates a structure like this:
+// Creates a structure like this:
 // [
 //   {
 //     name : "field_1",
@@ -42,6 +41,7 @@ $( "#myForm" ).serializeArray();
 ```
 
 ### Client-side validation
+
 Client-side validation is, much like many other things, extremely easy using jQuery. While there are several cases developers can test for, some of the most common ones are: presence of a required input, valid usernames/emails/phone numbers/etc…, or checking an "I agree…" box.
 
 Please note that it is advisable that you also perform server-side validation for your inputs. However, it typically makes for a better user experience to be able to validate some things without submitting the form.
@@ -51,14 +51,17 @@ With that being said, let's jump on in to some examples! First, we'll see how ea
 ```
 // Using validation to check for the presence of an input
 $( "#form" ).submit(function( event ) {
-	// if .required's value's length is zero
+
+	// If .required's value's length is zero
 	if ( $( ".required" ).val().length === 0 ) {
-		// usually show some kind of error message here
 
-		// this prevents the form from submitting
-		return false;
+		// Usually show some kind of error message here
+
+		// Prevent the form from submitting
+		event.preventDefault();
 	} else {
-		// run $.ajax here
+
+		// Run $.ajax() here
 	}
 });
 ```
@@ -70,22 +73,25 @@ Let's see how easy it is to check for invalid characters in a phone number:
 $( "#form" ).submit(function( event ) {
 	var inputtedPhoneNumber = $( "#phone" ).val();
 
-	// match only numbers
+	// Match only numbers
 	var phoneNumberRegex = /^\d*$/;
 
-	// if the phone number doesn't match the regex
+	// If the phone number doesn't match the regex
 	if ( !phoneNumberRegex.test( inputtedPhoneNumber ) ) {
-		// usually show some kind of error message here
 
-		// prevent the form from submitting
-		return false;
+		// Usually show some kind of error message here
+
+		// Prevent the form from submitting
+		event.preventDefault();
 	} else {
-		// run $.ajax here
+
+		// Run $.ajax() here
 	}
 });
 ```
 
 ### Prefiltering
+
 A prefilter is a way to modify the ajax options before each request is sent (hence, the name `prefilter`).
 
 For example, say we would like to modify all cross-domain requests through a proxy. To do so with a prefilter is quite simple:
@@ -105,7 +111,8 @@ You can pass in an optional argument before the callback function that specifies
 ```
 // Using the optional dataTypes argument
 $.ajaxPrefilter( "json script", function( options, originalOptions, jqXHR ) {
-	// do all of the prefiltering here, but only for
+
+	// Do all of the prefiltering here, but only for
 	// requests that indicate a dataType of "JSON" or "script"
 });
 ```
diff --git a/page/ajax/ajax-events.md b/page/ajax/ajax-events.md
index dcae3359..5cc70bfb 100644
--- a/page/ajax/ajax-events.md
+++ b/page/ajax/ajax-events.md
@@ -1,21 +1,19 @@
----
-title   : Ajax Events
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-Often, you'll want to perform an operation whenever an Ajax requests starts or
-stops, such as showing or hiding a loading indicator. Rather than defining
-this behavior inside every Ajax request, you can bind Ajax events to elements
-just like you'd bind other events. For a complete list of Ajax events, visit
-[Ajax Events documentation on docs.jquery.com](http://docs.jquery.com/Ajax_Events).
+<script>{
+	"title": "Ajax Events",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+Often, you'll want to perform an operation whenever an Ajax request starts or stops, such as showing or hiding a loading indicator. Rather than defining this behavior inside every Ajax request, you can bind Ajax events to elements just like you'd bind other events. For a complete list of Ajax events, visit [Ajax Events documentation on docs.jquery.com](http://docs.jquery.com/Ajax_Events).
 
 ```
 // Setting up a loading indicator using Ajax Events
-$( "#loading_indicator" ).ajaxStart(function() {
-	$( this ).show();
-}).ajaxStop(function() {
-	$( this ).hide();
-});
+$( "#loading_indicator" )
+	.ajaxStart(function() {
+		$( this ).show();
+	})
+	.ajaxStop(function() {
+		$( this ).hide();
+	});
 ```
diff --git a/page/ajax/jquery-ajax-methods.md b/page/ajax/jquery-ajax-methods.md
index 5629c93f..54a62e1e 100644
--- a/page/ajax/jquery-ajax-methods.md
+++ b/page/ajax/jquery-ajax-methods.md
@@ -1,136 +1,99 @@
----
-title   : jQuery's Ajax-Related Methods
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-    - jQuery Fundamentals
----
-While jQuery does offer many Ajax-related convenience methods, the core
-`$.ajax()` method is at the heart of all of them, and understanding it is
-imperative. We'll review it first, and then touch briefly on the convenience
-methods.
-
-I generally use the `$.ajax()` method and do not use convenience methods. As
-you'll see, it offers features that the convenience methods do not, and its
-syntax is more easily understandable, in my opinion.
+<script>{
+	"title": "jQuery's Ajax-Related Methods",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+While jQuery does offer many Ajax-related convenience methods, the core `$.ajax()` method is at the heart of all of them, and understanding it is imperative. We'll review it first, and then touch briefly on the convenience methods.
+
+It's often considered good practice to use the `$.ajax()` method over the jQuery provided [convenience methods](#convenience-methods). As you'll see, it offers features that the convenience methods do not, and its syntax allows for the ease of readability.
 
 ### `$.ajax()`
 
-jQuery’s core `$.ajax()` method is a powerful and straightforward way of creating
-Ajax requests. It takes a configuration object that contains all the
-instructions jQuery requires to complete the request. The `$.ajax()` method is
-particularly valuable because it offers the ability to specify both success and
-failure callbacks. Also, its ability to take a configuration object that can
-be defined separately makes it easier to write reusable code. For complete
-documentation of the configuration options, visit
-[http://api.jquery.com/jQuery.ajax/](http://api.jquery.com/jQuery.ajax/ "$.ajax
-documentation on api.jquery.com").
+jQuery’s core `$.ajax()` method is a powerful and straightforward way of creating Ajax requests. It takes a configuration object that contains all the instructions jQuery requires to complete the request. The `$.ajax()` method is particularly valuable because it offers the ability to specify both success and failure callbacks. Also, its ability to take a configuration object that can be defined separately makes it easier to write reusable code. For complete documentation of the configuration options, visit [http://api.jquery.com/jQuery.ajax/](http://api.jquery.com/jQuery.ajax/).
 
 ```
 // Using the core $.ajax() method
 $.ajax({
-	// the URL for the request
+
+	// The URL for the request
 	url: "post.php",
 
-	// the data to send (will be converted to a query string)
+	// The data to send (will be converted to a query string)
 	data: {
 		id: 123
 	},
 
-	// whether this is a POST or GET request
+	// Whether this is a POST or GET request
 	type: "GET",
 
-	// the type of data we expect back
+	// The type of data we expect back
 	dataType : "json",
+})
+  // Code to run if the request succeeds (is done);
+  // The response is passed to the function
+  .done(function( json ) {
+     $( "<h1>" ).text( json.title ).appendTo( "body" );
+     $( "<div class=\"content\">").html( json.html ).appendTo( "body" );
+  })
+  // Code to run if the request fails; the raw request and
+  // status codes are passed to the function
+  .fail(function( xhr, status, errorThrown ) {
+    alert( "Sorry, there was a problem!" );
+    console.log( "Error: " + errorThrown );
+    console.log( "Status: " + status );
+    console.dir( xhr );
+  })
+  // Code to run regardless of success or failure;
+  .always(function( xhr, status ) {
+    alert( "The request is complete!" );
+  });
 
-	// code to run if the request succeeds;
-	// the response is passed to the function
-	success: function( json ) {
-		$( "<h1/>" ).text( json.title ).appendTo( "body" );
-		$( "<div class=\"content\"/>").html( json.html ).appendTo( "body" );
-	},
-
-	// code to run if the request fails; the raw request and
-	// status codes are passed to the function
-	error: function( xhr, status, errorThrown ) {
-		alert( "Sorry, there was a problem!" );
-		console.log( "Error: " + errorThrown );
-		console.log( "Status: " + status );
-		console.dir( xhr );
-	},
-
-	// code to run regardless of success or failure
-	complete: function( xhr, status ) {
-		alert( "The request is complete!" );
-	}
-});
 ```
 
-**Note:** A note about the `dataType` setting: if the server sends back data that is in a
-different format than you specify, your code may fail, and the reason will not
-always be clear, because the HTTP response code will not show an error. When
-working with Ajax requests, make sure your server is sending back the data type
-you're asking for, and verify that the `Content-type` header is accurate for the
-data type. For example, for JSON data, the `Content-type` header should be
-`application/json`.
+**Note:** Regarding the `dataType` setting, if the server sends back data that is in a different format than you specify, your code may fail, and the reason will not always be clear, because the HTTP response code will not show an error. When working with Ajax requests, make sure your server is sending back the data type you're asking for, and verify that the `Content-type` header is accurate for the data type. For example, for JSON data, the `Content-type` header should be `application/json`.
 
 ### `$.ajax()` Options
 
-There are many, many options for the `$.ajax()` method, which is part of its
-power. For a complete list of options, visit
-[http://api.jquery.com/jQuery.ajax/](http://api.jquery.com/jQuery.ajax/ "$.ajax
-documentation on api.jquery.com"); here are several that you will use
-frequently:
+There are many, many options for the `$.ajax()` method, which is part of its power. For a complete list of options, visit [http://api.jquery.com/jQuery.ajax/](http://api.jquery.com/jQuery.ajax/); here are several that you will use frequently:
 
 #### async
 
-Set to `false` if the request should be sent synchronously. Defaults to `true`.
-Note that if you set this option to `false`, your request will block execution
-of other code until the response is received.
+Set to `false` if the request should be sent synchronously. Defaults to `true`. Note that if you set this option to `false`, your request will block execution of other code until the response is received.
 
 #### cache
 
-Whether to use a cached response if available. Defaults to `true` for all
-`dataType`s except "script" and "jsonp". When set to `false`, the URL will simply
-have a cachebusting parameter appended to it.
+Whether to use a cached response if available. Defaults to `true` for all `dataType`s except "script" and "jsonp". When set to `false`, the URL will simply have a cachebusting parameter appended to it.
 
-#### complete
+#### done
 
-A callback function to run when the request is complete, regardless of success
-or failure. The function receives the raw request object and the text status of
-the request.
+A callback function to run if the request succeeds. The function receives the response data (converted to a JavaScript object if the `dataType` was JSON), as well as the text status of the request and the raw request object.
+
+#### fail
+
+A callback function to run if the request results in an error. The function receives the raw request object and the text status of the request.
+
+#### always 
+
+A callback function to run when the request is complete, regardless of success or failure. The function receives the raw request object and the text status of the request.
 
 #### context
 
-The scope in which the callback function(s) should run (i.e. what `this` will
-mean inside the callback function(s)). By default, `this` inside the callback
-function(s) refers to the object originally passed to `$.ajax()`.
+The scope in which the callback function(s) should run (i.e. what `this` will mean inside the callback function(s)). By default, `this` inside the callback function(s) refers to the object originally passed to `$.ajax()`.
 
 #### data
 
-The data to be sent to the server. This can either be an object or a query
-string, such as `foo=bar&baz=bim`.
+The data to be sent to the server. This can either be an object or a query string, such as `foo=bar&baz=bim`.
 
 #### dataType
 
-The type of data you expect back from the server. By default, jQuery will look
-at the MIME type of the response if no `dataType` is specified.
-
-#### error
-
-A callback function to run if the request results in an error. The function
-receives the raw request object and the text status of the request.
+The type of data you expect back from the server. By default, jQuery will look at the MIME type of the response if no `dataType` is specified.
 
 #### jsonp
 
-The callback name to send in a query string when making a JSONP request.
-Defaults to "callback".
+The callback name to send in a query string when making a JSONP request. Defaults to "callback".
 
-#### success
-
-A callback function to run if the request succeeds. The function receives the
-response data (converted to a JavaScript object if the `dataType` was JSON), as
-well as the text status of the request and the raw request object.
 
 #### timeout
 
@@ -138,32 +101,21 @@ The time in milliseconds to wait before considering the request a failure.
 
 #### traditional
 
-Set to `true` to use the param serialization style in use prior to jQuery 1.4.
-For details, see
-[http://api.jquery.com/jQuery.param/](http://api.jquery.com/jQuery.param/
-"$.param documentation on api.jquery.com").
+Set to `true` to use the param serialization style in use prior to jQuery 1.4. For details, see [http://api.jquery.com/jQuery.param/](http://api.jquery.com/jQuery.param/).
 
 #### type
 
-The type of the request, "POST" or "GET". Defaults to "GET". Other request
-types, such as "PUT" and "DELETE" can be used, but they may not be supported by
-all browsers.
+The type of the request, "POST" or "GET". Defaults to "GET". Other request types, such as "PUT" and "DELETE" can be used, but they may not be supported by all browsers.
 
 #### url
 
 The URL for the request.
 
-The `url` option is the only required property of the `$.ajax()` configuration
-object; all other properties are optional. This can also be passed as the first
-argument to `$.ajax()`, and the options object as the second argument.
+The `url` option is the only required property of the `$.ajax()` configuration object; all other properties are optional. This can also be passed as the first argument to `$.ajax()`, and the options object as the second argument.
 
 ### Convenience Methods
 
-If you don't need the extensive configurability of `$.ajax()`, and you don't care
-about handling errors, the Ajax convenience functions provided by jQuery can be
-useful, terse ways to accomplish Ajax requests. These methods are just
-"wrappers" around the core `$.ajax()` method, and simply pre-set some of the
-options on the `$.ajax()` method.
+If you don't need the extensive configurability of `$.ajax()`, and you don't care about handling errors, the Ajax convenience functions provided by jQuery can be useful, terse ways to accomplish Ajax requests. These methods are just "wrappers" around the core `$.ajax()` method, and simply pre-set some of the options on the `$.ajax()` method.
 
 The convenience methods provided by jQuery are:
 
@@ -191,43 +143,39 @@ The URL for the request. Required.
 
 #### data
 
-The data to be sent to the server. Optional. This can either be an object or a
-query string, such as `foo=bar&baz=bim`.
+The data to be sent to the server. Optional. This can either be an object or a query string, such as `foo=bar&baz=bim`.
 
 **Note:** This option is not valid for `$.getScript`.
 
 #### success callback
 
-A callback function to run if the request succeeds. Optional. The function
-receives the response data (converted to a JavaScript object if the data type
-was JSON), as well as the text status of the request and the raw request
-object.
+A callback function to run if the request succeeds. Optional. The function receives the response data (converted to a JavaScript object if the data type was JSON), as well as the text status of the request and the raw request object.
 
 #### data type
 
 The type of data you expect back from the server. Optional.
 
-**Note:** This option is only applicable for methods that don't already specify the data
-type in their name.
+**Note:** This option is only applicable for methods that don't already specify the data type in their name.
 
 ```
 // Using jQuery's Ajax convenience methods
 
-// get plain text or HTML
+// Get plain text or HTML
 $.get( "/users.php", {
 	userId: 1234
 }, function( resp ) {
 	console.log( resp ); // server response
 });
 
-// add a script to the page, then run a function defined in it
+// Add a script to the page, then run a function defined in it
 $.getScript( "/static/js/myScript.js", function() {
 	functionFromMyScript();
 });
 
-// get JSON-formatted data from the server
+// Get JSON-formatted data from the server
 $.getJSON( "/details.php", function( resp ) {
-	// log each key in the response data
+
+	// Log each key in the response data
 	$.each( resp, function( key, value ) {
 		console.log( key + " : " + value );
 	});
@@ -236,19 +184,15 @@ $.getJSON( "/details.php", function( resp ) {
 
 ### `$.fn.load`
 
-The `.load()` method is unique among jQuery’s Ajax methods in that it is
-called on a selection. The `.load()` method fetches HTML from a URL, and
-uses the returned HTML to populate the selected element(s). In addition to
-providing a URL to the method, you can optionally provide a selector; jQuery
-will fetch only the matching content from the returned HTML.
+The `.load()` method is unique among jQuery’s Ajax methods in that it is called on a selection. The `.load()` method fetches HTML from a URL, and uses the returned HTML to populate the selected element(s). In addition to providing a URL to the method, you can optionally provide a selector; jQuery will fetch only the matching content from the returned HTML.
 
 ```
-// Using $.fn.load to populate an element
+// Using .load() to populate an element
 $( "#newContent" ).load( "/foo.html" );
 ```
 
 ```
-// Using $.fn.load to populate an element based on a selector
+// Using .load() to populate an element based on a selector
 $( "#newContent" ).load( "/foo.html #myDiv h1:first", function( html ) {
 	alert( "Content updated!" );
 });
diff --git a/page/ajax/key-concepts.md b/page/ajax/key-concepts.md
index bf393129..68f14596 100644
--- a/page/ajax/key-concepts.md
+++ b/page/ajax/key-concepts.md
@@ -1,37 +1,23 @@
----
-title   : Key Concepts
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-Proper use of Ajax-related jQuery methods requires understanding some key
-concepts first.
+<script>{
+	"title": "Key Concepts",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+Proper use of Ajax-related jQuery methods requires understanding some key concepts first.
 
 ### GET vs. POST
 
-The two most common "methods" for sending a request to a server are GET and
-POST. It's important to understand the proper application of each.
+The two most common "methods" for sending a request to a server are GET and POST. It's important to understand the proper application of each.
 
-The GET method should be used for non-destructive operations — that is,
-operations where you are only "getting" data from the server, not changing data
-on the server. For example, a query to a search service might be a GET
-request. GET requests may be cached by the browser, which can lead to
-unpredictable behavior if you are not expecting it. GET requests generally
-send all of their data in a query string.
+The GET method should be used for non-destructive operations — that is, operations where you are only "getting" data from the server, not changing data on the server. For example, a query to a search service might be a GET request. GET requests may be cached by the browser, which can lead to unpredictable behavior if you are not expecting it. GET requests generally send all of their data in a query string.
 
-The POST method should be used for destructive operations — that is, operations
-where you are changing data on the server. For example, a user saving a blog
-post should be a POST request. POST requests are generally not cached by the
-browser; a query string can be part of the URL, but the data tends to be sent
-separately as post data.
+The POST method should be used for destructive operations — that is, operations where you are changing data on the server. For example, a user saving a blog post should be a POST request. POST requests are generally not cached by the browser; a query string can be part of the URL, but the data tends to be sent separately as post data.
 
 ### Data Types
 
-jQuery generally requires some instruction as to the type of data you expect to
-get back from an Ajax request; in some cases the data type is specified by the
-method name, and in other cases it is provided as part of a configuration
-object. There are several options:
+jQuery generally requires some instruction as to the type of data you expect to get back from an Ajax request; in some cases the data type is specified by the method name, and in other cases it is provided as part of a configuration object. There are several options:
 
 #### text
 
@@ -49,11 +35,7 @@ For adding a new script to the page.
 
 For transporting JSON-formatted data, which can include strings, arrays, and objects.
 
-**Note:** As of jQuery 1.4, if the JSON data sent by your server isn't properly
-formatted, the request may fail silently. See
-[http://json.org](http://json.org) for details on properly formatting JSON, but
-as a general rule, use built-in language methods for generating JSON on the
-server to avoid syntax issues.
+**Note:** As of jQuery 1.4, if the JSON data sent by your server isn't properly formatted, the request may fail silently. See [http://json.org](http://json.org) for details on properly formatting JSON, but as a general rule, use built-in language methods for generating JSON on the server to avoid syntax issues.
 
 #### jsonp
 
@@ -63,16 +45,11 @@ For transporting JSON data from another domain.
 
 For transporting data in a custom XML schema.
 
-I am a strong proponent of using the JSON format in most cases, as it provides
-the most flexibility. It is especially useful for sending both HTML and data at
-the same time.
+Consider using the JSON format in most cases, as it provides the most flexibility. It is especially useful for sending both HTML and data at the same time.
 
 ### A is for Asynchronous
 
-The asynchronicity of Ajax catches many new jQuery users off guard. Because
-Ajax calls are asynchronous by default, the response is not immediately
-available. Responses can only be handled using a callback. So, for example,
-the following code will not work:
+The asynchronicity of Ajax catches many new jQuery users off guard. Because Ajax calls are asynchronous by default, the response is not immediately available. Responses can only be handled using a callback. So, for example, the following code will not work:
 
 ```
 var response;
@@ -84,9 +61,7 @@ $.get( "foo.php", function( r ) {
 console.log( response ); // undefined
 ```
 
-Instead, we need to pass a callback function to our request; this callback will
-run when the request succeeds, at which point we can access the data that it
-returned, if any.
+Instead, we need to pass a callback function to our request; this callback will run when the request succeeds, at which point we can access the data that it returned, if any.
 
 ```
 $.get( "foo.php", function( response ) {
@@ -96,22 +71,12 @@ $.get( "foo.php", function( response ) {
 
 ### Same-Origin Policy and JSONP
 
-In general, Ajax requests are limited to the same protocol (http or https), the
-same port, and the same domain as the page making the request. This limitation
-does not apply to scripts that are loaded via jQuery's Ajax methods.
+In general, Ajax requests are limited to the same protocol (http or https), the same port, and the same domain as the page making the request. This limitation does not apply to scripts that are loaded via jQuery's Ajax methods. 
+
+Note: Versions of Internet Explorer less than 10 do not support cross-domain AJAX requests. 
 
-The other exception is requests targeted at a JSONP service on another domain.
-In the case of JSONP, the provider of the service has agreed to respond to your
-request with a script that can be loaded into the page using a `<script>`
-tag, thus avoiding the same-origin limitation; that script will include the
-data you requested, wrapped in a callback function you provide.
+The other exception is requests targeted at a JSONP service on another domain. In the case of JSONP, the provider of the service has agreed to respond to your request with a script that can be loaded into the page using a `<script>` tag, thus avoiding the same-origin limitation; that script will include the data you requested, wrapped in a callback function you provide.
 
 ### Ajax and Firebug
 
-Firebug (or the Webkit Inspector in Chrome or Safari) is an invaluable tool for
-working with Ajax requests. You can see Ajax requests as they happen in the
-Console tab of Firebug (and in the Resources > XHR panel of Webkit Inspector),
-and you can click on a request to expand it and see details such as the request
-headers, response headers, response content, and more. If something isn't
-going as expected with an Ajax request, this is the first place to look to
-track down what's wrong.
+Firebug (or the Webkit Inspector in Chrome or Safari) is an invaluable tool for working with Ajax requests. You can see Ajax requests as they happen in the Console tab of Firebug (and in the Resources > XHR panel of Webkit Inspector), and you can click on a request to expand it and see details such as the request headers, response headers, response content, and more. If something isn't going as expected with an Ajax request, this is the first place to look to track down what's wrong.
diff --git a/page/ajax/working-with-jsonp.md b/page/ajax/working-with-jsonp.md
index ec93cf2a..a50d302d 100644
--- a/page/ajax/working-with-jsonp.md
+++ b/page/ajax/working-with-jsonp.md
@@ -1,42 +1,34 @@
----
-title   : Working with JSONP
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-The advent of JSONP — essentially a consensual cross-site scripting hack — has
-opened the door to powerful mashups of content. Many prominent sites provide
-JSONP services, allowing you access to their content via a predefined API. A
-particularly great source of JSONP-formatted data is the [Yahoo! Query
-Language](http://developer.yahoo.com/yql/console/), which we'll use in the
-following example to fetch news about cats.
+<script>{
+	"title": "Working with JSONP",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+The advent of JSONP — essentially a consensual cross-site scripting hack — has opened the door to powerful mashups of content. Many prominent sites provide JSONP services, allowing you access to their content via a predefined API. A particularly great source of JSONP-formatted data is the [Wikipedia API](https://en.wikipedia.org/w/api.php?action=help&modules=query), which we'll use in the following example to fetch a list of articles about [JavaScript libraries](https://en.wikipedia.org/wiki/Category:Free_software_programmed_in_JavaScript).
 
 ```
-// Using YQL and JSONP
-$.ajax({
-	url: "http://query.yahooapis.com/v1/public/yql",
+$.ajax( {
+	// Tell MediaWiki what we want and that we want JSON
+	url: "https://en.wikipedia.org/w/api.php",
+	data: {
+		format: "json",
+		action: "query",
+		list: "categorymembers",
+		cmtitle: "Category:Free_software_programmed_in_JavaScript",
+		cmprop: "title",
+		cmlimit: 500
+	},
 
-	// the name of the callback parameter, as specified by the YQL service
+	// Name of the query parameter that jQuery will add to set the callback function
 	jsonp: "callback",
 
-	// tell jQuery we're expecting JSONP
+	// Tell jQuery we're expecting JSONP
 	dataType: "jsonp",
 
-	// tell YQL what we want and that we want JSON
-	data: {
-		q: "select title,abstract,url from search.news where query=\"cat\"",
-    	format: "json"
-	},
-
-	// work with the response
-	success: function( response ) {
-		console.log( response ); // server response
-	}
-});
+} ).then( function( response ) {
+	console.log( response.query.categorymembers );
+} );
 ```
 
-jQuery handles all the complex aspects of JSONP behind-the-scenes — all we have
-to do is tell jQuery the name of the JSONP callback parameter specified by YQL
-("callback" in this case), and otherwise the whole process looks and feels like
-a normal Ajax request.
+jQuery handles all the complex aspects of JSONP behind-the-scenes. All we have to do is set `dataType` to `"jsonp"` and tell jQuery the name of the JSONP parameter ("callback" in this case). Beyond that one option, the whole process looks and feels like a normal Ajax request for fetching JSON.
diff --git a/page/code-organization.md b/page/code-organization.md
index 8b46c316..696a78b6 100644
--- a/page/code-organization.md
+++ b/page/code-organization.md
@@ -1,9 +1,12 @@
----
-title: Code Organization
-level: intermediate
-customFields:
- -
-    key: "icon"
-    value: "sitemap"
----
+<script>{
+	"title": "Code Organization",
+	"level": "intermediate",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "sitemap"
+		}
+	]
+}</script>
+
 Understanding the basic mechanics is one thing, but the essence of building applications is understanding how to organize code so that it is navigable and well-encapsulated instead of a whole slew of global functions.
diff --git a/page/code-organization/beware-anonymous-functions.md b/page/code-organization/beware-anonymous-functions.md
index 5890b408..31bd9e60 100644
--- a/page/code-organization/beware-anonymous-functions.md
+++ b/page/code-organization/beware-anonymous-functions.md
@@ -1,14 +1,12 @@
----
-title:        Beware Anonymous Functions
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Anonymous functions bound everywhere are a pain. They're difficult to debug,
-maintain, test, or reuse. Instead, use an object literal to organize and name
-your handlers and callbacks.
+<script>{
+	"title": "Beware Anonymous Functions",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+Anonymous functions bound everywhere are a pain. They're difficult to debug, maintain, test, or reuse. Instead, use an object literal to organize and name your handlers and callbacks.
+
 ```
 // BAD
 $( document ).ready(function() {
diff --git a/page/code-organization/concepts.md b/page/code-organization/concepts.md
index 89faccfa..509de7bd 100644
--- a/page/code-organization/concepts.md
+++ b/page/code-organization/concepts.md
@@ -1,57 +1,34 @@
----
-title:        Code Organization Concepts
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-When you move beyond adding simple enhancements to your website with jQuery and
-start developing full-blown client-side applications, you need to consider how
-to organize your code. In this chapter, we'll take a look at various code
-organization patterns you can use in your jQuery application and explore the
-RequireJS dependency management and build system.
+<script>{
+	"title": "Code Organization Concepts",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+When you move beyond adding simple enhancements to your website with jQuery and start developing full-blown client-side applications, you need to consider how to organize your code. In this chapter, we'll take a look at various code organization patterns you can use in your jQuery application and explore the [RequireJS](http://requirejs.org/) dependency management and build system.
 
 ## Key Concepts
 
-Before we jump into code organization patterns, it's important to understand
-some concepts that are common to all good code organization patterns.
-
-- Your code should be divided into units of functionality — modules, services,
-  etc. Avoid the temptation to have all of your code in one huge
-  `$( document ).ready()` block. This concept, loosely, is known as
-  encapsulation.
-- Don't repeat yourself. Identify similarities among pieces of functionality,
-  and use inheritance techniques to avoid repetitive code.
-- Despite jQuery's DOM-centric nature, JavaScript applications are not all
-  about the DOM. Remember that not all pieces of functionality need to — or
-  should — have a DOM representation.
-- Units of functionality should be [loosely coupled](http://en.wikipedia.org/wiki/Loose_coupling), that is,
-  a unit of functionality should be able to exist on its own, and communication between
-  units should be handled via a messaging system such as custom events or
-  pub/sub. Stay away from direct communication between units of functionality
-  whenever possible.
-
-The concept of loose coupling can be especially troublesome to developers
-making their first foray into complex applications, so be mindful of this as
-you're getting started.
+Before we jump into code organization patterns, it's important to understand some concepts that are common to all good code organization patterns.
+
+* Your code should be divided into units of functionality — modules, services, etc. Avoid the temptation to have all of your code in one huge `$( document ).ready()` block. This concept, loosely, is known as encapsulation.
+* Don't repeat yourself. Identify similarities among pieces of functionality, and use inheritance techniques to avoid repetitive code.
+* Despite jQuery's DOM-centric nature, JavaScript applications are not all about the DOM. Remember that not all pieces of functionality need to — or should — have a DOM representation.
+* Units of functionality should be [loosely coupled](http://en.wikipedia.org/wiki/Loose_coupling), that is, a unit of functionality should be able to exist on its own, and communication between units should be handled via a messaging system such as custom events or pub/sub. Stay away from direct communication between units of functionality whenever possible.
+
+The concept of loose coupling can be especially troublesome to developers making their first foray into complex applications, so be mindful of this as you're getting started.
 
 ## Encapsulation
 
-The first step to code organization is separating pieces of your application
-into distinct pieces; sometimes, even just this effort is sufficient to lend
+The first step to code organization is separating pieces of your application into distinct pieces; sometimes, even just this effort is sufficient to improve the structure of your code and its maintainability.
 
 ### The Object Literal
 
-An object literal is perhaps the simplest way to encapsulate related code. It
-doesn't offer any privacy for properties or methods, but it's useful for
-eliminating anonymous functions from your code, centralizing configuration
-options, and easing the path to reuse and refactoring.
+An object literal is perhaps the simplest way to encapsulate related code. It doesn't offer any privacy for properties or methods, but it's useful for eliminating anonymous functions from your code, centralizing configuration options, and easing the path to reuse and refactoring.
 
 ```
 // An object literal
 var myFeature = {
-
 	myProperty: "hello",
 
 	myMethod: function() {
@@ -65,7 +42,6 @@ var myFeature = {
 	readSettings: function() {
 		console.log( myFeature.settings );
 	}
-
 };
 
 myFeature.myProperty === "hello"; // true
@@ -79,21 +55,15 @@ myFeature.init({
 myFeature.readSettings(); // { foo: "bar" }
 ```
 
-The object literal above is simply an object assigned to a variable. The object
-has one property and several methods. All of the properties and methods are
-public, so any part of your application can see the properties and call methods
-on the object. While there is an init method, there's nothing requiring that it
-be called before the object is functional.
+The object literal above is simply an object assigned to a variable. The object has one property and several methods. All of the properties and methods are public, so any part of your application can see the properties and call methods on the object. While there is an init method, there's nothing requiring that it be called before the object is functional.
 
-How would we apply this pattern to jQuery code? Let's say that we had this code
-written in the traditional jQuery style:
+How would we apply this pattern to jQuery code? Let's say that we had this code written in the traditional jQuery style:
 
 ```
-// clicking on a list item loads some content using the
+// Clicking on a list item loads some content using the
 // list item's ID, and hides content in sibling list items
 $( document ).ready(function() {
-
-	$( "#myFeature li" ).append( "<div/>" ).click(function() {
+	$( "#myFeature li" ).append( "<div>" ).click(function() {
 		var item = $( this );
 		var div = item.find( "div" );
 		div.load( "foo.php?item=" + item.attr( "id" ), function() {
@@ -101,21 +71,14 @@ $( document ).ready(function() {
 			item.siblings().find( "div" ).hide();
 		});
 	});
-
 });
 ```
 
-If this were the extent of our application, leaving it as-is would be fine. On
-the other hand, if this was a piece of a larger application, we'd do well to
-keep this functionality separate from unrelated functionality. We might also
-want to move the URL out of the code and into a configuration area. Finally, we
-might want to break up the chain to make it easier to modify pieces of the
-functionality later.
+If this were the extent of our application, leaving it as-is would be fine. On the other hand, if this was a piece of a larger application, we'd do well to keep this functionality separate from unrelated functionality. We might also want to move the URL out of the code and into a configuration area. Finally, we might want to break up the chain to make it easier to modify pieces of the functionality later.
 
 ```
 // Using an object literal for a jQuery feature
 var myFeature = {
-
 	init: function( settings ) {
 		myFeature.config = {
 			items: $( "#myFeature li" ),
@@ -123,7 +86,7 @@ var myFeature = {
 			urlBase: "/foo.php?item="
 		};
 
-		// allow overriding the default config
+		// Allow overriding the default config
 		$.extend( myFeature.config, settings );
 
 		myFeature.setup();
@@ -148,7 +111,7 @@ var myFeature = {
 	},
 
 	showItem: function() {
-		var myFeature.currentItem = $( this );
+		myFeature.currentItem = $( this );
 		myFeature.getContent( myFeature.showContent );
 	},
 
@@ -167,43 +130,29 @@ var myFeature = {
 			$( this ).data( "container" ).hide();
 		});
 	}
-
 };
 
 $( document ).ready( myFeature.init );
 ```
 
-The first thing you'll notice is that this approach is obviously far longer
-than the original — again, if this were the extent of our application, using an
-object literal would likely be overkill. Assuming it's not the extent of our
-application, though, we've gained several things:
-
-- We've broken our feature up into tiny methods. In the future, if we want to
-  change how content is shown, it's clear where to change it. In the original
-  code, this step is much harder to locate.
-- We've eliminated the use of anonymous functions.
-- We've moved configuration options out of the body of the code and put them in
-  a central location.
-- We've eliminated the constraints of the chain, making the code easier to
-  refactor, remix, and rearrange.
-
-For non-trivial features, object literals are a clear improvement over a long
-stretch of code stuffed in a `$( document ).ready()` block, as they get us
-thinking about the pieces of our functionality. However, they aren't a whole
-lot more advanced than simply having a bunch of function declarations inside of
-that `$( document ).ready()` block.
+The first thing you'll notice is that this approach is obviously far longer than the original — again, if this were the extent of our application, using an object literal would likely be overkill. Assuming it's not the extent of our application, though, we've gained several things:
+
+* We've broken our feature up into tiny methods. In the future, if we want to change how content is shown, it's clear where to change it. In the original code, this step is much harder to locate.
+* We've eliminated the use of anonymous functions.
+* We've moved configuration options out of the body of the code and put them in a central location.
+* We've eliminated the constraints of the chain, making the code easier to refactor, remix, and rearrange.
+
+For non-trivial features, object literals are a clear improvement over a long stretch of code stuffed in a `$( document ).ready()` block, as they get us thinking about the pieces of our functionality. However, they aren't a whole lot more advanced than simply having a bunch of function declarations inside of that `$( document ).ready()` block.
 
 ### The Module Pattern
 
-The module pattern overcomes some of the limitations of the object literal,
-offering privacy for variables and functions while exposing a public API if
-desired.
+The module pattern overcomes some of the limitations of the object literal, offering privacy for variables and functions while exposing a public API if desired.
 
 ```
 // The module pattern
 var feature = (function() {
 
-	// private variables and functions
+	// Private variables and functions
 	var privateThing = "secret";
 	var publicThing = "not secret";
 
@@ -216,43 +165,29 @@ var feature = (function() {
 		changePrivateThing();
 	};
 
-	// public API
+	// Public API
 	return {
 		publicThing: publicThing,
 		sayPrivateThing: sayPrivateThing
 	};
-
 })();
 
 feature.publicThing; // "not secret"
 
-// logs "secret" and changes the value of privateThing
+// Logs "secret" and changes the value of privateThing
 feature.sayPrivateThing();
 ```
 
-In the example above, we self-execute an anonymous function that returns an
-object. Inside of the function, we define some variables. Because the variables
-are defined inside of the function, we don't have access to them outside of the
-function unless we put them in the return object. This means that no code
-outside of the function has access to the `privateThing` variable or to the
-`changePrivateThing` function. However, `sayPrivateThing` does have access to
-`privateThing` and `changePrivateThing`, because both were defined in the same
-scope as `sayPrivateThing`.
+In the example above, we self-execute an anonymous function that returns an object. Inside of the function, we define some variables. Because the variables are defined inside of the function, we don't have access to them outside of the function unless we put them in the return object. This means that no code outside of the function has access to the `privateThing` variable or to the `changePrivateThing` function. However, `sayPrivateThing` does have access to `privateThing` and `changePrivateThing`, because both were defined in the same scope as `sayPrivateThing`.
 
-This pattern is powerful because, as you can gather from the variable names, it
-can give you private variables and functions while exposing a limited API
-consisting of the returned object's properties and methods.
+This pattern is powerful because, as you can gather from the variable names, it can give you private variables and functions while exposing a limited API consisting of the returned object's properties and methods.
 
-Below is a revised version of the previous example, showing how we could create
-the same feature using the module pattern while only exposing one public method
-of the module, `showItemByIndex()`.
+Below is a revised version of the previous example, showing how we could create the same feature using the module pattern while only exposing one public method of the module, `showItemByIndex()`.
 
 ```
 // Using the module pattern for a jQuery feature
 $( document ).ready(function() {
-
 	var feature = (function() {
-
 		var items = $( "#myFeature li" );
 		var container = $( "<div class='container'></div>" );
 		var currentItem = null;
@@ -260,33 +195,33 @@ $( document ).ready(function() {
 
 		var createContainer = function() {
 			var item = $( this );
-			var container = container.clone().appendTo( item );
-			item.data( "container", container );
-		},
+			var _container = container.clone().appendTo( item );
+			item.data( "container", _container );
+		};
 
-		buildUrl = function() {
+		var buildUrl = function() {
 			return urlBase + currentItem.attr( "id" );
-		},
+		};
 
-		showItem = function() {
+		var showItem = function() {
 			currentItem = $( this );
 			getContent( showContent );
-		},
+		};
 
-		showItemByIndex = function( idx ) {
-			$.proxy( showItem, items.get( idx ) );
-		},
+		var showItemByIndex = function( idx ) {
+			$.proxy( showItem, items.get( idx ) )();
+		};
 
-		getContent = function( callback ) {
+		var getContent = function( callback ) {
 			currentItem.data( "container" ).load( buildUrl(), callback );
-		},
+		};
 
-		showContent = function() {
+		var showContent = function() {
 			currentItem.data( "container" ).show();
 			hideContent();
-		},
+		};
 
-		hideContent = function() {
+		var hideContent = function() {
 			currentItem.siblings().each(function() {
 				$( this ).data( "container" ).hide();
 			});
@@ -297,10 +232,8 @@ $( document ).ready(function() {
 		return {
 			showItemByIndex: showItemByIndex
 		};
-
 	})();
 
 	feature.showItemByIndex( 0 );
-
 });
 ```
diff --git a/page/code-organization/deferreds.md b/page/code-organization/deferreds.md
index 5317fa53..1c921b6e 100644
--- a/page/code-organization/deferreds.md
+++ b/page/code-organization/deferreds.md
@@ -1,80 +1,60 @@
----
-title: Deferreds
-level: advanced
-source: http://msdn.microsoft.com/en-us/magazine/gg723713.aspx
-attribution:
-  - Julian Aubourg <j@ubourg.net>
-  - Addy Osmani <addyosmani@gmail.com>
-  - Andree Hansson <peolanha@gmail.com>
----
-
-At a high-level, deferreds can be thought of as a way to represent
-asynchronous operations which can take a long time to complete. They're the
-asynchronous alternative to blocking functions and the general idea is
-that rather than your application blocking while it awaits some request
-to complete before returning a result, a deferred object can instead be
-returned immediately. You can then attach callbacks to the deferred
-object: they will be called once the request has actually completed.
-
-##Promises
-
-In its most basic form, a "promise" is a model that provides a solution
-for the concept of deferred (or future) results in software engineering.
-The main idea behind it is something we've already covered: rather than
-executing a call which may result in blocking, we instead return a
-promise for a future value that will eventually be satisfied.
-
-If it helps to have an example here, consider that you are building a
-web application which heavily relies on data from a third party API. A
-common problem that's faced is having an unknown knowledge of the API
-server's latency at a given time so it's possible that other parts of
-your application may be blocked from running until a result from it is
-returned. Deferreds provide a better solution to this problem, one which
-is void of "blocking" effects and completely decoupled.
-
-The [Promise/A](http://wiki.commonjs.org/wiki/Promises/A) proposal
-defines a method called "then" that can be used to register callbacks to
-a promise and, thus, get the future result when it is available. The
-pseudo-code for dealing with a third party API that returns a promise
-may look like:
+<script>{
+	"title": "Deferreds",
+	"level": "advanced",
+	"source": "http://msdn.microsoft.com/en-us/magazine/gg723713.aspx",
+	"attribution": [
+		"Julian Aubourg <j@ubourg.net>",
+		"Addy Osmani <addyosmani@gmail.com>",
+		"Andree Hansson <peolanha@gmail.com>"
+	]
+}</script>
+
+At a high-level, deferreds can be thought of as a way to represent asynchronous operations which can take a long time to complete. They're the asynchronous alternative to blocking functions and the general idea is that rather than your application blocking while it awaits some request to complete before returning a result, a deferred object can instead be returned immediately. You can then attach callbacks to the deferred object: they will be called once the request has actually completed.
+
+## Promises
+
+In its most basic form, a "promise" is a model that provides a solution for the concept of deferred (or future) results in software engineering. The main idea behind it is something we've already covered: rather than executing a call which may result in blocking, we instead return a promise for a future value that will eventually be satisfied.
+
+If it helps to have an example here, consider that you are building a web application which heavily relies on data from a third party API. A common problem that's faced is having an unknown knowledge of the API server's latency at a given time so it's possible that other parts of your application may be blocked from running until a result from it is returned. Deferreds provide a better solution to this problem, one which is void of "blocking" effects and completely decoupled.
+
+The [Promises/A](http://wiki.commonjs.org/wiki/Promises/A) proposal defines a method called "then" that can be used to register callbacks to a promise and, thus, get the future result when it is available. The pseudo-code for dealing with a third party API that returns a promise may look like:
 
 ```
-promise = callToAPI( arg1, arg2, ...);
+var promise = callToAPI( arg1, arg2, ...);
 
 promise.then(function( futureValue ) {
-	/* handle futureValue */
+
+	// Handle futureValue
+
 });
 
 promise.then(function( futureValue ) {
-	/* do something else */
+
+	// Do something else
+
 });
 ```
 
-Furthermore, a promise can actually end up being in two different
-states:
+Furthermore, a promise can actually end up being in two different states:
 
--   Resolved: in which case data is available
--   Rejected: in which case something went wrong and no value is
-    available
+* Resolved: in which case data is available
+* Rejected: in which case something went wrong and no value is available
 
-Thankfully, the "then" method accepts two parameters: one for when the
-promise was resolved, another for when the promise was rejected. If we
-get back to pseudo-code, we may do things like:
+Thankfully, the "then" method accepts two parameters: one for when the promise was resolved, another for when the promise was rejected. If we get back to pseudo-code, we may do things like:
 
 ```
 promise.then(function( futureValue ) {
-	/* we got a value */
+
+	// We got a value
+
 }, function() {
-	/* something went wrong */
+
+	// Something went wrong
+
 });
 ```
 
-In the case of certain applications, it is necessary to have several
-results returned before your application can continue at all (for
-example, displaying a dynamic set of options on a screen before a user
-is able to select the option that interests them). Where this is the
-case, a method called "when" exists, which can be used to perform some
-action once all the promises have been fully fulfilled:
+In the case of certain applications, it is necessary to have several results returned before your application can continue at all (for example, displaying a dynamic set of options on a screen before a user is able to select the option that interests them). Where this is the case, a method called "when" exists, which can be used to perform some action once all the promises have been fully fulfilled:
 
 ```
 when(
@@ -82,18 +62,13 @@ when(
 	promise2,
 	...
 ).then(function( futureValue1, futureValue2, ... ) {
-	/* all promises have completed and are resolved */
+
+	// All promises have completed and are resolved
+
 });
 ```
 
-A good example is a scenario where you may have multiple concurrent
-animations that are being run. Without keeping track of each callback
-firing on completion, it can be difficult to truly establish once all
-your animations have finished running. Using promises and "when" however
-this is very straightforward as each of your animations can effectively
-say "we promise to let you know once we're done". The compounded result
-of this means it's a trivial process to execute a single callback once
-the animations are done. For example:
+A good example is a scenario where you may have multiple concurrent animations that are being run. Without keeping track of each callback firing on completion, it can be difficult to truly establish once all your animations have finished running. Using promises and "when" however this is very straightforward as each of your animations can effectively say "we promise to let you know once we're done". The compounded result of this means it's a trivial process to execute a single callback once the animations are done. For example:
 
 ```
 var promise1 = $( "#id1" ).animate().promise();
@@ -102,13 +77,11 @@ when(
 	promise1,
 	promise2
 ).then(function() {
-	/* once both animations have completed
-	we can then run our additional logic  */
+
+	// Once both animations have completed
+	// we can then run our additional logic
+
 });
 ```
 
-This means that one can basically write non-blocking logic that can be
-executed without synchronization. Rather than directly passing callbacks
-to functions, something which can lead to tightly coupled interfaces,
-using promises allows one to separate concerns for code that is
-synchronous or asynchronous.
+This means that one can basically write non-blocking logic that can be executed without synchronization. Rather than directly passing callbacks to functions, something which can lead to tightly coupled interfaces, using promises allows one to separate concerns for code that is synchronous or asynchronous.
diff --git a/page/code-organization/deferreds/examples.md b/page/code-organization/deferreds/examples.md
index 31ddce78..d4b74e38 100644
--- a/page/code-organization/deferreds/examples.md
+++ b/page/code-organization/deferreds/examples.md
@@ -1,37 +1,30 @@
----
-title: Deferred examples
-level: advanced
-source: http://msdn.microsoft.com/en-us/magazine/gg723713.aspx
-attribution:
-  - Julian Aubourg <j@ubourg.net>
-  - Addy Osmani <addyosmani@gmail.com>
-  - Andree Hansson <peolanha@gmail.com>
----
-
-##Further Deferreds examples
-
-Deferreds are used behind the hood in Ajax but it doesn't mean they can't also
-be used elsewhere. This section describes situations where deferreds will help
-abstract away asynchronous behaviour and decouple our code.
+<script>{
+	"title": "Deferred examples",
+	"level": "advanced",
+	"source": "http://msdn.microsoft.com/en-us/magazine/gg723713.aspx",
+	"attribution": [
+		"Julian Aubourg <j@ubourg.net>",
+		"Addy Osmani <addyosmani@gmail.com>",
+		"Andree Hansson <peolanha@gmail.com>"
+	]
+}</script>
+
+## Further Deferreds examples
+
+Deferreds are used behind the hood in Ajax but it doesn't mean they can't also be used elsewhere. This section describes situations where deferreds will help abstract away asynchronous behavior and decouple our code.
 
 ### Caching
 
 #### Asynchronous cache
 
-When it comes to asynchronous tasks, caching can be a bit demanding
-since you have to make sure a task is only performed once for a given
-key. As a consequence, the code has to somehow keep track of inbound
-tasks.
+When it comes to asynchronous tasks, caching can be a bit demanding since you have to make sure a task is only performed once for a given key. As a consequence, the code has to somehow keep track of inbound tasks.
 
 ```
 $.cachedGetScript( url, callback1 );
 $.cachedGetScript( url, callback2 );
 ```
 
-The caching mechanism has to make sure the URL is only requested once
-even if the script isn't in cache yet. This shows some logic
-to keep track of callbacks bound to a given URL in order for the cache
-system to properly handle both complete and inbound requests.
+The caching mechanism has to make sure the URL is only requested once even if the script isn't in cache yet. This shows some logic to keep track of callbacks bound to a given URL in order for the cache system to properly handle both complete and inbound requests.
 
 ```
 var cachedScriptPromises = {};
@@ -46,13 +39,7 @@ $.cachedGetScript = function( url, callback ) {
 };
 ```
 
-One promise is cached per URL. If there is no promise for the given URL yet,
-then a deferred is created and the request is issued. If it already exists, however,
-the callback is attached to the existing deferred. The big advantage of this
-solution is that it will handle both complete and inbound requests
-transparently. Another advantage is that a deferred-based cache will deal with
-failure gracefully. The promise will end up rejected which can be tested for by
-providing an error callback:
+One promise is cached per URL. If there is no promise for the given URL yet, then a deferred is created and the request is issued. When the request is complete, the deferred is resolved (with `defer.resolve`); if an error occurs, the deferred is rejected (with `defer.reject`). If the promise already exists, the callback is attached to the existing deferred; otherwise, the promise is first created and then the callback is attached. The big advantage of this solution is that it will handle both complete and inbound requests transparently. Another advantage is that a deferred-based cache will deal with failure gracefully. The promise will end up rejected which can be tested for by providing an error callback:
 
 ```
 $.cachedGetScript( url ).then( successCallback, errorCallback );
@@ -60,9 +47,7 @@ $.cachedGetScript( url ).then( successCallback, errorCallback );
 
 #### Generic asynchronous cache
 
-It is also possible to make the code completely generic and build a
-cache factory that will abstract out the actual task to be performed
-when a key isn't in the cache yet:
+It is also possible to make the code completely generic and build a cache factory that will abstract out the actual task to be performed when a key isn't in the cache yet:
 
 ```
 $.createCache = function( requestFunction ) {
@@ -75,11 +60,10 @@ $.createCache = function( requestFunction ) {
 		}
 		return cache[ key ].done( callback );
 	};
-}
+};
 ```
 
-Now that the request logic is abstracted away, `cachedGetScript` can be rewritten
-as follows:
+Now that the request logic is abstracted away, `$.cachedGetScript()` can be rewritten as follows:
 
 ```
 $.cachedGetScript = $.createCache(function( defer, url ) {
@@ -87,8 +71,7 @@ $.cachedGetScript = $.createCache(function( defer, url ) {
 });
 ```
 
-This will work because every call to `createCache` will create a new cache
-repository and return a new cache-retrieval function.
+This will work because every call to `$.createCache()` will create a new cache repository and return a new cache-retrieval function.
 
 #### Image loading
 
@@ -116,13 +99,11 @@ $.loadImage( "my-image.png" ).done( callback1 );
 $.loadImage( "my-image.png" ).done( callback2 );
 ```
 
-will work regardless of whether `my-image.png` has already been loaded or
-not, or if it is actually in the process of being loaded.
+will work regardless of whether `my-image.png` has already been loaded or not, or if it is actually in the process of being loaded.
 
 #### Caching Data API responses
 
-API requests that are considered immutable during the lifetime of your
-page are also perfect candidates. For instance, the following:
+API requests that are considered immutable during the lifetime of your page are also perfect candidates. For instance, the following:
 
 ```
 $.searchTwitter = $.createCache(function( defer, query ) {
@@ -138,8 +119,7 @@ $.searchTwitter = $.createCache(function( defer, query ) {
 });
 ```
 
-will allow you to perform searches on Twitter and cache them at the same
-time:
+will allow you to perform searches on Twitter and cache them at the same time:
 
 ```
 $.searchTwitter( "jQuery Deferred", callback1 );
@@ -148,16 +128,9 @@ $.searchTwitter( "jQuery Deferred", callback2 );
 
 #### Timing
 
-This deferred-based cache is not limited to network requests; it can
-also be used for timing purposes.
+This deferred-based cache is not limited to network requests; it can also be used for timing purposes.
 
-For instance, you may need to perform an action on the page after a
-given amount of time so as to attract the user's attention to a specific
-feature they may not be aware of or deal with a timeout (for a quiz
-question for instance). While `setTimeout` is good for most use-cases it
-doesn't handle the situation when the timer is asked for later, even
-after it has theoretically expired. We can handle that with the
-following caching system:
+For instance, you may need to perform an action on the page after a given amount of time so as to attract the user's attention to a specific feature they may not be aware of or deal with a timeout (for a quiz question for instance). While `setTimeout()` is good for most use-cases it doesn't handle the situation when the timer is asked for later, even after it has theoretically expired. We can handle that with the following caching system:
 
 ```
 var readyTime;
@@ -179,20 +152,13 @@ $.afterDOMReady = $.createCache(function( defer, delay ) {
 });
 ```
 
-The new `afterDOMReady` helper method provides proper timing after the DOM
-is ready while ensuring the bare minimum of timers will be used. If the
-delay is already expired, any callback will be called right away.
+The new `$.afterDOMReady()` helper method provides proper timing after the DOM is ready while ensuring the bare minimum of timers will be used. If the delay is already expired, any callback will be called right away.
 
 ### One-time event
 
-While jQuery offers all the event binding one may need, it can become a
-bit cumbersome to handle events that are only supposed to be dealt with
-once.
+While jQuery offers all the event binding one may need, it can become a bit cumbersome to handle events that are only supposed to be dealt with once.
 
-For instance, you may wish to have a button that will open a panel the
-first time it is clicked and leave it open afterwards or take special
-initialization actions the first time said button is clicked. When
-dealing with such a situation, one usually end up with code like this:
+For instance, you may wish to have a button that will open a panel the first time it is clicked and leave it open afterward or take special initialization actions the first time said button is clicked. When dealing with such a situation, one usually ends up with code like this:
 
 ```
 var buttonClicked = false;
@@ -206,30 +172,25 @@ $( "#myButton" ).click(function() {
 });
 ```
 
-then, later on, you may wish to take actions, but only if the panel is
-opened:
+then, later on, you may wish to take actions, but only if the panel is opened:
 
 ```
 if ( buttonClicked ) {
-	/* perform specific action */
+
+	// Perform specific action
+
 }
 ```
 
-This is a very coupled solution. If you want to add some other action,
-you have to edit the bind code or just duplicate it all. If you don't,
-your only option is to test for `buttonClicked` and you may lose that new
-action because the `buttonClicked` variable may be false and your new code
-may never be executed.
+This is a very coupled solution. If you want to add some other action, you have to edit the bind code or just duplicate it all. If you don't, your only option is to test for `buttonClicked` and you may lose that new action because the `buttonClicked` variable may be `false` and your new code may never be executed.
 
-We can do much better using deferreds (for simplification sake, the
-following code will only work for a single element and a single event
-type, but it can be easily generalized for full-fledged collections with
-multiple event types):
+We can do much better using deferreds (for simplification sake, the following code will only work for a single element and a single event type, but it can be easily generalized for full-fledged collections with multiple event types):
 
 ```
 $.fn.bindOnce = function( event, callback ) {
 	var element = $( this[ 0 ] ),
 		defer = element.data( "bind_once_defer_" + event );
+
 	if ( !defer ) {
 		defer = $.Deferred();
 		function deferCallback() {
@@ -239,22 +200,18 @@ $.fn.bindOnce = function( event, callback ) {
 		element.bind( event, deferCallback )
 		element.data( "bind_once_defer_" + event , defer );
 	}
+
 	return defer.done( callback ).promise();
 };
 ```
 
 The code works as follows:
 
--   Check if the element already has a deferred attached for the given
-    event
--   if not, create it and make it so it is resolved when the event is
-    fired the first time around
--   then attach the given callback to the deferred and return the
-    promise
+* Check if the element already has a deferred attached for the given event
+* if not, create it and make it so it is resolved when the event is fired the first time around
+* then attach the given callback to the deferred and return the promise
 
-While the code is definitely more verbose, it makes dealing with the
-problem at hand much simpler in a compartmentalized and decoupled way.
-But let's define a helper method first:
+While the code is definitely more verbose, it makes dealing with the problem at hand much simpler in a compartmentalized and decoupled way. But let's define a helper method first:
 
 ```
 $.fn.firstClick = function( callback ) {
@@ -275,24 +232,21 @@ If an action should be performed only when a panel is opened later on:
 
 ```
 openPanel.done(function() {
-	/* perform specific action */
+
+	// Perform specific action
+
 });
 ```
 
-Nothing is lost if the panel isn't opened yet, the action will just get
-deferred until the button is clicked.
+Nothing is lost if the panel isn't opened yet, the action will just get deferred until the button is clicked.
 
 ### Combining helpers
 
-All of the samples above can seem a bit limited when looked at
-separately. However, the true power of promises comes into play when you
-mix them together.
+All of the samples above can seem a bit limited when looked at separately. However, the true power of promises comes into play when you mix them together.
 
 #### Requesting panel content on first click and opening said panel
 
-Following is the code for a button that, when clicked, opens a panel.
-It requests its content over the wire and then fades the content in. Using
-the helpers defined earlier, it could be defined as:
+Following is the code for a button that, when clicked, opens a panel. It requests its content over the wire and then fades the content in. Using the helpers defined earlier, it could be defined as:
 
 ```
 $( "#myButton" ).firstClick(function() {
@@ -308,29 +262,27 @@ $( "#myButton" ).firstClick(function() {
 
 #### Loading images in a panel on first click and opening said panel
 
-Another possible goal is to have the panel fade in, only after the button
-has been clicked and after all of the images have been loaded.
+Another possible goal is to have the panel fade in, only after the button has been clicked and after all of the images have been loaded.
 
 The HTML code for this would look something like:
 
 ```
 <div id="myPanel">
-	<img data-src="image1.png" />
-	<img data-src="image2.png" />
-	<img data-src="image3.png" />
-	<img data-src="image4.png" />
+	<img data-src="image1.png" alt="">
+	<img data-src="image2.png" alt="">
+	<img data-src="image3.png" alt="">
+	<img data-src="image4.png" alt="">
 </div>
 ```
 
-We use the `data-src` attribute to keep track of the real image location.
-The code to handle our use case using our promise helpers is as follows:
+We use the `data-src` attribute to keep track of the real image location. The code to handle our use case using our promise helpers is as follows:
 
 ```
 $( "#myButton" ).firstClick(function() {
 	var panel = $( "#myPanel" ),
 		promises = [];
 
-	$( "img", panel ).each(function() {
+	panel.find( "img" ).each(function() {
 		var image = $( this ),
 			src = element.attr( "data-src" );
 		if ( src ) {
@@ -344,9 +296,7 @@ $( "#myButton" ).firstClick(function() {
 		}
 	});
 
-	promises.push(
-		panel.slideDownPromise()
-	);
+	promises.push( panel.slideDownPromise() );
 
 	$.when.apply( null, promises ).done(function() {
 		panel.fadeIn();
@@ -354,30 +304,23 @@ $( "#myButton" ).firstClick(function() {
 });
 ```
 
-The trick here is to keep track of all the `loadImage` promises. We later
-join them with the panel `slideDown` animation using `$.when`. So when the
-button is first clicked, the panel will slide down and the images will
-start loading. Once the panel has finished sliding down and all the
-images have been loaded, then, and only then, will the panel fade in.
+The trick here is to keep track of all the `$.loadImage()` promises. We later join them with the panel `.slideDown()` animation using `$.when()`. So when the button is first clicked, the panel will slide down and the images will start loading. Once the panel has finished sliding down and all the images have been loaded, then, and only then, will the panel fade in.
 
 #### Loading images on the page after a specific delay
 
-In order to implement deferred image display on the entire page,
-the following format in HTML can be used.
+In order to implement deferred image display on the entire page, the following format in HTML can be used.
 
 ```
-<img data-src="image1.png" data-after="1000" src="placeholder.png" />
-<img data-src="image2.png" data-after="1000" src="placeholder.png" />
-<img data-src="image1.png" src="placeholder.png" />
-<img data-src="image2.png" data-after="2000" src="placeholder.png" />
+<img data-src="image1.png" data-after="1000" src="placeholder.png" alt="">
+<img data-src="image2.png" data-after="1000" src="placeholder.png" alt="">
+<img data-src="image1.png" src="placeholder.png" alt="">
+<img data-src="image2.png" data-after="2000" src="placeholder.png" alt="">
 ```
 
 What it says is pretty straight-forward:
 
--   Load `image1.png` and show it immediately for the third image and
-    after one second for the first one
--   Load `image2.png` and show it after one second for the second image
-    and after two seconds for the fourth image
+* Load `image1.png` and show it immediately for the third image and after one second for the first one
+* Load `image2.png` and show it after one second for the second image and after two seconds for the fourth image
 
 ```
 $( "img" ).each(function() {
@@ -420,6 +363,4 @@ $( "img" ).each(function() {
 });
 ```
 
-Here, after the delay to be fulfilled then the image is loaded. It can make a
-lot of sense when you want to limit the number or network requests on page
-load.
+Here, after the delay to be fulfilled then the image is loaded. It can make a lot of sense when you want to limit the number or network requests on page load.
diff --git a/page/code-organization/deferreds/jquery-deferreds.md b/page/code-organization/deferreds/jquery-deferreds.md
index 9b59237e..0c3621c8 100644
--- a/page/code-organization/deferreds/jquery-deferreds.md
+++ b/page/code-organization/deferreds/jquery-deferreds.md
@@ -1,55 +1,32 @@
----
-title: jQuery Deferreds
-level: advanced
-source: http://msdn.microsoft.com/en-us/magazine/gg723713.aspx
-attribution:
-  - Julian Aubourg <j@ubourg.net>
-  - Addy Osmani <addyosmani@gmail.com>
-  - Andree Hansson <peolanha@gmail.com>
----
-
-##jQuery Deferreds
-
-Deferreds were added as a part of a large rewrite of the ajax module,
-led by Julian Aubourg following the CommonJS Promises/A design. Whilst 1.5 and
-above include deferred capabilities, former versions of jQuery had
-`jQuery.ajax()` accept callbacks that would be invoked upon completion or
-error of the request, but suffered from heavy coupling — the same
-principle that would drive developers using other languages or toolkits
-to opt for deferred execution.
-
-In practice what jQuery's version provides you with are several
-enhancements to the way callbacks are managed, giving you significantly
-more flexible ways to provide callbacks that can be invoked whether the
-original callback dispatch has already fired or not. It is also worth
-noting that jQuery's Deferred object supports having multiple callbacks
-bound to the outcome of particular tasks (and not just one) where the
-task itself can either be synchronous or asynchronous.
-
-At the heart of jQuery's implementation is `jQuery.Deferred` — a chainable
-constructor which is able to create new deferred objects that can check
-for the existence of a promise to establish whether the object can be
-observed. It can also invoke callback queues and pass on the success of
-synchronous and asynchronous functions. It's quite essential to note
-that the default state of any Deferred object is unresolved. Callbacks
-which may be added to it through `.then()` or `.fail()` are queued up and get
-executed later on in the process.
-
-You are able to use Deferred objects in conjunction with the promise concept of
-when(), implemented in jQuery as `$.when()` to wait for all of the Deferred
-object's requests to complete executing (i.e. for all of the promises to be
-fulfilled). In technical terms, `$.when()` is effectively a way to execute
-callbacks based on any number of promises that represent asynchronous events.
-
-An example of `$.when()` accepting multiple arguments can be seen below in
-conjunction with `.then()`:
+<script>{
+	"title": "jQuery Deferreds",
+	"level": "advanced",
+	"source": "http://msdn.microsoft.com/en-us/magazine/gg723713.aspx",
+	"attribution": [
+		"Julian Aubourg <j@ubourg.net>",
+		"Addy Osmani <addyosmani@gmail.com>",
+		"Andree Hansson <peolanha@gmail.com>"
+	]
+}</script>
+
+## jQuery Deferreds
+
+Deferreds were added as a part of a large rewrite of the Ajax module, led by Julian Aubourg following the CommonJS Promises/A design. Whilst 1.5 and above include deferred capabilities, former versions of jQuery had `jQuery.ajax()` accept callbacks that would be invoked upon completion or error of the request, but suffered from heavy coupling — the same principle that would drive developers using other languages or toolkits to opt for deferred execution.
+
+In practice what jQuery's version provides you with are several enhancements to the way callbacks are managed, giving you significantly more flexible ways to provide callbacks that can be invoked whether the original callback dispatch has already fired or not. It is also worth noting that jQuery's Deferred object supports having multiple callbacks bound to the outcome of particular tasks (and not just one) where the task itself can either be synchronous or asynchronous.
+
+At the heart of jQuery's implementation is `jQuery.Deferred` — a chainable constructor which is able to create new deferred objects that can check for the existence of a promise to establish whether the object can be observed. It can also invoke callback queues and pass on the success of synchronous and asynchronous functions. It's quite essential to note that the default state of any Deferred object is unresolved. Callbacks which may be added to it through `.then()` or `.fail()` are queued up and get executed later on in the process.
+
+You are able to use Deferred objects in conjunction with the promise concept of when(), implemented in jQuery as `$.when()` to wait for all of the Deferred object's requests to complete executing (i.e. for all of the promises to be fulfilled). In technical terms, `$.when()` is effectively a way to execute callbacks based on any number of promises that represent asynchronous events.
+
+An example of `$.when()` accepting multiple arguments can be seen below in conjunction with `.then()`:
 
 ```
-function successFunc(){
+function successFunc() {
 	console.log( "success!" );
 }
 
-function failureFunc(){
+function failureFunc() {
 	console.log( "failure!" );
 }
 
@@ -60,21 +37,9 @@ $.when(
 ).then( successFunc, failureFunc );
 ```
 
-The `$.when()` implementation offered in jQuery is quite interesting as it not
-only interprets deferred objects, but when passed arguments that are not
-deferreds, it treats these as if they were resolved deferreds and executes any
-callbacks (doneCallbacks) right away. It is also worth noting that jQuery's
-deferred implementation, in addition to exposing deferred.then(), a jQuery
-promise also supports the deferred.done() and deferred.fail() methods which can
-also be used to add callbacks to the deferred's queues.
-
-We will now take a look at a code example that utilizes many of the deferred
-features mentioned in the table presented earlier. Here is a very basic
-application that consumes (1) an external news feed and (2) a reactions feed
-for pulling in the latest comments via `$.get()` (which will return a promise).
-The application also has a function (`prepareInterface()`) which returns a
-promise to complete animating our containers for both the news and
-reactions.
+The `$.when()` implementation offered in jQuery is quite interesting as it not only interprets deferred objects, but when passed arguments that are not deferreds, it treats these as if they were resolved deferreds and executes any callbacks (`doneCallbacks`) right away. It is also worth noting that jQuery's deferred implementation, in addition to exposing `deferred.then()`, also supports the `deferred.done()` and `deferred.fail()` methods which can also be used to add callbacks to the deferred's queues.
+
+We will now take a look at a code example that uses many deferred features. This very basic script begins by consuming (1) an external news feed and (2) a reactions feed for pulling in the latest comments via `$.get()` (which will return a promise-like object). When both requests are received, the `showAjaxedContent()` function is called. The `showAjaxedContent()` function returns a promise that is resolved when animating both containers has completed. When the `showAjaxedContent()` promise is resolved, `removeActiveClass()` is called. The `removeActiveClass()` returns a promise that is resolved inside a `setTimeout()` after 4 seconds have elapsed. Finally, after the `removeActiveClass()` promise is resolved, the last `then()` callback is called, provided no errors occurred along the way.
 
 ```
 function getLatestNews() {
@@ -91,21 +56,32 @@ function getLatestReactions() {
 	});
 }
 
-function prepareInterface() {
+function showAjaxedContent() {
+	// The .promise() is resolved *once*, after all animations complete
+	return $( ".news, .reactions" ).slideDown( 500, function() {
+		// Called once *for each element* when animation completes
+		$(this).addClass( "active" );
+	}).promise();
+}
+
+function removeActiveClass() {
 	return $.Deferred(function( dfd ) {
-		var latest = $( ".news, .reactions" );
-			latest.slideDown( 500, dfd.resolve );
-			latest.addClass( "active" );
+		setTimeout(function () {
+			$( ".news, .reactions" ).removeClass( "active" );
+			dfd.resolve();
+		}, 4000);
 	}).promise();
 }
 
 $.when(
 	getLatestNews(),
-	getLatestReactions(),
-	prepareInterface()
-).then(function(){
-	console.log( "fire after requests succeed" );
-}).fail(function(){
+	getLatestReactions()
+)
+.then(showAjaxedContent)
+.then(removeActiveClass)
+.then(function() {
+	console.log( "Requests succeeded and animations completed" );
+}).fail(function() {
 	console.log( "something went wrong!" );
 });
 ```
diff --git a/page/code-organization/dont-repeat-yourself.md b/page/code-organization/dont-repeat-yourself.md
index d79bd700..c01a1cab 100644
--- a/page/code-organization/dont-repeat-yourself.md
+++ b/page/code-organization/dont-repeat-yourself.md
@@ -1,10 +1,10 @@
----
-title: Keep Things DRY
-level: beginner
-attribution:
-source: http://jqfundamentals.com/legacy
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Keep Things DRY",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
 Don't repeat yourself; if you're repeating yourself, you're doing it wrong.
 
 ```
diff --git a/page/code-organization/feature-browser-detection.md b/page/code-organization/feature-browser-detection.md
index 67d7040d..c54b8ea9 100644
--- a/page/code-organization/feature-browser-detection.md
+++ b/page/code-organization/feature-browser-detection.md
@@ -1,7 +1,7 @@
----
-title: Feature & Browser Detection
-level: beginner
----
+<script>{
+	"title": "Feature & Browser Detection",
+	"level": "beginner"
+}</script>
 
 ### Can I Use This Browser Feature?
 
@@ -14,13 +14,13 @@ In general, we recommend specific feature detection. Let's look at why.
 
 ### Browser Detection
 
-Browser detection is a method where the browser's User Agent (UA) string is checked for a particular pattern unique to a browser family or version. For example, this is Chrome 18's UA string on Mac OS X Lion:
+Browser detection is a method where the browser's User Agent (UA) string is checked for a particular pattern unique to a browser family or version. For example, this is Chrome 39's UA string on Mac OS X Yosemite:
 
 ```
-Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.142 Safari/535.19
+Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.99 Safari/537.36
 ```
 
-Browser UA detection may check this string for something like "Chrome" or "Chrome/18" or any other part the developer feels identifies the browser they intend to target.
+Browser UA detection may check this string for something like "Chrome" or "Chrome/39" or any other part the developer feels identifies the browser they intend to target.
 
 While this seems to be an easy solution, there are several problems:
 
@@ -51,7 +51,6 @@ Now how would you go about doing that?
 There are several ways to go about feature detection:
 
 * Straight JavaScript
-* `$.support`
 * A Helper Library
 
 #### Straight JavaScript
@@ -70,23 +69,11 @@ if ( elem.getContext && elem.getContext( "2d" ) ) {
 }
 ```
 
-This is a very simple way to provide conditional experiences, depending on the features present in the user's browser. We can extract this into a helper function for reuse, but still have to write a test for every feature we're concerned about. This can be time-consuming and error-prone.
-
-What if someone else wrote all of that for us?
-
-#### $.support
-
-jQuery performs many tests to determine feature support to allow cross-browser use of many of the features we've come to love. jQuery's internal feature detection can be accessed through [jQuery.support](http://api.jquery.com/jQuery.support/).
-
-However, we do not recommend this for general use. As the API page says:
-
-> Since jQuery requires these tests internally, they must be performed on every page load. Although some of these properties are documented below, they are not subject to a long deprecation/removal cycle and may be removed once internal jQuery code no longer needs them.
-
-This detection may be removed from jQuery without notice. That's reason enough not to use it. What other options do we have?
+This is a very simple way to provide conditional experiences, depending on the features present in the user's browser. We can extract this into a helper function for reuse, but still have to write a test for every feature we're concerned about. This can be time-consuming and error-prone. Instead you might be interested in using a helper library.
 
 #### A Helper Library
 
-Thankfully, there are some great helper libraries (like [Modernizr](http://modernizr.com)) that provide a simple, high-level API for determining if a browser has a specific feature available or not.
+Thankfully, there are some great helper libraries (like [Modernizr](http://modernizr.com/)) that provide a simple, high-level API for determining if a browser has a specific feature available or not.
 
 For example, utilizing Modernizr, we are able to do the same canvas detection test with this code:
 
@@ -98,39 +85,26 @@ if ( Modernizr.canvas ) {
 }
 ```
 
-That's it. Easy.
+For more in-depth information on Modernizr, feel free to check out their [documentation](http://modernizr.com/docs/).
 
 ### Performance Considerations
 
 So, while the Modernizr syntax is great, it can end up being quite cumbersome to have several conditionals. Secondly, we're sending the code for both conditions to every browser, regardless if we'll need it or not.
 
-The `Modernizr` object exposes a `load()` method that many prefer over the syntax mentioned previously. This is due to the another library that Modernizr now uses internally: [yepnope](http://yepnopejs.com/). Testing for canvas can now become something like this:
-
-```
-Modernizr.load({
-	test: Modernizr.canvas,
-	yep: "canvas.js",
-	nope: "canvas-polyfill.js"
-});
-```
-
-Using the `load` method allows us to send only the required polyfills and code over the wire. You can also pass an array of objects as an argument to `.load()`, and it will serve the correct files to the correct audience.
-
-Additionally, Modernizr has a [production build configurator](http://modernizr.com/download/) that allows you to specify exactly what parts of Modernizr you want to include and exclude the parts you don't.
+If you're using Modernizr, we highly encourage you to use the [build configurator](http://modernizr.com/download/), a tool that allows you to create custom builds of the library. You can exclude checks you don't need, which will save bytes and reduce the time it takes the page to load. Running every check that Modernizr can do, even when you don't need them, can slow down the page load.
 
 ### Other Resources
 
 #### Feature Detection Tools
 
-- [modernizr](http://modernizr.com/) — Conditionally check to see if a specific feature is available in a browser.
-- [html5please](http://html5please.com/) — Use the new and shiny responsibly.
-- [html5please api](http://api.html5please.com/) — An API you can query to see how good (or bad) support for a specific feature is.
-- [caniuse](http://caniuse.com/) — Browser compatibility tables for HTML5, CSS3, SVG, etc.
-- [yepnope](http://yepnopejs.com/) — Conditional polyfill loader.
+* [modernizr](http://modernizr.com/) — Conditionally check to see if a specific feature is available in a browser.
+* [html5please](http://html5please.com/) — Use the new and shiny responsibly.
+* [html5please API](http://api.html5please.com/) — An API you can query to see how good (or bad) support for a specific feature is.
+* [caniuse](http://caniuse.com/) — Browser compatibility tables for HTML5, CSS3, SVG, etc.
 
 #### Helpful Articles
 
-- [Browser Feature Detection](https://developer.mozilla.org/en-US/docs/Browser_Feature_Detection)
-- [Using Modernizr to detect HTML5 and CSS3 browser support](http://www.adobe.com/devnet/dreamweaver/articles/using-modernizr.html)
-- [polyfilling the html5 gap](http://addyosmani.com/polyfillthehtml5gaps/slides/#1) by Addy Osmani
-- [Feature, Browser, and Form Factor Detection: It's Good for the Environment](http://www.html5rocks.com/en/tutorials/detection/index.html) by Michael Mahemoff
+* [Browser Feature Detection](https://developer.mozilla.org/en-US/docs/Browser_Feature_Detection)
+* [Using Modernizr to detect HTML5 and CSS3 browser support](http://www.adobe.com/devnet/dreamweaver/articles/using-modernizr.html)
+* [Polyfilling the HTML5 gaps](http://addyosmani.com/polyfillthehtml5gaps/slides/#1) by Addy Osmani
+* [Feature, Browser, and Form Factor Detection: It's Good for the Environment](http://www.html5rocks.com/en/tutorials/detection/index.html) by Michael Mahemoff
diff --git a/page/contributing.md b/page/contributing.md
deleted file mode 120000
index 44fcc634..00000000
--- a/page/contributing.md
+++ /dev/null
@@ -1 +0,0 @@
-../CONTRIBUTING.md
\ No newline at end of file
diff --git a/page/contributing.md b/page/contributing.md
new file mode 100644
index 00000000..3b75228c
--- /dev/null
+++ b/page/contributing.md
@@ -0,0 +1,11 @@
+<script>{
+    "title": "Contributing",
+    "customFields": [
+        {
+            "key": "is_chapter",
+            "value": 0
+        }
+    ]
+}</script>
+
+@partial(CONTRIBUTING.md)
diff --git a/page/effects.md b/page/effects.md
index 3a91733b..2d32c1ca 100644
--- a/page/effects.md
+++ b/page/effects.md
@@ -1,14 +1,14 @@
----
-title: Effects
-level: beginner
-customFields:
- -
-    key: "icon"
-    value: "picture"
----
-jQuery makes it trivial to add simple effects to your page. Effects can use
-the built-in settings, or provide a customized duration. You can also create
-custom animations of arbitrary CSS properties.
+<script>{
+	"title": "Effects",
+	"level": "beginner",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "picture"
+		}
+	]
+}</script>
 
-For complete details on jQuery effects, visit the
-[Effects documentation on api.jquery.com](http://api.jquery.com/category/effects/).
+jQuery makes it trivial to add simple effects to your page. Effects can use the built-in settings, or provide a customized duration. You can also create custom animations of arbitrary CSS properties.
+
+For complete details on jQuery effects, visit the [Effects documentation on api.jquery.com](http://api.jquery.com/category/effects/).
diff --git a/page/effects/custom-effects.md b/page/effects/custom-effects.md
index 21c2b096..082f827c 100644
--- a/page/effects/custom-effects.md
+++ b/page/effects/custom-effects.md
@@ -1,41 +1,37 @@
----
-title   : Custom Effects with .animate()
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-    - jQuery Fundamentals
----
-jQuery makes it possible to animate arbitrary CSS properties via the
-`.animate()` method. The `.animate()` method lets you animate to a set
-value, or to a value relative to the current value.
+<script>{
+	"title": "Custom Effects with .animate()",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+jQuery makes it possible to animate arbitrary CSS properties via the `.animate()` method. The `.animate()` method lets you animate to a set value, or to a value relative to the current value.
 
 ```
 // Custom effects with .animate()
-$( "div.funtimes" ).animate({
+$( "div.funtimes" ).animate(
+	{
 		left: "+=50",
 		opacity: 0.25
 	},
-	300, // Duration
-	function() { // Callback when the animation is finished
+
+	// Duration
+	300,
+
+	// Callback to invoke when the animation is finished
+	function() {
 		console.log( "done!" );
 	}
 );
 ```
 
-**Note:** Color-related properties cannot be animated with `.animate()` using jQuery
-out of the box. Color animations can easily be accomplished by including the
-[color plugin](http://github.com/jquery/jquery-color). We'll discuss using
-plugins later in the book.
+**Note:** Color-related properties cannot be animated with `.animate()` using jQuery out of the box. Color animations can easily be accomplished by including the [color plugin](https://github.com/jquery/jquery-color). We'll discuss using plugins later in the book.
 
 ### Easing
 
-Definition: Easing describes the manner in which an effect occurs — whether
-the rate of change is steady, or varies over the duration of the animation.
-jQuery includes only two methods of easing: swing and linear. If you want more
-natural transitions in your animations, various easing plugins are available.
+Definition: Easing describes the manner in which an effect occurs — whether the rate of change is steady, or varies over the duration of the animation. jQuery includes only two methods of easing: swing and linear. If you want more natural transitions in your animations, various easing plugins are available.
 
-As of jQuery 1.4, it is possible to do per-property easing when using the
-`.animate()` method.
+As of jQuery 1.4, it is possible to do per-property easing when using the `.animate()` method.
 
 ```
 // Per-property easing
@@ -45,5 +41,4 @@ $( "div.funtimes" ).animate({
 }, 300 );
 ```
 
-For more details on easing options, see
-[Animation documentation on api.jquery.com](http://api.jquery.com/animate/).
+For more details on easing options, see [Animation documentation on api.jquery.com](http://api.jquery.com/animate/).
diff --git a/page/effects/intro-to-effects.md b/page/effects/intro-to-effects.md
index 29d6179a..abbcfbe1 100644
--- a/page/effects/intro-to-effects.md
+++ b/page/effects/intro-to-effects.md
@@ -1,7 +1,7 @@
----
-title: Introduction to Effects
-level: beginner
----
+<script>{
+	"title": "Introduction to Effects",
+	"level": "beginner"
+}</script>
 
 ## Showing and Hiding Content
 
@@ -15,12 +15,9 @@ $( "p" ).hide();
 $( "div.hidden" ).show();
 ```
 
-When jQuery hides an element, it sets its CSS `display` property to `none`. This means the content will have
-zero width and height; it does not mean that the content will simply become transparent and leave an empty area on the page.
+When jQuery hides an element, it sets its CSS `display` property to `none`. This means the content will have zero width and height; it does not mean that the content will simply become transparent and leave an empty area on the page.
 
-jQuery can also show or hide content by means of animation effects. You can tell
-`.show()` and `.hide()` to use animation in a couple of ways. One is to pass
-in an argument of `'slow'`, `'normal'`, or `'fast'`:
+jQuery can also show or hide content by means of animation effects. You can tell `.show()` and `.hide()` to use animation in a couple of ways. One is to pass in an argument of `'slow'`, `'normal'`, or `'fast'`:
 
 ```
 // Slowly hide all paragraphs
@@ -30,8 +27,7 @@ $( "p" ).hide( "slow" );
 $( "div.hidden" ).show( "fast" );
 ```
 
-If you prefer more direct control over the duration of the animation effect, you
-can pass the desired duration in milliseconds to `.show()` and `.hide()`:
+If you prefer more direct control over the duration of the animation effect, you can pass the desired duration in milliseconds to `.show()` and `.hide()`:
 
 ```
 // Hide all paragraphs over half a second
@@ -41,16 +37,11 @@ $( "p" ).hide( 500 );
 $( "div.hidden" ).show( 1250 );
 ```
 
-Most developers pass in a number of milliseconds to have more precise control
-over the duration.
+Most developers pass in a number of milliseconds to have more precise control over the duration.
 
-##Fade and Slide Animations
+## Fade and Slide Animations
 
-You may have noticed that `.show()` and `.hide()` use a combination of slide and fade effects
-when showing and hiding content in an animated way. If you would rather show or hide content with
-one effect or the other, there are additional methods that can help. `.slideDown()` and `.slideUp()`
-show and hide content, respectively, using only a slide effect. Slide animations are accomplished by
-rapidly making changes to an element's CSS `height` property.
+You may have noticed that `.show()` and `.hide()` use a combination of slide and fade effects when showing and hiding content in an animated way. If you would rather show or hide content with one effect or the other, there are additional methods that can help. `.slideDown()` and `.slideUp()` show and hide content, respectively, using only a slide effect. Slide animations are accomplished by rapidly making changes to an element's CSS `height` property.
 
 ```
 // Hide all paragraphs using a slide up animation over 0.8 seconds
@@ -60,8 +51,7 @@ $( "p" ).slideUp( 800 );
 $( "div.hidden" ).slideDown( 600 );
 ```
 
-Similarly `.fadeIn()` and `.fadeOut()` show and hide content, respectively, by means of a fade
-animation. Fade animations involve rapidly making changes to an element's CSS `opacity` property.
+Similarly `.fadeIn()` and `.fadeOut()` show and hide content, respectively, by means of a fade animation. Fade animations involve rapidly making changes to an element's CSS `opacity` property.
 
 ```
 // Hide all paragraphs using a fade out animation over 1.5 seconds
@@ -71,11 +61,9 @@ $( "p" ).fadeOut( 1500 );
 $( "div.hidden" ).fadeIn( 750 );
 ```
 
-##Changing Display Based on Current Visibility State
+## Changing Display Based on Current Visibility State
 
-jQuery can also let you change a content's visibility based on its current visibility state. `.toggle()`
-will show content that is currently hidden and hide content that is currently visible. You can pass the
-same arguments to `.toggle()` as you pass to any of the effects methods above.
+jQuery can also let you change a content's visibility based on its current visibility state. `.toggle()` will show content that is currently hidden and hide content that is currently visible. You can pass the same arguments to `.toggle()` as you pass to any of the effects methods above.
 
 ```
 // Instantaneously toggle the display of all paragraphs
@@ -88,8 +76,7 @@ $( "img" ).toggle( "slow" );
 $( "div" ).toggle( 1800 );
 ```
 
-`.toggle()` will use a combination of slide and fade effects, just as `.show()` and `.hide()` do. You can
-toggle the display of content with just a slide or a fade using `.slideToggle()` and `.fadeToggle()`.
+`.toggle()` will use a combination of slide and fade effects, just as `.show()` and `.hide()` do. You can toggle the display of content with just a slide or a fade using `.slideToggle()` and `.fadeToggle()`.
 
 ```
 // Toggle the display of all ordered lists over 1 second using slide up/down animations
@@ -99,25 +86,18 @@ $( "ol" ).slideToggle( 1000 );
 $( "blockquote" ).fadeToggle( 400 );
 ```
 
-##Doing Something After an Animation Completes
+## Doing Something After an Animation Completes
 
-A common mistake when implementing jQuery effects is assuming that the execution of the next method in your
-chain will wait until the animation runs to completion.
+A common mistake when implementing jQuery effects is assuming that the execution of the next method in your chain will wait until the animation runs to completion.
 
 ```
 // Fade in all hidden paragraphs; then add a style class to them (not quite right)
 $( "p.hidden" ).fadeIn( 750 ).addClass( "lookAtMe" );
 ```
 
-It is important to realize that `.fadeIn()` above only *kicks off* the animation. Once started, the
-animation is implemented by rapidly changing CSS properties in a JavaScript `setInterval()` loop. When
-you call `.fadeIn()`, it starts the animation loop and then returns the jQuery object, passing it along
-to `.addClass()` which will then add the `lookAtMe` style class while the animation loop is just
-getting started.
+It is important to realize that `.fadeIn()` above only *kicks off* the animation. Once started, the animation is implemented by rapidly changing CSS properties in a JavaScript `setInterval()` loop. When you call `.fadeIn()`, it starts the animation loop and then returns the jQuery object, passing it along to `.addClass()` which will then add the `lookAtMe` style class while the animation loop is just getting started.
 
-To defer an action until after an animation has run to completion, you need to use an animation callback
-function. You can specify your animation callback as the second argument passed to any of the
-animation methods discussed above. For the code snippet above, we can implement a callback as follows:
+To defer an action until after an animation has run to completion, you need to use an animation callback function. You can specify your animation callback as the second argument passed to any of the animation methods discussed above. For the code snippet above, we can implement a callback as follows:
 
 ```
 // Fade in all hidden paragraphs; then add a style class to them (correct with animation callback)
@@ -127,10 +107,7 @@ $( "p.hidden" ).fadeIn( 750, function() {
 });
 ```
 
-Note that you can use the keyword `this` to refer to the DOM element being animated. Also note
-that the callback will be called for each element in the jQuery object. This means that if your
-selector returns no elements, your animation callback will never run! You can solve this problem by
-testing whether your selection returned any elements; if not, you can just run the callback immediately.
+Note that you can use the keyword `this` to refer to the DOM element being animated. Also note that the callback will be called for each element in the jQuery object. This means that if your selector returns no elements, your animation callback will never run! You can solve this problem by testing whether your selection returned any elements; if not, you can just run the callback immediately.
 
 ```
 // Run a callback even if there were no elements to animate
@@ -153,8 +130,7 @@ jQuery provides some additional features for controlling your animations:
 
 ### `.stop()`
 
-`.stop()` will immediately terminate all animations running on the elements in your selection. You might give
-end-users control over page animations by rigging a button they can click to stop the animations.
+`.stop()` will immediately terminate all animations running on the elements in your selection. You might give end-users control over page animations by rigging a button they can click to stop the animations.
 
 ```
 // Create a button to stop all animations on the page:
@@ -178,9 +154,7 @@ $( "h1" ).hide( 500 ).delay( 1500 ).show( 300 );
 
 ### `jQuery.fx`
 
-The `jQuery.fx` object has a number of properties that control how effects are implemented. `jQuery.fx.speeds` maps
-the `slow`, `normal`, and `fast` duration arguments mentioned above to a specific
-number of milliseconds. The default value of `jQuery.fx.speeds` is:
+The `jQuery.fx` object has a number of properties that control how effects are implemented. `jQuery.fx.speeds` maps the `slow`, `normal`, and `fast` duration arguments mentioned above to a specific number of milliseconds. The default value of `jQuery.fx.speeds` is:
 
 ```
 {
@@ -198,17 +172,9 @@ jQuery.fx.speeds.blazing = 100;
 jQuery.fx.speeds.excruciating = 60000;
 ```
 
-`jQuery.fx.interval` controls the number of frames per second that is
-displayed in an animation. The default value is 13 milliseconds between
-successive frames. You can set this to a lower value for faster browsers
-to make the animations run smoother. However this will mean more frames
-per second and thus a higher computational load for the browser, so you
-should be sure to test the performance implications of doing so thoroughly.
+`jQuery.fx.interval` controls the number of frames per second that is displayed in an animation. The default value is 13 milliseconds between successive frames. You can set this to a lower value for faster browsers to make the animations run smoother. However this will mean more frames per second and thus a higher computational load for the browser, so you should be sure to test the performance implications of doing so thoroughly.
 
-Finally, `jQuery.fx.off` can be set to true to disable all animations. Elements
-will immediately be set to the target final state instead. This can be
-especially useful when dealing with older browsers; you also may want to
-provide the option to disable all animations to your users.
+Finally, `jQuery.fx.off` can be set to true to disable all animations. Elements will immediately be set to the target final state instead. This can be especially useful when dealing with older browsers; you also may want to provide the option to disable all animations to your users.
 
 ```
 $( "<button type='button'></button>" )
diff --git a/page/effects/queue-and-dequeue-explained.md b/page/effects/queue-and-dequeue-explained.md
index aaa95f2b..0bc59825 100644
--- a/page/effects/queue-and-dequeue-explained.md
+++ b/page/effects/queue-and-dequeue-explained.md
@@ -1,58 +1,118 @@
----
-title:        Queue & Dequeue Explained
-level:        advanced
-source:       http://jqueryfordesigners.com/api-queue-dequeue/
----
+<script>{
+	"title": "Queue & Dequeue Explained",
+	"level": "advanced",
+	"source": "http://jqueryfordesigners.com/api-queue-dequeue/"
+}</script>
 
-When you use the `animate`, and `show`, `hide`, `slideUp`, etc. effect methods, you're
-adding a job to the effects queue. By default, using `queue()` and passing a function,
-will add it to the effects queue. So we're creating our own bespoke animation step:
+Queues are the foundation for all animations in jQuery, they allow a series functions to be executed asynchronously on an element.  Methods such as `.slideUp()`, `.slideDown()`, `.fadeIn()`, and `.fadeOut()` all use `.animate()`, which leverages *queues* to build up the series of steps that will transition one or more CSS values throughout the duration of the animation.
+
+We can pass a callback function to the `.animate()` method, which will execute once the animation has completed.
+
+```
+$( ".box" )
+	.animate( {
+		height: 20
+	}, "slow", function() {
+		$( "#title" ).html( "We're in the callback, baby!" );
+	} );
+```
+
+## Queues As Callbacks
+
+Instead of passing a callback as an argument, we can add another function to the *queue* that will act as our callback. This will execute after all of the steps in the animation have completed.
+
+```
+$( ".box" )
+	.animate( {
+		height: 20
+	}, "slow")
+	.queue( function() {
+		$( "#title" ).html( "We're in the animation, baby!" );
+
+		// This tells jQuery to continue to the next item in the queue
+		$( this ).dequeue();
+	} );
+
+```
+
+In this example, the queued function will execute right after the animation.
+
+jQuery does not have any insight into how the queue items function, so we need to call `.dequeue()`, which tells jQuery when to move to the next item in the queue.
+
+Another way of *dequeuing* is by calling the function that is passed to your callback. That function will automatically call `.dequeue()` for you.
 
 ```
-$( ".box" ).animate({
-	height: 20
-}, "slow" ).queue(function() {
-	$( "#title" ).html( "We're in the animation, baby!" );
-});
+.queue( function( next ) {
+	console.log( "I fired!" );
+	next();
+} );
 ```
 
-As I said though, these methods come in pairs, so anything you add using `queue()`,
-you need to dequeue to allow the process to continue. In the code above, if I
-chained more animations on, until I call `$( this ).dequeue()`, the subsequent
-animations wouldn't run:
+## Custom Queues
+
+Up to this point all of our animation and queue examples have been using the default queue name which is `fx`.  Elements can have multiple queues attached to them, and we can give each of these queues a different name.  We can specify a custom queue name as the first argument to the `.queue()` method.
+
+```
+$( ".box" )
+	.queue( "steps", function( next ) {
+		console.log( "Step 1" );
+		next();
+	} )
+	.queue( "steps", function( next ) {
+		console.log( "Step 2" );
+		next();
+	} )
+	.dequeue( "steps" );
+```
+
+Notice that we have to call the `.dequeue()` method passing it the name of our custom queue to start the execution. Every queue except for the default, `fx`, has to be manually kicked off by calling `.dequeue()` and passing it the name of the queue.
+
+## Clearing The Queue
+
+Since queues are just a set of ordered operations, our application may have some logic in place that needs to prevent the remaining queue entries from executing. We can do this by calling the `.clearQueue()` method, which will empty the queue.
 
 ```
-$( ".box" ).animate({
-	height: 20
-}, "slow" ).queue(function() {
-	$( "#title" ).html( "We're in the animation, baby!" );
-	$( this ).dequeue();
-}).animate({
-	height: 150
-});
+$( ".box" )
+	.queue( "steps", function( next ) {
+		console.log( "Will never log because we clear the queue" );
+		next();
+	} )
+	.clearQueue( "steps" )
+	.dequeue( "steps" );
 ```
 
-Keeping in mind that the animation won't continue until we've explicitly called
-`dequeue()`, we can easily create a pausing plugin, by adding a step in the queue
-that sets a timer and triggers after `n` milliseconds, at which time, it dequeues
-the element:
+In this example, nothing will happen as we removed everything from the `steps` queue.
 
+Another way of clearing the queue is to call `.stop( true )`. That will stop the currently running animations and will clear the queue.
+
+## Replacing The Queue
+
+When you pass an array of functions as the second argument to `.queue()`, that array will replace the queue.
+
+```
+$( ".box" )
+	.queue( "steps", function( next ) {
+		console.log( "I will never fire as we totally replace the queue" );
+		next();
+	} )
+	.queue( "steps", [
+		function( next ) {
+			console.log( "I fired!" );
+			next();
+		}
+	] )
+	.dequeue( "steps" );
 ```
-$.fn.pause = function( n ) {
-	return this.queue(function() {
-		var el = this;
-		setTimeout(function() {
-			return $( el ).dequeue();
-		}, n );
-	});
-};
 
-$( ".box" ).animate({
-	height: 20
-}, "slow" ).pause( 1000 ).animate({
-	height: 150
-});
+You can also call `.queue()` without passing it functions, which will return the queue of that element as an array.
+
 ```
+$( ".box" ).queue( "steps", function( next ) {
+	console.log( "I fired!" );
+	next();
+} );
+
+console.log( $( ".box" ).queue( "steps" ) );
 
-Remember that the first argument for `queue()` and `dequeue()` is `fx`, and that in
-all of these examples I'm not including it because jQuery sets the argument to `fx` by default — so I don't have to specify it.
+$( ".box" ).dequeue( "steps" );
+```
diff --git a/page/effects/uses-of-queue-and-dequeue.md b/page/effects/uses-of-queue-and-dequeue.md
deleted file mode 100644
index df79588e..00000000
--- a/page/effects/uses-of-queue-and-dequeue.md
+++ /dev/null
@@ -1,225 +0,0 @@
----
-title:        The uses of jQuery .queue() and .dequeue()
-level:        advanced
-source:       http://gnarf.net/2010/09/30/the-uses-of-jquery-queue-and-dequeue/
----
-
-Queues in jQuery are used for animations. You can use them for any purpose you
-like. They are an array of functions stored on a per element basis, using
-`jQuery.data()`. They are First In, First Out (FIFO). You can add a function to the
-queue by calling `.queue()`, and you remove (by calling) the functions using
-`.dequeue()`.
-
-To understand the internal jQuery queue functions, reading the source and
-looking at examples helps me out tremendously. One of the best examples of a
-queue function I've seen is `.delay()`:
-
-```
-$.fn.delay = function( time, type ) {
-
-	time = jQuery.fx ? jQuery.fx.speeds[ time ] || time : time;
-
-	type = type || "fx";
-
-	return this.queue( type, function() {
-
-		var elem = this;
-
-		setTimeout(function() {
-
-			jQuery.dequeue( elem, type );
-
-		}, time );
-
-	});
-
-};
-```
-
-## The default queue – fx
-
-The default queue in jQuery is `fx`. The default queue has some special
-properties that are not shared with other queues.
-
-- Auto Start: When calling `$(elem).queue( function() {} );` the fx queue will
-  automatically dequeue the next function and run it if the queue hasn't
-  started.
-- “inprogress” sentinel: Whenever you `dequeue()` a function from the fx queue,
-  it will `unshift()` (push into the first location of the array) the string
-  “inprogress” — which flags that the queue is currently being run.
-- It's the default! The fx queue is used by `.animate()` and all functions that
-  call it by default.
-
-**Note:** If you are using a custom queue, you must manually `.dequeue()` the functions, they will not auto start!
-
-## Retrieving/Setting the queue
-
-You can retrieve a reference to a jQuery queue by calling `.queue()` without a
-function argument. You can use the method if you want to see how many items are
-in the queue. You can use `push`, `pop`, `unshift`, and `shift` to manipulate the queue in
-place. You can replace the entire queue by passing an array to the `.queue()`
-function.
-
-## Quick Examples:
-
-```
-// Let's assume elem is a jQuery object that points to some element we are animating.
-var queue = elem.queue();
-
-// Remove the last function from the animation queue.
-var lastFunc = queue.pop();
-
-// Insert it at the beginning:
-queue.unshift( lastFunc );
-
-// Replace queue with the first three items in the queue.
-elem.queue( queue.slice( 0, 3 ) );
-```
-
-### An animation (fx) queue example:
-
-```
-$(function() {
-	// Let's do something with Google Maps:
-	var canvas = $( "#map_canvas" );
-
-	var myLatlng = new google.maps.LatLng( -34.397, 150.644 );
-
-	var myOptions = {
-		zoom: 8,
-		center: myLatlng,
-		mapTypeId: google.maps.MapTypeId.ROADMAP
-	};
-
-	var geocoder = new google.maps.Geocoder();
-
-	var map = new google.maps.Map( canvas[0], myOptions );
-
-	var resized = function() {
-		// simple animation callback - let maps know we resized
-		google.maps.event.trigger( map, "resize" );
-	};
-
-	canvas.delay( 2000 ); // Wait for two seconds.
-
-	// resize the div:
-	canvas.animate({
-		width: 250,
-		height: 250,
-		marginLeft: 250,
-		marginTop:250
-	}, resized );
-
-	// geocode something
-	canvas.queue(function( next ) {
-		// find stackoverflow's whois address:
-		geocoder.geocode( {
-			address: "55 Broadway New York NY 10006"
-		}, handleResponse );
-
-		function handleResponse( results, status ) {
-			if ( status === google.maps.GeocoderStatus.OK ) {
-				var location = results[ 0 ].geometry.location;
-				map.setZoom( 13 );
-				map.setCenter( location );
-				new google.maps.Marker({
-					map: map,
-					position: location
-				});
-			}
-
-			// geocoder result returned, continue with animations:
-			next();
-		}
-	});
-
-	// after we find stack overflow, wait 3 more seconds
-	canvas.delay( 3000 );
-
-	// and resize the map again
-	canvas.animate({
-		width: 500,
-		height: 500,
-		marginLeft:0,
-		marginTop: 0
-	}, resized );
-});
-```
-
-### Queueing something like Ajax Calls:
-
-```
-// jQuery on an empty object, we are going to use this as our queue
-var ajaxQueue = $({});
-
-$.ajaxQueue = function( ajaxOpts ) {
-	// Hold the original complete function.
-	var oldComplete = ajaxOpts.complete;
-
-	// Queue our ajax request.
-	ajaxQueue.queue(function( next ) {
-		// Create a complete callback to fire the next event in the queue.
-		ajaxOpts.complete = function() {
-			// Fire the original complete if it was there.
-			if ( oldComplete ) {
-				oldComplete.apply( this, arguments );
-			}
-			// Run the next query in the queue.
-			next();
-		};
-
-		// Run the query.
-		$.ajax( ajaxOpts );
-	});
-};
-
-// Get each item we want to copy.
-$( "#items li" ).each(function( idx ) {
-	// Queue up an ajax request.
-	$.ajaxQueue({
-		url: "/ajax_html_echo/",
-		data: {
-			html: "[" + idx + "] " + $( this ).html()
-		},
-		type: "POST",
-		success: function( data ) {
-			// Write to #output.
-			$( "#output" ).append( $( "<li>", {
-				html: data
-			}));
-		}
-	});
-});
-```
-
-### Another custom queue example
-
-```
-var theQueue = $({}); // jQuery on an empty object - a perfect queue holder
-
-$.each([ 1, 2, 3 ], function( i, num ) {
-	// Let's add some really simple functions to a queue:
-	theQueue.queue( "alerts", function( next ) {
-		// Show something, and if they hit "yes", run the next function.
-		if ( confirm( "index: " + i + " = " + num + "\nRun the next function?" ) ) {
-			next();
-		}
-	});
-});
-
-// Create a button to run the queue.
-$( "<button>", {
-	text: "Run Queue",
-	click: function() {
-		theQueue.dequeue( "alerts" );
-	}
-}).appendTo( "body" );
-
-// Create a button to show the length.
-$( "<button>", {
-	text: "Show Length",
-	click: function() {
-		alert( theQueue.queue( "alerts" ).length );
-	}
-}).appendTo( "body" );
-```
diff --git a/page/events.md b/page/events.md
index 1fffebe9..106405f5 100644
--- a/page/events.md
+++ b/page/events.md
@@ -1,21 +1,18 @@
----
-title: Events
-level: beginner
-customFields:
- -
-    key: "icon"
-    value: "tasks"
----
-jQuery provides simple methods for attaching event handlers to selections.
-When an event occurs, the provided function is executed. Inside the function,
-`this` refers to the element that was clicked.
+<script>{
+	"title": "Events",
+	"level": "beginner",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "tasks"
+		}
+	]
+}</script>
 
-For details on jQuery events, visit the
-[Events documentation on api.jquery.com](http://api.jquery.com/category/events/).
+jQuery provides simple methods for attaching event handlers to selections. When an event occurs, the provided function is executed. Inside the function, `this` refers to the DOM element that initiated the event.
 
-The event handling function can receive an event object. This object can be
-used to determine the nature of the event, and to prevent the event’s default
-behavior.
+For details on jQuery events, visit the [Events documentation on api.jquery.com](http://api.jquery.com/category/events/).
 
-For details on the event object, visit the
-[Event object documentation on api.jquery.com](http://api.jquery.com/category/events/event-object/).
+The event handling function can receive an event object. This object can be used to determine the nature of the event, and to prevent the event’s default behavior.
+
+For details on the event object, visit the [Event object documentation on api.jquery.com](http://api.jquery.com/category/events/event-object/).
diff --git a/page/events/event-basics.md b/page/events/event-basics.md
index 3c727623..e0007c8c 100644
--- a/page/events/event-basics.md
+++ b/page/events/event-basics.md
@@ -1,26 +1,16 @@
----
-title: jQuery Event Basics
-attribution:
-  - jQuery Fundamentals
-level: beginner
----
+<script>{
+	"title": "jQuery Event Basics",
+	"level": "beginner",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 ## jQuery Event Basics
 
 ### Setting Up Event Responses on DOM Elements
 
-jQuery makes it straightforward to set up event-driven responses on page elements.
-These events are often triggered by the end user's interaction with the page,
-such as when text is entered into a form element or the mouse pointer is moved.
-In some cases, such as the page load and unload events, the browser itself will
-trigger the event.
+jQuery makes it straightforward to set up event-driven responses on page elements. These events are often triggered by the end user's interaction with the page, such as when text is entered into a form element or the mouse pointer is moved. In some cases, such as the page load and unload events, the browser itself will trigger the event.
 
-jQuery offers convenience methods for most native browser events. These methods —
-including `.click()`, `.focus()`, `.blur()`, `.change()`, etc. — are shorthand
-for jQuery's `.on()` method. The on method is useful for binding the same handler
-function to multiple events, when you want to provide data to the event handler,
-when you are working with custom events, or when you want to pass an object of
-multiple events and handlers.
+jQuery offers convenience methods for most native browser events. These methods — including `.click()`, `.focus()`, `.blur()`, `.change()`, etc. — are shorthand for jQuery's `.on()` method. The on method is useful for binding the same handler function to multiple events, when you want to provide data to the event handler, when you are working with custom events, or when you want to pass an object of multiple events and handlers.
 
 ```
 // Event setup using a convenience method
@@ -38,43 +28,37 @@ $( "p" ).on( "click", function() {
 
 ### Extending Events to New Page Elements
 
-It is important to note that `.on()` can only create event listeners
-on elements that exist *at the time you set up the listeners*. Similar elements created
-after the event listeners are established will not automatically pick up event behaviors
-you've set up previously. For example:
+It is important to note that `.on()` can only create event listeners on elements that exist *at the time you set up the listeners*. Similar elements created after the event listeners are established will not automatically pick up event behaviors you've set up previously. For example:
 
 ```
 $( document ).ready(function(){
+
 	// Sets up click behavior on all button elements with the alert class
 	// that exist in the DOM when the instruction was executed
 	$( "button.alert" ).on( "click", function() {
 		console.log( "A button with the alert class was clicked!" );
 	});
+
 	// Now create a new button element with the alert class. This button
 	// was created after the click listeners were applied above, so it
 	// will not have the same click behavior as its peers
-	$( "button" ).addClass( "alert" ).appendTo( document.body );
+	$( "<button class='alert'>Alert!</button>" ).appendTo( document.body );
 });
 ```
 
-Consult the article on event delegation to see how to use `.on()` so that
-event behaviors will be extended to new elements without having to rebind them.
+Consult the article on event delegation to see how to use `.on()` so that event behaviors will be extended to new elements without having to rebind them.
 
 ### Inside the Event Handler Function
 
-Every event handling function receives an event object, which contains many
-properties and methods. The event object is most commonly used to prevent the
-default action of the event via the `.preventDefault()` method. However, the event
-object contains a number of other useful properties and methods, including:
+Every event handling function receives an event object, which contains many properties and methods. The event object is most commonly used to prevent the default action of the event via the `.preventDefault()` method. However, the event object contains a number of other useful properties and methods, including:
 
 #### pageX, pageY
 
-The mouse position at the time the event occurred, relative to the top left corner of
-the page display area (not the entire browser window).
+The mouse position at the time the event occurred, relative to the top left corner of the page display area (not the entire browser window).
 
 #### type
 
-The type of the event (e.g. "click").
+The type of the event (e.g., "click").
 
 #### which
 
@@ -88,7 +72,7 @@ Any data that was passed in when the event was bound. For example:
 // Event setup using the `.on()` method with data
 $( "input" ).on(
 	"change",
-	{ foo: "bar" }, // associate data with event binding
+	{ foo: "bar" }, // Associate data with event binding
 	function( eventObject ) {
 		console.log("An input value has changed! ", eventObject.data.foo);
 	}
@@ -115,10 +99,7 @@ Prevent the default action of the event (e.g. following a link).
 
 Stop the event from bubbling up to other elements.
 
-In addition to the event object, the event handling function also has access to
-the DOM element that the handler was bound to via the keyword `this`. To turn
-the DOM element into a jQuery object that we can use jQuery methods on, we
-simply do `$( this )`, often following this idiom:
+In addition to the event object, the event handling function also has access to the DOM element that the handler was bound to via the keyword `this`. To turn the DOM element into a jQuery object that we can use jQuery methods on, we simply do `$( this )`, often following this idiom:
 
 ```
 var element = $( this );
@@ -139,23 +120,19 @@ $( "a" ).click(function( eventObject ) {
 
 ### Setting Up Multiple Event Responses
 
-Quite often elements in your application will be bound to multiple events. If
-multiple events are to share the same handling function, you can provide the event types
-as a space-separated list to `.on()`:
+Quite often elements in your application will be bound to multiple events. If multiple events are to share the same handling function, you can provide the event types as a space-separated list to `.on()`:
 
 ```
 // Multiple events, same handler
 $( "input" ).on(
-	"click change",  // bind listeners for multiple events
+	"click change", // Bind handlers for multiple events
 	function() {
-		console.log( "An input was clicked or changed!" )
+		console.log( "An input was clicked or changed!" );
 	}
 );
 ```
 
-When each event has its own handler, you can pass an object into `.on()` with one or
-more key/value pairs, with the key being the event name and the value being the function
-to handle the event.
+When each event has its own handler, you can pass an object into `.on()` with one or more key/value pairs, with the key being the event name and the value being the function to handle the event.
 
 ```
 // Binding multiple events with different handlers
@@ -167,23 +144,18 @@ $( "p" ).on({
 
 ### Namespacing Events
 
-For complex applications and for plugins you share with others, it can be
-useful to namespace your events so you don't unintentionally disconnect events
-that you didn't or couldn't know about.
+For complex applications and for plugins you share with others, it can be useful to namespace your events so you don't unintentionally disconnect events that you didn't or couldn't know about.
 
 ```
 // Namespacing events
 $( "p" ).on( "click.myNamespace", function() { /* ... */ } );
 $( "p" ).off( "click.myNamespace" );
-$( "p" ).off( ".myNamespace" ); // unbind all events in the namespace
+$( "p" ).off( ".myNamespace" ); // Unbind all events in the namespace
 ```
 
 ### Tearing Down Event Listeners
 
-To remove an event listener, you use the `.off()` method and pass in
-the event type to off. If you attached a named function to the event, then
-you can isolate the event tear down to just that named function by passing it as the
-second argument.
+To remove an event listener, you use the `.off()` method and pass in the event type to off. If you attached a named function to the event, then you can isolate the event tear down to just that named function by passing it as the second argument.
 
 ```
 // Tearing down all click handlers on a selection
@@ -201,25 +173,22 @@ $( "p" ).off( "click", bar ); // foo is still bound to the click event
 
 ### Setting Up Events to Run Only Once
 
-Sometimes you need a particular handler to run only once — after that, you may
-want no handler to run, or you may want a different handler to run. jQuery
-provides the `.one()` method for this purpose.
+Sometimes you need a particular handler to run only once — after that, you may want no handler to run, or you may want a different handler to run. jQuery provides the `.one()` method for this purpose.
 
 ```
-// Switching handlers using the `$.fn.one` method
+// Switching handlers using the `.one()` method
 $( "p" ).one( "click", firstClick );
 
 function firstClick() {
 	console.log( "You just clicked this for the first time!" );
+
 	// Now set up the new handler for subsequent clicks;
 	// omit this step if no further click responses are needed
 	$( this ).click( function() { console.log( "You have clicked this before!" ); } );
 }
 ```
 
-Note that in the code snippet above, the `firstClick` function will be executed for
-the first click on *each* paragraph element rather than the function being removed from
-*all* paragraphs when *any* paragraph is clicked for the first time.
+Note that in the code snippet above, the `firstClick` function will be executed for the first click on *each* paragraph element rather than the function being removed from *all* paragraphs when *any* paragraph is clicked for the first time.
 
 `.one()` can also be used to bind multiple events:
 
@@ -232,6 +201,4 @@ function firstEvent( eventObject ) {
 }
 ```
 
-In this case, the `firstEvent` function will be executed once *for each event*. For the snippet above, this means
-that once an input element gains focus, the handler function will still execute for the first keydown event on that
-element.
+In this case, the `firstEvent` function will be executed once *for each event*. For the snippet above, this means that once an input element gains focus, the handler function will still execute for the first keydown event on that element.
diff --git a/page/events/event-delegation.md b/page/events/event-delegation.md
index ca3fde5d..7dff6ef6 100644
--- a/page/events/event-delegation.md
+++ b/page/events/event-delegation.md
@@ -1,10 +1,9 @@
----
-title   : Understanding Event Delegation
-level: intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Understanding Event Delegation",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 ## Introduction
 
@@ -31,7 +30,7 @@ For the remainder of the lesson, we will reference the following HTML structure:
 When an anchor in our `#list` group is clicked, we want to log its text to the console. Normally we could directly bind to the click event of each anchor using the `.on()` method:
 
 ```
-// attach a directly bound event
+// Attach a directly bound event handler
 $( "#list a" ).on( "click", function( event ) {
 	event.preventDefault();
 	console.log( $( this ).text() );
@@ -41,7 +40,7 @@ $( "#list a" ).on( "click", function( event ) {
 While this works perfectly fine, there are drawbacks. Consider what happens when we add a new anchor after having already bound the above listener:
 
 ```
-// add a new element on to our existing list
+// Add a new element on to our existing list
 $( "#list" ).append( "<li><a href='http://newdomain.com'>Item #5</a></li>" );
 ```
 
@@ -61,10 +60,10 @@ Understanding how events propagate is an important factor in being able to lever
 
 This means that anytime you click one of our bound anchor tags, you are effectively clicking the entire document body! This is called *event bubbling* or *event propagation*.
 
-Since we know how events bubble, we can create a *delegated* event: 
+Since we know how events bubble, we can create a *delegated* event:
 
 ```
-// attach a delegated event
+// Attach a delegated event handler
 $( "#list" ).on( "click", "a", function( event ) {
 	event.preventDefault();
 	console.log( $( this ).text() );
@@ -75,10 +74,10 @@ Notice how we have moved the `a` part from the selector to the second parameter
 
 ### Using the Triggering Element
 
-What if we wanted to open the link in a new window if that link is an external one (as denoted here by beginning with "http")? 
+What if we wanted to open the link in a new window if that link is an external one (as denoted here by beginning with "http")?
 
 ```
-// attach a delegated event
+// Attach a delegated event handler
 $( "#list" ).on( "click", "a", function( event ) {
 	var elem = $( this );
 	if ( elem.is( "[href^='http']" ) ) {
@@ -92,11 +91,12 @@ This simply passes the `.is()` method a selector to see if the `href` attribute
 We can actually simplify our code by allowing the selector parameter of `.on()` do our logic for us:
 
 ```
-// attach a delegated event with a more refined selector
+// Attach a delegated event handler with a more refined selector
 $( "#list" ).on( "click", "a[href^='http']", function( event ) {
 	$( this ).attr( "target", "_blank" );
 });
 ```
 
-##Summary
+## Summary
+
 Event delegation refers to the process of using event propagation (bubbling) to handle events at a higher level in the DOM than the element on which the event originated. It allows us to attach a single event listener for elements that exist now or in the future.
diff --git a/page/events/event-extensions.md b/page/events/event-extensions.md
index 86241760..39f9bd7d 100644
--- a/page/events/event-extensions.md
+++ b/page/events/event-extensions.md
@@ -1,16 +1,17 @@
----
-title: jQuery Event Extensions
-level: advanced
----
+<script>{
+	"title": "jQuery Event Extensions",
+	"level": "advanced"
+}</script>
+
 jQuery offers several ways to extend its event system to provide custom functionality when events are attached to elements. Internally in jQuery, these extensions are primarily used to ensure that standard events such as `submit` and `change` behave consistently across browsers. However, they can also be used to define new events with custom behavior.
 
 This document covers the extensions available starting with jQuery 1.7; a sparsely documented subset of this functionality has been available since jQuery 1.3 but the differences in functionality are extensive. For an overview of special events in earlier versions, see [Ben Alman's jQuery Special Events](http://benalman.com/news/2010/03/jquery-special-events/) article.
 
-<div class="warning">**Note:** jQuery event extensions are an advanced feature; they require deeper knowledge of both browser behavior and jQuery internals than most of the API. Most users of jQuery will not need to use event extensions, and those who do should use them with care. For example, on a large project with third-party plugins, changing the behavior of standard events such as `click` or `mouseover` can cause serious compatibility issues.</div>
+<div class="warning">**Note:** jQuery event extensions are an advanced feature; they require a deeper knowledge of both browser behavior and jQuery internals than most of the API. Most users of jQuery will not need to use event extensions, and those who do should use them with care. For example, on a large project with third-party plugins, changing the behavior of standard events such as `click` or `mouseover` can cause serious compatibility issues.</div>
 
 ### Events overview and general advice
 
-When writing an event extension, it is essential to understand the flow of events through jQuery's internal event system. For a description of the event system from the API level, including a discussion of event delegation, see the [`.on()`](http://api.jquery.com/on) method.
+When writing an event extension, it is essential to understand the flow of events through jQuery's internal event system. For a description of the event system from the API level, including a discussion of event delegation, see the [`.on()`](http://api.jquery.com/on/) method.
 
 To simplify event management, jQuery only attaches a single event handler per element per event type (using `addEventListener` on W3C-compliant browsers or `attachEvent` on older IE) and then dispatches to event handlers that are attached via jQuery's APIs. For example, if three "click" event handlers are attached to an element, jQuery attaches its own handler when the first handler is attached and adds the user's event handler to a list to be executed when the event occurs. For subsequent event handlers, jQuery only adds them to its own internal list since it has already called the browser to attach its solitary handler. Conversely, jQuery removes its own event handler from the browser when the final event of a particular type is removed from the element.
 
@@ -26,7 +27,7 @@ Although jQuery's event system is oriented towards delivering DOM events to DOM
 
 ### jQuery.event.props: Array
 
-jQuery defines an [Event object](http://api.jquery.com/jQuery.Event/) that represents a cross-browser subset of the information available when an event occurs. The `jQuery.event.props` property is an array of string names for properties that are always copied when jQuery processes a *native* browser event. (Events fired in code by `.trigger()` do not use this list, since the code can construct a `jQuery.Event` object with the needed values and trigger using that object.)
+jQuery defines an [Event object](https://api.jquery.com/category/events/event-object/) that represents a cross-browser subset of the information available when an event occurs. The `jQuery.event.props` property is an array of string names for properties that are always copied when jQuery processes a *native* browser event. (Events fired in code by `.trigger()` do not use this list, since the code can construct a `jQuery.Event` object with the needed values and trigger using that object.)
 
 To add a property name to this list, use `jQuery.event.props.push( "newPropertyName" )`. However, be aware that every event processed by jQuery will now attempt to copy this property name from the native browser event to jQuery's constructed event. If the property does not exist for that event type, it will get an undefined value. Adding many properties to this list can significantly reduce event delivery performance, so for infrequently-needed properties it is more efficient to use the value directly from `event.originalEvent` instead. If properties must be copied, you are strongly advised to use `jQuery.event.fixHooks` as of version 1.7.
 
@@ -122,11 +123,11 @@ elem.on( "pushy", function( event ) {
 	$( "body" ).append( "I am pushy but still a " + event.type + "!" );
 });
 
-elem.trigger( "click" ); // triggers both handlers
+elem.trigger( "click" ); // Triggers both handlers
 
 elem.off( "click" );
 
-elem.trigger( "click" ); // still triggers "pushy"
+elem.trigger( "click" ); // Still triggers "pushy"
 
 elem.off( "pushy" );
 ```
diff --git a/page/events/event-helpers.md b/page/events/event-helpers.md
index 2fad9c72..209b1ae6 100644
--- a/page/events/event-helpers.md
+++ b/page/events/event-helpers.md
@@ -1,18 +1,15 @@
----
-title: Event Helpers
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-jQuery offers two event-related helper functions that save you a few keystrokes.
+<script>{
+	"title": "Event Helpers",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+jQuery offers a few event-related helper functions that save you a few keystrokes.  Here is an example of one, the `.hover()` function.
 
 ### `.hover()`
 
-The [`.hover()`](http://api.jquery.com/hover/) method lets you pass one or two functions to be run when the
-`mouseenter` and `mouseleave` events occur on an element. If you pass one
-function, it will be run for both events; if you pass two functions, the first
-will run for `mouseenter`, and the second will run for `mouseleave`.
+The [`.hover()`](http://api.jquery.com/hover/) method lets you pass one or two functions to be run when the `mouseenter` and `mouseleave` events occur on an element. If you pass one function, it will be run for both events; if you pass two functions, the first will run for `mouseenter`, and the second will run for `mouseleave`.
 
 **Note:** Prior to jQuery 1.4, the `.hover()` method required two functions.
 
@@ -23,21 +20,4 @@ $( "#menu li" ).hover(function() {
 });
 ```
 
-### `.toggle()`
-
-<div class="warning">Note: This method signature was removed in jQuery 1.9. jQuery also provides an animation method named .toggle() that toggles the visibility of elements.</div>
-
-The [`.toggle()`](http://api.jquery.com/toggle-event/) method is triggered by the "click" event and accepts two or
-more functions. Each time the click event occurs, the next function in the
-list is called. Generally, `.toggle()` is used with just two functions;
-however, it will accept an unlimited number of functions. Be careful, though:
-providing a long list of functions can be difficult to debug.
-
-```
-// The toggle helper function
-$( "p.expander" ).toggle( function() {
-	$( this ).prev().addClass( "open" );
-}, function() {
-	$( this ).prev().removeClass( "open" );
-});
-```
+You can find more helper functions on the [API site for Events](https://api.jquery.com/category/events/).
\ No newline at end of file
diff --git a/page/events/handling-events.md b/page/events/handling-events.md
index c4267fba..d1ca45af 100644
--- a/page/events/handling-events.md
+++ b/page/events/handling-events.md
@@ -1,28 +1,25 @@
----
-title   : Handling Events
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-jQuery provides a method `.on()` to
-respond to any event on the selected elements. This is called an _event binding_.
-Although `.on()` isn't the only method provided for event binding, it is a best
-practice to use this for jQuery 1.7+. To learn more, [read more about
-the evolution of event binding in jQuery](/events/history-of-events).
+<script>{
+	"title": "Handling Events",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+jQuery provides a method `.on()` to respond to any event on the selected elements. This is called an _event binding_. Although `.on()` isn't the only method provided for event binding, it is a best practice to use this for jQuery 1.7+. To learn more, [read more about the evolution of event binding in jQuery](/events/history-of-events/).
 
 The `.on()` method provides several useful features:
 
 - [Bind any event triggered on the selected elements to an event handler](#simple-event-binding)
-- [Bind multiple events to one event handler](#multiple-events-one-handler)
-- [Bind multiple events and multiple handlers to the selected elements](#multiple-events-multiple-handlers)
-- [Use details about the event in the event handler](#event-object)
-- [Pass data to the event handler for custom events](#passing-data)
-- [Bind events to elements that will be rendered in the future](#event-delegation)
+- [Bind multiple events to one event handler](#many-events-but-only-one-event-handler)
+- [Bind multiple events and multiple handlers to the selected elements](#many-events-and-handlers)
+- [Use details about the event in the event handler](#the-event-object)
+- [Pass data to the event handler for custom events](#passing-data-to-the-event-handler)
+- [Bind events to elements that will be rendered in the future](#binding-events-to-elements-that-don-39-t-exist-yet)
 
 ### Examples
 
-#### <a name="simple-event-binding">Simple event binding</a>
+#### Simple event binding
+
 ```
 // When any <p> tag is clicked, we expect to see '<p> was clicked' in the console.
 $( "p" ).on( "click", function() {
@@ -30,25 +27,21 @@ $( "p" ).on( "click", function() {
 });
 ```
 
-#### <a name="multiple-events-one-handler">Many events, but only one event handler</a>
+#### Many events, but only one event handler
 
-Suppose you want to trigger the same event whenever the mouse hovers over or leaves
-the selected elements. The best practice for this is to use "mouseenter mouseleave".
-Note the difference between this and the next example.
+Suppose you want to trigger the same event whenever the mouse hovers over or leaves the selected elements. The best practice for this is to use "mouseenter mouseleave". Note the difference between this and the next example.
 
 ```
-// When a user focuses on or changes any input element, we expect a console message
-// bind to multiple events
+// When a user focuses on or changes any input element,
+// we expect a console message bind to multiple events
 $( "div" ).on( "mouseenter mouseleave", function() {
 	console.log( "mouse hovered over or left a div" );
 });
 ```
 
-#### <a name="multiple-events-multiple-handlers">Many events and handlers</a>
+#### Many events and handlers
 
-Suppose that instead you want different event handlers for when the mouse enters and
-leaves an element. This is more common than the previous example. For example, if you
-want to show and hide a tooltip on hover, you would use this.
+Suppose that instead you want different event handlers for when the mouse enters and leaves an element. This is more common than the previous example. For example, if you want to show and hide a tooltip on hover, you would use this.
 
 `.on()` accepts an object containing multiple events and handlers.
 
@@ -66,12 +59,9 @@ $( "div" ).on({
 });
 ```
 
-#### <a name="event-object">The event object</a>
+#### The event object
 
-Handling events can be tricky. It's often helpful to use the extra information contained
-in the event object passed to the event handler for more control. To become familiar with
-the event object, use this code to inspect it in your browser console after you click on
-a `<div>` in the page. For a breakdown of the event object, see [Inside the Event Handling Function](/events/inside-event-handling-function/).
+Handling events can be tricky. It's often helpful to use the extra information contained in the event object passed to the event handler for more control. To become familiar with the event object, use this code to inspect it in your browser console after you click on a `<div>` in the page. For a breakdown of the event object, see [Inside the Event Handling Function](/events/inside-event-handling-function/).
 
 ```
 $( "div" ).on( "click", function( event ) {
@@ -80,7 +70,7 @@ $( "div" ).on( "click", function( event ) {
 });
 ```
 
-#### <a name="passing-data">Passing data to the event handler</a>
+#### Passing data to the event handler
 
 You can pass your own data to the event object.
 
@@ -93,10 +83,9 @@ $( "p" ).on( "click", {
 ```
 
 
-#### <a name="event-delegation">Binding events to elements that don't exist yet</a>
+#### Binding events to elements that don't exist yet
 
-This is called _event delegation_. Here's an example just for completeness, but see the
-page on [Event Delegation](/events/event-delegation/) for a full explanation.
+This is called _event delegation_. Here's an example just for completeness, but see the page on [Event Delegation](/events/event-delegation/) for a full explanation.
 
 ```
 $( "ul" ).on( "click", "li", function() {
@@ -106,9 +95,7 @@ $( "ul" ).on( "click", "li", function() {
 
 ### Connecting Events to Run Only Once
 
-Sometimes you need a particular handler to run only once — after that, you may
-want no handler to run, or you may want a different handler to run. jQuery
-provides the `.one()` method for this purpose.
+Sometimes you need a particular handler to run only once — after that, you may want no handler to run, or you may want a different handler to run. jQuery provides the `.one()` method for this purpose.
 
 ```
 // Switching handlers using the `.one()` method
@@ -120,19 +107,13 @@ $( "p" ).one( "click", function() {
 });
 ```
 
-The `.one()` method is especially useful if you need to do some complicated
-setup the first time an element is clicked, but not subsequent times.
+The `.one()` method is especially useful if you need to do some complicated setup the first time an element is clicked, but not subsequent times.
 
-`.one()` accepts the same arguments as `.on()` which means it supports multiple events to one
-or multiple handlers, passing custom data and event delegation.
+`.one()` accepts the same arguments as `.on()` which means it supports multiple events to one or multiple handlers, passing custom data and event delegation.
 
 ### Disconnecting Events
 
-Although all the fun of jQuery occurs in the `.on()` method, it's counterpart is just as important
-if you want to be a responsible developer. `.off()` cleans up that event
-binding when you don't need it anymore. Complex user interfaces with lots of event bindings
-can bog down browser performance, so using the `.off()` method diligently is a best practice to
-ensure that you only have the event bindings that you need, when you need them.
+Although all the fun of jQuery occurs in the `.on()` method, its counterpart is just as important if you want to be a responsible developer. `.off()` cleans up that event binding when you don't need it anymore. Complex user interfaces with lots of event bindings can bog down browser performance, so using the `.off()` method diligently is a best practice to ensure that you only have the event bindings that you need, when you need them.
 
 ```
 // Unbinding all click handlers on a selection
@@ -157,8 +138,4 @@ $( "p" ).off( "click", bar );
 
 ### Namespacing Events
 
-For complex applications and for plugins you share with others, it can be
-useful to namespace your events so you don't unintentionally disconnect events
-that you didn't or couldn't know about. For details, see Event Namespacing.
-
-
+For complex applications and for plugins you share with others, it can be useful to namespace your events so you don't unintentionally disconnect events that you didn't or couldn't know about. For details, see [Event Namespacing](/events/event-basics/#namespacing-events).
diff --git a/page/events/history-of-events.md b/page/events/history-of-events.md
index 4a5d443c..280749bf 100644
--- a/page/events/history-of-events.md
+++ b/page/events/history-of-events.md
@@ -1,7 +1,8 @@
----
-title: History of jQuery Events
-level: intermediate
----
+<script>{
+	"title": "History of jQuery Events",
+	"level": "intermediate"
+}</script>
+
 Throughout the evolution of jQuery the means of event binding has changed for various reasons ranging from performance to semantics. As of jQuery v1.7 the `.on()` method is the accepted means of both directly binding events and creating delegated events. This article aims to explore the history of *event delegation* from jQuery v1.0 to the present and how each version leverages it.
 
 Given the following HTML, for our example we want to log the text of the each `<li>` to console whenever it is clicked.
@@ -19,6 +20,7 @@ Given the following HTML, for our example we want to log the text of the each `<
 ```
 
 ### [.bind()](http://api.jquery.com/bind/) (Deprecated)
+
 Introduced in jQuery v1.0
 
 It is possible to use `.bind()` and attach a handler to every element.
@@ -29,13 +31,15 @@ It is possible to use `.bind()` and attach a handler to every element.
 	console.log( elem.text() );
 });
 ```
-As discussed in the [event delegation](/event/event-delegation) article, this is not optimal.
+
+As discussed in the [event delegation](/event/event-delegation/) article, this is not optimal.
 
 ### liveQuery
 *liveQuery* was a popular jQuery plugin that allowed for the creation of events which would be triggered for elements that existed now or in the future. This plugin did not use event delegation and used expensive CPU processing to poll the DOM for changes every 20ms and fire events accordingly.
 
 
 ### [.bind()](http://api.jquery.com/bind/) delegation (Deprecated)
+
 Introduced in jQuery v1.0
 
 Generally we don't associate `.bind()` with *event delegation*, however prior to jQuery v1.3 it was the only means of delegation available to us.
@@ -53,6 +57,7 @@ We are able to take advantage of *event bubbling* here by attaching a *click* ev
 
 
 ### [.live()](http://api.jquery.com/live/) (Deprecated)
+
 Introduced in jQuery v1.3
 
 All `.live()` event handlers are bound to the *document* root by default.
@@ -76,6 +81,7 @@ The last element to receive the *click* event is *document*, this is where our `
 
 
 ### [.live()](http://api.jquery.com/live/) w/ context (Deprecated)
+
 Introduced in jQuery v1.4
 
 Passing the *context* as a second optional argument to the `$()` function has been supported since v1.0. However support for using this *context* with the `$.live()` method was not added until v1.4.
@@ -101,6 +107,7 @@ $( "li", "#list" ).live( "click", function( event ) {
 In this instance when an `<li>` is clicked the event still bubbles all the way up the *document tree* as it did before. However, our event handler is now bound to the parent `<ul>` tag, so we do not have to wait for the event to bubble all the way up to the *document* root.
 
 ### [.delegate()](http://api.jquery.com/delegate/) (Deprecated)
+
 First introduced in jQuery v1.4.2
 
 The `.delegate()` method provides a clear difference between the *context* of where to attach delegated event handler, and the *selector* to match when the event bubbles up to the delegated element.
@@ -113,9 +120,10 @@ $( "#list" ).delegate( "li", "click", function( event ) {
 ```
 
 ### [.on()](http://api.jquery.com/on/)
+
 First introduced in jQuery v1.7
 
-The `on.()` method gives us a semantic approach for creating directly bound events as well as delegated events. It eliminates the need to use the deprecated `.bind()`, `.live()`, and `.delegate()` methods, providing a single API for creating events.
+The `.on()` method gives us a semantic approach for creating directly bound events as well as delegated events. It eliminates the need to use the deprecated `.bind()`, `.live()`, and `.delegate()` methods, providing a single API for creating events.
 
 ```
 $( "#list" ).on( "click", "li", function( event ) {
@@ -125,4 +133,5 @@ $( "#list" ).on( "click", "li", function( event ) {
 ```
 
 ### Summary
+
 All of these ways of *event delegation* were innovative and considered a best practice at the time of their release. Depending on what version of jQuery you have implemented use the appropriate means of *event delegation*.
diff --git a/page/events/inside-event-handling-function.md b/page/events/inside-event-handling-function.md
index cab3b000..0e0f9519 100644
--- a/page/events/inside-event-handling-function.md
+++ b/page/events/inside-event-handling-function.md
@@ -1,19 +1,15 @@
----
-title   : Inside the Event Handling Function
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-Every event handling function receives an event object, which contains many
-properties and methods. The event object is most commonly used to prevent the
-default action of the event via the `.preventDefault()` method. However, the event
-object contains a number of other useful properties and methods, including:
+<script>{
+	"title": "Inside the Event Handling Function",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
+
+Every event handling function receives an event object, which contains many properties and methods. The event object is most commonly used to prevent the default action of the event via the `.preventDefault()` method. However, the event object contains a number of other useful properties and methods, including:
 
 #### pageX, pageY
 
-The mouse position at the time the event occurred, relative to the top left of
-the page.
+The mouse position at the time the event occurred, relative to the top left of the page.
 
 #### type
 
@@ -39,10 +35,7 @@ Prevent the default action of the event (e.g. following a link).
 
 Stop the event from bubbling up to other elements.
 
-In addition to the event object, the event handling function also has access to
-the DOM element that the handler was bound to via the keyword `this`. To turn
-the DOM element into a jQuery object that we can use jQuery methods on, we
-simply do `$( this )`, often following this idiom:
+In addition to the event object, the event handling function also has access to the DOM element that the handler was bound to via the keyword `this`. To turn the DOM element into a jQuery object that we can use jQuery methods on, we simply do `$( this )`, often following this idiom:
 
 ```
 var elem = $( this );
diff --git a/page/events/introduction-to-custom-events.md b/page/events/introduction-to-custom-events.md
index 7074fa54..56be0577 100644
--- a/page/events/introduction-to-custom-events.md
+++ b/page/events/introduction-to-custom-events.md
@@ -1,53 +1,39 @@
----
-title:        Introducing Custom Events
-level: intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Introducing Custom Events",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 ## Custom Events
 
-We're all familiar with the basic events — click, mouseover, focus, blur,
-submit, etc. — that we can latch on to as a user interacts with the browser.
-Custom events open up a whole new world of event-driven programming. In this
-chapter, we'll use jQuery's custom events system to make a simple Twitter
-search application.
+We're all familiar with the basic events — click, mouseover, focus, blur, submit, etc. — that we can latch on to as a user interacts with the browser. Custom events open up a whole new world of event-driven programming.
 
-It can be difficult at first to understand why you'd want to use custom events,
-when the built-in events seem to suit your needs just fine. It turns out that
-custom events offer a whole new way of thinking about event-driven JavaScript.
-Instead of focusing on the element that triggers an action, custom events put
-the spotlight on the element being acted upon. This brings a bevy of benefits,
-including:
+It can be difficult at first to understand why you'd want to use custom events, when the built-in events seem to suit your needs just fine. It turns out that custom events offer a whole new way of thinking about event-driven JavaScript. Instead of focusing on the element that triggers an action, custom events put the spotlight on the element being acted upon. This brings a bevy of benefits, including:
 
-- Behaviors of the target element can easily be triggered by different elements using the same code.
-- Behaviors can be triggered across multiple, similar, target elements at once.
-- Behaviors are more clearly associated with the target element in code, making code easier to read and maintain.
+* Behaviors of the target element can easily be triggered by different elements using the same code.
+* Behaviors can be triggered across multiple, similar, target elements at once.
+* Behaviors are more clearly associated with the target element in code, making code easier to read and maintain.
 
-Why should you care? An example is probably the best way to explain. Suppose
-you have a lightbulb in a room in a house. The lightbulb is currently turned
-on, and it's controlled by two three-way switches and a clapper:
+Why should you care? An example is probably the best way to explain. Suppose you have a lightbulb in a room in a house. The lightbulb is currently turned on, and it's controlled by two three-way switches and a clapper:
 
 ```
 <div class="room" id="kitchen">
-	<div class="lightbulb on"></div>
-	<div class="switch"></div>
-	<div class="switch"></div>
-	<div class="clapper"></div>
+	<div class="lightbulb on">Kitchen light</div>
+	<div class="switch">Kitchen switch 1</div>
+	<div class="switch">Kitchen switch 2</div>
+	<div class="clapper">Kitchen clapper switch</div>
 </div>
 ```
 
-Triggering the clapper or either of the switches will change the state of the
-lightbulb. The switches and the clapper don't care what state the lightbulb is
-in; they just want to change the state.
+Triggering the clapper or either of the switches will change the state of the lightbulb. The switches and the clapper don't care what state the lightbulb is in; they just want to change the state.
 
 Without custom events, you might write some code like this:
 
 ```
 $( ".switch, .clapper" ).click(function() {
-	var light = $( this ).parent().find( ".lightbulb" );
-	if ( light.hasClass( "on" ) ) {
+	var light = $( this ).closest( ".room" ).find( ".lightbulb" );
+	if ( light.is( ".on" ) ) {
 		light.removeClass( "on" ).addClass( "off" );
 	} else {
 		light.removeClass( "off" ).addClass( "on" );
@@ -58,9 +44,9 @@ $( ".switch, .clapper" ).click(function() {
 With custom events, your code might look more like this:
 
 ```
-$( ".lightbulb" ).on( "changeState", function( e ) {
+$( ".lightbulb" ).on( "light:toggle", function( event ) {
 	var light = $( this );
-	if ( light.hasClass( "on" ) ) {
+	if ( light.is( ".on" ) ) {
 		light.removeClass( "on" ).addClass( "off" );
 	} else {
 		light.removeClass( "off" ).addClass( "on" );
@@ -68,7 +54,8 @@ $( ".lightbulb" ).on( "changeState", function( e ) {
 });
 
 $( ".switch, .clapper" ).click(function() {
-	$( this ).parent().find( ".lightbulb" ).trigger( "changeState" );
+	var room = $( this ).closest( ".room" );
+	room.find( ".lightbulb" ).trigger( "light:toggle" );
 });
 ```
 
@@ -78,83 +65,68 @@ Let's make our example a little more interesting. We'll add another room to our
 
 ```
 <div class="room" id="kitchen">
-	<div class="lightbulb on"></div>
-	<div class="switch"></div>
-	<div class="switch"></div>
-	<div class="clapper"></div>
+	<div class="lightbulb on">Kitchen light</div>
+	<div class="switch">Kitchen switch 1</div>
+	<div class="switch">Kitchen switch 2</div>
+	<div class="clapper">Kitchen clapper switch</div>
 </div>
 <div class="room" id="bedroom">
-	<div class="lightbulb on"></div>
-	<div class="switch"></div>
-	<div class="switch"></div>
-	<div class="clapper"></div>
+	<div class="lightbulb on">Bedroom light</div>
+	<div class="switch">Bedroom switch 1</div>
+	<div class="switch">Bedroom switch 2</div>
+	<div class="clapper">Bedroom clapper switch</div>
 </div>
-<div id="master_switch"></div>
+<div id="master_switch">Master switch</div>
 ```
 
-If there are any lights on in the house, we want the master switch to turn all
-the lights off; otherwise, we want it to turn all lights on. To accomplish
-this, we'll add two more custom events to the lightbulbs: `turnOn` and
-`turnOff`. We'll make use of them in the `changeState` custom event, and use
-some logic to decide which one the master switch should trigger:
+If there are any lights on in the house, we want the master switch to turn all the lights off; otherwise, we want it to turn all lights on. To accomplish this, we'll add two more custom events to the lightbulbs: `light:on` and `light:off`. We'll make use of them in the `light:toggle` custom event, and use some logic to decide which one the master switch should trigger:
 
 ```
-$( ".lightbulb" ).on( "changeState", function( e ) {
+$( ".lightbulb" ).on( "light:toggle", function( event ) {
 	var light = $( this );
-	if ( light.hasClass( "on" ) ) {
-		light.trigger( "turnOff" );
+	if ( light.is( ".on" ) ) {
+		light.trigger( "light:off" );
 	} else {
-		light.trigger( "turnOn" );
+		light.trigger( "light:on" );
 	}
-}).on( "turnOn", function( e ) {
+}).on( "light:on", function( event ) {
 	$( this ).removeClass( "off" ).addClass( "on" );
-}).on( "turnOff", function( e ) {
+}).on( "light:off", function( event ) {
 	$( this ).removeClass( "on" ).addClass( "off" );
 });
 
 $( ".switch, .clapper" ).click(function() {
-	$( this ).parent().find( ".lightbulb" ).trigger( "changeState" );
+	var room = $( this ).closest( ".room" );
+	room.find( ".lightbulb" ).trigger( "light:toggle" );
 });
 
 $( "#master_switch" ).click(function() {
-	if ( $( ".lightbulb.on" ).length ) {
-		$( ".lightbulb" ).trigger( "turnOff" );
+	var lightbulbs = $( ".lightbulb" );
+
+	// Check if any lightbulbs are on
+	if ( lightbulbs.is( ".on" ) ) {
+		lightbulbs.trigger( "light:off" );
 	} else {
-		$( ".lightbulb" ).trigger( "turnOn" );
+		lightbulbs.trigger( "light:on" );
 	}
 });
 ```
 
-Note how the behavior of the master switch is attached to the master switch;
-the behavior of a lightbulb belongs to the lightbulbs.
+Note how the behavior of the master switch is attached to the master switch; the behavior of a lightbulb belongs to the lightbulbs.
+
+### Naming Custom Events
 
-If you're accustomed to object-oriented programming, you may find it useful to
-think of custom events as methods of objects. Loosely speaking, the object to
-which the method belongs is created via the jQuery selector. Binding the
-`changeState` custom event to all `$( ".light" )` elements is akin to having a
-class called `Light` with a method of `changeState`, and then instantiating new
-`Light` objects for each element with a classname of `light`.
+You can use any name for a custom event, however you should beware of creating new events with names that might be used by future DOM events.  For this reason, in this article we have chosen to use `light:` for all of our event names, as events with colons are unlikely to be used by a future DOM spec.
 
 ### Recap: `.on()` and `.trigger()`
 
-In the world of custom events, there are two important jQuery methods:
-`.on()` and `.trigger()`. In the [Events](/events/) chapter, we saw how to use these
-methods for working with user events; for this chapter, it's important to
-remember two things:
+In the world of custom events, there are two important jQuery methods: `.on()` and `.trigger()`. In the [Events](/events/) chapter, we saw how to use these methods for working with user events; for this chapter, it's important to remember two things:
 
-- `.on()` method takes an event type and an event handling function as
-  arguments. Optionally, it can also receive event-related data as its second
-  argument, pushing the event handling function to the third argument. Any data
-  that is passed will be available to the event handling function in the `data`
-  property of the event object. The event handling function always receives the
-  event object as its first argument.
+* `.on()` method takes an event type and an event handling function as arguments. Optionally, it can also receive event-related data as its second argument, pushing the event handling function to the third argument. Any data that is passed will be available to the event handling function in the `data` property of the event object. The event handling function always receives the event object as its first argument.
 
-- `.trigger()` method takes an event type as its argument. Optionally, it can
-  also take an array of values. These values will be passed to the event
-  handling function as arguments after the event object.
+* `.trigger()` method takes an event type as its argument. Optionally, it can also take an array of values. These values will be passed to the event handling function as arguments after the event object.
 
-Here is an example of the usage of `.on()` and `.trigger()` that uses
-custom data in both cases:
+Here is an example of the usage of `.on()` and `.trigger()` that uses custom data in both cases:
 
 ```
 $( document ).on( "myCustomEvent", {
@@ -168,281 +140,6 @@ $( document ).on( "myCustomEvent", {
 $( document ).trigger( "myCustomEvent", [ "bim", "baz" ] );
 ```
 
-### A Sample Application
-
-To demonstrate the power of custom events, we're going to create a simple tool
-for searching Twitter. The tool will offer several ways for a user to add
-search terms to the display: by entering a search term in a text box, by
-entering multiple search terms in the URL, and by querying Twitter for trending
-terms.
-
-The results for each term will be shown in a results container; these
-containers will be able to be expanded, collapsed, refreshed, and removed,
-either individually or all at once.
-
-When we're done, it will look like this:
-
-![Our finished application](http://gyazo.com/70415e9fffab1c47953f5264ecf722fe.png)
-
-```
-<h1>Twitter Search</h1>
-<input type="button" id="get_trends" value="Load Trending Terms" />
-
-<form>
-	<input type="text" class="input_text" id="search_term" />
-	<input type="submit" class="input_submit" value="Add Search Term" />
-</form>
-
-<div id="twitter">
-	<div class="template results">
-		<h2>Search Results for
-		<span class="search_term"></span></h2>
-	</div>
-</div>
-```
-
-This gives us a container (`#twitter`) for our widget, a template for our results
-containers (hidden via CSS), and a simple form where users can input a search
-term. (For the sake of simplicity, we're going to assume that our application
-is JavaScript-only and that our users will always have CSS.)
-
-There are two types of objects we'll want to act on: the results containers,
-and the Twitter container.
-
-The results containers are the heart of the application. We'll create a plugin
-that will prepare each results container once it's added to the Twitter
-container. Among other things, it will bind the custom events for each
-container and add the action buttons at the top right of each container. Each
-results container will have the following custom events:
-
-- `refresh` — Mark the container as being in the "refreshing" state, and fire
-  the request to fetch the data for the search term.
-
-- `populate` — Receive the returned JSON data and use it to populate the container.
-
-- `remove` — Remove the container from the page after the user verifies the
-  request to do so. Verification can be bypassed by passing `true` as the second
-  argument to the event handler. The `remove` event also removes the term
-  associated with the results container from the global object containing the
-  search terms.
-
-- `collapse` — Add a class of collapsed to the container, which will hide the
-  results via CSS. It will also turn the container's "Collapse" button into an
-  "Expand" button.
-
-- `expand` — Remove the collapsed class from the container. It will also turn
-  the container's "Expand" button into a "Collapse" button.
-
-The plugin is also responsible for adding the action buttons to the container.
-It binds a click event to each action's list item, and uses the list item's
-class to determine which custom event will be triggered on the corresponding
-results container.
-
-```
-$.fn.twitterResult = function( settings ) {
-	return this.each(function() {
-		var results = $( this );
-		var actions = $.fn.twitterResult.actions =
-			$.fn.twitterResult.actions || $.fn.twitterResult.createActions();
-		var a = actions.clone().prependTo( results );
-		var term = settings.term;
-
-		results.find( "span.search_term" ).text( term );
-		$.each([ "refresh", "populate", "remove", "collapse", "expand" ], function( i, ev ) {
-			results.on( ev, {
-				term: term
-			}, $.fn.twitterResult.events[ ev ] );
-		});
-
-		// use the class of each action to figure out
-		// which event it will trigger on the results panel
-		a.find( "li" ).click(function() {
-			// pass the li that was clicked to the function
-			// so it can be manipulated if needed
-			results.trigger( $( this ).attr( "class" ), [ $( this ) ] );
-		});
-	});
-};
-
-$.fn.twitterResult.createActions = function() {
-	return $( "<ul class='actions' />" ).append(
-		"<li class='refresh'>Refresh</li>" +
-		"<li class='remove'>Remove</li>" +
-		"<li class='collapse'>Collapse</li>"
-	);
-};
-
-$.fn.twitterResult.events = {
-
-	refresh: function( e ) {
-		// indicate that the results are refreshing
-		var elem = $( this ).addClass( "refreshing" );
-
-		elem.find( "p.tweet" ).remove();
-		results.append( "<p class='loading'>Loading...</p>" );
-
-		// get the twitter data using jsonp
-		$.getJSON( "http://search.twitter.com/search.json?q=" + escape( e.data.term ) + "&rpp=5&callback=?", function( json ) {
-			elem.trigger( "populate", [ json ] );
-		});
-	},
-
-	populate: function( e, json ) {
-		var results = json.results;
-		var elem = $( this );
-
-		elem.find( "p.loading" ).remove();
-		$.each( results, function( i, result ) {
-			var tweet = "<p class='tweet'>" +
-			"<a href='http://twitter.com/" +
-			result.from_user +
-			"'>" +
-			result.from_user +
-			"</a>: " +
-			result.text +
-			" <span class='date'>" +
-			result.created_at +
-			"</span>" +
-			"</p>";
-
-			elem.append( tweet );
-		});
-
-		// indicate that the results are done refreshing
-		elem.removeClass("refreshing");
-	},
-
-	remove: function( e, force ) {
-		if ( !force && !confirm( "Remove panel for term " + e.data.term + "?" ) ) {
-			return;
-		}
-		$( this ).remove();
-
-		// indicate that we no longer have a panel for the term
-		search_terms[ e.data.term ] = 0;
-	},
-
-	collapse: function( e ) {
-		$( this ).find( "li.collapse" )
-		.removeClass( "collapse" )
-		.addClass( "expand" )
-		.text( "Expand" );
-
-		$( this ).addClass( "collapsed" );
-	},
-
-	expand: function( e ) {
-		$( this ).find( "li.expand" )
-		.removeClass( "expand" )
-		.addClass( "collapse" )
-		.text( "Collapse" );
-
-		$( this ).removeClass( "collapsed" );
-	}
-
-};
-```
-
-The Twitter container itself will have just two custom events:
-
-- `getResults` — Receives a search term and checks to determine whether there's
-  already a results container for the term; if not, adds a results container
-  using the results template, set up the results container using the
-  `$.fn.twitterResult` plugin discussed above, and then triggers the `refresh`
-  event on the results container in order to actually load the results.
-  Finally, it will store the search term so the application knows not to
-  re-fetch the term.
-
-- `getTrends` — Queries Twitter for the top 10 trending terms, then iterates
-  over them and triggers the `getResults` event for
-  each of them, thereby adding a results container for each term.
-
-Here's how the Twitter container bindings look:
-
-```
-$( "#twitter" ).on( "getResults", function( e, term ) {
-	// make sure we don't have a box for this term already
-	if ( !search_terms[ term ] ) {
-		var elem = $( this );
-		var template = elem.find( "div.template" );
-
-		// make a copy of the template div
-		// and insert it as the first results box
-		results = template.clone()
-		.removeClass( "template" )
-		.insertBefore( elem.find( "div:first" ) )
-		.twitterResult({
-			"term": term
-		});
-
-		// load the content using the "refresh"
-		// custom event that we bound to the results container
-		results.trigger( "refresh" );
-
-		search_terms[ term ] = 1;
-	}
-}).on( "getTrends", function( e ) {
-	var elem = $( this );
-
-	$.getJSON( "http://search.twitter.com/trends.json?callback=?", function( json ) {
-		var trends = json.trends;
-		$.each( trends, function( i, trend ) {
-			elem.trigger( "getResults", [ trend.name ] );
-		});
-	});
-});
-```
-
-So far, we've written a lot of code that does approximately nothing, but that's
-OK. By specifying all the behaviors that we want our core objects to have,
-we've created a solid framework for rapidly building out the interface.
-
-Let's start by hooking up our text input and the "Load Trending Terms" button.
-For the text input, we'll capture the term that was entered in the input and
-pass it as we trigger the Twitter container's `getResults` event. Clicking the
-"Load Trending Terms" will trigger the Twitter container's `getTrends` event:
-
-```
-$( "form" ).submit(function( event ) {
-	var term = $( "#search_term" ).val();
-	$( "#twitter" ).trigger( "getResults", [ term ] );
-	event.preventDefault();
-});
-
-$( "#get_trends" ).click(function() {
-	$( "#twitter" ).trigger( "getTrends" );
-});
-```
-
-By adding a few buttons with the appropriate ID's, we can make it possible to
-remove, collapse, expand, and refresh all results containers at once, as shown
-below. For the remove button, note how we're passing a value of `true` to the
-event handler as its second argument, telling the event handler that we don't
-want to verify the removal of individual containers.
-
-```
-$.each([ "refresh", "expand", "collapse" ], function( i, ev ) {
-	$( "#" + ev ).click( function( e ) {
-		$( "#twitter div.results" ).trigger( ev );
-	});
-});
-
-$( "#remove" ).click(function( e ) {
-	if ( confirm( "Remove all results?" ) ) {
-		$( "#twitter div.results" ).trigger( "remove", [ true ] );
-	}
-});
-```
-
 ### Conclusion
 
-Custom events offer a new way of thinking about your code: they put the
-emphasis on the target of a behavior, not on the element that triggers it. If
-you take the time at the outset to spell out the pieces of your application, as
-well as the behaviors those pieces need to exhibit, custom events can provide a
-powerful way for you to "talk" to those pieces, either one at a time or en
-masse. Once the behaviors of a piece have been described, it becomes trivial to
-trigger those behaviors from anywhere, allowing for rapid creation of and
-experimentation with interface options. Finally, custom events can enhance code
-readability and maintainability, by making clear the relationship between an
-element and its behaviors.
+Custom events offer a new way of thinking about your code: they put the emphasis on the target of a behavior, not on the element that triggers it. If you take the time at the outset to spell out the pieces of your application, as well as the behaviors those pieces need to exhibit, custom events can provide a powerful way for you to "talk" to those pieces, either one at a time or en masse. Once the behaviors of a piece have been described, it becomes trivial to trigger those behaviors from anywhere, allowing for rapid creation of and experimentation with interface options. Finally, custom events can enhance code readability and maintainability, by making clear the relationship between an element and its behaviors.
diff --git a/page/events/introduction-to-events.md b/page/events/introduction-to-events.md
index 849dede4..c105de82 100644
--- a/page/events/introduction-to-events.md
+++ b/page/events/introduction-to-events.md
@@ -1,10 +1,9 @@
----
-title:        Introducing Events
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Introducing Events",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 ## Introduction
 
@@ -13,7 +12,7 @@ Web pages are all about interaction. Users perform a countless number of actions
 
 ## What's a DOM event?
 
-As mentioned, there are a myriad of event types, but perhaps the ones that are easiest to understand are user events, like when someone clicks on an element or types into a form. These types of events occur on an element, meaning that when a user clicks on a button for example, the button has had an event occur on it. While user interactions aren't the only types of DOM events, they're certainly the easiest to understand when starting out. MDN has a good reference of [available DOM events](https://developer.mozilla.org/en/DOM/DOM_event_reference).
+As mentioned, there are a myriad of event types, but perhaps the ones that are easiest to understand are user events, like when someone clicks on an element or types into a form. These types of events occur on an element, meaning that when a user clicks on a button for example, the button has had an event occur on it. While user interactions aren't the only types of DOM events, they're certainly the easiest to understand when starting out. Mozilla Developer Network has a good reference of [available DOM events](https://developer.mozilla.org/en-US/docs/Web/Events).
 
 
 ## Ways to listen for events
@@ -106,11 +105,13 @@ Let's look at the `on` examples from above and discuss their differences. In the
 
 In the second `on` example, we're passing an object (denoted by the curly braces `{}`), which has a property of `click` whose value is an anonymous function. The second argument to the `on` method is a jQuery selector string of `button`. While examples 1–3 are functionally equivalent, example 4 is different in that the `body` element is listening for click events that occur on *any* button element, not just `#helloBtn`. The final example above is exactly the same as the one preceding it, but instead of passing an object, we pass an event string, a selector string, and the callback. Both of these are examples of event delegation, a process by which an element higher in the DOM tree listens for events occurring on its children.
 
+## Event delegation
+
 Event delegation works because of the notion of *event bubbling*. For most events, whenever something occurs on a page (like an element is clicked), the event travels from the element it occurred on, up to its parent, then up to the parent's parent, and so on, until it reaches the root element, a.k.a. the `window`. So in our table example, whenever a `td` is clicked, its parent `tr` would also be notified of the click, the parent `table` would be notified, the `body` would be notified, and ultimately the `window` would be notified as well. While event bubbling and delegation work well, the delegating element (in our example, the `table`) should always be as close to the delegatees as possible so the event doesn't have to travel way up the DOM tree before its handler function is called.
 
 The two main pros of event delegation over binding directly to an element (or set of elements) are performance and the aforementioned event bubbling. Imagine having a large table of 1,000 cells and binding to an event for each cell. That's 1,000 separate event handlers that the browser has to attach, even if they're all mapped to the same function. Instead of binding to each individual cell though, we could instead use delegation to listen for events that occur on the parent table and react accordingly. One event would be bound instead of 1,000, resulting in way better performance and memory management.
 
-The event bubbling that occurs affords us the ability to add cells via AJAX for example, without having to bind events directly to those cells since the parent table is listening for clicks and is therefore notified of clicks on its children. If we weren't using delegation, we'd have to constantly bind events for every cell that's added which is not only a performance issue, but could also become a maintenance nightmare.
+The event bubbling that occurs affords us the ability to add cells via Ajax for example, without having to bind events directly to those cells since the parent table is listening for clicks and is therefore notified of clicks on its children. If we weren't using delegation, we'd have to constantly bind events for every cell that's added which is not only a performance issue, but could also become a maintenance nightmare.
 
 
 ## The event object
@@ -130,7 +131,7 @@ In this slightly different example, we're defining a function called `sayHello`
 
 But what about that `event` argument in the `sayHello` function — what is it and why does it matter? In all DOM event callbacks, jQuery passes an *event object* argument which contains information about the event, such as precisely when and where it occurred, what type of event it was, which element the event occurred on, and a plethora of other information. Of course you don't have to call it `event`; you could call it `e` or whatever you want to, but `event` is a pretty common convention.
 
-If the element has default functionality for a specific event (like a link opens a new page, a button in a form submits the form, etc.), that default functionality can be cancelled. This is often useful for AJAX requests. When a user clicks on a button to submit a form via AJAX, we'd want to cancel the button/form's default action (to submit it to the form's `action` attribute), and we would instead do an AJAX request to accomplish the same task for a more seamless experience. To do this, we would utilize the event object and call its `.preventDefault()` method. We can also prevent the event from bubbling up the DOM tree using `.stopPropagation()` so that parent elements aren't notified of its occurrence (in the case that event delegation is being used).
+If the element has default functionality for a specific event (like a link opens a new page, a button in a form submits the form, etc.), that default functionality can be canceled. This is often useful for Ajax requests. When a user clicks on a button to submit a form via Ajax, we'd want to cancel the button/form's default action (to submit it to the form's `action` attribute), and we would instead do an Ajax request to accomplish the same task for a more seamless experience. To do this, we would utilize the event object and call its `.preventDefault()` method. We can also prevent the event from bubbling up the DOM tree using `.stopPropagation()` so that parent elements aren't notified of its occurrence (in the case that event delegation is being used).
 
 ```
 // Preventing a default action from occurring and stopping the event bubbling
@@ -143,7 +144,6 @@ $( "form" ).on( "submit", function( event ) {
 	event.stopPropagation();
 
 	// Make an AJAX request to submit the form data
-
 });
 ```
 
@@ -164,6 +164,5 @@ $( "form" ).on( "submit", function( event ) {
 	console.log( event );
 
 	// Make an AJAX request to submit the form data
-
 });
 ```
diff --git a/page/events/triggering-event-handlers.md b/page/events/triggering-event-handlers.md
index b4a55a0b..99d3a3a3 100644
--- a/page/events/triggering-event-handlers.md
+++ b/page/events/triggering-event-handlers.md
@@ -1,26 +1,20 @@
----
-title   : Triggering Event Handlers
-level: intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Triggering Event Handlers",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
-jQuery provides a way to trigger the event handlers bound to an element without any user interaction via the
-`.trigger()` method.
+jQuery provides a way to trigger the event handlers bound to an element without any user interaction via the `.trigger()` method.
 
 ## What handlers can be .trigger()'d?
 
-jQuery's event handling system is a layer on top of native browser events. When an event handler is added using
-`.on( "click", function() {...} )`, it can be triggered using jQuery's `.trigger( "click" )` because jQuery stores a
-reference to that handler when it is originally added. Additionally, it will trigger the JavaScript inside the
-`onclick` attribute. The `.trigger()` function cannot be used to mimic native browser events, such as
-clicking on a file input box or an anchor tag. This is because, there is no event handler attached using jQuery's
-event system that corresponds to these events.
+jQuery's event handling system is a layer on top of native browser events. When an event handler is added using `.on( "click", function() {...} )`, it can be triggered using jQuery's `.trigger( "click" )` because jQuery stores a reference to that handler when it is originally added. Additionally, it will trigger the JavaScript inside the `onclick` attribute. The `.trigger()` function cannot be used to mimic native browser events, such as clicking on a file input box or an anchor tag. This is because, there is no event handler attached using jQuery's event system that corresponds to these events.
 
 ```
 <a href="http://learn.jquery.com">Learn jQuery</a>
 ```
+
 ```
 // This will not change the current page
 $( "a" ).trigger( "click" );
@@ -28,10 +22,9 @@ $( "a" ).trigger( "click" );
 
 ## How can I mimic a native browser event, if not `.trigger()`?
 
-In order to trigger a native browser event, you have to use [document.createEventObject](http://msdn.microsoft.com/en-us/library/ie/ms536390%28v=vs.85%29.aspx) for < IE9 and  [document.createEvent](https://developer.mozilla.org/en/DOM/document.createEvent) for all other browsers.
-Using these two APIs, you can programmatically create an event that behaves exactly as if someone has actually clicked on a file input box. The default action will happen, and the browse file dialog will display.
+In order to trigger a native browser event, you have to use [document.createEventObject](http://msdn.microsoft.com/en-us/library/ie/ms536390%28v=vs.85%29.aspx) for < IE9 and  [document.createEvent](https://developer.mozilla.org/en-US/docs/Web/API/Document/createEvent) for all other browsers. Using these two APIs, you can programmatically create an event that behaves exactly as if someone has actually clicked on a file input box. The default action will happen, and the browse file dialog will display.
 
-The jQuery UI Team created [jquery.simulate.js](https://github.com/eduardolundgren/jquery-simulate/blob/master/jquery.simulate.js) in order to simplify triggering a native browser event for use in their automated testing. Its usage is modeled after jQuery's trigger.
+The jQuery UI Team created [jquery.simulate.js](https://github.com/jquery/jquery-simulate/) in order to simplify triggering a native browser event for use in their automated testing. Its usage is modeled after jQuery's trigger.
 
 ```
 // Triggering a native browser event using the simulate plugin
@@ -50,15 +43,11 @@ There are four differences between `.trigger()` and `.triggerHandler()`
 3. `.triggerHandler()` will not cause the default behavior of the event (such as a form submission).
 4. Events triggered by `.triggerHandler()`, will not bubble up the DOM hierarchy. Only the handlers on the single element will fire.
 
-For more information see the [triggerHandler documentation](http://api.jquery.com/triggerHandler)
+For more information see the [triggerHandler documentation](http://api.jquery.com/triggerHandler/)
 
 ## Don't use `.trigger()` simply to execute specific functions
 
-While this method has its uses, it should not be used simply to call a function that was bound as a click
-handler. Instead, you should store the function you want to call in a
-variable, and pass the variable name when you do your binding. Then, you can
-call the function itself whenever you want, without the need for
-`.trigger()`.
+While this method has its uses, it should not be used simply to call a function that was bound as a click handler. Instead, you should store the function you want to call in a variable, and pass the variable name when you do your binding. Then, you can call the function itself whenever you want, without the need for `.trigger()`.
 
 ```
 // Triggering an event handler the right way
@@ -75,5 +64,4 @@ $( "p" ).on( "click", foo );
 foo(); // instead of $( "p" ).trigger( "click" )
 ```
 
-A more complex architecture can built on top of trigger using the [publish-subscribe pattern](http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) using [jQuery plugins](https://gist.github.com/661855).
-With this technique, `.trigger()` can be used to notify other sections of code that an application specific event has happened.
+A more complex architecture can be built on top of trigger using the [publish-subscribe pattern](http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) using [jQuery plugins](https://gist.github.com/661855). With this technique, `.trigger()` can be used to notify other sections of code that an application specific event has happened.
diff --git a/page/index.html b/page/index.html
index c2109909..fe5825a0 100644
--- a/page/index.html
+++ b/page/index.html
@@ -1,14 +1,22 @@
 <script>{
 	"title": "jQuery Learning Site",
 	"pageTemplate": "home.php",
-	"customFields": [{ "key": "icon", "value": "home" }, { "key": "is_chapter", "value": 0 }]
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "home"
+		},
+		{
+			"key": "is_chapter",
+			"value": 0
+		}
+	]
 }</script>
-<div id="banner-secondary" class="large-banner">
 
+<div id="banner-secondary" class="large-banner">
 	<h1>Learning Center</h1>
 
 	<div class="row">
-
 		<aside class="six columns" id="for-users">
 			<h2>Users</h2>
 			<p>There's a lot more to learn about building web sites and applications with jQuery than can fit in API documentation. If you're looking for explanations of the basics, workarounds for common problems, best practices, and how-tos, you're in the right place!</p>
@@ -18,7 +26,5 @@ <h2>Users</h2>
 			<h2>Authors</h2>
 			<p>Too much good information is spread across corners of the web, languishing in blog and forum posts, often just out of reach of people who need it, while the same questionable advice is duplicated across even more questionable sites. Help us stem the tide and educate today's — and tomorrow's — web developers.</p>
 		</aside>
-
 	</div>
-
-</div>
\ No newline at end of file
+</div>
diff --git a/page/javascript-101.md b/page/javascript-101.md
deleted file mode 100644
index ba6a4763..00000000
--- a/page/javascript-101.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title : JavaScript 101
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
-customFields:
- -
-    key: "icon"
-    value: "pencil"
----
-
-## Introduction
-
-So you want to unlock the power of jQuery to make the web a better place? Awesome, but there are a few things you should know about JavaScript first.
-
-Introduced at the dawn of the web, [JavaScript](http://en.wikipedia.org/wiki/JavaScript) is a powerful and expressive language that runs inside the browser in conjunction with HTML and CSS. Based on an open standard called [ECMAScript](http://en.wikipedia.org/wiki/ECMAScript), JavaScript has quickly become the "programming language of the web." All the power of jQuery is accessed via JavaScript, so needless to say, it's an important language to learn. Having a basic knowledge of JavaScript will go a long way in understanding, structuring, and debugging your code.
-
-This guide covers the foundational concepts of JavaScript, as well as frequent pitfalls developers fall into during their first foray into the language. When possible, we'll relate the JavaScript you learn here to how it's applied in jQuery.
-
-If you have experience with other programming languages, good for you! If not, don't worry. We'll take it slow and teach you everything you need to know to unlock the power of jQuery with JavaScript.
-
-## Table of Contents
diff --git a/page/javascript-101/arrays.md b/page/javascript-101/arrays.md
deleted file mode 100644
index af86d78c..00000000
--- a/page/javascript-101/arrays.md
+++ /dev/null
@@ -1,272 +0,0 @@
----
-title:        Arrays
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Arrays are zero-indexed, ordered lists of values. They are a handy way to store a set of related items of the same type (such as strings), though in reality, an array can include multiple types of items, including other arrays.
-
-To create an array, either use the object constructor or the literal declaration, by assigning the variable a list of values after the declaration.
-
-```
-// A simple array with constructor.
-var myArray1 = new Array( "hello", "world" );
-
-// Literal declaration, the preferred way.
-var myArray2 = [ "hello", "world" ];
-```
-
-The literal declaration is generally preferred. See the [Google Coding Guidelines](http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml#Array_and_Object_literals) for more information.
-
-If the values are unknown, it is also possible to declare an empty array, and add elements either through functions or through accessing by index:
-
-```
-// Creating empty arrays and adding values
-
-var myArray = [];
-
-// Adds "hello" on index 0
-myArray.push( "hello" );
-
-// Adds "world" on index 1
-myArray.push( "world" );
-
-// Adds "!" on index 2
-myArray[ 2 ] = "!";
-```
-
-`.push()` is a function that adds an element on the end of the array and expands the array respectively. You also can directly add items by index. Missing indices will be filled with `undefined`.
-
-```
-// Leaving indices
-
-var myArray = [];
-
-myArray[ 0 ] = "hello";
-myArray[ 1 ] = "world";
-myArray[ 3 ] = "!";
-
-console.log( myArray ); // [ "hello", "world", undefined, "!" ];
-```
-
-If the size of the array is unknown, `.push()` is far more safe. You can both access and assign values to array items with the index.
-
-```
-// Accessing array items by index
-
-var myArray = [ "hello", "world", "!" ];
-
-console.log( myArray[ 2 ] ); // "!"
-```
-
-## Array Methods and Properties
-
-### .length
-
-The `.length` property is used to determine the amount of items in an array.
-
-```
-// Length of an array
-
-var myArray = [ "hello", "world", "!" ];
-
-console.log( myArray.length ); // 3
-```
-
-You will need the `.length` property for looping through an array:
-
-```
-// For loops and arrays - a classic
-
-var myArray = [ "hello", "world", "!" ];
-
-for ( var i = 0; i < myArray.length; i = i + 1 ) {
-
-	console.log( myArray[ i ] );
-
-}
-```
-
-### .concat()
-
-Concatenate two or more arrays with `.concat()`:
-
-```
-var myArray = [ 2, 3, 4 ];
-var myOtherArray = [ 5, 6, 7 ];
-var wholeArray = myArray.concat( myOtherArray ); // [ 2, 3, 4, 5, 6, 7 ]
-```
-
-### .join()
-
-`.join()` creates a string representation of an array by joining all of its elements using a separator string. If no separator is supplied (i.e., `.join()` is called without arguments) the array will be joined using a comma.
-
-```
-// Joining elements
-
-var myArray = [ "hello", "world", "!" ];
-
-// The default separator is a comma.
-console.log( myArray.join() );     // "hello,world,!"
-
-// Any string can be used as separator...
-console.log( myArray.join( " " ) );  // "hello world !";
-console.log( myArray.join( "!!" ) ); // "hello!!world!!!";
-
-// ...including an empty one.
-console.log( myArray.join( "" ) );   // "helloworld!"
-
-```
-
-### .pop()
-
-`.pop()` removes the last element of an array. It is the opposite method of `.push()`:
-
-```
-// Pushing and popping
-
-var myArray = [];
-
-myArray.push( 0 ); // [ 0 ]
-myArray.push( 2 ); // [ 0 , 2 ]
-myArray.push( 7 ); // [ 0 , 2 , 7 ]
-myArray.pop();     // [ 0 , 2 ]
-```
-
-### .reverse()
-
-As the name suggests, the elements of the array are in reverse order after calling this method:
-
-```
-var myArray = [ "world" , "hello" ];
-myArray.reverse(); // [ "hello", "world" ]
-```
-
-### .shift()
-
-Removes the first element of an array. With `.push()` and `.shift()`, you can recreate the method of a [queue](http://en.wikipedia.org/wiki/Queue_(abstract_data_type%29):
-
-```
-// Queue with shift() and push()
-
-var myArray = [];
-
-myArray.push( 0 ); // [ 0 ]
-myArray.push( 2 ); // [ 0 , 2 ]
-myArray.push( 7 ); // [ 0 , 2 , 7 ]
-myArray.shift();   // [ 2 , 7 ]
-```
-
-### .slice()
-
-Extracts a part of the array and returns that part in a new array. This method takes one parameter, which is the starting index:
-
-```
-// Slicing
-
-var myArray = [ 1, 2, 3, 4, 5, 6, 7, 8 ];
-var newArray = myArray.slice( 3 );
-
-console.log( myArray );  // [ 1, 2, 3, 4, 5, 6, 7, 8 ]
-console.log( newArray ); // [ 4, 5, 6, 7, 8 ]
-```
-
-### .splice()
-
-Removes a certain amount of elements and adds new ones at the given index. It takes at least three parameters:
-
-```
-myArray.splice( index, length, values, ... );
-```
-
-* *Index* – The starting index.
-* *Length* – The number of elements to remove.
-* *Values* – The values to be inserted at the index position.
-
-For example:
-
-```
-var myArray = [ 0, 7, 8, 5 ];
-myArray.splice( 1, 2, 1, 2, 3, 4 );
-
-console.log( myArray ); // [ 0, 1, 2, 3, 4, 5 ]
-```
-
-### .sort()
-
-Sorts an array. It takes one parameter, which is a comparing function. If this function is not given, the array is sorted ascending:
-
-```
-// Sorting without comparing function.
-
-var myArray = [ 3, 4, 6, 1 ];
-
-myArray.sort(); // 1, 3, 4, 6
-```
-
-```
-// Sorting with comparing function.
-
-function descending( a, b ) {
-	return b - a;
-}
-
-var myArray = [ 3, 4, 6, 1 ];
-
-myArray.sort( descending ); // [ 6, 4, 3, 1 ]
-```
-
-The return value of descending (for this example) is important. If the return value is less than zero, the index of `a` is before `b`, and if it is greater than zero it's vice-versa. If the return value is zero, the elements' index is equal.
-
-### .unshift()
-
-Inserts an element at the first position of the array:
-
-```
-var myArray = [];
-
-myArray.unshift( 0 ); // [ 0 ]
-myArray.unshift( 2 ); // [ 2 , 0 ]
-myArray.unshift( 7 ); // [ 7 , 2 , 0 ]
-```
-
-### .forEach()
-
-In modern browsers it is possible to traverse through arrays with a `.forEach()` method, where you pass a function that is called for each element in the array.
-
-The function takes up to three arguments:
-
-* *Element* – The element itself.
-* *Index* – The index of this element in the array.
-* *Array* – The array itself.
-
-All of these are optional, but you will need at least the *Element* parameter in most cases.
-
-```
-// Native .forEach()
-
-function printElement( elem ) {
-	console.log( elem );
-}
-
-function printElementAndIndex( elem, index ) {
-	console.log( "Index " + index + ": " + elem );
-}
-
-function negateElement( elem, index, array ) {
-	array[ index ] = -elem;
-}
-
-myArray = [ 1, 2, 3, 4, 5 ];
-
-// Prints all elements to the console
-myArray.forEach( printElement );
-
-// Prints "Index 0: 1", "Index 1: 2", "Index 2: 3", ...
-myArray.forEach( printElementAndIndex );
-
-// myArray is now [ -1, -2, -3, -4, -5 ]
-myArray.forEach( negateElement );
-```
diff --git a/page/javascript-101/closures.md b/page/javascript-101/closures.md
deleted file mode 100644
index 878f66ac..00000000
--- a/page/javascript-101/closures.md
+++ /dev/null
@@ -1,139 +0,0 @@
----
-title:        Closures
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Closures are an extension of the concept of scope. With closures, functions have access to variables that were available in the scope where the function was created. If that seems confusing, don’t worry: closures are generally best understood by example.
-
-As shown in the [Scope](/scope/) section, functions have access to changing variable values. The same sort of behavior exists with functions defined within loops – the function "sees" the change in the variable's value even after the function is defined, resulting in each function referencing the last value stored in the variable.
-
-```
-// Each function executed within the loop will reference
-// the last value stored in i (5).
-// This won't behave as we want it to - every 100 milliseconds, 5 will alert
-for ( var i = 0; i < 5; i++ ) {
-	setTimeout(function() {
-		alert( i );
-	}, i * 100 );
-}
-```
-
-Closures can be used to prevent this by creating a unique scope for each iteration – storing each unique value of the variable within its scope.
-
-```
-// Using a closure to create a new private scope
-// fix: “close” the value of i inside createFunction, so it won't change
-var createFunction = function( i ) {
-	return function() {
-		alert( i );
-	};
-};
-
-for ( var i = 0; i < 5; i++ ) {
-	setTimeout( createFunction( i ), i * 100 );
-}
-```
-
-Closures can also be used to resolve issues with the `this` keyword, which is unique to each scope:
-
-```
-// Using a closure to access inner and outer object instances simultaneously.
-var outerObj = {
-	myName: "outer",
-	outerFunction: function() {
-
-		// Provide a reference to outerObj through innerFunction's closure
-		var self = this;
-		var innerObj = {
-			myName: "inner",
-			innerFunction: function() {
-				console.log( self.myName, this.myName ); // "outer inner"
-			}
-		};
-
-		innerObj.innerFunction();
-
-		console.log( this.myName ); // "outer"
-	}
-};
-
-outerObj.outerFunction();
-```
-
-## Function.bind
-
-Closures can be particularly useful when dealing with callbacks. However, it is often better to use `Function.bind`, which will avoid any overhead associated with scope traversal.
-
-`Function.bind` is used to create a new function. When called, the new function then calls itself in the context of the supplied `this` value, using a given set of arguments that will precede any arguments provided when the new function was initially called.
-
-As `.bind()` is a recent addition to ECMAScript 5, it may not be present in all browsers, which is something to be wary of when deciding whether to use it. However, it's possible to work around support by using [this shim](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Function/bind) from MDN:
-
-```
-// Shim from MDN
-if (!Function.prototype.bind) {
-
-	Function.prototype.bind = function( oThis ) {
-
-		if (typeof this !== "function") {
-			// closest thing possible to the ECMAScript 5 internal
-			// IsCallable function
-			throw new TypeError( "Function.prototype.bind - what is trying to be bound is not callable" );
-		}
-
-		var fSlice = Array.prototype.slice,
-			aArgs = fSlice.call( arguments, 1 ),
-			fToBind = this,
-			fNOP = function() {},
-			fBound = function() {
-				return fToBind.apply( this instanceof fNOP
-					? this
-					: oThis || window,
-					aArgs.concat( fSlice.call( arguments ) ) );
-			};
-
-		fNOP.prototype = this.prototype;
-
-		fBound.prototype = new fNOP();
-
-		return fBound;
-	};
-}
-```
-
-One of the simplest uses of `.bind()` is making a function that is called with a particular value for `this`, regardless of how it's called. A common mistake developers make is attempting to extract a method from an object, then later calling that method and expecting it to the use the origin object as its `this`. However, this can be solved by creating a bound function using the original object as demonstrated below:
-
-```
-// Let's manipulate "this" with a basic example.
-var user = "johnsmith";
-var module = {
-	getUser: function() {
-		return this.user;
-	},
-	user: "janedoe"
-};
-
-// module.getUser() is called where "module" is "this"
-// and "module.user" is returned.
-
-// janedoe
-module.getUser();
-
-// let's now store a reference in the global version of "this"
-var getUser = module.getUser;
-
-// getUser() called, "this" is global, "user" is returned
-
-// johnsmith
-getUser();
-
-// store a ref with "module" bound as "this"
-var boundGetUser = getUser.bind( module );
-
-// boundGetUser() called, "module" is "this" again, "module.user" returned.
-
-// janedoe
-boundGetUser();
-```
diff --git a/page/javascript-101/conditional-code.md b/page/javascript-101/conditional-code.md
deleted file mode 100644
index dcf60d94..00000000
--- a/page/javascript-101/conditional-code.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title:        Conditional Code
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Sometimes a block of code should only be run under certain conditions. Flow control – via `if` and `else` blocks – lets you run code if certain conditions have been met.
-
-```
-// Flow control
-
-var foo = true;
-var bar = false;
-
-if ( bar ) {
-	// This code will never run.
-	console.log( "hello!" );
-}
-
-if ( bar ) {
-
-	// This code won't run.
-
-} else {
-
-	if ( foo ) {
-		// This code will run.
-	} else {
-		// This code would run if foo and bar were both false.
-	}
-
-}
-```
-
-While curly braces aren't strictly required around single-line `if` statements, using them consistently, even when they aren't strictly required, makes for vastly more readable code.
-
-Be mindful not to define functions with the same name multiple times within separate `if`/`else` blocks, as doing so may not have the expected result.
-
-## Truthy and Falsy Things
-
-In order to use flow control successfully, it's important to understand which kinds of values are "truthy" and which kinds of values are "falsy." Sometimes, values that seem like they should evaluate one way actually evaluate another.
-
-```
-// Values that evaluate to false:
-false
-"" // An empty string.
-NaN // JavaScript's "not-a-number" variable.
-null
-undefined // Be careful -- undefined can be redefined!
-0 // The number zero.
-```
-
-```
-// Everything else evaluates to true, some examples:
-"0"
-"any string"
-[] // An empty array.
-{} // An empty object.
-1 // Any non-zero number.
-```
-
-## Conditional Variable Assignment with the Ternary Operator
-
-Sometimes a variable should be set depending on some condition. An `if`/`else` statement works, but in many cases the ternary operator is more convenient. The ternary operator tests a condition; if the condition is true, it returns a certain value, otherwise it returns a different value.
-
-The ternary operator:
-
-```
-// Set foo to 1 if bar is true; otherwise, set foo to 0:
-var foo = bar ? 1 : 0;
-```
-
-While the ternary operator can be used without assigning the return value to a variable, this is generally discouraged.
-
-## Switch Statements
-
-Rather than using a series of `if`/`else` blocks, sometimes it can be useful to use a `switch` statement instead. `switch` statements look at the value of a variable or expression, and run different blocks of code depending on the value.
-
-```
-// A switch statement
-
-switch ( foo ) {
-
-	case "bar":
-		alert( "the value was bar -- yay!" );
-		break;
-
-	case "baz":
-		alert( "boo baz :(" );
-		break;
-
-	default:
-		alert( "everything else is just ok" );
-
-}
-```
-
-Switch statements have somewhat fallen out of favor in JavaScript, because often the same behavior can be accomplished by creating an object that has more potential for reuse or testing. For example:
-
-```
-var stuffToDo = {
-
-	"bar": function() {
-		alert( "the value was bar -- yay!" );
-	},
-
-	"baz": function() {
-		alert( "boo baz :(" );
-	},
-
-	"default": function() {
-		alert( "everything else is just ok" );
-	}
-
-};
-
-// Check if the property exists in the object.
-if ( stuffToDo[ foo ] ) {
-	// This code won't run.
-	stuffToDo[ foo ]();
-
-} else {
-	// This code will run.
-	stuffToDo[ "default" ]();
-
-}
-```
-
-Objects are covered further in the [Types](/types/) and [Objects](/objects/) sections.
diff --git a/page/javascript-101/functions.md b/page/javascript-101/functions.md
deleted file mode 100644
index 2080a68b..00000000
--- a/page/javascript-101/functions.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title:        Functions
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Functions contain blocks of code that need to be executed repeatedly. Functions can take zero or more arguments, and can optionally return a value.
-
-Functions can be created in a variety of ways, two of which are shown below:
-
-```
-// Function declaration.
-
-function foo() {
-	// Do something.
-}
-```
-
-```
-// Named function expression.
-
-var foo = function() {
-	// Do something.
-};
-```
-
-## Using Functions
-
-```
-// A simple function.
-
-var greet = function( person, greeting ) {
-	var text = greeting + ", " + person;
-	console.log( text );
-};
-
-greet( "Rebecca", "Hello" ); // "Hello, Rebecca"
-```
-
-```
-// A function that returns a value.
-
-var greet = function( person, greeting ) {
-	var text = greeting + ", " + person;
-	return text;
-};
-
-console.log( greet( "Rebecca", "Hello" ) ); // "Hello, Rebecca"
-```
-
-```
-// A function that returns another function.
-
-var greet = function( person, greeting ) {
-	var text = greeting + ", " + person;
-	return function() {
-		console.log( text );
-	};
-};
-
-var greeting = greet( "Rebecca", "Hello" );
-
-greeting(); // "Hello, Rebecca"
-```
-
-## Immediately-Invoked Function Expression (IIFE)
-
-A common pattern in JavaScript is the immediately-invoked function expression. This pattern creates a function expression and then immediately executes the function. This pattern is extremely useful for cases where you want to avoid polluting the global namespace with code – no variables declared inside of the function are visible outside of it.
-
-```
-// An immediately-invoked function expression.
-
-(function() {
-	var foo = "Hello world";
-})();
-
-console.log( foo ); // undefined!
-```
-
-## Functions as Arguments
-
-In JavaScript, functions are "first-class citizens" – they can be assigned to variables or passed to other functions as arguments. Passing functions as arguments is an extremely common idiom in jQuery.
-
-```
-// Passing an anonymous function as an argument.
-
-var myFn = function( fn ) {
-	var result = fn();
-	console.log( result );
-};
-
-// Logs "hello world"
-myFn( function() {
-	return "hello world";
-});
-```
-
-```
-// Passing a named function as an argument
-
-var myFn = function( fn ) {
-	var result = fn();
-	console.log( result );
-};
-
-var myOtherFn = function() {
-	return "hello world";
-};
-
-myFn( myOtherFn ); // "hello world"
-```
diff --git a/page/javascript-101/getting-started.md b/page/javascript-101/getting-started.md
deleted file mode 100644
index 9c803c76..00000000
--- a/page/javascript-101/getting-started.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Getting Started
-level: Beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-## Anatomy of a Web Page
-
-Before diving into JavaScript, it helps to understand how it aligns with the other web technologies.
-
-### HTML is for Content
-
-HTML is a markup language used to define and describe content. Whether it be a blog post, a search engine result, or an e-commerce site, the core content of a web page is written in HTML. A semantic markup, HTML is used to describe content in universal terms (headers, paragraphs, images, etc.)
-
-### CSS is for Presentation
-
-CSS is a supplemental language that applies style to HTML documents. CSS is all about making content look better by defining fonts, colors, and other visual aesthetics. The power of CSS comes from the fact that styling is not intermingled with content. This means you can apply different styles to the same piece of content, which is critical when building responsive websites that look good across a range of devices.
-
-### JavaScript is for Interactivity
-
-In the browser, JavaScript adds interactivity and behavior to HTML content. Without JavaScript, web pages would be static and boring. JavaScript helps bring a web page to life.
-
-Look at this simple HTML page that includes CSS and JavaScript to see how it all fits together:
-
-```
-<!doctype html>
-<html lang="en">
-<head>
-	<meta charset="utf-8" />
-	<title>Hello World</title>
-
-	
-	<style>
-	h1 { font-size: 14px; color: hotpink; }
-	button { color: red; }
-	</style>
-</head>
-<body>
-	<h1>Hello World</h1>
-	<button>Click Me!</button>
-
-	
-	<script>
-
-	// Get a handle on the first button element in the document.
-	var button = document.querySelector( "button" );
-
-	// If a user clicks on it, say hello!
-	button.addEventListener( "click", function( ev ) {
-		alert( "Hello" );
-	}, false);
-
-	</script>
-</body>
-</html>
-```
-
-In the example above, HTML is used to describe the content. The "Hello World" text is described as a heading with the `<h1>` tag and "Click Me!" is described as a button with the `<button>` tag. The `<style>` block contains CSS that changes the font size and color of the header text. The `<script>` block contains JavaScript that adds interactivity to the button. When a user clicks on the button, an alert message will appear that says "Hello!"
-
-## A Scripting Language for the Web
-
-JavaScript was originally designed to add interactivity to web pages, not to be a general programming language, which makes it a scripting language. [Scripting languages](http://en.wikipedia.org/wiki/Scripting_language) are regarded to be more productive than general languages because they are optimized for their specific domain (in this case, the web browser). However, recent advancements have brought JavaScript to the server-side (via [Node.js](http://nodejs.org/)) so it can now be used in place of languages like PHP, Ruby, or ASP. This guide will focus exclusively on JavaScript running in the browser with jQuery.
-
-The name "JavaScript" is a bit misleading. Despite the similarity in name, JavaScript has no relationship with [Java](http://en.wikipedia.org/wiki/Java_$programming_language$, a general purpose language. JavaScript is based on an open web standard called [ECMAScript](http://en.wikipedia.org/wiki/ECMAScript). Standards-based languages are not controlled by any one entity or corporation – instead, developers work together to define the language, which is why JavaScript will run in *every* web browser regardless of the operating system or device.
-
-## What You Need to Get Started with JavaScript and jQuery
-
-1. Web Browser
-2. Text Editor
-3. Developer Tools (optional)
-
-One of JavaScript's greatest strengths is its simplicity. It can be written and run on any operating system, and the only requirements are a web browser and a text editor. There are also numerous tools that can make JavaScript development more productive, but they are completely optional.
-
-### Developer Tools
-
-Commonly referred to as "developer tools," many browsers ship with built-in features that provide better insight into JavaScript and jQuery while they run in the browser. Although they aren't required, you may find developer tools helpful when it comes to debugging errors in your code. Check out these browsers' developer tools:
-
-- [Apple Safari](https://developer.apple.com/technologies/safari/developer-tools.html)
-- [Google Chrome Developer Tools](https://developers.google.com/chrome-developer-tools/)
-- [Microsoft Internet Explorer](http://msdn.microsoft.com/en-us/library/ie/gg589507.aspx)
-- [Mozilla Firefox Developer Tools](https://developer.mozilla.org/en-US/docs/Tools)
-- [Opera Dragonfly](http://www.opera.com/dragonfly/)
diff --git a/page/javascript-101/loops.md b/page/javascript-101/loops.md
deleted file mode 100644
index ba56987c..00000000
--- a/page/javascript-101/loops.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title:        Loops
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Loops let a block of code run a certain number of times:
-
-```
-for ( var i = 0; i < 5; i++ ) {
-	// Logs "try 0", "try 1", ..., "try 4".
-	console.log( "try " + i );
-}
-```
-
-Note that in loops, the variable `i` is not "scoped" to the loop block even though the keyword `var` is used before the variable name. Scope is covered in more depth in the [Scope](/scope/) section.
-
-## The `for` Loop
-
-A `for` loop is made up of four statements and has the following structure:
-
-```
-for ( [initialization]; [conditional]; [iteration] ) {
-
-	[loopBody]
-
-}
-```
-
-The _initialization_ statement is executed only once, before the loop starts. It gives you an opportunity to prepare or declare any variables.
-
-The _conditional_ statement is executed before each iteration, and its return value decides whether the loop is to continue. If the conditional statement evaluates to a falsy value, then the loop stops.
-
-The _iteration_ statement is executed at the end of each iteration and gives you an opportunity to change the state of important variables. Typically, this will involve incrementing or decrementing a counter and thus bringing the loop closer to its end.
-
-The _loopBody_ statement is what runs on every iteration. It can contain anything. Typically, there will be multiple statements that need to be executed, and should be wrapped in a block (`{...}`).
-
-Here's a typical `for` loop:
-
-```
-for (var i = 0, limit = 100; i < limit; i++) {
-	// This block will be executed 100 times.
-	console.log( "Currently at " + i );
-	// Note: The last log will be "Currently at 99".
-}
-```
-
-## The `while` loop
-
-A while loop is similar to an `if` statement, except that its body will keep executing until the condition evaluates to a falsy value.
-
-```
-while ( [conditional] ) {
-
-	[loopBody]
-
-}
-```
-
-Here's a typical `while` loop:
-
-```
-var i = 0;
-while ( i < 100 ) {
-	// This block will be executed 100 times.
-	console.log( "Currently at " + i );
-	i++; // Increment i
-}
-```
-
-Notice that the counter is incrementing within the loop's body. It's possible to combine the conditional and incrementer, like so:
-
-```
-var i = -1;
-while ( ++i < 100 ) {
-	// This block will be executed 100 times.
-	console.log( "Currently at " + i );
-}
-```
-
-Notice that the counter starts at -1 and uses the prefix incrementer (`++i`).
-
-## The `do-while` Loop
-
-This is almost exactly the same as the `while` loop, except for the fact that the loop's body is executed at least once before the condition is tested.
-
-```
-do {
-
-	[loopBody]
-
-} while ( [conditional] )
-```
-
-Here's a `do-while` loop:
-
-```
-do {
-	// Even though the condition evaluates to false
-	// this loop's body will still execute once.
-	alert( "Hi there!" );
-
-} while ( false );
-```
-
-These types of loops are quite rare since only few situations require a loop that blindly executes at least once. Regardless, it's good to be aware of it.
-
-## Breaking and Continuing
-
-Usually, a loop's termination will result from the conditional statement not evaluating to a truthy value, but it is possible to stop a loop in its tracks from within the loop's body with the `break` statement:
-
-```
-// Stopping a loop
-for ( var i = 0; i < 10; i++ ) {
-	if ( something ) {
-		break;
-	}
-}
-```
-
-You may also want to continue the loop without executing more of the loop's body. This is done using the `continue` statement:
-
-```
-// Skipping to the next iteration of a loop
-for ( var i = 0; i < 10; i++ ) {
-	if ( something ) {
-		continue;
-	}
-
-	// The following statement will only be executed
-	// if the conditional "something" has not been met
-	console.log( "I have been reached" );
-
-}
-```
diff --git a/page/javascript-101/objects.md b/page/javascript-101/objects.md
deleted file mode 100644
index 56f066ce..00000000
--- a/page/javascript-101/objects.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title:        Objects
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-Objects contain one or more key-value pairs. The key portion can be any string. The value portion can be any type of value: a number, a string, an array, a function, or even another object.  When one of these values is a function, it’s called a method of the object. Otherwise, they are called properties.
-
-As it turns out, nearly everything in JavaScript is an object – arrays, functions, numbers, even strings – and they all have properties and methods.
-
-```
-// Creating an object literal.
-
-var myObject = {
-	sayHello: function() {
-		console.log( "hello" );
-	},
-	myName: "Rebecca"
-};
-
-myObject.sayHello(); // "hello"
-
-console.log( myObject.myName ); // "Rebecca"
-```
-
-When creating object literals, note that the key portion of each key-value pair can be written as any valid JavaScript identifier, a string (wrapped in quotes), or a number:
-
-```
-var myObject = {
-	validIdentifier: 123,
-	"some string": 456,
-	99999: 789
-};
-```
diff --git a/page/javascript-101/operators.md b/page/javascript-101/operators.md
deleted file mode 100644
index e87ad977..00000000
--- a/page/javascript-101/operators.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-title:        Operators
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Basic operators allow you to manipulate values.
-
-```
-// Concatenation
-var foo = "hello";
-var bar = "world";
-
-console.log( foo + " " + bar ); // "hello world"
-```
-
-```
-// Multiplication and division
-2 * 3;
-2 / 3;
-```
-
-```
-// Incrementing and decrementing
-// The pre-increment operator increments the operand before any further processing.
-var i = 1;
-console.log( ++i ); // 2 - because i was incremented before evaluation
-console.log( i );   // 2
-
-// The post-increment operator increments the operand after processing it.
-var i = 1;
-console.log( i++ ); // 1 - because i was evaluated to 1 and _then_ incremented
-console.log( i );   // 2 - incremented after using it
-```
-
-## Operations on Numbers & Strings
-
-In JavaScript, numbers and strings will occasionally behave in unexpected ways.
-
-```
-// Addition vs. Concatenation
-var foo = 1;
-var bar = "2";
-
-console.log( foo + bar ); // 12
-```
-
-```
-// Coercing a string to act as a number.
-var foo = 1;
-var bar = "2";
-
-console.log( foo + Number(bar) ); // 3
-```
-
-The `Number` constructor, when called as a function (as in the above example), will have the effect of casting its argument into a number. The unary plus operator also does the same thing:
-
-```
-// Forcing a string to act as a number (using the unary plus operator).
-console.log( foo + +bar ); // 3
-```
-
-## Logical Operators
-
-Logical operators allow evaluation of a series of operands using AND (`&&`) and OR (`||`) operations.
-
-```
-// Logical AND and OR operators
-
-var foo = 1;
-var bar = 0;
-var baz = 2;
-
-// returns 1, which is true
-foo || bar;
-
-// returns 1, which is true
-bar || foo;
-
-// returns 0, which is false
-foo && bar;
-
-// returns 2, which is true
-foo && baz;
-
-// returns 1, which is true
-baz && foo;
-```
-
-In the above example, the `||` operator returns the value of the first truthy operand, or in cases where neither operand is truthy, it returns the last operand. The `&&` operator returns the value of the first false operand, or the value of the last operand if both operands are truthy.
-
-You'll sometimes see developers use these logical operators for flow control instead of using `if` statements. For example:
-
-```
-// Do something with foo if foo is truthy.
-foo && doSomething( foo );
-
-// Set bar to baz if baz is truthy;
-// otherwise, set it to the return value of createBar()
-var bar = baz || createBar();
-```
-
-This style is quite elegant and pleasantly terse; that said, it can be really hard to read or use, especially for beginners. See the section on truthy and falsy things in the [Conditional Code](/conditional-code/) article for more about evaluating truthiness.
-
-## Comparison Operators
-
-Comparison operators allow you to test whether values are equivalent or whether values are identical.
-
-```
-// Comparison operators
-
-var foo = 1;
-var bar = 0;
-var baz = "1";
-var bim = 2;
-
-foo == bar; // false
-foo != bar; // true
-foo == baz; // true; but note that the types are different
-
-foo === baz;             // false
-foo !== baz;             // true
-foo === parseInt( baz ); // true
-
-foo > bim;  // false
-bim > baz;  // true
-foo <= baz; // true
-```
-
-For more information about comparison operators, visit the [Mozilla Developer Network](https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Operators/Comparison_Operators "MDN - Comparison Operators").
diff --git a/page/javascript-101/reserved-words.md b/page/javascript-101/reserved-words.md
deleted file mode 100644
index 38a22e4f..00000000
--- a/page/javascript-101/reserved-words.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title:        Reserved Words
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-JavaScript has a number of "reserved words," or words that have special meaning in the language. You should avoid using these words in your code except when using them with their intended meaning.
-
-- break
-- case
-- catch
-- class
-- const
-- continue
-- debugger
-- default
-- delete
-- do
-- else
-- enum
-- export
-- extends
-- false
-- finally
-- for
-- function
-- if
-- implements
-- import
-- in
-- instanceof
-- interface
-- let
-- new
-- null
-- package
-- private
-- protected
-- public
-- return
-- static
-- super
-- switch
-- this
-- throw
-- true
-- try
-- typeof
-- var
-- void
-- while
-- with
-- yield
diff --git a/page/javascript-101/running-code.md b/page/javascript-101/running-code.md
deleted file mode 100644
index 1f5cebc0..00000000
--- a/page/javascript-101/running-code.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title:        Running Code
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-### External
-
-The first and recommended option is to write code in an external file (with a `.js` extension), which can then be included on our web page using an HTML `<script>` tag and pointing the `src` attribute to the file's location. Having JavaScript in a separate file will reduce code duplication if you want to reuse it on other pages. It will also allow the browser to cache the file on the remote client's computer, decreasing page load time.
-
-```
-
-<script src="/path/to/example.js"></script>
-```
-### Inline
-
-The second option is to inline the code directly on the web page. This is also achieved using HTML `<script>` tags, but instead of pointing the `src` attribute to a file, the code is placed between the tags. While there are use cases for this option, the majority of the time it is best to keep our code in an external file as described above.
-
-```
-
-<script>
-alert( "Hello World!" );
-</script>
-```
-
-### Attributes
-
-The last option is to use the event handler attributes of HTML elements. This method is strongly discouraged:
-
-```
-
-<a href="javascript:alert( 'Hello World' );">Click Me!</a>
-<button onClick="alert( 'Good Bye World' );">Click Me Too!</button>
-```
-
-### Placement
-
-Placement of the previous two options is important and can vary depending on the situation. If you are including JavaScript that doesn't access the elements on the page, you can safely place the script before the closing HTML `<head>` tag. However, if the code will interact with the elements on the page, you have to make sure those elements exist at the time the script is executed. This common pitfall can be seen in the example below. The script for finding the element with the ID `hello-world` will be executed before the element is defined in the document.
-
-```
-<!doctype html>
-<html>
-<head>
-	<script>
-	// Attempting to access an element too early will have unexpected results.
-	var title = document.getElementById( "hello-world" );
-	console.log( title );
-	</script>
-</head>
-<body>
-
-<h1 id="hello-world">Hello World</h1>
-
-</body>
-</html>
-```
-
-It is a common pattern to move scripts to the bottom of the page, prior to the closing HTML `<body>` tag. This will guarantee that elements are defined when the script is executed:
-
-```
-<!doctype html>
-<html>
-<head></head>
-<body>
-
-<h1 id="hello-world">Hello World</h1>
-<script>
-// Moving the script to the bottom of the page will make sure the element exists.
-var title = document.getElementById( "hello-world" );
-console.log( title );
-</script>
-
-</body>
-</html>
-```
diff --git a/page/javascript-101/scope.md b/page/javascript-101/scope.md
deleted file mode 100644
index a7963964..00000000
--- a/page/javascript-101/scope.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
-title: Scope
-level: beginner
-source: http://jqfundamentals.com/legacy, http://javascriptplayground.com/blog/2012/04/javascript-variable-scope-this
-attribution:
-  - jQuery Fundamentals
----
-
-"Scope" refers to the variables that are available to a piece of code at a given time. A lack of understanding of scope can lead to frustrating debugging experiences. The idea of scope is that it's where certain functions or variables are accessible from in our code, and the context in which they exist and are executed in.
-
-There are two types of scopes in JavaScript: global and local. Let's talk about each of them in turn.
-
-## Global Scope
-
-The first scope is __Global Scope__. This is very easy to define. If a variable or function is _global_, it can be accessed from anywhere within a program. In a browser, the global scope is the `window` object. If a variable declaration occurs outside of a function, then that variable exists on the global object. For example:
-
-```
-var x = 9;
-```
-
-Once that variable had been defined, it could be referenced as `window.x`, but because it exists on the global object we can simply refer to it as `x`.
-
-## Local Scope
-
-JavaScript also creates a __Local Scope__ inside each function body. For example:
-
-```
-function myFunc() {
-	var x = 5;
-}
-
-console.log( x ); // ReferenceError: x is not defined
-```
-
-Since `x` was initialized within `.myFunc()`, it is only accessible within `.myFunc()`, and we get a reference error if we try to access it outside of `.myFunc()`.
-
-## A Word of Caution
-
-If you declare a variable and forget to use the `var` keyword, that variable is automatically made global. So this code would work:
-
-```
-function myFunc() {
-	x = 5;
-}
-
-console.log( x ); // 5
-```
-
-This is a bad idea. Any variable that is global can have its value changed by any other parts of a program or any other script. This is undesirable, as it could lead to unforseen side effects.
-
-Secondly, Immediately-Invoked Function Expressions provide a way to avoid global variables. You'll see many libraries such as  jQuery often use these:
-
-```
-(function() {
-	var jQuery = { /* All my methods go here. */ };
-	window.jQuery = jQuery;
-})();
-```
-
-Wrapping everything in a function which is then immediately invoked means all the variables within that function are bound to the _local scope_. At the very end you can then expose all your methods by binding the `jQuery` object to the `window`, the _global object_. To read more about Immediately-Invoked Functions, check out Ben Alman's [Immediately-Invoked Function Expression](http://benalman.com/news/2010/11/immediately-invoked-function-expression/) article.
-
-Because local scope works through functions, any functions defined within another have access to variables defined in the outer function:
-
-```
-function outer() {
-	var x = 5;
-
-	function inner() {
-		console.log( x );
-	}
-
-	inner(); // 5
-}
-```
-
-But the `.outer()` function doesn't have access to any variables declared within `.inner()`:
-
-```
-function outer() {
-	var x = 5;
-
-	function inner() {
-		console.log( x );
-		var y = 10;
-	}
-
-	inner(); // 5
-
-	console.log( y ); // ReferenceError: y is not defined
-}
-```
-
-Furthermore, variables that are declared inside a function without the `var` keyword are not local to the function – JavaScript will traverse the scope chain all the way up to the window scope to find where the variable was previously defined. If the variable wasn't previously defined, it will be defined in the global scope, which can have unexpected consequences.
-
-```
-// Functions have access to variables defined in the same scope.
-
-var foo = "hello";
-
-var sayHello = function() {
-	console.log( foo );
-};
-
-sayHello(); // "hello"
-
-console.log( foo ); // "hello"
-```
-
-Variables with the same name can exist in different scopes with different values:
-
-```
-var foo = "world";
-
-var sayHello = function() {
-	var foo = "hello";
-	console.log( foo );
-};
-
-sayHello(); // "hello"
-
-console.log( foo ); // "world"
-```
-
-When, within a function, you reference a variable defined in an outer scope, that function can see changes to the variable's value after the function is defined.
-
-```
-var myFunction = function() {
-	var foo = "hello";
-	var myFn = function() {
-		console.log( foo );
-	};
-	foo = "world";
-	return myFn;
-};
-
-var f = myFunction();
-
-f(); // "world"
-```
-
-Here's a more complex example of scopes at play:
-
-```
-(function() {
-
-	var baz = 1;
-
-	var bim = function() {
-		console.log( baz );
-	};
-
-	bar = function() {
-		console.log( baz );
-	};
-
-})();
-```
-In this instance, running:
-
-```
-console.log( baz ); // baz is not defined outside of the function
-```
-
-Gives us a `ReferenceError`. `baz` was only defined within the function, and was never exposed to the global scope.
-
-```
-bar(); //  1
-```
-
-`.bar()` may have been defined within the anonymous function, but it was defined without the `var` keyword, which means it wasn't bound to the local scope and was instead created globally. Furthermore, it has access to the `baz` variable because `.bar()` was defined within the same scope as `baz`. This means it has access to it, even though other code outside of the function does not.
-
-
-```
-bim(); // ReferenceError: bim is not defined
-```
-
-`.bim()` was only defined within the function, so does not exist on the global object as it was defined locally.
diff --git a/page/javascript-101/syntax-basics.md b/page/javascript-101/syntax-basics.md
deleted file mode 100644
index 3579f7ca..00000000
--- a/page/javascript-101/syntax-basics.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title:        Syntax Basics
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-### Comments
-
-JavaScript has support for single- and multi-line comments. Comments are ignored by the JavaScript engine and therefore have no side-effects on the outcome of the program. Use comments to document the code for other developers. Libraries like [JSDoc](https://code.google.com/p/jsdoc-toolkit/ "JSDoc Toolkit") are available to help generate project documentation pages based on commenting conventions.
-
-```
-// Single- and multi-line comments.
-
-// This is an example of a single-line comment.
-
-/*
- * this is an example
- * of a
- * multi-line
- * comment.
- */
-```
-
-### Whitespace
-
-Whitespace is also ignored in JavaScript. There are many tools that will strip out all the whitespace in a program, reducing the overall file size and improving network latency. Given the availability of tools like these, whitespace should be leveraged to make the code as readable as possible.
-
-```
-// Whitespace is insignificant.
-var hello = "Hello";
-var world     =      "World!";
-```
-
-```
-// Semantic whitespace promotes readability.
-// Readable code is good!
-var foo = function() {
-
-	for ( var i = 0; i < 10; i++ ) {
-
-		alert( i );
-
-	}
-
-};
-
-foo();
-
-// This is much harder to read!
-var foo=function() {for(var i=0;i<10;i++){alert(i);}};foo();
-```
-
-### Reserved Words
-
-There are a handful of reserved words that can't be used when declaring user-defined variables and functions. Some of these reserved words are currently implemented, some are saved for future use, and others are reserved for historical reasons. A list of reserved words can be found [here](/javascript-101/reserved-words/), and in-depth explanations for each can be found on the [MDN JavaScript Reference](https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Reserved_Words "MDN Reserved Words.") site.
-
-### Identifiers
-
-Identifiers are used to give variables and functions a unique name so they can subsequently be referred to by that name. The name of an identifier must follow a few rules:
-
-* Cannot be a reserved word.
-* Can only be composed of letters, numbers, dollar signs, and underscores.
-* The first character cannot be a number.
-
-It's a best practice to name identifiers in a way that will make sense to you and other developers later on.
-
-```
-// Valid identifier names.
-var myAwesomeVariable = "a";
-var myAwesomeVariable2 = "b";
-var my_awesome_variable = "c";
-var $my_AwesomeVariable = "d";
-var _my_awesome_variable_$ = "e";
-```
-
-### Variable Definition
-
-Variables can be defined using multiple `var` statements, or in a single combined `var` statement.
-
-```
-// This works:
-var test = 1;
-var test2 = function() { ... };
-var test3 = test2( test );
-
-// And so does this:
-var test4 = 1,
-	test5 = function() { ... },
-	test6 = test2( test );
-```
-
-Variables can be declared without assigning them a value. The value of a variable declared without a value is `undefined`.
-
-```
-var x;
-x === undefined; // true
-```
diff --git a/page/javascript-101/testing-type.md b/page/javascript-101/testing-type.md
deleted file mode 100644
index c6620215..00000000
--- a/page/javascript-101/testing-type.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title:        Testing Type
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-JavaScript offers a way to test the type of a variable. However, the result can be confusing – for example, the type of an array is "Object."
-
-It's common practice to use the `typeof` operator when trying to determining the type of a specific value.
-
-```
-// Testing the type of various variables.
-var myFunction = function() {
-	console.log( "hello" );
-};
-var myObject = {
-	foo: "bar"
-};
-var myArray = [ "a", "b", "c" ];
-var myString = "hello";
-var myNumber = 3;
-var myRegExp = /(\w+)\s(\w+)/;
-
-typeof myFunction; // "function"
-typeof myObject;   // "object"
-typeof myArray;    // "object" -- Careful!
-typeof myString;   // "string"
-typeof myNumber;   // "number"
-typeof null;       // "object" -- Careful!
-typeof undefined;  // "undefined"
-typeof meh;        // "undefined" -- undefined variable.
-typeof myRegExp;   // "function" or "object" depending on environment.
-
-
-if ( myArray.push && myArray.slice && myArray.join ) {
-	// probably an array (this is called "duck typing")
-}
-
-if ( Object.prototype.toString.call( myArray ) === "[object Array]" ) {
-	// Definitely an array!
-	// This is widely considered as the most robust way
-	// to determine if a specific value is an Array.
-}
-```
-
-jQuery also offers utility methods to help determine the type of an arbitrary value.
diff --git a/page/javascript-101/this-keyword.md b/page/javascript-101/this-keyword.md
deleted file mode 100644
index 53be72ba..00000000
--- a/page/javascript-101/this-keyword.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title:        The "this" Keyword
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-In JavaScript, as in most object-oriented programming languages, `this` is a special keyword that is used in methods to refer to the object on which a method is being invoked. The value of `this` is determined using a simple series of steps:
-
-- If the function is invoked using `Function.call()` or `Function.apply()`, `this` will be set to the first argument passed to `.call()`/`.apply()`. If the first argument passed to `.call()`/`.apply()` is `null` or `undefined`, `this` will refer to the global object (which is the `window` object in web browsers).
-- If the function being invoked was created using `Function.bind()`, `this` will be the first argument that was passed to `.bind()` at the time the function was created.
-- If the function is being invoked as a method of an object, `this` will refer to that object.
-- Otherwise, the function is being invoked as a standalone function not attached to any object, and `this` will refer to the global object.
-
-```
-// A function invoked using Function.call()
-
-var myObject = {
-	sayHello: function() {
-		console.log( "Hi! My name is " + this.myName );
-	},
-	myName: "Rebecca"
-};
-
-var secondObject = {
-	myName: "Colin"
-};
-
-myObject.sayHello();                    // "Hi! My name is Rebecca"
-myObject.sayHello.call( secondObject ); // "Hi! My name is Colin"
-```
-
-```
-// A function created using Function.bind()
-
-var myName = "the global object";
-var sayHello = function() {
-	console.log( "Hi! My name is " + this.myName );
-};
-var myObject = {
-	myName: "Rebecca"
-};
-var myObjectHello = sayHello.bind( myObject );
-
-sayHello();      // "Hi! My name is the global object"
-myObjectHello(); // "Hi! My name is Rebecca"
-```
-
-```
-// A function being attached to an object at runtime.
-
-var myName = "the global object";
-var sayHello = function() {
-	console.log( "Hi! My name is " + this.myName );
-};
-var myObject = {
-	myName: "Rebecca"
-};
-var secondObject = {
-	myName: "Colin"
-};
-
-myObject.sayHello = sayHello;
-secondObject.sayHello = sayHello;
-
-sayHello();              // "Hi! My name is the global object"
-myObject.sayHello();     // "Hi! My name is Rebecca"
-secondObject.sayHello(); // "Hi! My name is Colin"
-```
-
-When invoking a function deep within a long namespace, it is often tempting to reduce the amount of code you need to type by storing a reference to the actual function as a single, shorter variable. It is important not to do this with instance methods as this will cause the value of `this` within the function to change, leading to incorrect code operation. For instance:
-
-```
-var myNamespace = {
-	myObject: {
-		sayHello: function() {
-			console.log( "Hi! My name is " + this.myName );
-		},
-		myName: "Rebecca"
-	}
-};
-
-var hello = myNamespace.myObject.sayHello;
-
-hello(); // "Hi! My name is undefined"
-```
-
-You can, however, safely reduce everything up to the object on which the method is invoked:
-
-```
-var myNamespace = {
-	myObject: {
-		sayHello: function() {
-			console.log( "Hi! My name is " + this.myName );
-		},
-		myName: "Rebecca"
-	}
-};
-
-var obj = myNamespace.myObject;
-
-obj.sayHello(); // "Hi! My name is Rebecca"
-```
diff --git a/page/javascript-101/types.md b/page/javascript-101/types.md
deleted file mode 100644
index 9127cd3b..00000000
--- a/page/javascript-101/types.md
+++ /dev/null
@@ -1,206 +0,0 @@
----
-title:        Types
-level:        beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
-
-Types in JavaScript fall into two categories: primitives and objects. Primitive types include:
-
-* String
-* Number
-* Boolean
-* null
-* undefined
-
-### String
-
-Strings are text wrapped in single or double quotation marks. It is best practice to consistently use one or the other. There may be times when the string contains quotation marks that collide with the ones used to create the string. In this case, either escape the characters using a `\` backslash or use different quotes around the string.
-
-```
-// Strings can be created with double or single quotes.
-var a = "I am a string";
-var b = 'So am I!';
-alert( a );
-alert( b );
-```
-
-```
-// Sometimes a string may contain quotation marks.
-var statement1 = 'He said "JavaScript is awesome!"';
-var statement2 = "He said \"JavaScript is awesome!\"";
-```
-
-### Number
-
-Number types are any positive or negative numeric value. There is no distinction between integer and floating point values.
-
-```
-// Numbers are any whole or floating point integer.
-var num1 = 100;
-var num2 = 100.10;
-var num3 = 0.10;
-```
-
-### Boolean
-Boolean types are either `true` or `false`.
-
-```
-// Boolean values.
-var okay = true;
-var fail = false;
-```
-
-### null and undefined
-
-`null` and `undefined` are special types in JavaScript. Null types are values that represent the absence of a value, similar to many other programming languages. Undefined types represent a state in which no value has been assigned at all. This type is created in two ways: by using the `undefined` keyword or by not defining a value at all.
-
-```
-// Define a null value.
-var foo = null;
-
-// Two ways to achieve an undefined value.
-var bar1 = undefined;
-var bar2;
-```
-
-## Objects
-
-Everything else in JavaScript is considered an object. While there are [numerous built-in objects](https://developer.mozilla.org/en/JavaScript/Reference#Global_Objects, "MDN - Global Object Reference"), this chapter will cover:
-
-* Object
-* Array
-* Function
-
-The simplest way to create an object is either through the `Object` constructor or the shorthand syntax known as object literal. These simple objects are unordered key/value pairs. The key is formally known as a property and the value can be any valid JavaScript type, even another object. To create or access a property on an object, we use what is known as "dot notation" or "bracket notation."
-
-```
-// Creating an object with the constructor:
-var person1 = new Object;
-
-person1.firstName = "John";
-person1.lastName = "Doe";
-
-alert( person1.firstName + " " + person1.lastName );
-
-// Creating an object with the object literal syntax:
-var person2 = {
-	firstName: "Jane",
-	lastName: "Doe"
-};
-
-alert( person2.firstName + " " + person2.lastName );
-```
-
-```
-// As mentioned, objects can also have objects as a property.
-var people = {};
-
-people[ "person1" ] = person1;
-people[ "person2" ] = person2;
-
-alert( people[ "person1" ].firstName );
-alert( people[ "person2" ].firstName );
-```
-
-If a property is accessed that has not been defined, it will return a type of `undefined`.
-
-```
-// Properties that have not been created are undefined.
-var person = { name: "John Doe" };
-alert( person.email ); // undefined
-```
-
-Objects are covered further in the [Objects](/objects/) section.
-
-### Array
-
-An array is a type of object that is ordered by the index of each item it contains. The index starts at zero and extends to however many items have been added, which is a property of the array known as the `.length`. Similar to a basic object, an array can be created with the `Array` constructor or the shorthand syntax known as array literal.
-
-```
-// Creating an array with the constructor:
-var foo = new Array;
-
-// Creating an array with the array literal syntax:
-var bar = [];
-```
-
-There is an important distinction to be made between the two. Both an array constructor and an array literal can contain items to be added to the array upon creating it. However, if just a single numeric item is passed in, the array constructor will assume its length to be that value.
-
-```
-// The array literal returns a foo.length value of 1:
-var foo = [ 100 ];
-alert( foo[ 0 ] ); // 100
-alert( foo.length ); // 1
-
-// The array constructor returns a bar.length value of 100:
-var bar = new Array( 100 );
-alert( bar[ 0 ] ); // undefined
-alert( bar.length ); // 100
-```
-
-An array can be manipulated through methods that are available on the instance of the array. Items in the array can be accessed using bracket notation with a given index. If the index does not exist or contains no value, the return type will be `undefined`.
-
-A few common array methods are shown below:
-
-```
-// Using the push(), pop(), unshift() and shift() methods on an array.
-
-var foo = [];
-
-foo.push( "a" );
-foo.push( "b" );
-
-alert( foo[ 0 ] ); // a
-alert( foo[ 1 ] ); // b
-
-alert( foo.length ); // 2
-
-foo.pop();
-
-alert( foo[ 0 ] ); // a
-alert( foo[ 1 ] ); // undefined
-
-alert( foo.length ); // 1
-
-foo.unshift( "z" );
-
-alert( foo[ 0 ] ); // z
-alert( foo[ 1 ] ); // a
-
-alert( foo.length ); // 2
-
-foo.shift();
-
-alert( foo[ 0 ] ); // a
-alert( foo[ 1 ] ); // undefined
-
-alert( foo.length ); // 1
-```
-
-There are many more methods for manipulating arrays, some of which are covered further in the [Arrays](/arrays/) section. Details can be found on the [Mozilla Developer Network](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Array "MDN - Array Reference").
-
-## Type Checking with jQuery
-
-jQuery offers a few basic utility methods for determining the type of a specific value. Type checking is covered further in the [Testing Type](/testing-type/) section, but here are some examples:
-
-```
-// Checking the type of an arbitrary value.
-
-var myValue = [ 1, 2, 3 ];
-
-// Using JavaScript's typeof operator to test for primitive types:
-typeof myValue === "string"; // false
-typeof myValue === "number"; // false
-typeof myValue === "undefined"; // false
-typeof myValue === "boolean"; // false
-
-// Using strict equality operator to check for null:
-myValue === null; // false
-
-// Using jQuery's methods to check for non-primitive types:
-jQuery.isFunction( myValue ); // false
-jQuery.isPlainObject( myValue ); // false
-jQuery.isArray( myValue ); // true
-```
diff --git a/page/jquery-mobile.md b/page/jquery-mobile.md
index f30e102e..bddba3c2 100644
--- a/page/jquery-mobile.md
+++ b/page/jquery-mobile.md
@@ -1,9 +1,11 @@
----
-title: jQuery Mobile
-customFields:
- -
-    key: "icon"
-    value: "th-large"
----
+<script>{
+	"title": "jQuery Mobile",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "th-large"
+		}
+	]
+}</script>
 
 jQuery Mobile is the easiest way to build sites and apps that are accessible on all popular smartphone, tablet, and desktop devices. This framework provides a set of touch-friendly UI widgets and an AJAX-powered navigation system to support animated page transitions.
diff --git a/page/jquery-mobile/getting-started.md b/page/jquery-mobile/getting-started.md
index fc5720b6..e557a526 100644
--- a/page/jquery-mobile/getting-started.md
+++ b/page/jquery-mobile/getting-started.md
@@ -1,17 +1,17 @@
----
-title: Getting Started with jQuery Mobile
-level: Beginner
----
+<script>{
+	"title": "Getting Started with jQuery Mobile",
+	"level": "Beginner"
+}</script>
 
-jQuery Mobile provides a set of touch-friendly UI widgets and an AJAX-powered navigation system to support animated page transitions. This guide will show you how you can build your first jQuery Mobile application.
+jQuery Mobile provides a set of touch-friendly UI widgets and an Ajax-powered navigation system to support animated page transitions. This guide will show you how you can build your first jQuery Mobile application.
 
 ## Create a Basic Page Template
 
 To get started, you can simply paste the template below in your favorite text editor, save, and open the document in a browser.
 
-In the `<head>` of this template, a meta `viewport` tag sets the screen width to the pixel width of the device. References to jQuery, jQuery Mobile, and the mobile theme stylesheet from the CDN add all the styles and scripts. jQuery Mobile 1.2 (1.2.0) works with versions of jQuery core from 1.7.0 to 1.8.2.
+In the `<head>` of this template, a meta `viewport` tag sets the screen width to the pixel width of the device. References to jQuery, jQuery Mobile, and the mobile theme stylesheet from the CDN add all the styles and scripts. jQuery Mobile 1.4 works with versions of jQuery core 1.8 and newer.
 
-In the `<body>`, a div with a `data-role` of `page` is the wrapper used to delineate a page. A header bar (`data-role="header"`), a content region (`data-role="content"`) and a footer bar (`data-role="footer"`) are added inside to create a basic page (all three are optional). These `data-` attributes are HTML5 attributes used throughout jQuery Mobile to transform basic markup into an enhanced and styled widget.
+In the `<body>`, a div with a `data-role` of `page` is the wrapper used to delineate a page. A header bar (`data-role="header"`), a content region (`role="main" class="ui-content"`) and a footer bar (`data-role="footer"`) are added inside to create a basic page (all three are optional). These `data-` attributes are HTML5 attributes used throughout jQuery Mobile to transform basic markup into an enhanced and styled widget.
 
 ```
 <!doctype html>
@@ -19,9 +19,9 @@ In the `<body>`, a div with a `data-role` of `page` is the wrapper used to delin
 <head>
 	<title>My Page</title>
 	<meta name="viewport" content="width=device-width, initial-scale=1">
-	<link rel="stylesheet" href="http://code.jquery.com/mobile/1.2.0/jquery.mobile-1.2.0.min.css">
-	<script src="http://code.jquery.com/jquery-1.8.2.min.js"></script>
-	<script src="http://code.jquery.com/mobile/1.2.0/jquery.mobile-1.2.0.min.js"></script>
+	<link rel="stylesheet" href="https://code.jquery.com/mobile/[version]/jquery.mobile-[version].min.css">
+	<script src="https://code.jquery.com/jquery-[version].min.js"></script>
+	<script src="https://code.jquery.com/mobile/[version]/jquery.mobile-[version].min.js"></script>
 </head>
 <body>
 	<div data-role="page">
@@ -30,7 +30,7 @@ In the `<body>`, a div with a `data-role` of `page` is the wrapper used to delin
 			<h1>My Title</h1>
 		</div>
 
-		<div data-role="content">
+		<div role="main" class="ui-content">
 			<p>Hello world</p>
 		</div>
 
@@ -82,19 +82,19 @@ There are a few ways to make buttons. A common one is to turn a link into a butt
 
 ### Choose a Theme Swatch
 
-jQuery Mobile has a robust theme framework that supports up to 26 sets of toolbar, content, and button colors, called a "swatch". You can add a `data-theme="e"` attribute to any of the widgets on this page: page, header, list, input for the slider, or button to turn it yellow. Different swatch letters from a-e in the default theme can be used to mix and match swatches.
+jQuery Mobile has a robust theme framework that supports up to 26 sets of toolbar, content, and button colors, called a "swatch". You can add a `data-theme="b"` attribute to any of the widgets on this page: page, header, list, input for the slider, or button to turn it a dark shade of grey. Different swatch letters from a-b in the default theme can be used to mix and match swatches.
 
-If you add the theme swatch to the page, all the widgets inside the content will automatically inherit the theme (headers and footers don't inherit and default to swatch "a").
+If you add the theme swatch to the page, all the widgets inside the content will automatically inherit the theme.
 
 ```
 <a href="#" data-role="button" data-icon="star" data-theme="a">Button</a>
 ```
 
-If you would like to create a custom theme, you can use [ThemeRoller](http://jquerymobile.com/themeroller/) that allows users to create their own theme through an easy to use drag and drop interface. You will then be able to download and use your newly created theme.
+If you would like to create a custom theme, you can use [ThemeRoller](https://themeroller.jquerymobile.com/) that allows users to create their own theme through an easy to use drag and drop interface. You will then be able to download and use your newly created theme.
 
 ### Go Forth and Build Something
 
-This guide has provided you with a basic structure for a jQuery Mobile page and a few enhanced elements. You can explore the full [jQuery Mobile documentation](http://jquerymobile.com/demos/1.2.0/) to learn about linking pages, adding animated page transitions, and creating dialogs and popups.
+This guide has provided you with a basic structure for a jQuery Mobile page and a few enhanced elements. You can explore the full [jQuery Mobile API Documentation](http://api.jquerymobile.com) and [jQuery Mobile Demo Center](http://demos.jquerymobile.com/1.4.5/) to learn about linking pages, adding animated page transitions, and creating dialogs and popups.
 
 If you're more of the type who prefers actually writing JavaScript to build your apps, and you don't want to use the `data-` attribute configuration system, you can take full control of everything and call plugins directly as these are all standard jQuery plugins built with the UI widget factory. Particularly useful information for such cases can be found in the global configuration, events, and methods sections.
 
diff --git a/page/jquery-mobile/theme-roller.md b/page/jquery-mobile/theme-roller.md
index 4211b31c..fe9c7247 100644
--- a/page/jquery-mobile/theme-roller.md
+++ b/page/jquery-mobile/theme-roller.md
@@ -1,21 +1,19 @@
----
-title: Creating a Custom Theme with ThemeRoller
-level: Beginner
----
+<script>{
+	"title": "Creating a Custom Theme with ThemeRoller",
+	"level": "beginner"
+}</script>
 
 ## Theming Overview
 
-jQuery Mobile has a robust theme framework that supports up to 26 sets of toolbar, content, and button colors, called a "swatch". The framework comes with five defined themes (swatches "a" to "e") which can be used readily, removed, or overwritten.
+jQuery Mobile has a robust theme framework that supports up to 26 sets of toolbar, content, and button colors, called a "swatch". The framework comes with two defined themes A and B (light and dark) which can be used readily, removed, or overwritten.
 
 ### Default Theme Swatch Mapping for Components
 
-If no theme swatch letter is set at all, the framework uses the "a" swatch (black in the default theme) for headers and footers and the "c" swatch (light gray in the default theme) for the page content to maximize contrast between the both.
-
-All items in containers inherit the swatch from their parent. Exceptions to this rule are the listdivider in listviews, the header of nested list pages, and the button of split button lists, which all default to "b" (blue in the default theme). Count bubbles default to "c" (silver in the default theme).
+If no theme swatch letter is set at all, the framework uses the "a" swatch (light color in the default theme) for headers and footers. All items in containers inherit the swatch from their parent.
 
 Note that there is also a swatch named "active" (bright blue in the default theme) which is used to indicate an active selected item. See the global "Active" state further down this page for more information on the active swatch.
 
-The page loading dialog and error message don't inherit a swatch theme. The loading dialog defaults to swatch "a" (black in the default theme) and the error message to swatch "e" (yellow in the default theme). You can configure those defaults globally.
+The page loading dialog and error message don't inherit a swatch theme. The loading dialog's overlay defaults to swatch "a" (white in the default theme). You can configure those defaults globally.
 
 ### Themes and Swatches
 
@@ -23,7 +21,7 @@ The theme system separates color and texture from structural styles that define
 
 Each theme includes several global settings, including font family, drop shadows for overlays, and corner radius values for buttons and boxes. In addition, the theme can include multiple color swatches, each with color values for bars, content blocks, buttons and list items, and font text-shadow.
 
-The default theme includes five swatches that are given letters (a, b, c, d, e) for quick reference. To make mapping of color swatches consistent across our widgets, we have followed the convention that swatch "a" is the highest level of visual priority (black in our default theme), "b" is secondary level (blue), "c" is the baseline level (gray) that we use by default in many situations, "d" for an alternate secondary level, and "e" as an accent swatch. Themes may have additional swatches for accent colors or specific situations. For example, you could add a new theme swatch "f" that has a red bar and button for use in error situations.
+The default theme includes two swatches that are given letters (a, b) for quick reference. Themes may have additional swatches for accent colors or specific situations. For example, you could add a new theme swatch "c" that has a red bar and button for use in error situations.
 
 Most theme changes can be done using ThemeRoller, but it is also fairly simple to manually edit the base swatches in the default theme and/or add additional swatches by editing the theme CSS file. Just copy a block of swatch styles, rename the classes with the new swatch letter name, and tweak colors as you see fit.
 
@@ -35,11 +33,11 @@ The easiest way to create custom themes is with the ThemeRoller tool. It allows
 
 ### Creating the Theme Swatches
 
-The [ThemeRoller](http://jquerymobile.com/themeroller/) allows users to create their own theme through an easy to use drag and drop interface. By default, ThemeRoller offers three swatches (a, b and c). You can use the offered default colors, the Adobe kuler colors, or create your own. You will create your theme by dragging the chosen color onto the chosen element in the swatch of your choice. You can add more swatches by pressing the "+" sign near the "A", "B", and "C" tabs, in the left-hand side menu.
+The [ThemeRoller](http://jquerymobile.com/themeroller/) allows users to create their own theme through an easy to use drag and drop interface. By default, ThemeRoller offers three swatches (a, b and c). You can use the offered default colors, the Adobe Kuler colors, or create your own. You will create your theme by dragging the chosen color onto the chosen element in the swatch of your choice. You can add more swatches by pressing the "+" sign near the "A", "B", and "C" tabs, in the left-hand side menu.
 
 You can further edit your swatch from the menu. For example, you can expand the various element parts and carry out detailed editing. This will allow you to change text color, text shadow size, position and color, etc. You can also edit the gradient used on each element.
 
-Here are two examples of theme swatches created, one with the default colors, and one with the kuler colors:
+Here are two examples of theme swatches created, one with the default colors, and one with the Kuler colors:
 
 ![picture Default colors theme example](/resources/jquery-mobile/Theme.png "Default colors theme example") ![picture Kuler theme example](/resources/jquery-mobile/Kuler.png "Kuler theme example")
 
@@ -63,9 +61,9 @@ To start using your theme, you can either start from the provided `index.html`,
 	<meta charset="utf-8">
 	<meta name="viewport" content="width=device-width, initial-scale=1">
 	<link rel="stylesheet" href="css/themes/my-custom-theme.css">
-	<link rel="stylesheet" href="http://code.jquery.com/mobile/1.2.0/jquery.mobile.structure-1.2.0.min.css">
-	<script src="http://code.jquery.com/jquery-1.8.2.min.js"></script>
-	<script src="http://code.jquery.com/mobile/1.2.0/jquery.mobile-1.2.0.min.js"></script>
+	<link rel="stylesheet" href="https://code.jquery.com/mobile/1.2.0/jquery.mobile.structure-1.2.0.min.css">
+	<script src="https://code.jquery.com/jquery-1.8.2.min.js"></script>
+	<script src="https://code.jquery.com/mobile/1.2.0/jquery.mobile-1.2.0.min.js"></script>
 </head>
 ```
 
diff --git a/page/jquery-ui.md b/page/jquery-ui.md
index 79c03ea8..489e7d2e 100644
--- a/page/jquery-ui.md
+++ b/page/jquery-ui.md
@@ -1,10 +1,12 @@
----
-title: jQuery UI
-customFields:
- -
-    key: "icon"
-    value: "magnet"
----
+<script>{
+	"title": "jQuery UI",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "magnet"
+		}
+	]
+}</script>
 
 [jQuery UI](http://jqueryui.com) is a curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library. Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice.
 
diff --git a/page/jquery-ui/environments.md b/page/jquery-ui/environments.md
index 0243d0d1..7b49e02b 100644
--- a/page/jquery-ui/environments.md
+++ b/page/jquery-ui/environments.md
@@ -1,6 +1,6 @@
----
-title: Using jQuery UI
-level: intermediate
----
+<script>{
+	"title": "Using jQuery UI",
+	"level": "intermediate"
+}</script>
 
-In addition to being available on [CDN](http://code.jquery.com/)s and [Download Builder](http://jqueryui.com/download/), jQuery UI also integrates into a number of development environments.
\ No newline at end of file
+In addition to being available on [CDN](https://releases.jquery.com/ui/)s and [Download Builder](http://jqueryui.com/download/), jQuery UI also integrates into a number of development environments.
diff --git a/page/jquery-ui/environments/amd.md b/page/jquery-ui/environments/amd.md
index e2baa4ca..9214e985 100644
--- a/page/jquery-ui/environments/amd.md
+++ b/page/jquery-ui/environments/amd.md
@@ -1,7 +1,7 @@
----
-title: Using jQuery UI with AMD
-level: intermediate
----
+<script>{
+	"title": "Using jQuery UI with AMD",
+	"level": "intermediate"
+}</script>
 
 <div class="warning">**Note:** This documentation refers to functionality made available in jQuery UI 1.11.</div>
 
@@ -13,7 +13,7 @@ In this article we'll walk through the process of using AMD with jQuery UI. Let'
 
 We'll need to download three things to get up and running: jQuery core, jQuery UI, and an AMD loader.
 
-While any AMD loader will work, we'll use RequireJS in this article, which you can download from <http://requirejs.org/docs/download.html>. If you don't have a version of jQuery core handy, you can get it from <http://jquery.com/download/>, and you can download jQuery UI directly from <http://jqueryui.com/>. Alternatively you can [download these libraries using a package manager such as Bower](/jquery-ui/environments/bower/).
+While any AMD loader will work, we'll use RequireJS in this article, which you can download from <http://requirejs.org/docs/download.html>. If you don't have a version of jQuery core handy, you can get it from <http://jquery.com/download/>, and you can download the jQuery UI source files from <https://github.com/jquery/jquery-ui/releases> (use the files in the `ui` directory). You can alternatively [download these libraries using a package manager such as Bower](/jquery-ui/environments/bower/).
 
 ### Directory Structure
 
diff --git a/page/jquery-ui/environments/bower.md b/page/jquery-ui/environments/bower.md
index 8c094133..37793006 100644
--- a/page/jquery-ui/environments/bower.md
+++ b/page/jquery-ui/environments/bower.md
@@ -1,7 +1,7 @@
----
-title: Using jQuery UI with Bower
-level: intermediate
----
+<script>{
+	"title": "Using jQuery UI with Bower",
+	"level": "intermediate"
+}</script>
 
 <div class="warning">**Note:** This documentation refers to functionality made available in jQuery UI 1.11.</div>
 
@@ -35,13 +35,13 @@ As an example, suppose we're starting a new project and we need to use [jQuery U
 </html>
 ```
 
-This examples fails with a JavaScript error because neither jQuery core nor jQuery UI are loaded. Let's load them with Bower.
+This example fails with a JavaScript error because neither jQuery core nor jQuery UI are loaded. Let's load them with Bower.
 
 ### Downloading jQuery UI With Bower
 
 Libraries are downloaded with Bower using the `bower install` command. To install jQuery UI, run `bower install jquery-ui`. Doing so creates the following (simplified) directory structure.
 
-*Note: If you get an error that the `bower` command is not found, checkout [Bower's installation instructions](http://bower.io/#installing-bower).*
+*Note: If you get an error that the `bower` command is not found, check out [Bower's installation instructions](http://bower.io/#installing-bower).*
 
 <pre>
 .
@@ -53,23 +53,16 @@ Libraries are downloaded with Bower using the `bower install` command. To instal
 │   │   └── src
 │   └── jquery-ui
 │       ├── themes
-│       │   ├── base
+│       │   ├── smoothness
 │       │   │   ├── jquery-ui.css
-│       │   │   ├── accordion.css
-│       │   │   ├── ...
-│       │   │   └── minified
-│       │   │       ├── jquery-ui.min.css
-│       │   │       ├── accordion.min.css
-│       │   │       └── ...
+│       │   │   └── jquery-ui.min.css
 │       │   └── [The rest of jQuery UI's themes]
-│       └── ui
-│           ├── jquery-ui.js
-│           ├── accordion.js
-│           ├── ...
-│           └── minified
-│               ├── jquery-ui.min.js
-│               ├── accordion.min.js
-│               └── ...
+│       ├── ui
+│       │   ├── accordion.js
+│       │   ├── autocomplete.js
+│       │   └── ...
+│       ├── jquery-ui.js
+│       └── jquery-ui.min.js
 └── index.html
 </pre>
 
@@ -89,7 +82,7 @@ We have a few different options for using the files downloaded with Bower. The e
 <head>
 	<meta charset="utf-8">
 	<title>jQuery Projects</title>
-	<link rel="stylesheet" href="bower_components/jquery-ui/themes/base/jquery-ui.css">
+	<link rel="stylesheet" href="bower_components/jquery-ui/themes/smoothness/jquery-ui.min.css">
 </head>
 <body>
 
@@ -103,7 +96,7 @@ We have a few different options for using the files downloaded with Bower. The e
 </div>
 
 <script src="bower_components/jquery/dist/jquery.min.js"></script>
-<script src="bower_components/jquery-ui/ui/minified/jquery-ui.min.js"></script>
+<script src="bower_components/jquery-ui/jquery-ui.min.js"></script>
 <script>
 	$( "#projects" ).accordion();
 </script>
@@ -122,9 +115,7 @@ Because Bower also downloaded jQuery UI's individual source files, we can altern
 <head>
 	<meta charset="utf-8">
 	<title>jQuery Projects</title>
-	<link rel="stylesheet" href="bower_components/jquery-ui/themes/base/core.css">
-	<link rel="stylesheet" href="bower_components/jquery-ui/themes/base/theme.css">
-	<link rel="stylesheet" href="bower_components/jquery-ui/themes/base/accordion.css">
+	<link rel="stylesheet" href="bower_components/jquery-ui/themes/smoothness/jquery-ui.min.css">
 </head>
 <body>
 
@@ -149,4 +140,4 @@ Because Bower also downloaded jQuery UI's individual source files, we can altern
 </html>
 ```
 
-From here, you can hook jQuery UI's files into your own custom build system to concatenate and minify your resources for production. If you're a RequireJS user, checkout our [guide on how to use jQuery UI with AMD](/jquery-ui/environments/amd/).
\ No newline at end of file
+From here, you can hook jQuery UI's files into your own custom build system to concatenate and minify your resources for production. If you're a RequireJS user, check out our [guide on how to use jQuery UI with AMD](/jquery-ui/environments/amd/).
diff --git a/page/jquery-ui/getting-started.md b/page/jquery-ui/getting-started.md
index a2c0fe25..b32a53dc 100644
--- a/page/jquery-ui/getting-started.md
+++ b/page/jquery-ui/getting-started.md
@@ -1,7 +1,7 @@
----
-title: Getting Started with jQuery UI
-level: beginner
----
+<script>{
+	"title": "Getting Started with jQuery UI",
+	"level": "beginner"
+}</script>
 
 ### What is jQuery UI?
 
@@ -32,32 +32,20 @@ You can either choose from the various themes we provide, or you can design your
 
 #### Step 3: Choose a Version of jQuery UI
 
-The last step in the Download Builder is to select a version number. This is a very important step because jQuery UI versions are designed to work with specific versions of jQuery. The current versions are:
-
-* jQuery UI 1.10.2 – Requires jQuery 1.6 or later.
-* jQuery UI 1.9.2 – Requires jQuery 1.6 or later.
+The last step in the Download Builder is to select a version number. Make sure to check not only what version of jQuery UI you pick, but also the version of jQuery Core that version supports, as different versions of the library support different versions of jQuery. For more information on what's new in each version of jQuery UI, see the project's [upgrade guides](http://jqueryui.com/upgrade-guide/) and [changelogs](http://jqueryui.com/changelog/).
 
 #### Click Download!
 
 You're finished with the Download Builder! Click the download button and you'll get a customized zip file containing everything you selected.
 
-### After Downloading: Intro to Using jQuery UI
-
-Once you've downloaded jQuery UI, you'll get a zip containing the following files:
-
-* `/css/`
-* `/development-bundle/`
-* `/js/`
-* `index.html`
-
 ### Basic Overview: Using jQuery UI on a Web Page
 
-Open up `index.html` in a text editor and you'll see that it links to a few dependencies: your theme, jQuery, and jQuery UI. Generally, you'll need to include these three files on any page to use jQuery UI widgets and interactions:
+Next, open up `index.html` from the downloaded zip in a text editor. You'll see that it references your theme, jQuery, and jQuery UI. Generally, you'll need to include these three files on any page to use the jQuery UI widgets and interactions:
 
 ```html
-<link rel="stylesheet" href="css/themename/jquery-ui.custom.css" />
-<script src="js/jquery.min.js"></script>
-<script src="js/jquery-ui.custom.min.js"></script>
+<link rel="stylesheet" href="jquery-ui.min.css">
+<script src="external/jquery/jquery.js"></script>
+<script src="jquery-ui.min.js"></script>
 ```
 
 Once you've included the necessary files, you can add some jQuery widgets to your page. For example, to make a datepicker widget, you'll add a text input element to your page and then call `.datepicker()` on it. Like this:
@@ -65,7 +53,7 @@ Once you've included the necessary files, you can add some jQuery widgets to you
 **HTML:**
 
 ```html
-<input type="text" name="date" id="date" />
+<input type="text" name="date" id="date">
 ```
 
 **JavaScript:**
@@ -123,8 +111,8 @@ When you click the "Download theme" button in ThemeRoller, you'll be directed to
 
 ### Support: Where Can I Get Help?
 
-JQuery UI user and developer resources are kept up-to-date at the [Support Center](http://jqueryui.com/support).
+JQuery UI user and developer resources are kept up-to-date at the [Support Center](http://jqueryui.com/support/).
 
 ### Developers Wanted!
 
-Want to join the jQuery UI team? We'd love your help! Visit the UI [Development Center](http://jqueryui.com/development) for details on how to get involved.
+Want to join the jQuery UI team? We'd love your help! Visit the UI [Development Center](http://jqueryui.com/development/) for details on how to get involved.
diff --git a/page/jquery-ui/how-jquery-ui-works.md b/page/jquery-ui/how-jquery-ui-works.md
index f69abcc1..a03196cc 100644
--- a/page/jquery-ui/how-jquery-ui-works.md
+++ b/page/jquery-ui/how-jquery-ui-works.md
@@ -1,7 +1,7 @@
----
-title: How jQuery UI Works
-level: Beginner
----
+<script>{
+	"title": "How jQuery UI Works",
+	"level": "beginner"
+}</script>
 
 jQuery UI contains many widgets that maintain [state](http://en.wikipedia.org/wiki/State_%28computer_science%29) and therefore may have a slightly different usage pattern than typical jQuery plugins you are already used to. While the initialization is the same as most jQuery plugins, jQuery UI's widgets are built on top of the [Widget Factory](/jquery-ui/widget-factory/) which provides the same general API to all of them. So if you learn how to use one, then you'll know how to use all of them! This document will walk you through the common functionality, using the [progressbar](http://jqueryui.com/progressbar/) widget for the code examples.
 
diff --git a/page/jquery-ui/theming/themeroller.md b/page/jquery-ui/themeroller.md
similarity index 60%
rename from page/jquery-ui/theming/themeroller.md
rename to page/jquery-ui/themeroller.md
index c223f4e2..096dd226 100644
--- a/page/jquery-ui/theming/themeroller.md
+++ b/page/jquery-ui/themeroller.md
@@ -1,12 +1,13 @@
----
-title: Using jQuery UI ThemeRoller
-level: beginner
----
+<script>{
+	"title": "Using jQuery UI ThemeRoller",
+	"level": "beginner"
+}</script>
+
 ![ThemeRoller logo](/resources/jquery-ui/themeroller-logo.png)
 
 ### About ThemeRoller
 
-ThemeRoller is a web app that offers a fun and intuitive interface for designing and downloading custom themes for jQuery UI. You can find ThemeRoller in the "Themes" section of the jQuery UI site, or by following this link: [jQuery UI ThemeRoller](http://jqueryui.com/themeroller)
+ThemeRoller is a web app that offers a fun and intuitive interface for designing and downloading custom themes for jQuery UI. You can find ThemeRoller in the "Themes" section of the jQuery UI site, or by following this link: [jQuery UI ThemeRoller](http://jqueryui.com/themeroller/)
 
 ![ThemeRoller Sidebar](/resources/jquery-ui/themeroller-interface-new.png)
 ![ThemeRoller Sidebar](/resources/jquery-ui/themeroller-gallery-new.png)
@@ -21,13 +22,11 @@ ThemeRoller themes can be viewed via permalink URLs, and it includes a gallery o
 
 ### Downloading Themes
 
-When you're done designing a theme, you can download it for use in your projects. ThemeRoller has a "Download theme" button at the top which will generate a zip file containing all of the theme assets. Images included in your download will be generated to your specifications and saved as high-quality PNG files.
-
-Your theme will include images and CSS that make up a customized version of the jQuery UI CSS Framework including images and CSS for all of our plugins.
+When you're done designing a theme, you can download it for use in your projects. ThemeRoller has a "Download theme" button at the top which will lead you to the download builder page. From there you can also pick the components to download with your theme. Finally the Download button at the bottom will generate a zip file containing the theme along with assets like images and any components you picked. Images included in your download will be generated to your specifications and saved as high-quality PNG files.
 
 ### Installing Downloaded Themes Into Your Project
 
-Once the theme has been downloaded and unzipped, you will see a folder named `themes`. This folder contains the CSS and images needed for your theme. Copy the theme directory into your project and link to the `themes/all.css` file from your pages.
+Once you've unzipped the package, you will see several `css` and `js` files, along with two folders. If you're only interested in the full theme, copy `jquery-ui.css` and the `images` folder into your project and link to the `jquery-ui.css` file from your pages.
 
 ### Building Custom "ThemeRoller-Ready" Components
 ![ThemeRoller Ready Banner](/resources/jquery-ui/themeroller-ready-black-200px.png)
@@ -35,13 +34,4 @@ Once the theme has been downloaded and unzipped, you will see a folder named `th
 
 ThemeRoller generates a customized version of the jQuery UI CSS Framework for developing your own ThemeRoller-ready jQuery components. The classes generated by this framework are designed to accommodate common user interface design situations and include states, icons, and various helper classes as well.
 
-For information on developing with the jQuery UI CSS Framework, visit our [Theming API documentation](/jquery-ui/theming/api).
-
-### ThemeRoller Links
-* [Tutorial: Develop Your Own jQuery "ThemeRoller-Ready" Components, Filament Group](http://www.filamentgroup.com/lab/developer_your_own_jquery_themeroller_ready_components/)
-* [Introducing ThemeRoller: Design & Download Custom Themes for jQuery UI, Filament Group](http://www.filamentgroup.com/lab/introducing_themeroller_design_download_custom_themes_for_jquery_ui/)
-* [Videos about Design & Download Custom Themes for jQuery UI, Filament Group](http://www.dizi-izle-film-izle.net)
-
-### Credits
-
-ThemeRoller was designed and developed for jQuery UI by [Filament Group, Inc](http://www.filamentgroup.com), of Boston, MA.
+For information on developing with the jQuery UI CSS Framework, visit our [Theming API documentation](http://api.jqueryui.com/theming/css-framework/).
diff --git a/page/jquery-ui/theming.md b/page/jquery-ui/theming.md
index e6795eed..56e5cf5b 100644
--- a/page/jquery-ui/theming.md
+++ b/page/jquery-ui/theming.md
@@ -1,15 +1,15 @@
----
-title: Theming jQuery UI
-level: intermediate
----
+<script>{
+	"title": "Theming jQuery UI",
+	"level": "intermediate"
+}</script>
 
-All jQuery UI plugins are designed to allow a developer to seamlessly integrate UI widgets into the look and feel of their site or application. Each plugin is styled with CSS and contains two layers of style information: standard [jQuery UI CSS Framework](/jquery-ui/theming/api/) styles and plugin-specific styles.
+All jQuery UI plugins are designed to allow a developer to seamlessly integrate UI widgets into the look and feel of their site or application. Each plugin is styled with CSS and contains two layers of style information: standard [jQuery UI CSS Framework](http://api.jqueryui.com/theming/css-framework/) styles and plugin-specific styles.
 
-The jQuery UI CSS Framework provide semantic presentation classes to indicate the role of an element within a widget such as a header, content area, or clickable region. These are applied consistently across all widgets so a clickable tab, accordion, or button will all have the same `ui-state-default` class applied to indicate that it is clickable. When a user mouses over one of these elements, this class is changed to `ui-state-hover`, then `ui-state-active` when selected. This level of class consistency makes it easy to ensure that all elements with a similar role or interaction state will look the same across all widgets.
+The jQuery UI CSS Framework provides semantic presentation classes to indicate the role of an element within a widget such as a header, content area, or clickable region. These are applied consistently across all widgets so a clickable tab, accordion, or button will all have the same `ui-state-default` class applied to indicate that it is clickable. When a user mouses over one of these elements, this class is changed to `ui-state-hover`, then `ui-state-active` when selected. This level of class consistency makes it easy to ensure that all elements with a similar role or interaction state will look the same across all widgets.
 
-The CSS Framework styles are encapsulated in a single file called `ui.theme.css` and this is the file modified by the [ThemeRoller](/jquery-ui/theming/themeroller/) application. Framework styles only include attributes that affect the look and feel (primarily color, background images, and icons) so these are "safe" styles that will not affect functionality of individual plugins. This separation means that a developer can create a custom look and feel by modifying the colors and images in the `theme.css` file and know that as future plugins or bug fixes become available, these should work with the theme without modification.
+The CSS Framework styles are encapsulated in a single file called `theme.css` and this is the file modified by the [ThemeRoller](/jquery-ui/themeroller/) application. Framework styles only include attributes that affect the look and feel (primarily color, background images, and icons) so these are "safe" styles that will not affect functionality of individual plugins. This separation means that a developer can create a custom look and feel by modifying the colors and images in the `theme.css` file and know that as future plugins or bug fixes become available, these should work with the theme without modification.
 
-Since the framework styles only cover look and feel, plugin specific stylesheets are included that contain all the additional structural style rules required to make the widget functional, such as dimensions, padding, margins, positioning, and floats. Stylesheets for each plugin are located in the `themes/base` folder of the download and are named to match the plugin such as "jquery.ui.accordion.css". These styles must be carefully edited because they work in conjunction with the scripting and provide overrides of framework styles as needed.
+Since the framework styles only cover look and feel, plugin specific stylesheets are separated. These contain all the additional structural style rules required to make the widget functional, such as dimensions, padding, margins, positioning, and floats. When downloading jQuery UI, these can be found in `jquery-ui.structure.css`.
 
 We encourage all developers creating jQuery plugins to leverage the jQuery UI CSS Framework because it will make it much easier for end users to theme and use your plugin.
 
@@ -17,8 +17,6 @@ We encourage all developers creating jQuery plugins to leverage the jQuery UI CS
 
 There are three general approaches to theming jQuery UI plugins:
 
-* **Download a ThemeRoller theme**: The easiest way to build a theme is to use the [ThemeRoller](/jquery-ui/theming/themeroller/) to generate and download a theme. This app will create a new `ui.theme.css` file and an `images` directory containing all necessary background images and icon sprites which can simply be dropped into your project. This approach will be the easiest to create and maintain but limits customization to the options provided in ThemeRoller.
-* **Modify the CSS files**: To get a bit more control over the look and feel, you may choose to start with the default theme (Smoothness) or a ThemeRoller-generated theme and then adjust the `ui.theme.css` file or any of the individual plugin stylesheets. For example, you could easily tweak the corner radius for all buttons to be different than the rest of the UI components or change the path for the icon sprite to use a custom set.  With a bit of style scoping, you can even use multiple themes together in a single UI. To keep maintenance simple, restricting changes to just the `ui.theme.css` file and images is recommended.
+* **Download a ThemeRoller theme**: The easiest way to build a theme is to use [ThemeRoller](/jquery-ui/themeroller/) to generate and download a theme. This app will create a new `jquery-ui.theme.css` file and an `images` directory containing all necessary background images and icon sprites which can simply be dropped into your project. This approach will be the easiest to create and maintain but limits customization to the options provided in ThemeRoller.
+* **Modify the CSS files**: To get a bit more control over the look and feel, you may choose to start with the default theme (Smoothness) or a ThemeRoller-generated theme and then adjust the `jquery-ui.theme.css` file or any of the individual plugin stylesheets. For example, you could easily tweak the corner radius for all buttons to be different than the rest of the UI components or change the path for the icon sprite to use a custom set.  With a bit of style scoping, you can even use multiple themes together in a single UI. To keep maintenance simple, restricting changes to just the `jquery-ui.theme.css` file and images is recommended.
 * **Write completely custom CSS**: For the greatest amount of control, the CSS for each plugin can be written from scratch without using the framework classes or plugin-specific stylesheet. This may be necessary if the desired look and feel can't be achieved by modifying the CSS or if highly customized markup is used. This approach requires deep expertise in CSS and will require manual updates for future plugins.
-
-### Using ThemeRoller, the jQuery UI CSS Framework, and Writing Custom Themes
diff --git a/page/jquery-ui/theming/api.md b/page/jquery-ui/theming/api.md
deleted file mode 100644
index f59946aa..00000000
--- a/page/jquery-ui/theming/api.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: jQuery UI CSS Framework API
-level: intermediate
----
-
-[Back to jQuery UI Theming](/jquery-ui/theming/)
-
-### The jQuery UI CSS Framework
-
-jQuery UI includes a robust CSS Framework designed for building custom jQuery widgets. The framework includes classes that cover a wide array of common user interface needs, and can be manipulated using jQuery UI ThemeRoller. By building your UI components using the jQuery UI CSS Framework, you will be adopting shared markup conventions and allowing for ease of code integration across the plugin community at large.
-
-### Framework Classes
-
-The following CSS classes are split between `ui.core.css` and `ui.theme.css`, depending on whether styles are fixed and structural, or themeable (colors, fonts, backgrounds, etc.) respectively. These classes are designed to be applied to user interface elements to achieve visual consistency across an application and allow components to be themeable by jQuery UI ThemeRoller.
-
-### Layout Helpers
-
-* `.ui-helper-hidden`: Applies `display: none` to elements.
-* `.ui-helper-hidden-accessible`: Applies accessible hiding to elements (via absolute positioning off the page.)
-* `.ui-helper-reset`: A basic style reset for UI elements. Resets things such as `padding`, `margin`, `text-decoration`, `list-style, etc.
-* `.ui-helper-clearfix`: Applies float wrapping properties to parent elements.
-* `.ui-helper-zfix`: Applies iframe "fix" CSS to `<iframe>` elements when needed in overlays.
-
-### Widget Containers
-
-* `.ui-widget`: Class to be applied on outer container of all widgets. Applies font family and font size to widget. Also applies same family and 1em font size to child form elements specifically, to combat inheritance issues in Windows browsers.
-* `.ui-widget-header`: Class to be applied to header containers. Applies header container styles to an element and its child text, links, and icons.
-* `.ui-widget-content`: Class to be applied to content containers. Applies content container styles to an element and its child text, links, and icons. (Can be applied to parent or sibling of header.)
-
-### Interaction States
-
-* `.ui-state-default`: Class to be applied to clickable button-like elements. Applies "clickable default" container styles to an element and its child text, links, and icons.
-* `.ui-state-hover`: Class to be applied on mouseover to clickable button-like elements. Applies "clickable hover" container styles to an element and its child text, links, and icons.
-* `.ui-state-focus`: Class to be applied on keyboard focus to clickable button-like elements. Applies "clickable hover" container styles to an element and its child text, links, and icons.
-* `.ui-state-active`: Class to be applied on mousedown to clickable button-like elements. Applies "clickable active" container styles to an element and its child text, links, and icons.
-
-### Interaction Cues
-
-* `.ui-state-highlight`: Class to be applied to highlighted or selected elements. Applies "highlight" container styles to an element and its child text, links, and icons.
-* `.ui-state-error`: Class to be applied to error messaging container elements. Applies "error" container styles to an element and its child text, links, and icons.
-* `.ui-state-error-text`: An additional class that applies just the error text color without background. Can be used on form labels for instance. Also applies error icon color to child icons.
-* `.ui-state-disabled`: Applies a dimmed opacity to disabled UI elements. Meant to be added in addition to an already-styled element.
-* `.ui-priority-primary`: Class to be applied to a priority-1 button in situations where button hierarchy is needed. Applies bold text.
-* `.ui-priority-secondary`: Class to be applied to a priority-2 button in situations where button hierarchy is needed. Applies normal weight text and slight transparency to element.
-
-### Icons
-
-#### States and Images
-
-* `.ui-icon`: Base class to be applied to an icon element. Sets dimensions to 16px square block, hides inner text, sets background image to "content" state sprite image. **Note:** *`.ui-icon` class will be given a different sprite background image depending on its parent container. For example, a `ui-icon` element within a `ui-state-default` container will get colored according to the `ui-state-default`'s icon color.*
-
-#### Icon Types
-
-After declaring a `.ui-icon` class, you can follow up with a second class describing the type of icon you'd like. Icon classes generally follow a syntax of `.ui-icon-{icon type}-{icon sub description}-{direction}`.
-
-For example, a single triangle icon pointing to the right looks like this:
-`.ui-icon-triangle-1-e`
-
-jQuery UI's [ThemeRoller](http://jqueryui.com/themeroller) provides the full set of CSS framework icons in its preview column. Hover over them to see the class name.
-
-### Miscellaneous Visuals
-
-#### Corner Radius Helpers
-
-* `.ui-corner-tl`: Applies corner-radius to top left corner of element.
-* `.ui-corner-tr`: Applies corner-radius to top right corner of element.
-* `.ui-corner-bl`: Applies corner-radius to bottom left corner of element.
-* `.ui-corner-br`: Applies corner-radius to bottom right corner of element.
-* `.ui-corner-top`: Applies corner-radius to both top corners of element.
-* `.ui-corner-bottom`: Applies corner-radius to both bottom corners of element.
-* `.ui-corner-right`: Applies corner-radius to both right corners of element.
-* `.ui-corner-left`: Applies corner-radius to both left corners of element.
-* `.ui-corner-all`: Applies corner-radius to all four corners of element.
-
-#### Overlay & Shadow
-
-* `.ui-widget-overlay`: Applies 100% width and height dimensions to an overlay screen, along with background color/texture, and screen opacity.
-* `.ui-widget-shadow`: Class to be applied to overlay with opacity, top/left offsets, and shadow "thickness". Thickness is applied via padding to all sides of a shadow that is set to match the dimensions of the overlay element. Offsets are applied via top and left margins (can be positive or negative).
diff --git a/page/jquery-ui/theming/write-a-theme.md b/page/jquery-ui/theming/write-a-theme.md
deleted file mode 100644
index 81146a7d..00000000
--- a/page/jquery-ui/theming/write-a-theme.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: How To Write a Theme
-level: advanced
----
-
-### File Structure
-
-Themes are meant to be structured in a specific manner in order to increase their ease of use. The general file directory structure is as follows:
-
-* `themename/` – Your theme should be completely contained within a single directory named the same as your theme.
-* `themename/themename.css` – This is your base CSS file. This file will be included on every page that uses your theme, regardless of which plugins are being used. This file should be very lightweight and only include the essentials.
-* `themename/themename.pluginname.css` – You'll need one CSS file for each plugin that you support. The name of the plugin should be included directly in the filename. For example, if you themed the tabs plugin, you would have: `themename.tabs.js`.
-* `themename/img.png` – Your theme can include images, if need be. They can be named whatever you'd like, there is no particular naming convention for these.
-
-For examples of how theme file structures are done, feel free to look through the [jQuery UI base theme](https://github.com/jquery/jquery-ui/tree/master/themes/base).
-
-### Styling
-
-Writing styles for themes is rather simplistic – which is good, as it allows for a great amount of flexibility.
-
-All themes should have a base CSS class to work off of. This main class allows the user to enable, and switch between, themes. Your root class should be of the format `.ui-themename`. And it will be used like so, within a user's HTML file:
-
-```html
-<html>
-<head>
-	<title>My Site</title>
-	<link rel="stylesheet" href="themename/themename.css" />
-	<link rel="stylesheet" href="othertheme/othertheme.css" />
-	<link rel="stylesheet" href="othertheme/othertheme.dialog.css" />
-</head>
-<body class="ui-themename">
-	<div class="ui-othertheme">
-		<div class="ui-dialog">This is a modal dialog.</div>
-	</div>
-</body>
-</html>
-```
-
-In the above example, a couple important things are occurring:
-
-* We're loading two themes into a document at the same time.
-* The whole page, and all of its contents, are themed according to themename's styling.
-* However, the `<div>` with the class of ui-othertheme, and everything inside of it (including the modal dialog), is themed according to othertheme's styling rules.
-
-If we were to take a look inside `themename.css` we might see something like the following:
-
-```css
-body.ui-themename { background:#111; color:snow; }
-.ui-themename a, a.ui-themename { color:#68D; outline:none; }
-.ui-themename a:visited, a.ui-themename:visited { color:#D66; }
-.ui-themename a:hover, a.ui-themename:hover { color:#FFF; }
-```
-
-If you'll notice, the `themename.css` file only contains styling information that is globally applicable (nothing plugin-specific is contained within here). This will be true for all cases where a theme is built. Don't worry about a theme taking up multiple files – that will be simplified within the build and download process.
diff --git a/page/jquery-ui/widget-factory.md b/page/jquery-ui/widget-factory.md
index c25cde4c..6e31bb9f 100644
--- a/page/jquery-ui/widget-factory.md
+++ b/page/jquery-ui/widget-factory.md
@@ -1,6 +1,6 @@
----
-title: Widget Factory
-level: intermediate
----
+<script>{
+	"title": "Widget Factory",
+	"level": "intermediate"
+}</script>
 
 The jQuery UI Widget Factory is an extensible base on which all of jQuery UI's widgets are built. Using the widget factory to build a plugin provides conveniences for state management, as well as conventions for common tasks like exposing plugin methods and changing options after instantiation.
diff --git a/page/jquery-ui/widget-factory/classes-option.md b/page/jquery-ui/widget-factory/classes-option.md
new file mode 100644
index 00000000..f5504f47
--- /dev/null
+++ b/page/jquery-ui/widget-factory/classes-option.md
@@ -0,0 +1,87 @@
+<script>{
+	"title": "Using the classes Option",
+	"level": "advanced"
+}</script>
+
+As of the 1.12 release, the jQuery UI widget factory includes a means of managing CSS class names through the [`classes` option](http://api.jqueryui.com/jquery.widget/#option-classes). This article will give you an overview of how the `classes` option works, and discuss what you can do with it.
+
+## Syntax overview
+
+The `classes` option is used to map structural class names to theme-related class names that you define. To see what this means let's look at an example. The code below uses the `classes` option to create a red dialog:
+
+```
+<style>
+	.custom-red { background: red; }
+</style>
+<script>
+	var dialog = $( "<div>Red</div>" ).dialog({
+		classes: {
+			"ui-dialog": "custom-red"
+		}
+	});
+</script>
+```
+
+Here, the presentational `custom-red` class name is associated with the structural `ui-dialog` class name. Now, whenever the dialog applies the `ui-dialog` class name, it will also add a `custom-red` class name. However, something other than adding the `custom-red` class has happened here, which isn't immediately obvious. This code also *removes* the existing default value which was `"ui-corner-all"`. You can associate multiple class names by including multiple space-delimited class names in the object's value. For instance the following code creates a dialog that is red and still has rounded corners:
+
+```
+<style>
+	.custom-red { background: red; }
+</style>
+<script>
+	var dialog = $( "<div>Big and red</div>" ).dialog({
+		classes: {
+			"ui-dialog": "ui-corner-all custom-red"
+		}
+	});
+</script>
+```
+
+*Note: To get a full list of the class names you can use with the `classes` option, check the API documentation for the jQuery UI widget you're interested in. For example, here's the list of classes for the dialog width: <http://api.jqueryui.com/dialog/#theming>.*
+
+The `classes` option works like any other widget factory option, which means all the widget factory option mechanisms still apply. For instance, the following code uses the [`option()` method](http://api.jqueryui.com/jquery.widget/#method-option) to remove all class names currently associated with the `ui-dialog` class name:
+
+```
+dialog.dialog( "option", "classes.ui-dialog", null );
+```
+
+And the following creates a [widget extension](http://learn.jquery.com/jquery-ui/widget-factory/extending-widgets/) that automatically associates the `custom-red` class with the `ui-dialog` class:
+
+```
+<style>
+	.custom-red { background: red; }
+</style>
+<script>
+	$.widget( "custom.dialog", $.ui.dialog, {
+		options: {
+			classes: {
+				"ui-dialog": "ui-corner-all custom-red custom-big"
+			}
+		}
+	});
+	$( "<div>Big and red</div>" ).dialog();
+</script>
+```
+
+As an added benefit, the widget factory also removes any class names specified in the `classes` option when the widget is destroyed.
+
+## Theming
+
+As the previous examples show, the `classes` option provides a quick way to associate theme-related class names with the structural class names used within a widget. This approach works for simple cases, but it can also be used to adapt third-party themes to work with widget-factory-built widgets. For example, if you're using [Bootstrap](http://getbootstrap.com/) and jQuery UI together, you can use the following code to create a jQuery UI dialog that uses Bootstrap's theming:
+
+```
+$.extend( $.ui.dialog.prototype.options.classes, {
+	"ui-dialog": "modal-content",
+	"ui-dialog-titlebar": "modal-header",
+	"ui-dialog-title": "modal-title",
+	"ui-dialog-titlebar-close": "close",
+	"ui-dialog-content": "modal-body",
+	"ui-dialog-buttonpane": "modal-footer"
+});
+```
+
+For more examples of this approach, check out [Alexander Schmitz's repo](https://github.com/arschmitz/jqueryui-bootstrap-adapter) that adapts jQuery UI to work with Boostrap using the `classes` option.
+
+## Conclusion
+
+The introduction of the `classes` option takes us one step further in the split between structural and theme-related classes, making it easier than ever to make jQuery UI widgets match the look and feel of your existing site. At the same time, this allows jQuery UI to be used alongside other CSS frameworks, just like jQuery can be used alongside other JavaScript frameworks.
diff --git a/page/jquery-ui/widget-factory/extending-widgets.md b/page/jquery-ui/widget-factory/extending-widgets.md
index 317ff57c..ae9fb5d0 100644
--- a/page/jquery-ui/widget-factory/extending-widgets.md
+++ b/page/jquery-ui/widget-factory/extending-widgets.md
@@ -1,7 +1,7 @@
----
-title: Extending Widgets with the Widget Factory
-level: advanced
----
+<script>{
+	"title": "Extending Widgets with the Widget Factory",
+	"level": "advanced"
+}</script>
 
 jQuery UI's widget factory makes it easy to build widgets that extend the functionality of existing widgets. Doing so allows you to build powerful widgets on top of an existing base, as well as make small tweaks to an existing widget's functionality.
 
@@ -23,7 +23,7 @@ Like the previous example, the following also creates a "superDialog" widget in
 $.widget( "custom.superDialog", $.ui.dialog, {} );
 ```
 
-Here superDialog and dialog are essentially equivalent widgets with different names and namepaces. To make our new widget more interesting we can add methods to its prototype object.
+Here superDialog and dialog are essentially equivalent widgets with different names and namespaces. To make our new widget more interesting we can add methods to its prototype object.
 
 A widget's prototype object is the final argument passed to `$.widget()`. So far, our examples have been using an empty object. Let's add a method to this object:
 
@@ -44,7 +44,7 @@ Now the `superDialog` has a `red()` method that will change the color of its tex
 
 ### Extending Existing Methods
 
-Sometimes you need to tweak or add to the behavior of existing widget methods. The do this, specify a method with the same name as the method you want to override on the prototype object. The following example overrides dialog's [`open()` method](http://api.jqueryui.com/dialog/#method-open). Since dialogs automatically open by default, `"open"` will be logged when this code runs.
+Sometimes you need to tweak or add to the behavior of existing widget methods. To do this, specify a method with the same name as the method you want to override on the prototype object. The following example overrides dialog's [`open()` method](http://api.jqueryui.com/dialog/#method-open). Since dialogs automatically open by default, `"open"` will be logged when this code runs.
 
 ```
 $.widget( "custom.superDialog", $.ui.dialog, {
diff --git a/page/jquery-ui/widget-factory/how-to-use-the-widget-factory.md b/page/jquery-ui/widget-factory/how-to-use-the-widget-factory.md
index 2841f7b5..60a36f22 100644
--- a/page/jquery-ui/widget-factory/how-to-use-the-widget-factory.md
+++ b/page/jquery-ui/widget-factory/how-to-use-the-widget-factory.md
@@ -1,9 +1,24 @@
----
-title: How To Use the Widget Factory
-level: Beginner
----
+<script>{
+	"title": "How To Use the Widget Factory",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [
+		"jQuery Fundamentals",
+		"Scott González <scott.gonzalez@gmail.com> (http://blog.nemikor.com/2010/05/15/building-stateful-jquery-plugins/)"
+	]
+}</script>
 
-To start, we'll create a progress bar that just lets us set the progress once. As we can see below, this is done by calling `jQuery.widget()` with two parameters: the name of the plugin to create, and an object literal containing functions to support our plugin. When our plugin gets called, it will create a new plugin instance and all functions will be executed within the context of that instance. This is different from a standard jQuery plugin in two important ways. First, the context is an object, not a DOM element. Second, the context is always a single object, never a collection.
+While most existing jQuery plugins are stateless – that is, we call them on an element and that is the extent of our interaction with the plugin – there's a large set of functionality that doesn't fit into the basic plugin pattern.
+
+In order to fill this gap, jQuery UI has implemented a more advanced plugin system. The new system manages state, allows multiple functions to be exposed via a single plugin, and provides various extension points. This system is called the Widget Factory and is exposed as `jQuery.widget` as part of jQuery UI 1.8; however, it can be used independently of jQuery UI.
+
+To demonstrate the capabilities of the Widget Factory, we'll build a simple progress bar plugin.
+
+To start, we'll create a progress bar that just lets us set the progress once. As we can see below, this is done by calling `jQuery.widget()` with two parameters: the name of the plugin to create, and an object literal containing functions to support our plugin.
+
+When our plugin gets called, it will create a new plugin instance and all functions will be executed within the context of that instance. This is different from a standard jQuery plugin in two important ways. First, the context is an object, not a DOM element. Second, the context is always a single object, never a collection.
+
+A simple, stateful plugin using the jQuery UI Widget Factory:
 
 ```
 $.widget( "custom.progressbar", {
@@ -18,15 +33,23 @@ $.widget( "custom.progressbar", {
 
 The name of the plugin must contain a namespace, in this case we've used the `custom` namespace. You can only create namespaces that are one level deep, therefore, `custom.progressbar` is a valid plugin name whereas `very.custom.progressbar` is not.
 
+*Note:* In our example we use the `custom` namespace. The `ui` namespace is reserved for official jQuery UI plugins. When building your own plugins, you should create your own namespace. This makes it clear where the plugin came from and whether it is part of a larger collection.
+
 We can also see that the widget factory has provided two properties for us. `this.element` is a jQuery object containing exactly one element. If our plugin is called on a jQuery object containing multiple elements, a separate plugin instance will be created for each element, and each instance will have its own `this.element`. The second property, `this.options`, is a hash containing key/value pairs for all of our plugin's options. These options can be passed to our plugin as shown here.
 
+Passing options to a widget:
+
 ```
 $( "<div></div>" )
 	.appendTo( "body" )
 	.progressbar({ value: 20 });
 ```
 
-When we call `jQuery.widget()` it extends jQuery by adding a function to `jQuery.fn` (the system for creating a standard plugin). The name of the function it adds is based on the name you pass to `jQuery.widget()`, without the namespace - in our case "progressbar". The options passed to our plugin are the values that get set in `this.options` inside of our plugin instance. As shown below, we can specify default values for any of our options. When designing your API, you should figure out the most common use case for your plugin so that you can set appropriate default values and make all options truly optional.
+When we call `jQuery.widget()` it extends jQuery by adding a method to `jQuery.fn` (the same way we'd create a standard plugin). The name of the function it adds is based on the name you pass to `jQuery.widget()`, without the namespace - in our case it will create `jQuery.fn.progressbar`. The options passed to our plugin are the values that get set in `this.options` inside of our plugin instance.
+
+As shown below, we can specify default values for any of our options. When designing your API, you should figure out the most common use case for your plugin so that you can set appropriate default values and make all options truly optional.
+
+Setting default options for a widget:
 
 ```
 $.widget( "custom.progressbar", {
@@ -44,17 +67,17 @@ $.widget( "custom.progressbar", {
 });
 ```
 
-### Calling Plugin Methods
+### Adding Methods to a Widget
 
 Now that we can initialize our progress bar, we'll add the ability to perform actions by calling methods on our plugin instance. To define a plugin method, we just include the function in the object literal that we pass to `jQuery.widget()`. We can also define "private" methods by prepending an underscore to the function name.
 
+Creating widget methods:
+
 ```
 $.widget( "custom.progressbar", {
-
 	options: {
 		value: 0
 	},
-
 	_create: function() {
 		var progress = this.options.value + "%";
 		this.element
@@ -93,6 +116,8 @@ To call a method on a plugin instance, you pass the name of the method to the jQ
 
 **Note:** Executing methods by passing the method name to the same jQuery function that was used to initialize the plugin may seem odd. This is done to prevent pollution of the jQuery namespace while maintaining the ability to chain method calls. Later in this article we'll see alternative uses that may feel more natural.
 
+Calling methods on a plugin instance:
+
 ```
 var bar = $( "<div></div>" )
 	.appendTo( "body" )
@@ -112,6 +137,8 @@ alert( bar.progressbar( "value" ) );
 
 One of the methods that are automatically available to our plugin is the `option()` method. The `option()` method allows you to get and set options after initialization. This method works exactly like jQuery's `.css()` and `.attr()` methods: You can pass just a name to use it as a getter, a name and value to use it as a single setter, or a hash of name/value pairs to set multiple values. When used as a getter, the plugin will return the current value of the option that corresponds to the name that was passed in. When used as a setter, the plugin's `_setOption` method will be called for each option that is being set. We can specify a `_setOption` method in our plugin to react to option changes. For actions to perform independent of the number of options changed, we can override `_setOptions()`.
 
+Responding when an option is set:
+
 ```
 $.widget( "custom.progressbar", {
 	options: {
@@ -150,7 +177,11 @@ $.widget( "custom.progressbar", {
 
 ### Adding Callbacks
 
-One of the easiest ways to make your plugin extensible is to add callbacks so users can react when the state of your plugin changes. We can see below how to add a callback to our progress bar to signify when the progress has reached 100%. The `_trigger()` method takes three parameters: the name of the callback, a jQuery event object that initiated the callback, and a hash of data relevant to the event. The callback name is the only required parameter, but the others can be very useful for users who want to implement custom functionality on top of your plugin. For example, if we were building a draggable plugin, we could pass the mousemove event when triggering a drag callback; this would allow users to react to the drag based on the x/y coordinates provided by the event object. Note that the original event passed to `_trigger()` must be a jQuery event, not a native browser event.
+One of the easiest ways to make your plugin extensible is to add callbacks so users can react when the state of your plugin changes. We can see below how to add a callback to our progress bar to signify when the progress has reached 100%. The `_trigger()` method takes three parameters: the name of the callback, a jQuery event object that initiated the callback, and a hash of data relevant to the event. The callback name is the only required parameter, but the others can be very useful for users who want to implement custom functionality on top of your plugin. For example, if we were building a draggable plugin, we could pass the mousemove event when triggering a drag callback; this would allow users to react to the drag based on the x/y coordinates provided by the event object.
+
+Note that the event passed to `_trigger()` must be a jQuery event, not a native browser event.
+
+Providing callbacks for user extension:
 
 ```
 $.widget( "custom.progressbar", {
@@ -191,7 +222,11 @@ $.widget( "custom.progressbar", {
 });
 ```
 
-Callback functions are essentially just additional options, so you can get and set them just like any other option. Whenever a callback is executed, a corresponding event is triggered as well. The event type is determined by concatenating the plugin name and the callback name. The callback and event both receive the same two parameters: an event object and a hash of data relevant to the event, as we'll see below. Your plugin may have functionality that you want to allow the user to prevent. The best way to support this is by creating cancelable callbacks. Users can cancel a callback, or its associated event, the same way they cancel any native event, by calling `event.preventDefault()` or returning `false`. If the user cancels the callback, the `_trigger()` method will return `false` so you can implement the appropriate functionality within your plugin.
+Callback functions are essentially just additional options, so you can get and set them just like any other option. Whenever a callback is executed, a corresponding event is triggered as well. The event type is determined by concatenating the plugin name and the callback name. The callback and event both receive the same two parameters: an event object and a hash of data relevant to the event, as we'll see below.
+
+Your plugin may have functionality that you want to allow the user to prevent. The best way to support this is by creating cancelable callbacks. Users can cancel a callback, or its associated event, the same way they cancel any event, by calling `event.preventDefault()` or returning `false`. If the user cancels the callback, the `_trigger()` method will return `false` so you can implement the appropriate functionality within your plugin.
+
+Binding to widget events:
 
 ```
 var bar = $( "<div></div>" )
@@ -211,7 +246,11 @@ bar.progressbar( "option", "value", 100 );
 
 ## Looking Under the Hood
 
-Now that we've seen how to build a plugin using the widget factory, let's take a look at how it actually works. When you call `jQuery.widget()`, it creates a constructor for your plugin and sets the object literal that you pass in as the prototype for your plugin instances. All of the functionality that automatically gets added to your plugin comes from a base widget prototype, which is defined as `jQuery.Widget.prototype`. When a plugin instance is created, it is stored on the original DOM element using `jQuery.data`, with the plugin name as the key.
+Now that we've seen how to build a plugin using the widget factory, let's take a look at how it actually works.
+
+When you call `jQuery.widget()`, it creates a constructor for your plugin and sets the object literal that you pass in as the prototype for your plugin instances. All of the functionality that automatically gets added to your plugin comes from a base widget prototype, which is defined as `jQuery.Widget.prototype`. When a plugin instance is created, it is stored on the original DOM element using `jQuery.data`, with the plugin's full name (the plugin's namespace, plus a hyphen, plus the plugin's name) as the key.
+
+For example the jQuery UI dialog widget uses a key of `"ui-dialog"`.
 
 Because the plugin instance is directly linked to the DOM element, you can access the plugin instance directly instead of going through the exposed plugin method if you want. This will allow you to call methods directly on the plugin instance instead of passing method names as strings and will also give you direct access to the plugin's properties.
 
@@ -253,6 +292,8 @@ For more information on extending widgets, including how to build entirely new w
 
 In some cases, it will make sense to allow users to apply and then later unapply your plugin. You can accomplish this via the `_destroy()` method. Within the `_destroy()` method, you should undo anything your plugin may have done during initialization or later use. `_destroy()` is called by the `destroy()` method, which is automatically called if the element that your plugin instance is tied to is removed from the DOM, so this can be used for garbage collection as well. That base `destroy()` method also handles some general cleanup operations, like removing the instance reference from the widget's DOM element, unbinding all events in the widget's namespace from the element, and unbinding generally all events that were added using `_bind()`.
 
+Adding a destroy method to a widget:
+
 ```
 $.widget( "custom.progressbar", {
 	options: {
@@ -299,6 +340,4 @@ $.widget( "custom.progressbar", {
 
 ## Closing Comments
 
-The widget factory is only one way of creating stateful plugins. There are a few different models that can be used and each have their own advantages and disadvantages. The widget factory solves lots of common problems for you and can greatly improve productivity, it also greatly improves code reuse, making it a great fit for jQuery UI as well as many other stateful plugins.
-
-You may have noticed that in this article we used the `custom` namespace. The `ui` namespace is reserved for official jQuery UI plugins. When building your own plugins, you should create your own namespace. This makes it clear where the plugin came from and if it is part of a larger collection.
+The Widget Factory is only one way of creating stateful plugins. There are a few different models that can be used and each has their own advantages and disadvantages. The Widget Factory solves lots of common problems for you and can greatly improve productivity, it also greatly improves code reuse, making it a great fit for jQuery UI as well as many other stateful plugins.
diff --git a/page/jquery-ui/widget-factory/why-use-the-widget-factory.md b/page/jquery-ui/widget-factory/why-use-the-widget-factory.md
index 601cb56e..37cb9738 100644
--- a/page/jquery-ui/widget-factory/why-use-the-widget-factory.md
+++ b/page/jquery-ui/widget-factory/why-use-the-widget-factory.md
@@ -1,7 +1,7 @@
----
-title: Why Use the Widget Factory?
-level: Beginner
----
+<script>{
+	"title": "Why Use the Widget Factory?",
+	"level": "beginner"
+}</script>
 
 Writing jQuery plugins is as simple as adding a method to `jQuery.prototype` (more commonly seen as `$.fn`) and following some simple conventions like returning `this` for chainability. So why does the widget factory exist? And why is it hundreds of lines of code?
 
diff --git a/page/jquery-ui/widget-factory/widget-method-invocation.md b/page/jquery-ui/widget-factory/widget-method-invocation.md
index 91e9986b..a381272c 100644
--- a/page/jquery-ui/widget-factory/widget-method-invocation.md
+++ b/page/jquery-ui/widget-factory/widget-method-invocation.md
@@ -1,7 +1,7 @@
----
-title: Widget Method Invocation
-level: intermediate
----
+<script>{
+	"title": "Widget Method Invocation",
+	"level": "intermediate"
+}</script>
 
 Widgets created with [the widget factory](/jquery-ui/widget-factory/) use methods to change their state and perform actions after initialization. There are two ways widget methods can be invoked - through the plugin created by the widget factory, or by invoking the method on the element's instance object.
 
diff --git a/page/performance.md b/page/performance.md
index 8c6c4c59..c6828407 100644
--- a/page/performance.md
+++ b/page/performance.md
@@ -1,8 +1,10 @@
----
-title: Performance
-level: intermediate
-customFields:
- -
-    key: "icon"
-    value: "dashboard"
----
+<script>{
+	"title": "Performance",
+	"level": "intermediate",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "dashboard"
+		}
+	]
+}</script>
diff --git a/page/performance/append-outside-loop.md b/page/performance/append-outside-loop.md
index 1831d770..d1adfa1c 100644
--- a/page/performance/append-outside-loop.md
+++ b/page/performance/append-outside-loop.md
@@ -1,10 +1,9 @@
----
-title:        Append Outside of Loops
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Append Outside of Loops",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 Touching the DOM comes at a cost. If you're appending a lot of elements to the DOM, you will want to append them all at once, rather than one at a time. This is a common problem when appending elements within a loop.
 
diff --git a/page/performance/cache-loop-length.md b/page/performance/cache-loop-length.md
index c9000ff9..05cc6269 100644
--- a/page/performance/cache-loop-length.md
+++ b/page/performance/cache-loop-length.md
@@ -1,10 +1,9 @@
----
-title:        Cache Length During Loops
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Cache Length During Loops",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 In a for loop, don't access the length property of an array every time; cache it beforehand.
 
diff --git a/page/performance/detach-elements-before-work-with-them.md b/page/performance/detach-elements-before-work-with-them.md
index 6af2e3d5..6431b27b 100644
--- a/page/performance/detach-elements-before-work-with-them.md
+++ b/page/performance/detach-elements-before-work-with-them.md
@@ -1,10 +1,9 @@
----
-title:        Detach Elements to Work with Them
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Detach Elements to Work with Them",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 The DOM is slow; you want to avoid manipulating it as much as possible. jQuery introduced `detach()` in version 1.4 to help address this issue, allowing you to remove an element from the DOM while you work with it.
 
diff --git a/page/performance/dont-act-on-absent-elements.md b/page/performance/dont-act-on-absent-elements.md
index 306ac813..5f6bcdcd 100644
--- a/page/performance/dont-act-on-absent-elements.md
+++ b/page/performance/dont-act-on-absent-elements.md
@@ -1,10 +1,9 @@
----
-title:        Don't Act on Absent Elements
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Don't Act on Absent Elements",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 jQuery won't tell you if you're trying to run a whole lot of code on an empty selection – it will proceed as though nothing's wrong. It's up to you to verify that your selection contains some elements.
 
diff --git a/page/performance/optimize-selectors.md b/page/performance/optimize-selectors.md
index 93ad6a0c..45304b9e 100644
--- a/page/performance/optimize-selectors.md
+++ b/page/performance/optimize-selectors.md
@@ -1,41 +1,38 @@
----
-title:        Optimize Selectors
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Optimize Selectors",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
-Selector optimization is less important than it used to be, as more browsers implement `document.querySelectorAll()` and the burden of selection shifts from jQuery to the browser. However, there are still some tips to keep in mind.
+Selector optimization is less important than it used to be, as more browsers implement `document.querySelectorAll()` and the burden of selection shifts from jQuery to the browser. However, there are still some tips to keep in mind when selector performance becomes a bottleneck.
 
-## ID-Based Selectors
+## jQuery Extensions
 
-Beginning your selector with an ID is always best.
+When possible, avoid selectors that include [jQuery extensions](https://api.jquery.com/category/selectors/jquery-selector-extensions/). These extensions cannot take advantage of the performance boost provided by the native `querySelectorAll()` DOM method and, therefore, require the use of the Sizzle selector engine provided by jQuery.
 
 ```
-// Fast:
-$( "#container div.robotarm" );
+// Slower (the zero-based :even selector is a jQuery extension)
+$( "#my-table tr:even" );
 
-// Super-fast:
-$( "#container" ).find( "div.robotarm" );
+// Better, though not exactly equivalent
+$( "#my-table tr:nth-child(odd)" );
 ```
 
-The `.find()` approach is faster because the first selection is handled without going through the Sizzle selector engine – ID-only selections are handled using `document.getElementById()`, which is extremely fast because it is native to the browser.
+Keep in mind that many jQuery extensions, including `:even` in the above example, do not have exact equivalents in the CSS specification. In some situations the convenience of these extensions could outweigh their performance cost.
 
-## Specificity
+## Try to segregate the nonstandard parts of your selection
 
-Be specific on the right-hand side of your selector, and less specific on the left.
+When you select elements, jQuery will call `querySelectorAll` with your selection. If `querySelectorAll` throws an error, jQuery will refer to its Sizzle engine. So, if you are using at least one of the nonstandard pseudo-classes such as `:contains()`, `:has`, `:even`, `:submit`, etc. You will not take advantage of the native `querySelectorAll`.
 
 ```
-// Unoptimized:
-$( "div.data .gonzalez" );
+// A long selection with nonstandard pseudo-classes inside
+$( "#global.ready .part .list li a:contains('qwerty'):first" );
 
-// Optimized:
-$( ".data td.gonzalez" );
+// A long standard selection with a filter outside (faster)
+$( "#global.ready .part .list li a").filter( ":contains('qwerty'):first" );
 ```
 
-Use `tag.class` if possible on your right-most selector, and just tag or just `.class` on the left.
-
 ## Avoid Excessive Specificity
 
 ```
@@ -47,15 +44,43 @@ $( ".data td.gonzalez" );
 
 A "flatter" DOM also helps improve selector performance, as the selector engine has fewer layers to traverse when looking for an element.
 
-## Avoid the Universal Selector
+## Save calls to `querySelectorAll`
 
-Selections that specify or imply that a match could be found anywhere can be very slow.
+`querySelectorAll` is already really fast, if you want maintain this speed try to call it the least possible.
 
 ```
-$( ".buttons > *" ); // Extremely expensive.
-$( ".buttons" ).children(); // Much better.
+// If in your HTML there are 2 .container with 5 div in each,
+// this line will call querySelectorAll 13 times (1 + 2 + 2*5).
+$( ".container" ).children( "div" ).find( ".robotarm" );
+
+// Against only 1 call with this:
+$( ".container div .robotarm" );
+```
+
+## Tips for Older Browsers
+
+When support for older browsers, such as Internet Explorer 8 and below, is necessary, consider the following tips:
+
+### Specificity
+
+Be specific on the right-hand side of your selector, and less specific on the left.
 
-$( ".category :radio" ); // Implied universal selection.
-$( ".category *:radio" ); // Same thing, explicit now.
-$( ".category input:radio" ); // Much better.
+```
+// Unoptimized:
+$( "div.data .gonzalez" );
+
+// Optimized:
+$( ".data td.gonzalez" );
+```
+
+Use `tag.class` if possible on your right-most selector, and just tag or just `.class` on the left.
+
+### Avoid the Universal Selector
+
+Selections that specify or imply that a match could be found anywhere can be very slow.
+
+```
+$( ":radio" ); // Implied universal selection.
+$( "*:radio" ); // Same thing, explicit now.
+$( "input:radio" ); // Much better.
 ```
diff --git a/page/performance/read-the-source.md b/page/performance/read-the-source.md
index f7fc894e..e7547d23 100644
--- a/page/performance/read-the-source.md
+++ b/page/performance/read-the-source.md
@@ -1,10 +1,8 @@
----
-title:        Don't Treat jQuery as a Black Box
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Don't Treat jQuery as a Black Box",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
-Use the source as your documentation. Bookmark
-[http://bit.ly/jqsource](http://bit.ly/jqsource) and refer to it often.
+Use the source as your documentation. Bookmark [the source code](https://releases.jquery.com/jquery/) and refer to it often.
diff --git a/page/performance/use-stylesheets-for-changing-css.md b/page/performance/use-stylesheets-for-changing-css.md
index 5018a62f..7cffe961 100644
--- a/page/performance/use-stylesheets-for-changing-css.md
+++ b/page/performance/use-stylesheets-for-changing-css.md
@@ -1,10 +1,9 @@
----
-title:        Use Stylesheets for Changing CSS on Many Elements
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Use Stylesheets for Changing CSS on Many Elements",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 If you're changing the CSS of more than 20 elements using `.css()`, consider adding a style tag to the page instead for a nearly 60% increase in speed.
 
diff --git a/page/plugins.md b/page/plugins.md
index a1075371..e0a92b9f 100644
--- a/page/plugins.md
+++ b/page/plugins.md
@@ -1,14 +1,18 @@
----
-title: Plugins
-level: intermediate
-customFields:
- -
-    key: "icon"
-    value: "bolt"
----
+<script>{
+	"title": "Plugins",
+	"level": "intermediate",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "bolt"
+		}
+	]
+}</script>
 
 A jQuery plugin is simply a new method that we use to extend jQuery's prototype object. By extending the prototype object you enable all jQuery objects to inherit any methods that you add. As established, whenever you call `jQuery()` you're creating a new jQuery object, with all of jQuery's methods inherited.
 
 The idea of a plugin is to do something with a collection of elements. You could consider each method that comes with the jQuery core a plugin, like `.fadeOut()` or `.addClass()`.
 
 You can make your own plugins and use them privately in your code or you can release them into the wild. There are thousands of jQuery plugins available online. The barrier to creating a plugin of your own is so low that you'll want to do it straight away!
+
+For details on how to create jQuery UI plugins via the Widget Factory, refer to [How To Use the Widget Factory](/jquery-ui/widget-factory/how-to-use-the-widget-factory/).
diff --git a/page/plugins/advanced-plugin-concepts.md b/page/plugins/advanced-plugin-concepts.md
index 2bf990ce..84826df2 100644
--- a/page/plugins/advanced-plugin-concepts.md
+++ b/page/plugins/advanced-plugin-concepts.md
@@ -1,7 +1,7 @@
----
-title: Advanced Plugin Concepts
-level: intermediate
----
+<script>{
+	"title": "Advanced Plugin Concepts",
+	"level": "intermediate"
+}</script>
 
 ### Provide Public Access to Default Plugin Settings
 
@@ -240,16 +240,21 @@ A bad implementation:
 
 ```
 // Plugin code
-$( "<div id=\"the-gallery-wrapper\" />").appendTo( "body" );
+$( "<div class='gallery-wrapper' />" ).appendTo( "body" );
 
-$( "#the-gallery-wrapper" ).append( "..." );
+$( ".gallery-wrapper" ).append( "..." );
+```
+
+To allow users to access and even manipulate that information, you can store it in a variable containing the settings of your plugin. A better implementation of the previous code is shown below:
 
+```
 // Retain an internal reference:
 var wrapper = $( "<div />" )
 	.attr( settings.wrapperAttrs )
 	.appendTo( settings.container );
 
-wrapper.append( "..." ); // Easy to reference later...
+// Easy to reference later...
+wrapper.append( "..." );
 ```
 
 Notice that we've created a reference to the injected wrapper and we're also calling the `.attr()` method to add any specified attributes to the element. So, in our settings it might be handled like this:
@@ -257,7 +262,7 @@ Notice that we've created a reference to the injected wrapper and we're also cal
 ```
 var defaults = {
 	wrapperAttrs : {
-		id: "gallery-wrapper"
+		class: "gallery-wrapper"
 	},
 	// ... rest of settings ...
 };
@@ -311,14 +316,17 @@ nextButton.on( "click", showNextImage );
 
 function showNextImage() {
 
+	// Returns reference to the next image node
+	var image = getNextImage();
+
 	// Stuff to show the image here...
 
 	// Here's the callback:
-	settings.onImageShow.call( this );
+	settings.onImageShow.call( image );
 }
 ```
 
-Instead of initiating the callback via traditional means (adding parenthesis) we're calling it in the context of `this` which will be a reference to the image node. This means that you have access to the actual image node through the `this` keyword within the callback:
+Instead of initiating the callback via traditional means (adding parenthesis) we're calling it in the context of `image` which will be a reference to the image node. This means that you have access to the actual image node through the `this` keyword within the callback:
 
 ```
 $( "ul.imgs li" ).superGallery({
diff --git a/page/plugins/basic-plugin-creation.md b/page/plugins/basic-plugin-creation.md
index 529e1f22..a186f2cc 100644
--- a/page/plugins/basic-plugin-creation.md
+++ b/page/plugins/basic-plugin-creation.md
@@ -1,14 +1,13 @@
----
-title   : How to Create a Basic Plugin
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "How to Create a Basic Plugin",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
-Sometimes you want to make a piece of functionality available throughout your code. For example, perhaps you want a single method you can call on a jQuery selection that performs a series of operations on the selection. Maybe you wrote a really useful utility function that you want to be able to move easily to other projects. In this case, you may want to write a plugin.
+Sometimes you want to make a piece of functionality available throughout your code. For example, perhaps you want a single method you can call on a jQuery selection that performs a series of operations on the selection. In this case, you may want to write a plugin.
 
-## How jQuery Works 101: jQuery Object Methods and Utility Methods
+## How jQuery Works 101: jQuery Object Methods
 
 Before we write our own plugins, we must first understand a little about how jQuery works. Take a look at this code:
 
@@ -18,8 +17,6 @@ $( "a" ).css( "color", "red" );
 
 This is some pretty basic jQuery code, but do you know what's happening behind the scenes? Whenever you use the `$` function to select elements, it returns a jQuery object. This object contains all of the methods you've been using (`.css()`, `.click()`, etc.) and all of the elements that fit your selector. The jQuery object gets these methods from the `$.fn` object. This object contains all of the jQuery object methods, and if we want to write our own methods, it will need to contain those as well.
 
-Additionally the jQuery utility method `$.trim()` is used above to remove any leading or trailing empty space characters from the user input. Utility methods are functions that reside directly in the `$` function itself. You may occasionally want to write a utility method plugin when your extension to the jQuery API does not have to do something to a set of DOM elements you've retrieved.
-
 ## Basic Plugin Authoring
 
 Let's say we want to create a plugin that makes text within a set of retrieved elements green. All we have to do is add a function called `greenify` to `$.fn` and it will be available just like any other jQuery object method.
@@ -36,7 +33,7 @@ Notice that to use `.css()`, another method, we use `this`, not `$( this )`. Thi
 
 ## Chaining
 
-This works, but there's a couple of things we need to do for our plugin to survive in the real world. One of jQuery's features is chaining, when you link five or six actions onto one selector. This is accomplished by having all jQuery object methods return the original jQuery object again (there are a few exceptions: `.width()` called without parameters returns the width of the selected element, and is not chainable). Making our plugin method chainable takes one line of code:
+This works, but there are a couple of things we need to do for our plugin to survive in the real world. One of jQuery's features is chaining, when you link five or six actions onto one selector. This is accomplished by having all jQuery object methods return the original jQuery object again (there are a few exceptions: `.width()` called without parameters returns the width of the selected element, and is not chainable). Making our plugin method chainable takes one line of code:
 
 ```
 $.fn.greenify = function() {
@@ -47,11 +44,9 @@ $.fn.greenify = function() {
 $( "a" ).greenify().addClass( "greenified" );
 ```
 
-Note that the notion of chaining is *not* applicable to jQuery utility methods like `$.trim()`.
-
 ## Protecting the $ Alias and Adding Scope
 
-The `$` variable is very popular among JavaScript libraries, and if you're using another library with jQuery, you will have to make jQuery not use the `$` with `jQuery.noConflict()`. However, this will break our plugin since it is written with the assumption that `$` is an alias to the `jQuery` function. To work well with other plugins, _and_ still use the jQuery `$` alias, we need to put all of our code inside of an [Immediately Invoked Function Expression](http://stage.learn.jquery.com/javascript-101/functions/#immediately-invoked-function-expression-iife), and then pass the function `jQuery`, and name the parameter `$`:
+The `$` variable is very popular among JavaScript libraries, and if you're using another library with jQuery, you will have to make jQuery not use the `$` with `jQuery.noConflict()`. However, this will break our plugin since it is written with the assumption that `$` is an alias to the `jQuery` function. To work well with other plugins, _and_ still use the jQuery `$` alias, we need to put all of our code inside of an [Immediately Invoked Function Expression](http://benalman.com/news/2010/11/immediately-invoked-function-expression/), and then pass the function `jQuery`, and name the parameter `$`:
 
 ```
 (function ( $ ) {
@@ -61,14 +56,6 @@ The `$` variable is very popular among JavaScript libraries, and if you're using
 		return this;
 	};
 
-	$.ltrim = function( str ) {
-		return str.replace( /^\s+/, "" );
-	};
-
-	$.rtrim = function( str ) {
-		return str.replace( /\s+$/, "" );
-	};
-
 }( jQuery ));
 ```
 
diff --git a/page/plugins/finding-evaluating-plugins.md b/page/plugins/finding-evaluating-plugins.md
index ea1c221a..266176ac 100644
--- a/page/plugins/finding-evaluating-plugins.md
+++ b/page/plugins/finding-evaluating-plugins.md
@@ -1,10 +1,9 @@
----
-title   : Finding & Evaluating Plugins
-level:        intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Finding & Evaluating Plugins",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 One of the most celebrated aspects of jQuery is its extensive plugin ecosystem. From table sorting to form validation to autocompletion – if there's a need for it, chances are good that someone has written a plugin for it.
 
@@ -12,6 +11,6 @@ The quality of jQuery plugins varies widely. Many plugins are extensively tested
 
 The easiest way to find plugins is to search Google or the [jQuery Plugins Registry](http://plugins.jquery.com/). Once you've identified some options, you may want to consult the [jQuery forums](http://forum.jquery.com/) or the `#jquery` IRC channel to get input from others.
 
-When looking for a plugin to fill a need, do your homework. Ensure that the plugin is well-documented, and look for the author to provide lots of examples of its use. Be wary of plugins that do far more than you need; they can end up adding substantial overhead to your page. For more tips on spotting a sub-par plugin, read [Signs of a poorly written jQuery plugin](http://remysharp.com/2010/06/03/signs-of-a-poorly-written-jquery-plugin/) by Remy Sharp.
+When looking for a plugin to fill a need, do your homework. Ensure that the plugin is well-documented, and look for the author to provide lots of examples of its use. Be wary of plugins that do far more than you need; they can end up adding substantial overhead to your page. For more tips on spotting a sub-par plugin, read [Signs of a poorly written jQuery plugin](https://remysharp.com/2010/06/03/signs-of-a-poorly-written-jquery-plugin/) by Remy Sharp.
 
-Once you choose a plugin, you'll need to add it to your page. Download the plugin, unzip it if necessary, place it your application's directory structure, then include the plugin in your page using a script tag (after you include jQuery).
+Once you choose a plugin, you'll need to add it to your page. Download the plugin, unzip it if necessary, place it within your application's directory structure, then include the plugin in your page using a script tag (after you include jQuery).
diff --git a/page/plugins/publishing-plugins.md b/page/plugins/publishing-plugins.md
new file mode 100644
index 00000000..4649f28b
--- /dev/null
+++ b/page/plugins/publishing-plugins.md
@@ -0,0 +1,83 @@
+<script>{
+	"title": "Publishing jQuery Plugins to npm",
+	"level": "intermediate"
+}</script>
+
+Publishing jQuery plugins to npm involves several steps to ensure that your plugin is properly packaged, documented, and easily installable for other developers. Here's a step-by-step guide on how to publish your jQuery plugin to npm:
+
+### 1\. Create Your jQuery Plugin
+
+Write your jQuery plugin code and make sure it follows best practices. Include comments to explain the functionality, parameters, and usage of your plugin. Test your plugin thoroughly to ensure it works as expected.
+
+### 2\. package.json
+
+Create a `package.json` file in the root directory of your plugin project. This file contains metadata about your plugin and its dependencies. Here's a basic example:
+
+```json
+{
+	"name": "your-plugin-name",
+	"version": "1.0.0",
+	"description": "Description of your jQuery plugin",
+	"main": "path-to-main-file.js",
+	"keywords": ["jquery", "jquery-plugin", "ecosystem:jquery"],
+	"author": "Your Name",
+	"license": "MIT",
+	"repository": {
+		"type": "git",
+		"url": "https://github.com/yourusername/your-plugin-name.git"
+	},
+	"bugs": {
+		"url": "https://github.com/yourusername/your-plugin-name/issues"
+	},
+	"homepage": "https://github.com/yourusername/your-plugin-name#readme",
+	"peerDependencies": {
+		"jquery": ">=3.5"
+	}
+}
+```
+
+Make sure to replace `"your-plugin-name"`, `"Description of your jQuery plugin"`, `"Your Name"`, `"https://github.com/yourusername/your-plugin-name.git"`, and other fields with appropriate values.
+
+The `"jquery-plugin"` and `"ecosystem:jquery"` are recommended keywords to help other developers find your plugin on npm.
+
+### 3\. Publish to npm
+
+#### 3\.1\. Create an npm Account
+
+If you haven't already, create an account on [npmjs.com](https://www.npmjs.com/signup).
+
+#### 3\.2\. Log in to npm
+
+In your terminal, log in to npm using the command:
+
+```sh
+npm login
+```
+
+Enter your username, password, and email when prompted.
+
+#### 3\.3\. Publish Your Package
+
+Navigate to the root directory of your plugin project and run:
+
+```sh
+npm publish
+```
+
+This command will package your plugin and publish it to the npm registry. For more details, refer to the [official npm documentation](https://docs.npmjs.com/cli/commands/npm-publish).
+
+### 4\. Documentation
+
+Ensure your plugin has comprehensive documentation. You can create a `README.md` file in the root directory of your project, detailing installation instructions, usage examples, API documentation, and any other relevant information.
+
+### 5\. Versioning
+
+Follow [semantic versioning (SemVer)](https://docs.npmjs.com/about-semantic-versioning) principles when updating your plugin. Increment the version number in your `package.json` file accordingly with each release.
+
+### 6\. Maintenance
+
+Regularly maintain and update your plugin to address issues, add features, and stay compatible with the latest jQuery versions.
+
+### Conclusion
+
+By following these steps, you can successfully publish your jQuery plugin to npm, making it easily accessible to other developers. Remember to keep your plugin well-documented, well-tested, and up-to-date to ensure its usefulness and usability within the developer community.
diff --git a/page/plugins/stateful-plugins-with-widget-factory.md b/page/plugins/stateful-plugins-with-widget-factory.md
deleted file mode 100644
index e3e2e3ef..00000000
--- a/page/plugins/stateful-plugins-with-widget-factory.md
+++ /dev/null
@@ -1,302 +0,0 @@
----
-title: Writing Stateful Plugins with the jQuery UI Widget Factory
-level: intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
-  - Scott González <scott.gonzalez@gmail.com>
----
-
-## Writing Stateful Plugins with the jQuery UI Widget Factory
-
-While most existing jQuery plugins are stateless – that is, we call them on an element and that is the extent of our interaction with the plugin – there's a large set of functionality that doesn't fit into the basic plugin pattern.
-
-In order to fill this gap, jQuery UI has implemented a more advanced plugin system. The new system manages state, allows multiple functions to be exposed via a single plugin, and provides various extension points. This system is called the Widget Factory and is exposed as `jQuery.widget` as part of jQuery UI 1.8; however, it can be used independently of jQuery UI.
-
-To demonstrate the capabilities of the Widget Factory, we'll build a simple progress bar plugin.
-
-To start, we'll create a progress bar that just lets us set the progress once. As we can see below, this is done by calling `jQuery.widget` with two parameters: the name of the plugin to create and an object literal containing functions to support our plugin.
-
-When our plugin gets called, it will create a new plugin instance and all functions will be executed within the context of that instance. This is different from a standard jQuery plugin in two important ways. First, the context is an object, not a DOM element. Second, the context is always a single object, never a collection.
-
-A simple, stateful plugin using the jQuery UI Widget Factory:
-
-```
-$.widget( "nmk.progressbar", {
-
-	_create: function() {
-		var progress = this.options.value + "%";
-		this.element.addClass( "progressbar" ).text( progress );
-	}
-
-});
-```
-
-The name of the plugin must contain a namespace; in this case we've used the `nmk` namespace. There is a limitation that namespaces be exactly one level deep – that is, we can't use a namespace like `nmk.foo`. We can also see that the Widget Factory has provided two properties for us. `this.element` is a jQuery object containing exactly one element. If our plugin is called on a jQuery object containing multiple elements, a separate plugin instance will be created for each element, and each instance will have its own `this.element`. The second property, `this.options`, is a hash containing key/value pairs for all of our plugin's options. These options can be passed to our plugin as shown here.
-
-*Note:* In our example we use the `nmk` namespace. The `ui` namespace is reserved for official jQuery UI plugins. When building your own plugins, you should create your own namespace. This makes it clear where the plugin came from and whether it is part of a larger collection.
-
-Passing options to a widget:
-
-```
-$( "<div />" ).appendTo( "body" ).progressbar({ value: 20 });
-```
-
-When we call `jQuery.widget` it extends jQuery by adding a method to `jQuery.fn` (the same way we'd create a standard plugin). The name of the function it adds is based on the name you pass to `jQuery.widget`, without the namespace; in our case it will create `jQuery.fn.progressbar`. The options passed to our plugin get set in `this.options` inside of our plugin instance.
-
-As shown below, we can specify default values for any of our options. When designing your API, you should figure out the most common use case for your plugin so that you can set appropriate default values and make all options truly optional.
-
-
-Setting default options for a widget:
-
-```
-
-$.widget( "nmk.progressbar", {
-
-	// Default options.
-	options: {
-		value: 0
-	},
-
-	_create: function() {
-		var progress = this.options.value + "%";
-		this.element.addClass( "progressbar" ).text( progress );
-	}
-
-});
-```
-
-### Adding Methods to a Widget
-
-Now that we can initialize our progress bar, we'll add the ability to perform actions by calling methods on our plugin instance. To define a plugin method, we just include the function in the object literal that we pass to `jQuery.widget`. We can also define "private" methods by prepending an underscore to the function name.
-
-Creating widget methods:
-
-```
-$.widget( "nmk.progressbar", {
-	options: {
-		value: 0
-	},
-
-	_create: function() {
-		var progress = this.options.value + "%";
-		this.element.addClass("progressbar").text( progress );
-	},
-
-	// Create a public method.
-	value: function( value ) {
-
-		// No value passed, act as a getter.
-		if ( value === undefined ) {
-
-			return this.options.value;
-
-		// Value passed, act as a setter.
-		} else {
-
-			this.options.value = this._constrain( value );
-			var progress = this.options.value + "%";
-			this.element.text( progress );
-
-		}
-
-	},
-
-	// Create a private method.
-	_constrain: function( value ) {
-
-		if ( value > 100 ) {
-			value = 100;
-		}
-
-		if ( value < 0 ) {
-			value = 0;
-		}
-
-		return value;
-	}
-
-});
-```
-
-To call a method on a plugin instance, you pass the name of the method to the jQuery plugin. If you are calling a method that accepts parameters, you simply pass those parameters after the method name.
-
-Calling methods on a plugin instance:
-
-```
-var bar = $( "<div />" ).appendTo( "body").progressbar({ value: 20 });
-
-// Get the current value.
-alert( bar.progressbar( "value" ) );
-
-// Update the value.
-bar.progressbar( "value", 50 );
-
-// Get the current value again.
-alert( bar.progressbar( "value" ) );
-```
-
-*Note:* Executing methods by passing the method name to the same jQuery function that was used to initialize the plugin may seem odd. This is done to prevent pollution of the jQuery namespace while maintaining the ability to chain method calls.
-
-### Working with Widget Options
-
-One of the methods that is automatically available to our plugin is the option method. The option method allows you to get and set options after initialization. This method works exactly like jQuery's `.css()` and `.attr()` methods: you can pass just a name to use it as a getter, a name and value to use it as a single setter, or a hash of name/value pairs to set multiple values. When used as a getter, the plugin will return the current value of the option that corresponds to the name that was passed in. When used as a setter, the plugin's `_setOption` method will be called for each option that is being set. We can specify a `_setOption` method in our plugin to react to option changes.
-
-Responding when an option is set:
-
-```
-$.widget( "nmk.progressbar", {
-
-	options: {
-		value: 0
-	},
-
-	_create: function() {
-		this.element.addClass( "progressbar" );
-		this._update();
-	},
-
-	_setOption: function( key, value ) {
-		this.options[ key ] = value;
-		this._update();
-	},
-
-	_update: function() {
-		var progress = this.options.value + "%";
-		this.element.text( progress );
-	}
-
-});
-```
-
-### Adding Callbacks
-
-One of the easiest ways to make your plugin extensible is to add callbacks so users can react when the state of your plugin changes. We can see below how to add a callback to our progress bar to signify when the progress has reached 100%. The `_trigger` method takes three parameters: the name of the callback, a native event object that initiated the callback, and a hash of data relevant to the event. The callback name is the only required parameter, but the others can be very useful for users who want to implement custom functionality on top of your plugin. For example, if we were building a draggable plugin, we could pass the native mousemove event when triggering a drag callback; this would allow users to react to the drag based on the x/y coordinates provided by the event object.
-
-Providing callbacks for user extension:
-
-```
-$.widget( "nmk.progressbar", {
-
-	options: {
-		value: 0
-	},
-
-	_create: function() {
-		this.element.addClass( "progressbar" );
-		this._update();
-	},
-
-	_setOption: function( key, value ) {
-		this.options[ key ] = value;
-		this._update();
-	},
-
-	_update: function() {
-		var progress = this.options.value + "%";
-		this.element.text( progress );
-		if ( this.options.value == 100 ) {
-			this._trigger( "complete", null, { value: 100 } );
-		}
-	}
-
-});
-```
-
-Callback functions are essentially just additional options, so you can get and set them just like any other option. Whenever a callback is executed, a corresponding event is triggered as well. The event type is determined by concatenating the plugin name and the callback name. The callback and event both receive the same two parameters: an event object and a hash of data relevant to the event, as we'll see below.
-
-If your plugin has functionality that you want to allow the user to prevent, the best way to support this is by creating cancelable callbacks. Users can cancel a callback, or its associated event, the same way they cancel any native event: by calling `event.preventDefault()` or using `return false`. If the user cancels the callback, the `_trigger` method will return false so you can implement the appropriate functionality within your plugin.
-
-Binding to widget events:
-
-```
-var bar = $( "<div />" ).appendTo( "body" ).progressbar({
-
-	complete: function( event, data ) {
-		alert( "Callbacks are great!" );
-	}
-
-}).bind( "progressbarcomplete", function( event, data ) {
-
- 	alert( "Events bubble and support many handlers for extreme flexibility." );
-
- 	alert( "The progress bar value is " + data.value );
-
-});
-
-bar.progressbar( "option", "value", 100 );
-```
-
-### The Widget Factory: Under the Hood
-
-When you call `jQuery.widget`, it creates a constructor function for your plugin and sets the object literal that you pass in as the prototype for your plugin instances. All of the functionality that automatically gets added to your plugin comes from a base widget prototype, which is defined as `jQuery.Widget.prototype`. When a plugin instance is created, it is stored on the original DOM element using `jQuery.data`, with the plugin name as the key.
-
-Because the plugin instance is directly linked to the DOM element, you can access the plugin instance directly instead of going through the exposed plugin method if you want. This will allow you to call methods directly on the plugin instance instead of passing method names as strings and will also give you direct access to the plugin's properties.
-
-```
-var bar = $( "<div />")
-	.appendTo( "body" )
-	.progressbar()
-	.data( "progressbar" );
-
-// Call a method directly on the plugin instance.
-bar.option( "value", 50 );
-
-// Access properties on the plugin instance.
-alert( bar.options.value );
-```
-
-One of the biggest benefits of having a constructor and prototype for a plugin is the ease of extending the plugin. By adding or modifying methods on the plugin's prototype, we can modify the behavior of all instances of our plugin. For example, if we wanted to add a method to our progress bar to reset the progress to 0% we could add this method to the prototype and it would instantly be available to be called on any plugin instance.
-
-```
-$.nmk.progressbar.prototype.reset = function() {
-	this._setOption( "value", 0 );
-};
-```
-
-### Cleaning Up
-
-In some cases, it will make sense to allow users to apply and then later unapply your plugin. You can accomplish this via the `destroy` method. Within the `destroy` method, you should undo anything your plugin may have done during initialization or later use. The `destroy` method is automatically called if the element that your plugin instance is tied to is removed from the DOM, so this can be used for garbage collection as well. The default `destroy` method removes the link between the DOM element and the plugin instance, so it's important to call the base function from your plugin's `destroy` method.
-
-Adding a destroy method to a widget:
-
-```
-$.widget( "nmk.progressbar", {
-
-	options: {
-		value: 0
-	},
-
-	_create: function() {
-		this.element.addClass("progressbar");
-		this._update();
-	},
-
-	_setOption: function( key, value ) {
-		this.options[ key ] = value;
-		this._update();
-	},
-
-	_update: function() {
-		var progress = this.options.value + "%";
-		this.element.text( progress );
-		if ( this.options.value === 100 ) {
-			this._trigger( "complete", null, { value: 100 } );
-		}
-	},
-
-	destroy: function() {
-		this.element
-			.removeClass( "progressbar" )
-			.text( "" );
-
-		// Call the base destroy function.
-		$.Widget.prototype.destroy.call( this );
-	}
-
-});
-```
-
-### Conclusion
-
-The Widget Factory is only one way of creating stateful plugins. There are a few different models that can be used and each have their own advantages and disadvantages. The Widget Factory solves lots of common problems for you and can greatly improve productivity, it also greatly improves code reuse, making it a great fit for jQuery UI as well as many other stateful plugins.
diff --git a/page/style-guide.md b/page/style-guide.md
index b646cb40..7f16ca74 100644
--- a/page/style-guide.md
+++ b/page/style-guide.md
@@ -1,37 +1,39 @@
----
-title: Style Guide
-attribution:
-  - jorydotcom <jory@bocoup.com>
-customFields:
-  -
-    key: "is_chapter"
-    value: 0
----
+<script>{
+	"title": "Style Guide",
+	"attribution": [ "jorydotcom <jory@bocoup.com>" ],
+	"customFields": [
+		{
+			"key": "is_chapter",
+			"value": 0
+		}
+	]
+}</script>
 
 ## Formatting Conventions
 
-Articles in the learn site are authored with [GitHub Flavored Markdown](http://github.github.com/github-flavored-markdown/), and the beginning of each article contains some [YAML](http://www.yaml.org/) "front matter" that contains metadata used when the article is published.
+Articles in the learn site are authored with [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/), and the beginning of each article contains some JSON "front matter" that contains metadata used when the article is published.
 
 ### Article Header Metadata
 
 Each article should have the following header (see below as some metatags are optional):
 
 ```
----
-title:  <article title>
-level:  [beginner|intermediate|advance]
-source:  <url of source of the material derived>
-attribution:
-  - Ralph Whitbeck <ralph@email.com>
-  - John Paul <john@email.com>
----
+<script>{
+	"title": <article title>,
+	"level": [beginner|intermediate|advance],
+	"source": <url of source of the material derived>,
+	"attribution": [
+		"Ralph Whitbeck <ralph@email.com>",
+		"John Paul <john@email.com>"
+	]
+}</script>
 ```
 
-The `source` and `attribution` properties are optional, and should be used primarily if you are importing an article from an outside source where it was published before being donated for inclusion in the learn site. You should **not** include these properties if you are adding a new article or editing an existing one, as your contribution will be acknowledged via the git commit logs.
+The `source` and `attribution` properties are optional, and should be used primarily if you are importing an article from an outside source where it was published before being donated for inclusion in the learn site. You should **not** include these properties if you are writing a new article or editing an existing one.
 
 ### Code Blocks
 
-Code blocks should be set off with triple backticks and should **not** be indented. (That is to say, the site prefers the use of "fenced blocks"notation supported by [gfm](http://github.github.com/github-flavored-markdown/).)
+Code blocks should be set off with triple backticks and should **not** be indented. (That is to say, the site prefers the use of "fenced blocks" notation supported by [gfm](http://github.github.com/github-flavored-markdown/).)
 
 ## Writing Style
 
@@ -58,7 +60,7 @@ Content should be educational and accessible to a broad audience of developers.
 #### Article & Sentence Structure
 
 - Use headings to break up content into easier-to-read sections. Begin headings within an article with `<h2>`.
-- Keep sentences short and to the point. A good rule-of-thumb is to break up any sentence longer than 21 words into two or more seperate thoughts.
+- Keep sentences short and to the point. A good rule-of-thumb is to break up any sentence longer than 21 words into two or more separate thoughts.
 - Lists:
 	- Use bulleted lists when necessary to share a series of five or more points.
 	- Use numbered lists only when providing step-by-step instruction – note that this should be avoided.
@@ -104,7 +106,7 @@ Content should be educational and accessible to a broad audience of developers.
 - Link to the jQuery blog or API documentation when necessary.
 - Use inline hyperlinks to reference relevant content.
 - Acceptable external resources:
-	- [Mozilla Developer Network](https://developer.mozilla.org/)
+	- [Mozilla Developer Network](https://developer.mozilla.org/en-US/)
 	- [Webplatform.org](http://www.webplatform.org/)
 	- [htmldog.com](http://www.htmldog.com/)
 
diff --git a/page/using-jquery-core.md b/page/using-jquery-core.md
index aa925283..2080731a 100644
--- a/page/using-jquery-core.md
+++ b/page/using-jquery-core.md
@@ -1,8 +1,10 @@
----
-title: Using jQuery Core
-level: beginner
-customFields:
- -
-    key: "icon"
-    value: "star-empty"
----
+<script>{
+	"title": "Using jQuery Core",
+	"level": "beginner",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "star-empty"
+		}
+	]
+}</script>
diff --git a/page/using-jquery-core/attributes.md b/page/using-jquery-core/attributes.md
index 2b30ddc6..0094e4ac 100644
--- a/page/using-jquery-core/attributes.md
+++ b/page/using-jquery-core/attributes.md
@@ -1,7 +1,7 @@
----
-title   : Attributes
-level   : beginner
----
+<script>{
+	"title": "Attributes",
+	"level": "beginner"
+}</script>
 
 An element's attributes can contain useful information for your application, so it's important to be able to get and set them.
 
diff --git a/page/using-jquery-core/avoid-conflicts-other-libraries.md b/page/using-jquery-core/avoid-conflicts-other-libraries.md
index 73172aff..caa91aac 100644
--- a/page/using-jquery-core/avoid-conflicts-other-libraries.md
+++ b/page/using-jquery-core/avoid-conflicts-other-libraries.md
@@ -1,11 +1,9 @@
----
-title   : Avoiding Conflicts with Other Libraries
-attribution: jQuery Fundamentals
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Avoiding Conflicts with Other Libraries",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 The jQuery library and virtually all of its plugins are contained within the `jQuery` namespace. As a general rule, global objects are stored inside the jQuery namespace as well, so you shouldn't get a clash between jQuery and any other library (like prototype.js, MooTools, or YUI).
 
@@ -125,7 +123,7 @@ jQuery.noConflict();
 </script>
 ```
 
-Note that if you use this technique, you will not be able to use prototype.js methods inside the immediately invoked function that expect `$` to be prototype.js's `$`.
+Note that if you use this technique, you will not be able to use prototype.js methods inside the immediately invoked function. `$` will be a reference to jQuery, not prototype.js.
 
 ### Use the Argument That's Passed to the `jQuery( document ).ready()` Function
 
diff --git a/page/using-jquery-core/css-styling-dimensions.md b/page/using-jquery-core/css-styling-dimensions.md
index 855d2223..7e980694 100644
--- a/page/using-jquery-core/css-styling-dimensions.md
+++ b/page/using-jquery-core/css-styling-dimensions.md
@@ -1,7 +1,7 @@
----
-title   : CSS, Styling, & Dimensions
-level: beginner
----
+<script>{
+	"title": "CSS, Styling, & Dimensions",
+	"level": "beginner"
+}</script>
 
 jQuery includes a handy way to get and set CSS properties of elements:
 
diff --git a/page/using-jquery-core/data-methods.md b/page/using-jquery-core/data-methods.md
index 85cde17a..33500e3d 100644
--- a/page/using-jquery-core/data-methods.md
+++ b/page/using-jquery-core/data-methods.md
@@ -1,10 +1,9 @@
----
-title   : Data Methods
-level: intermediate
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Data Methods",
+	"level": "intermediate",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 There's often data about an element you want to store with the element. In plain JavaScript, you might do this by adding a property to the DOM element, but you'd have to deal with memory leaks in some browsers. jQuery offers a straightforward way to store data related to an element, and it manages the memory issues for you.
 
diff --git a/page/using-jquery-core/document-ready.md b/page/using-jquery-core/document-ready.md
index a3001cd7..2ae07cc5 100644
--- a/page/using-jquery-core/document-ready.md
+++ b/page/using-jquery-core/document-ready.md
@@ -1,9 +1,9 @@
----
-title   : $( document ).ready()
-level: beginner
----
+<script>{
+	"title": "$( document ).ready()",
+	"level": "beginner"
+}</script>
 
-A page can't be manipulated safely until the document is "ready." jQuery detects this state of readiness for you. Code included inside `$( document ).ready()` will only run once the page Document Object Model (DOM) is ready for JavaScript code to execute. Code included inside `$( window ).load(function() { ... })` will run once the entire page (images or iframes), not just the DOM, is ready.
+A page can't be manipulated safely until the document is "ready." jQuery detects this state of readiness for you. Code included inside `$( document ).ready()` will only run once the page Document Object Model (DOM) is ready for JavaScript code to execute. Code included inside `$( window ).on( "load", function() { ... })` will run once the entire page (images or iframes), not just the DOM, is ready.
 
 ```
 // A $( document ).ready() block.
@@ -12,7 +12,7 @@ $( document ).ready(function() {
 });
 ```
 
-Experienced developers sometimes use shorthand for `$( document ).ready()`. If you are writing code that people who aren't experienced with jQuery may see, it's best to use the long form.
+Experienced developers sometimes use the shorthand `$()` for `$( document ).ready()`. If you are writing code that people who aren't experienced with jQuery may see, it's best to use the long form.
 
 ```
 // Shorthand for $( document ).ready()
@@ -32,21 +32,21 @@ function readyFn( jQuery ) {
 
 $( document ).ready( readyFn );
 // or:
-$( window ).load( readyFn );
+$( window ).on( "load", readyFn );
 ```
 
-The below example shows `$( document ).ready()` and `$( window ).load()` in action. The code tries to load a website URL in an `<iframe>` and checks for both events:
+The example below shows `$( document ).ready()` and `$( window ).on( "load" )` in action. The code tries to load a website URL in an `<iframe>` and checks for both events:
 
 ```
 <html>
 <head>
-	<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
+	<script src="https://code.jquery.com/jquery-1.9.1.min.js"></script>
 	<script>
 	$( document ).ready(function() {
 		console.log( "document loaded" );
 	});
 
-	$( window ).load(function() {
+	$( window ).on( "load", function() {
 		console.log( "window loaded" );
 	});
 	</script>
@@ -56,3 +56,5 @@ The below example shows `$( document ).ready()` and `$( window ).load()` in acti
 </body>
 </html>
 ```
+
+To learn more about `.ready()` method, you can read [the relevant documenation page](https://api.jquery.com/ready/).
diff --git a/page/using-jquery-core/dollar-object-vs-function.md b/page/using-jquery-core/dollar-object-vs-function.md
index 9a86791a..44763197 100644
--- a/page/using-jquery-core/dollar-object-vs-function.md
+++ b/page/using-jquery-core/dollar-object-vs-function.md
@@ -1,10 +1,9 @@
----
-title   : $ vs $()
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "$ vs $()",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 Until now, we've been dealing entirely with methods that are called on a jQuery object. For example:
 
diff --git a/page/using-jquery-core/faq.md b/page/using-jquery-core/faq.md
index b1b15bff..2e754bd6 100644
--- a/page/using-jquery-core/faq.md
+++ b/page/using-jquery-core/faq.md
@@ -1,8 +1,10 @@
----
-title: Frequently Asked Questions
-level: beginner
-customFields:
- -
-    key: "icon"
-    value: "question-sign"
----
+<script>{
+	"title": "Frequently Asked Questions",
+	"level": "beginner",
+	"customFields": [
+		{
+			"key": "icon",
+			"value": "question-sign"
+		}
+	]
+}</script>
diff --git a/page/using-jquery-core/faq/how-do-i-check-uncheck-a-checkbox-input-or-radio-button.md b/page/using-jquery-core/faq/how-do-i-check-uncheck-a-checkbox-input-or-radio-button.md
index 067f08c3..e6a6f6b5 100644
--- a/page/using-jquery-core/faq/how-do-i-check-uncheck-a-checkbox-input-or-radio-button.md
+++ b/page/using-jquery-core/faq/how-do-i-check-uncheck-a-checkbox-input-or-radio-button.md
@@ -1,7 +1,6 @@
----
-title:        How do I check/uncheck a checkbox input or radio button?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I check/uncheck a checkbox input or radio button?"
+}</script>
 
 You can check or uncheck a checkbox element or a radio button using the `.prop()` method:
 
diff --git a/page/using-jquery-core/faq/how-do-i-determine-the-state-of-a-toggled-element.md b/page/using-jquery-core/faq/how-do-i-determine-the-state-of-a-toggled-element.md
index 31e4cb7d..718df5e2 100644
--- a/page/using-jquery-core/faq/how-do-i-determine-the-state-of-a-toggled-element.md
+++ b/page/using-jquery-core/faq/how-do-i-determine-the-state-of-a-toggled-element.md
@@ -1,7 +1,6 @@
----
-title:        How do I determine the state of a toggled element?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I determine the state of a toggled element?"
+}</script>
 
 You can determine whether an element is collapsed or not by using the `:visible` and `:hidden` selectors.
 
diff --git a/page/using-jquery-core/faq/how-do-i-disable-enable-a-form-element.md b/page/using-jquery-core/faq/how-do-i-disable-enable-a-form-element.md
index 79cd18ae..9ab3afa5 100644
--- a/page/using-jquery-core/faq/how-do-i-disable-enable-a-form-element.md
+++ b/page/using-jquery-core/faq/how-do-i-disable-enable-a-form-element.md
@@ -1,7 +1,6 @@
----
-title:        How do I disable/enable a form element?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I disable/enable a form element?"
+}</script>
 
 You can enable or disable a form element using the `.prop()` method:
 
diff --git a/page/using-jquery-core/faq/how-do-i-get-the-text-value-of-a-selected-option.md b/page/using-jquery-core/faq/how-do-i-get-the-text-value-of-a-selected-option.md
index ad78b54e..b98cd07e 100644
--- a/page/using-jquery-core/faq/how-do-i-get-the-text-value-of-a-selected-option.md
+++ b/page/using-jquery-core/faq/how-do-i-get-the-text-value-of-a-selected-option.md
@@ -1,7 +1,6 @@
----
-title:        How do I get the text value of a selected option?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I get the text value of a selected option?"
+}</script>
 
 Select elements typically have two values that you want to access. First there's the value to be sent to the server, which is easy:
 
diff --git a/page/using-jquery-core/faq/how-do-i-pull-a-native-dom-element-from-a-jquery-object.md b/page/using-jquery-core/faq/how-do-i-pull-a-native-dom-element-from-a-jquery-object.md
index 4bc00f6b..e4ba9e95 100644
--- a/page/using-jquery-core/faq/how-do-i-pull-a-native-dom-element-from-a-jquery-object.md
+++ b/page/using-jquery-core/faq/how-do-i-pull-a-native-dom-element-from-a-jquery-object.md
@@ -1,7 +1,6 @@
----
-title:        How do I pull a native DOM element from a jQuery object?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I pull a native DOM element from a jQuery object?"
+}</script>
 
 A jQuery object is an array-like wrapper around one or more DOM elements. To get a reference to the actual DOM elements (instead of the jQuery object), you have two options. The first (and fastest) method is to use array notation:
 
diff --git a/page/using-jquery-core/faq/how-do-i-replace-text-from-the-3rd-element-of-a-list-of-10-items.md b/page/using-jquery-core/faq/how-do-i-replace-text-from-the-3rd-element-of-a-list-of-10-items.md
index efe3662a..02fe3e92 100644
--- a/page/using-jquery-core/faq/how-do-i-replace-text-from-the-3rd-element-of-a-list-of-10-items.md
+++ b/page/using-jquery-core/faq/how-do-i-replace-text-from-the-3rd-element-of-a-list-of-10-items.md
@@ -1,7 +1,6 @@
----
-title:        How do I replace text from the 3rd element of a list of 10 items?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I replace text from the 3rd element of a list of 10 items?"
+}</script>
 
 Either the `:eq()` selector or the `.eq()` method will allow you to select the proper item. However, to replace the text, you must get the value before you set it:
 
diff --git a/page/using-jquery-core/faq/how-do-i-select-an-element-by-an-id-that-has-characters-used-in-css-notation.md b/page/using-jquery-core/faq/how-do-i-select-an-element-by-an-id-that-has-characters-used-in-css-notation.md
index 8a8282cc..36f533f0 100644
--- a/page/using-jquery-core/faq/how-do-i-select-an-element-by-an-id-that-has-characters-used-in-css-notation.md
+++ b/page/using-jquery-core/faq/how-do-i-select-an-element-by-an-id-that-has-characters-used-in-css-notation.md
@@ -1,11 +1,8 @@
----
-title:        How do I select an element by an ID that has characters used in CSS notation?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I select an element by an ID that has characters used in CSS notation?"
+}</script>
 
-Because jQuery uses CSS syntax for selecting elements, some characters are interpreted as CSS notation. For example, ID attributes, after an initial letter (a-z or A-Z), may also use periods and colons, in addition to letters, numbers, hyphens, and underscores (see [W3C Basic HTML Data Types](http://www.w3.org/TR/html4/types.html#type-id)). The colon (":") and period (".") are problematic within the context of a jQuery selector because they indicate a pseudo-class and class, respectively.
-
-In order to tell jQuery to treat these characters literally rather than as CSS notation, they must be "escaped" by placing two backslashes in front of them.
+Because jQuery uses CSS syntax for selecting elements, some characters are interpreted as CSS notation. In order to tell jQuery to treat these characters literally rather than as CSS notation, they must be escaped by placing two backslashes in front of them. See the [Selector documentation](http://api.jquery.com/category/selectors/) for further details.
 
 ```
 // Does not work:
@@ -21,12 +18,14 @@ $( "#some.id" )
 $( "#some\\.id" )
 ```
 
-The following function takes care of escaping these characters and places a "#" at the beginning of the ID string:
+On jQuery version 3.0 or later, the function [jQuery.escapeSelector()](https://api.jquery.com/jQuery.escapeSelector/) should be used to escape such selectors.
+
+Otherwise, the following function takes care of escaping these characters and places a "#" at the beginning of the ID string for convenience:
 
 ```
-function jq( myid ) {
+function escapeSelector( myid ) {
 
-	return "#" + myid.replace( /(:|\.|\[|\])/g, "\\$1" );
+	return "#" + myid.replace( /(\/|:|\.|\[|\]|,|=|@)/g, "\\$1" );
 
 }
 ```
@@ -34,5 +33,5 @@ function jq( myid ) {
 The function can be used like so:
 
 ```
-$( jq( "some.id" ) )
+$( escapeSelector( "some.id" ) )
 ```
diff --git a/page/using-jquery-core/faq/how-do-i-select-an-item-using-class-or-id.md b/page/using-jquery-core/faq/how-do-i-select-an-item-using-class-or-id.md
index c0818d02..aad1bb1d 100644
--- a/page/using-jquery-core/faq/how-do-i-select-an-item-using-class-or-id.md
+++ b/page/using-jquery-core/faq/how-do-i-select-an-item-using-class-or-id.md
@@ -1,7 +1,6 @@
----
-title:        How do I select an item using class or ID?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I select an item using class or ID?"
+}</script>
 
 This code selects an element with an ID of "myDivId". Since IDs are unique, this expression always selects either zero or one elements depending upon whether or not an element with the specified ID exists.
 
diff --git a/page/using-jquery-core/faq/how-do-i-select-elements-when-i-already-have-a-dom-element.md b/page/using-jquery-core/faq/how-do-i-select-elements-when-i-already-have-a-dom-element.md
index 95adc726..10490556 100644
--- a/page/using-jquery-core/faq/how-do-i-select-elements-when-i-already-have-a-dom-element.md
+++ b/page/using-jquery-core/faq/how-do-i-select-elements-when-i-already-have-a-dom-element.md
@@ -1,7 +1,6 @@
----
-title:        How do I select elements when I already have a DOM element?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I select elements when I already have a DOM element?"
+}</script>
 
 If you have a variable containing a DOM element, and want to select elements related to that DOM element, simply wrap it in a jQuery object.
 
diff --git a/page/using-jquery-core/faq/how-do-i-test-whether-an-element-exists.md b/page/using-jquery-core/faq/how-do-i-test-whether-an-element-exists.md
index eb9dee0b..c6ef018e 100644
--- a/page/using-jquery-core/faq/how-do-i-test-whether-an-element-exists.md
+++ b/page/using-jquery-core/faq/how-do-i-test-whether-an-element-exists.md
@@ -1,7 +1,6 @@
----
-title:        How do I test whether an element exists?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I test whether an element exists?"
+}</script>
 
 Use the [.length](http://api.jquery.com/length/) property of the jQuery collection returned by your selector:
 
diff --git a/page/using-jquery-core/faq/how-do-i-test-whether-an-element-has-a-particular-class.md b/page/using-jquery-core/faq/how-do-i-test-whether-an-element-has-a-particular-class.md
index bce0bd3b..8ebe9e19 100644
--- a/page/using-jquery-core/faq/how-do-i-test-whether-an-element-has-a-particular-class.md
+++ b/page/using-jquery-core/faq/how-do-i-test-whether-an-element-has-a-particular-class.md
@@ -1,7 +1,6 @@
----
-title:        How do I test whether an element has a particular class?
-source:       http://docs.jquery.com/Frequently_Asked_Questions
----
+<script>{
+	"title": "How do I test whether an element has a particular class?"
+}</script>
 
 [.hasClass()](http://api.jquery.com/hasClass/) (added in version 1.2) handles this common use case:
 
diff --git a/page/using-jquery-core/iterating.md b/page/using-jquery-core/iterating.md
index 9db4dd1c..1e95eeff 100644
--- a/page/using-jquery-core/iterating.md
+++ b/page/using-jquery-core/iterating.md
@@ -1,6 +1,6 @@
----
-title   : Iterating over jQuery and non-jQuery Objects
----
+<script>{
+	"title": "Iterating over jQuery and non-jQuery Objects"
+}</script>
 
 jQuery provides an object iterator utility called `$.each()` as well as a jQuery collection iterator: `.each()`. These are not interchangeable. In addition, there are a couple of helpful methods called `$.map()` and `.map()` that can shortcut one of our common iteration use cases.
 
@@ -115,7 +115,7 @@ $( "li" ).each( function( index, element ){
 
 The question is often raised, "If `this` is the element, why is there a second DOM element argument passed to the callback?"
 
-Whether intentional or inadvert, the execution context may change. When consistently using the keyword `this`, it's easy to end up confusing ourselves or other developers reading the code. Even if the execution context remains the same, it may be more readable to use the second parameter as a named parameter. For example:
+Whether intentional or inadvertent, the execution context may change. When consistently using the keyword `this`, it's easy to end up confusing ourselves or other developers reading the code. Even if the execution context remains the same, it may be more readable to use the second parameter as a named parameter. For example:
 
 ```
 $( "li" ).each( function( index, listItem ) {
@@ -266,7 +266,7 @@ $( "li" ).map( function( index, element ) {
 	return element.id;
 }).get();
 
-// Also returns ["a", "b", "c"]
+// Also returns [ "a", "b", "c" ]
 // Note that the value comes first with $.map
 $.map( arr, function( value, index ) {
 	return value.id;
diff --git a/page/using-jquery-core/jquery-object.md b/page/using-jquery-core/jquery-object.md
index cec6e12e..2a5f5e5a 100644
--- a/page/using-jquery-core/jquery-object.md
+++ b/page/using-jquery-core/jquery-object.md
@@ -1,7 +1,7 @@
----
-title      : The jQuery Object
-level      : beginner
----
+<script>{
+	"title": "The jQuery Object",
+	"level": "beginner"
+}</script>
 
 When creating new elements (or selecting existing ones), jQuery returns the elements in a collection. Many developers new to jQuery assume that this collection is an array. It has a zero-indexed sequence of DOM elements, some familiar array functions, and a `.length` property, after all. Actually, the jQuery object is more complicated than that.
 
@@ -15,7 +15,7 @@ Elements have properties like any JavaScript object. Among these properties are
 
 It turns out that working directly with DOM elements can be awkward. The jQuery object defines [many](http://api.jquery.com/) methods to smooth out the experience for developers. Some benefits of the jQuery Object include:
 
-*Compatibility* – The implementation of element methods varies across browser vendors and versions. The following snippet attempts to set the inner HTML of a `<tr>` element stored in `target`:
+*Compatibility* – The implementation of DOM methods varies across browser vendors and versions. The following snippet attempts to set the inner HTML of a `<tr>` element stored in `target`:
 
 ```
 var target = document.getElementById( "target" );
@@ -69,14 +69,14 @@ When the jQuery function is invoked with a CSS selector, it will return a jQuery
 var headings = $( "h1" );
 ```
 
-`headings` is now a jQuery element containing *all* the `<h1>` tags already on the page. This can be verified by inspecting the `.length` property of `headings`:
+`headings` is now a jQuery object containing *all* the `<h1>` tags already on the page. This can be verified by inspecting the `.length` property of `headings`:
 
 ```
 // Viewing the number of <h1> tags on the page.
 
-var allHeadings = $( "h1" );
+var headings = $( "h1" );
 
-alert( allHeadings.length );
+alert( headings.length );
 ```
 
 If the page has more than one `<h1>` tag, this number will be greater than one. If the page has no `<h1>` tags, the `.length` property will be zero. Checking the `.length` property is a common way to ensure that the selector successfully matched one or more elements.
@@ -170,7 +170,7 @@ Given a jQuery object with all the paragraph elements on the page:
 var allParagraphs = $( "p" );
 ```
 
-…one might expect that the contents will grow and shrink over time as `<p>` elements are added and removed from the document. jQuery objects do **not** behave in this manner. The set of elements contained within a jQuery object will not change unless explicitly modified. This means that the collection is not "live" – it does not automatically update as the document changes. If the document may have changed since the creation the jQuery object, the collection should be updated by creating a new one. It can be as easy as re-running the same selector:
+…one might expect that the contents will grow and shrink over time as `<p>` elements are added and removed from the document. jQuery objects do **not** behave in this manner. The set of elements contained within a jQuery object will not change unless explicitly modified. This means that the collection is not "live" – it does not automatically update as the document changes. If the document may have changed since the creation of the jQuery object, the collection should be updated by creating a new one. It can be as easy as re-running the same selector:
 
 ```
 // Updating the selection.
diff --git a/page/using-jquery-core/manipulating-elements.md b/page/using-jquery-core/manipulating-elements.md
index 74a0c4c0..d3fe9db1 100644
--- a/page/using-jquery-core/manipulating-elements.md
+++ b/page/using-jquery-core/manipulating-elements.md
@@ -1,16 +1,15 @@
----
-title   : Manipulating Elements
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Manipulating Elements",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 For complete documentation of jQuery manipulation methods, visit the [Manipulation documentation on api.jquery.com](http://api.jquery.com/category/manipulation/).
 
 ## Getting and Setting Information About Elements
 
-There are many ways to change an existing element. Among the most common tasks is changing the inner HTML or attribute of an element. jQuery offers simple, cross-browser methods for these sorts of manipulations. You can also get information about elements using many of the same methods in their getter incarnations. For more information on getters and setters, see the [Working with Selections](/working-with-selections/) section. Here are a few methods you can use to get and set information about elements:
+There are many ways to change an existing element. Among the most common tasks is changing the inner HTML or attribute of an element. jQuery offers simple, cross-browser methods for these sorts of manipulations. You can also get information about elements using many of the same methods in their getter incarnations. For more information on getters and setters, see the [Working with Selections](/using-jquery-core/working-with-selections/) section. Here are a few methods you can use to get and set information about elements:
 
 * **`.html()`** – Get or set the HTML contents.
 * **`.text()`** – Get or set the text contents; HTML will be stripped.
@@ -93,7 +92,7 @@ $( "<a/>", {
 });
 ```
 
-Note that the attributes object in the second argument above, the property name class is quoted, although the property names `html` and `href` are not. Property names generally do not need to be quoted unless they are [reserved words](/javascript-101/reserved-words/) (as `class` is in this case).
+Note that the attributes object in the second argument above, the property name class is quoted, although the property names `html` and `href` are not. Property names generally do not need to be quoted unless they are [reserved words](https://mathiasbynens.be/notes/reserved-keywords) (as `class` is in this case).
 
 When you create a new element, it is not immediately added to the page. There are several ways to add an element to the page once it's been created.
 
diff --git a/page/using-jquery-core/selecting-elements.md b/page/using-jquery-core/selecting-elements.md
index 30714ac1..08db0659 100644
--- a/page/using-jquery-core/selecting-elements.md
+++ b/page/using-jquery-core/selecting-elements.md
@@ -1,7 +1,7 @@
----
-title   : Selecting Elements
-level: beginner
----
+<script>{
+	"title": "Selecting Elements",
+	"level": "beginner"
+}</script>
 
 The most basic concept of jQuery is to "select some elements and do something with them." jQuery supports most CSS3 selectors, as well as some non-standard selectors. For a complete selector reference, visit the [Selectors documentation on api.jquery.com](http://api.jquery.com/category/selectors/).
 
@@ -20,7 +20,7 @@ $( ".myClass" );
 ## Selecting Elements by Attribute
 
 ```
-$( "input[name='first_name']" ); // Beware, this can be very slow in older browsers
+$( "input[name='first_name']" );
 ```
 
 ## Selecting Elements by Compound CSS Selector
@@ -29,6 +29,12 @@ $( "input[name='first_name']" ); // Beware, this can be very slow in older brows
 $( "#contents ul.people li" );
 ```
 
+## Selecting Elements with a Comma-separated List of Selectors
+
+```
+$( "div.myClass, ul.people" );
+```
+
 ## Pseudo-Selectors
 
 ```
@@ -54,16 +60,8 @@ Elements that have not been added to the DOM will always be considered hidden, e
 
 ## Choosing Selectors
 
-Choosing good selectors is one way to improve JavaScript's performance. A little specificity – for example, including an element type when selecting elements by class name – can go a long way. On the other hand, too much specificity can be a bad thing. A selector such as `#myTable thead tr th.special` is overkill if a selector such as `#myTable th.special` will get the job done.
+Choosing good selectors is one way to improve JavaScript's performance. Too much specificity can be a bad thing. A selector such as `#myTable thead tr th.special` is overkill if a selector such as `#myTable th.special` will get the job done.
 
-jQuery offers many attribute-based selectors, allowing selections based on the content of arbitrary attributes using simplified regular expressions.
-
-```
-// Find all <a> elements whose rel attribute ends with "thinger".
-$( "a[rel$='thinger']" );
-```
-
-While these can be useful in a pinch, they can also be extremely slow in older browsers. Wherever possible, make selections using IDs, class names, and tag names.
 
 ### Does My Selection Contain Any Elements?
 
@@ -116,29 +114,9 @@ $( "ul li" ).eq( 5 );              // the sixth
 
 jQuery offers several pseudo-selectors that help find elements in forms. These are especially helpful because it can be difficult to distinguish between form elements based on their state or type using standard CSS selectors.
 
-#### :button
-
-Using the `:button` pseudo-selector targets any `<button>` elements and elements with a `type="button"`:
-
-```
-$( "form :button" );
-```
-
-In order to get the best performance using `:button`, it's best to first select elements with a standard jQuery selector, then use `.filter( ":button" )`. More can be seen on the [jQuery :button documentation page](http://api.jquery.com/button-selector/). Another option is to precede the pseudo-selector with a tag name or some other selector.
-
-#### :checkbox
-
-Using the `:checkbox` pseudo-selector targets any `<input>` elements with a `type="checkbox"`:
-
-```
-$( "form :checkbox" );
-```
-
-Much like the `:button` pseudo-selector, it's best to first select elements with a standard jQuery selector, then to use `.filter( ":checkbox" )`, or to precede the pseudo-selector with some other selector.
-
 #### :checked
 
-Not to be confused with *:checkbox*, `:checked` targets *checked* checkboxes, but keep in mind that this selector works also for *checked* radio buttons, and select elements (for select elements only, use the `:selected` selector):
+Not to be confused with *:checkbox*, `:checked` targets *checked* checkboxes, but keep in mind that this selector works also for *checked* radio buttons, and `<select>` elements (for `<select>` elements only, use the `:selected` selector):
 
 ```
 $( "form :checked" );
@@ -166,30 +144,6 @@ $( "form :enabled" );
 
 In order to get the best performance using `:enabled`, first select elements with a standard jQuery selector, then use `.filter( ":enabled" )`, or precede the pseudo-selector with a tag name or some other selector.
 
-#### :file
-
-Using the `:file` pseudo-selector targets any `<input>` elements that have a `type="file"`:
-
-```
-$( "form :file" );
-```
-
-In order to get the best performance using `:file`, first select elements with a standard jQuery selector, then use `.filter( ":file" )`, or precede the pseudo-selector with a tag name or some other selector.
-
-**Note:** For better performance in modern browsers, use `[type="file"]` instead of the `:file` pseudo-selector.
-
-#### :image
-
-Using the `:image` pseudo-selector targets any `<input>` elements that have a `type="image"`:
-
-```
-$( "form :image" );
-```
-
-In order to get the best performance using `:image`, first select elements with a standard jQuery selector, then use `.filter( ":image" )`, or precede the pseudo-selector with a tag name or some other selector.
-
-**Note:** For better performance in modern browsers, use `[type="image"]` instead of the `:image` pseudo-selector.
-
 #### :input
 
 Using the `:input` selector selects all `<input>`, `<textarea>`, `<select>`, and `<button>` elements:
@@ -198,49 +152,6 @@ Using the `:input` selector selects all `<input>`, `<textarea>`, `<select>`, and
 $( "form :input" );
 ```
 
-#### :password
-
-Using the `:password` pseudo-selector targets any `<input>` elements with a `type="password"`:
-
-```
-$( "form :password" );
-```
-
-In order to get the best performance using `:password`, first select elements with a standard jQuery selector, then use `.filter( ":password" )`, or precede the pseudo-selector with a tag name or some other selector.
-
-**Note:** For better performance in modern browsers, use `[type="password"]` instead of the `:password` pseudo-selector.
-
-#### :radio
-
-Using the `:radio` pseudo-selector targets any `<input>` elements that have a `type="radio"`:
-
-```
-$( "form :radio" );
-```
-
-To select a set of associated radio buttons use:
-
-```
-// Selects all radio buttons with the name attribute of gender.
-$( "form input[name='gender']:radio" );
-```
-
-In order to get the best performance using `:radio`, first select elements with a standard jQuery selector, then use `.filter( ":radio" )`, or precede the pseudo-selector with a tag name or some other selector.
-
-**Note:** For better performance in modern browsers, use `[type="radio"]` instead of the `:radio` pseudo-selector.
-
-#### :reset
-
-Using the `:reset` pseudo-selector targets any `<input>` elements that have a `type="reset"`:
-
-```
-$( "form :reset" );
-```
-
-In order to get the best performance using `:reset`, first select elements with a standard jQuery selector, then use `.filter( ":reset" )`, or precede the pseudo-selector with a tag name or some other selector.
-
-**Note:** For better performance in modern browsers, use `[type="reset"]` instead of the `:reset` pseudo-selector.
-
 #### :selected
 
 Using the `:selected` pseudo-selector targets any selected items in `<option>` elements:
@@ -251,26 +162,18 @@ $( "form :selected" );
 
 In order to get the best performance using `:selected`, first select elements with a standard jQuery selector, then use `.filter( ":selected" )`, or precede the pseudo-selector with a tag name or some other selector.
 
-#### :submit
+#### Selecting by type
 
-Using the `:submit` pseudo-selector targets any `<button>` or `<input>` elements with a `type="submit"`:
-
-```
-$( "form :submit" );
-```
-
-The `:submit` selector usually applies to `<button>` or `<input>` elements. Some browsers (such as Internet Explorer) do not automatically give the `<button>` element a `type="submit"` by default.
-
-**Note:** For better performance in modern browsers, use `[type="submit"]` instead of the `:submit` pseudo-selector.
-
-#### :text
-
-Using the `:text` pseudo-selector targets any `<input>` elements with a `type="text"`:
-
-```
-$( "form :text" );
-```
+jQuery provides pseudo selectors to select form-specific elements according to their type:
 
-In order to get the best performance using `:text`, first select elements with a standard jQuery selector, then use `.filter( ":text" )`, or precede the pseudo-selector with a tag name or some other selector.
+* [`:password`](http://api.jquery.com/password-selector/)
+* [`:reset`](http://api.jquery.com/reset-selector/)
+* [`:radio`](http://api.jquery.com/radio-selector/)
+* [`:text`](http://api.jquery.com/text-selector/)
+* [`:submit`](http://api.jquery.com/submit-selector/)
+* [`:checkbox`](http://api.jquery.com/checkbox-selector/)
+* [`:button`](http://api.jquery.com/button-selector/)
+* [`:image`](http://api.jquery.com/image-selector/)
+* [`:file`](http://api.jquery.com/file-selector/)
 
-**Note:** As of jQuery 1.5.2, `:text` selects `<input>` elements that have no specified *type* attribute. So, `type="text"` is implied.
+For all of these there are side notes about performance, so be sure to check out [the API docs](http://api.jquery.com/category/selectors/form-selectors/) for more in-depth information.
diff --git a/page/using-jquery-core/traversing.md b/page/using-jquery-core/traversing.md
index 9c887b06..cc112dbb 100644
--- a/page/using-jquery-core/traversing.md
+++ b/page/using-jquery-core/traversing.md
@@ -1,7 +1,7 @@
----
-title   : Traversing
-level: beginner
----
+<script>{
+	"title": "Traversing",
+	"level": "beginner"
+}</script>
 
 Once you've made an initial selection with jQuery, you can traverse deeper into what was just selected. Traversing can be broken down into three basic parts: parents, children, and siblings. jQuery has an abundance of easy-to-use methods for all these parts. Notice that each of these methods can optionally be passed string selectors, and some can also take another jQuery object in order to filter your selection down. Pay attention and refer to the [API documentation on traversing](http://api.jquery.com/category/traversing/) to know what variation of arguments you have available.
 
diff --git a/page/using-jquery-core/understanding-index.md b/page/using-jquery-core/understanding-index.md
index 842552ec..beafeb36 100644
--- a/page/using-jquery-core/understanding-index.md
+++ b/page/using-jquery-core/understanding-index.md
@@ -1,9 +1,8 @@
----
-title   : Using jQuery's .index() Function
-level: intermediate
-attribution:
-  - John Paul <john@johnkpaul.com>
----
+<script>{
+	"title": "Using jQuery's .index() Function",
+	"level": "intermediate",
+	"attribution": [ "John Paul <john@johnkpaul.com>" ]
+}</script>
 
 `.index()` is a method on jQuery objects that's generally used to search for a given element within the jQuery object that it's called on. This method has four different signatures with different semantics that can be confusing. This article covers details about how to understand the way `.index()` works with each signature.
 
@@ -39,7 +38,8 @@ console.log( "Index: " + div.first().index() ); // 0
 
 In the first example, `.index()` gives the zero-based index of `#foo1` within its parent. Since `#foo1` is the second child of its parent, `index()` returns 1.
 
-When `.index()` is called on a jQuery object that contains more than one element, it calculates the index of the first element.
+
+__Note__: Before jQuery 1.9, `.index()` only worked reliably on a single element, which is why we've used `.first()` on each of our examples. In jQuery 1.9+ this can be ignored, as the API was updated to define that it operates on the first element only.
 
 ## `.index()` with a String Argument
 
diff --git a/page/using-jquery-core/utility-methods.md b/page/using-jquery-core/utility-methods.md
index 97b3e1d4..56aed1fe 100644
--- a/page/using-jquery-core/utility-methods.md
+++ b/page/using-jquery-core/utility-methods.md
@@ -1,10 +1,9 @@
----
-title   : Utility Methods
-level: beginner
-source: http://jqfundamentals.com/legacy
-attribution:
-  - jQuery Fundamentals
----
+<script>{
+	"title": "Utility Methods",
+	"level": "beginner",
+	"source": "http://jqfundamentals.com/legacy",
+	"attribution": [ "jQuery Fundamentals" ]
+}</script>
 
 jQuery offers several utility methods in the `$` namespace. These methods are helpful for accomplishing routine programming tasks. For a complete reference on jQuery utility methods, visit the [utilities documentation on api.jquery.com](http://api.jquery.com/category/utilities/).
 
@@ -104,3 +103,36 @@ var myObject = {
 $( "#foo" ).click( myObject.myFn ); // HTMLElement #foo
 $( "#foo" ).click( $.proxy( myObject, "myFn" ) ); // myObject
 ```
+
+## Testing Type
+
+Sometimes the `typeof` operator [can be confusing or inconsistent](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/typeof), so instead of using `typeof`, jQuery offers utility methods to help determine the type of a value.
+
+First of all, you have methods to test if a specific value is of a specific type.
+
+```
+$.isArray([]); // true
+$.isFunction(function() {}); // true
+$.isNumeric(3.14); // true
+```
+
+Additionally, there is `$.type()` which checks for the internal class used to create a value. You can see the method as a better alternative for the `typeof` operator.
+
+```
+$.type( true ); // "boolean"
+$.type( 3 ); // "number"
+$.type( "test" ); // "string"
+$.type( function() {} ); // "function"
+
+$.type( new Boolean() ); // "boolean"
+$.type( new Number(3) ); // "number"
+$.type( new String('test') ); // "string"
+$.type( new Function() ); // "function"
+
+$.type( [] ); // "array"
+$.type( null ); // "null"
+$.type( /test/ ); // "regexp"
+$.type( new Date() ); // "date"
+```
+
+As always, you can check the [API docs](http://api.jquery.com/jQuery.type/) for a more in-depth explanation.
diff --git a/page/using-jquery-core/working-with-selections.md b/page/using-jquery-core/working-with-selections.md
index 165217f7..86c45401 100644
--- a/page/using-jquery-core/working-with-selections.md
+++ b/page/using-jquery-core/working-with-selections.md
@@ -1,20 +1,22 @@
----
-title   : Working with Selections
-level: beginner
----
+<script>{
+	"title": "Working with Selections",
+	"level": "beginner"
+}</script>
 
 ### Getters & Setters
 
-jQuery "overloads" its methods, so the method used to set a value generally has the same name as the method used to get a value. When a method is used to set a value, it's called a setter. When a method is used to get (or read) a value, it's called a getter. Setters affect all elements in a selection. Getters get the requested value only for the first element in the selection.
+Some jQuery methods can be used to either assign or read some value on a selection. When the method is called with a value as an argument, it's referred to as a setter because it sets (or assigns) that value. When the method is called with no argument, it gets (or reads) the value of the element. Setters affect all elements in a selection, whereas getters return the requested value only for the first element in the selection, with the exception of [`.text()`](http://api.jquery.com/text/), which retrieves the values of all the elements.
 
 ```
-// The .html() method used as a setter:
+// The .html() method sets all the h1 elements' html to be "hello world":
 $( "h1" ).html( "hello world" );
 ```
 
 ```
-// The .html() method used as a getter:
+// The .html() method returns the html of the first h1 element:
 $( "h1" ).html();
+// > "hello world"
+
 ```
 
 Setters return a jQuery object, allowing you to continue calling jQuery methods on your selection. Getters return whatever they were asked to get, so you can't continue to call jQuery methods on the value returned by the getter.
diff --git a/redirects.json b/redirects.json
new file mode 100644
index 00000000..0915a485
--- /dev/null
+++ b/redirects.json
@@ -0,0 +1,3 @@
+{
+	"/plugins/stateful-plugins-with-widget-factory/": "/jquery-ui/widget-factory/how-to-use-the-widget-factory/"
+}
diff --git a/resources/jquery-mobile/Theme.png b/resources/jquery-mobile/Theme.png
index 9fc9b3ec..0052542e 100644
Binary files a/resources/jquery-mobile/Theme.png and b/resources/jquery-mobile/Theme.png differ