I am

.vscode/settings.json

@@ -0,0 +1,6 @@
+{
+  "cSpell.words": [
+    "exts",
+    "firstpaint"
+  ]
+}

README.md

@@ -2,19 +2,17 @@
 
 [![Join the chat at https://gitter.im/x-tag/core](https://badges.gitter.im/x-tag/core.svg)](https://gitter.im/x-tag/core?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
-[![Bower version](https://badge.fury.io/bo/x-tag-core.svg)](http://badge.fury.io/bo/x-tag-core)
-
 [![NPM version](https://badge.fury.io/js/x-tag.svg)](https://badge.fury.io/js/x-tag)
 
 [![CDNJS](https://img.shields.io/cdnjs/v/x-tag.svg)](https://cdnjs.com/libraries/x-tag) 
 
 **This is the repository for the core [X-Tag](http://x-tag.github.io/) library.**
 
-X-Tag is a Microsoft supported, open source, JavaScript library that wraps the W3C standard Web Components family of APIs to provide a compact, feature-rich interface for rapid component development. While X-Tag offers feature hooks for all Web Component APIs (Custom Elements, Shadow DOM, Templates, and HTML Imports), it only requires [Custom Element][1] support to operate. In the absence of native Custom Element support, X-Tag uses a set of polyfills shared with Google's Polymer framework.
+X-Tag is a Microsoft supported, open source, JavaScript library that wraps the W3C standard Web Components family of APIs to provide a compact, feature-rich interface for rapid component development. While X-Tag offers feature hooks for all Web Component APIs (Custom Elements, Shadow DOM, HTML Templates), it only requires [Custom Element][1] support to operate. In the absence of native Custom Element support, X-Tag relies on the same set of polyfills Google's Polymer framework uses.
 
 You can find out more about what X-Tag does, where it works, and how to use it, on the project page: [x-tag.github.io](http://x-tag.github.io/).
 
-  [1]: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html       "W3 Web Components Spec (Draft)"
+  [1]: http://w3c.github.io/webcomponents/spec/custom/       "W3 Web Components Spec (Draft)"
 
 ## Snag X-Tag from NPM
 
@@ -30,11 +28,9 @@ To get started hacking on X-Tag core:
 git clone https://github.com/x-tag/core x-tag-core --recursive
 cd x-tag-core
 npm install        # installs all the required dependencies using package.json
-grunt build     # outputs x-tag-core.js and x-tag-core.min.js to ./dist
+gulp all     # outputs x-tag-core.js and x-tag-core.min.js to ./dist
 ````
 
-If you are interested in building your own custom elements, you can use our [web-component-stub](https://github.com/x-tag/web-component-stub) as a starting point.
-
 ## Updating
 
 If you already cloned the library and want to update your build with changes to Core, do:
@@ -43,14 +39,14 @@ If you already cloned the library and want to update your build with changes to
 cd x-tag-core
 git pull origin master
 npm install
-grunt build
+gulp all
 ````
 
 This assumes you just cloned the library and its remote repository is labelled `origin`. Suppose you had your own fork where your own remote is `origin`; you should add another remote origin and label it as `upstream`. Then your `git pull` line would need to be `git pull upstream master` instead.
 
 ## Tests
 
-We use Jasmine to test the library, and you can verify it works as expected by opening [test/index.html](test/index.html) in your browser to run the tests.
+We use Jasmine to test the library, and you can verify it works as expected by opening [tests/core/index.html](tests/core/index.html) in your browser to run the tests.
 
 
 ## Regenerating the distributable build
@@ -60,16 +56,12 @@ In the interest of not reinventing the wheel, X-Tag core uses a few existing lib
 If you make changes on the library and want to regenerate the build, just run
 
 ````bash
-grunt build
+gulp all
 ````
 
-and both `x-tag-core.js` and `x-tag-core.min.js` will be rebuilt and placed in the `./dist` directory.
-
-
-## Creating your own web components
+and both `x-tag-raw.js` and `x-tag-polyfilled.js` will be rebuilt, minified, and placed in the `./dist` directory.
 
-To learn more about X-Tags visit [x-tag.github.io/docs](http://x-tag.github.io/docs).
 
-To create your own component, use our [web-component-stub](https://github.com/x-tag/web-component-stub).
+## Creating your own Web Components
 
-Share your components by adding them to the [Custom Elements Registry](http://customelements.io/) or Bower.
+To learn more about X-Tags visit [x-tag.github.io/docs](http://x-tag.github.io/docs).

bower.json

@@ -1,14 +1,14 @@
 {
   "name": "x-tag-core",
   "description": "X-Tag core library for creating custom elements as defined by the w3c Web Components spec.",
-  "version": "1.5.11",
+  "version": "2.0.3-beta",
   "keywords": [
     "web-components",
     "core",
     "library",
     "x-tag"
   ],
   "main": [
-    "dist/x-tag-core.js"
+    "dist/x-tag-polyfilled.js"
   ]
 }