update README, move instructions to docs

dcodeIO · dcodeIO · commit 913b8d1517d1 · 2019-11-09T00:48:20.000+01:00
diff --git a/README.md b/README.md
@@ -45,50 +45,17 @@ Motivation
 
 > I do think [compiling TypeScript into WASM] is tremendously useful. It allows JavaScript developers to create WASM modules without having to learn C. – Colin Eberhardt, [Exploring different approaches to building WebAssembly modules](http://blog.scottlogic.com/2017/10/17/wasm-mandelbrot.html) (Oct 17, 2017)
 
-Instructions
-------------
+Further resources
+-----------------
 
-For general usage instructions, please refer to the [documentation](https://docs.assemblyscript.org) instead. The following sets up a *development environment* of the compiler, for example if you plan to make a pull request:
+* [Documentation](https://docs.assemblyscript.org)<br />
+  Introduction, quick start, examples and general usage instructions.
 
-```
-$> git clone https://github.com/AssemblyScript/assemblyscript.git
-$> cd assemblyscript
-$> npm install
-$> npm link
-$> npm run clean
-```
+* [Development instructions](https://docs.assemblyscript.org/details/development)<br />
+  How to set up a development environment (to submit a pull request).
 
-Note that a fresh clone of the compiler will use the distribution files in `dist/`, but after an `npm run clean` it will run [the sources](./src) directly through ts-node, which is useful in development. This condition can also be checked by running `asc -v` (it is running the sources if it states `-dev`). Also please see our [contribution guidelines](./CONTRIBUTING.md) before making your first pull request.
+* [Project governance](https://github.com/AssemblyScript/meta)<br />
+  Meta information related to the AssemblyScript project.
 
-Building
---------
-
-To build an UMD bundle to `dist/assemblyscript.js` (depends on [binaryen.js](https://github.com/AssemblyScript/binaryen.js)), including a browser version of asc to `dist/asc.js` (depends on assemblyscript.js):
-
-```
-$> npm run build
-```
-
-Cleaning the distribution files (again):
-
-```
-$> npm run clean
-```
-
-Linting potential changes:
-
-```
-$> npm run check
-```
-
-Running the [tests](./tests):
-
-```
-$> npm test
-```
-
-Running everything in order (lint, clean, test, build, test):
-
-```
-$> npm run all
-```
+* [Media files](./media)<br />
+  Various media files, like logos etc.
