Migrate to Vuepress

.gitignore

@@ -1,27 +1,12 @@
-# Logs
-logs
-*.log
-
-# Runtime data
 pids
-*.pid
-*.seed
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
-coverage
-
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (http://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directory
-# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git
+logs
 node_modules
+npm-debug.log
+coverage/
+run
+dist
+.DS_Store
+.nyc_output
+.basement
+config.local.js
+basement_dist

.prettierrc

@@ -0,0 +1,22 @@
+{
+	"$schema": "http://json.schemastore.org/prettierrc",
+	"endOfLine": "lf",
+	"quoteProps": "as-needed",
+	"semi": true,
+	"singleQuote": true,
+	"tabWidth": 4,
+	"trailingComma": "none",
+	"useTabs": true,
+	"arrowParens": "always",
+	"bracketSpacing": true,
+	"printWidth": 120,
+	"overrides": [
+		{
+			"files": ["*.yml"],
+			"options": {
+				"tabWidth": 2,
+				"useTabs": false
+			}
+		}
+	]
+}

LICENSE

@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND 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.
+SOFTWARE.

README.md

@@ -1,6 +1,29 @@
-# inversify.github.io
+## Development / Testing
 
-[![Join the chat at https://gitter.im/inversify/InversifyJS](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/inversify/InversifyJS?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
-[![Build Status](https://travis-ci.org/inversify/inversify.github.io.svg?branch=master)](https://travis-ci.org/inversify/inversify.github.io)
+```sh
+$ yarn install
+```
 
-The InversifyJS official website
+```sh
+$ yarn dev
+```
+
+## Creating Translations
+
+We recommend that each individual file you update has its own commit.
+
+This keeps the history for commits clean and easy to track backwards.
+
+### Creating a New Locale / Translation
+
+It's a pretty short process but requires some work.
+
+0. Fork the Repository
+1. Copy `en.js` from `src/.vuepress/locales/en.js`.
+1. Rename it to your two letter [ISO-639-1 Code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes).
+1. Edit the titles and translate them. Follow instructions in the copied code. We left comments for you.
+1. Copy the folder `en` from the `src` directory.
+1. Rename it to your ISO-639-1 Code for your Country / Language.
+1. Begin converting documents from English to your language.
+1. Test locally! It's very important!
+1. Make a pull request.