more doc updates

1.0.0 is now feature complete :During

Author: jonathanong

Readme.md

@@ -57,4 +57,4 @@ Guide to Creating Apps with Components:
 - [Guide](https://github.com/component/guide)
 - [Specifications](https://github.com/component/spec)
 
-[component]: https://github.com/component/component
+[component]: https://github.com/component/component

changelogs/1.0.0.md

@@ -16,9 +16,6 @@ We don't want to bloat `component(1)` with options, commands, and features.
 
 For more specific changes, please read the [History.md](https://github.com/component/component/blob/master/History.md).
 
-_Please note that the changes described below will be included in the 1.0.0 release, but some may not be
-implemented yet in the release candidates.   2 April 2014_
-
 ## What's New
 
 ### Github Authentication
@@ -51,6 +48,7 @@ So Component has added a few commands to make pinning dependencies and updating
 - `component pin` - pin all your dependencies that users semver ranges to a single version.
 - `component outdated` - check whether any of your pinned dependencies are outdated.
 - `component update` - update all your pinned dependencies to the latest version.
+- `component duplicates` - list any duplicates of dependencies and their dependents
 
 Note that these commands only update the `component.json` files.
 To actually install these new versions,
@@ -71,8 +69,11 @@ Users can now search for your component using `component search` or at http://co
 
 Component v1 now supports ES6 modules by default.
 Simply write an ES6 module with node-like module references, and your app should still work.
-Note that CommonJS and ES6 modules are not completely compatible, so you may run into compatibility issues.
-However, please let us know if you find any issues!
+
+Note that CommonJS and ES6 modules are not completely compatible, ES6 modules aren't standardized yet, and ES6 to CommonJS transpilers are thus not yet stable.
+Thus, you may run into issues.
+Please let us know if you find any issues!
+The relevant repository is: http://github.com/component/builder-es6-module-to-cjs.
 
 ### Smarter `require()`s
 
@@ -82,6 +83,14 @@ However, this has been a pain as components are generally named with `npm`'s nam
 The solution now is to use `require(<user>-<repo>)` in your components, then publish the component to `npm` as `<user>-<repo>`.
 No more aliasing hackery will be required on the `browserify` and `node` side.
 
+### Watcher
+
+Component now has a `component build --watch` option, allowing incremental builds. It uses [sane](http://github.com/amasad/sane) under the hood, which seems to be one of the best JS watcher libraries currently published.
+
+### Linking
+
+You may now link local components as version dependencies in your app using the `component link ../path/to/folder` command.
+
 ### Glob Support
 
 Many people complained about having to list every single file in a `component.json` manually.

component/faq.md

@@ -1,3 +1,6 @@
+
+> Please note that this FAQ is a little out of date and was written before 1.0.0.
+
 ## Why components?
 
   Client-side development currently suffers from a lack of structure, more importantly this lack of structure and fundamental sharing of assets makes it difficult to abstract libraries into smaller subsets. Normally you would think twice about separating your library into several parts, because telling end-users to install several pieces is tedious, error-prone, and frankly annoying. Component makes this extremely easy, and we may all benefit from creating smaller lego-blocks for the web.