diff --git a/README.md b/README.md
index 2034a51f1a7edb5f118cfb88385099d2678c012e..a61a3469ee7907ef3f8b55941cc0c65caad13f7d 100644
--- a/README.md
+++ b/README.md
@@ -5,16 +5,29 @@ This repository contains documentation for Fuchsia.
 
 # Individual Project Documentation
 
-+ [Magenta](https://fuchsia.googlesource.com/magenta/+/master/README.md)
++ [Magenta][magenta]
 
     Magenta is the microkernel underlying the rest of Fuchsia. Magenta
     also provides core drivers and Fuchsia's libc implementation.
 
 # How do I?
 
++ [How do I get started with Fuchsia?][getting_started]
+
++ [How do I use the build system?][build_system]
+
 + How do I boot on my...
-  + [Acer Switch Alpha 12?](https://fuchsia.googlesource.com/magenta/+/master/docs/targets/acer12.md)
-  + [Intel NUC?](https://fuchsia.googlesource.com/magenta/+/master/docs/targets/nuc.md)
-  + [Raspberry Pi 3?](https://fuchsia.googlesource.com/magenta/+/master/docs/targets/rpi3.md)
+  + [Acer Switch Alpha 12?][acer_12]
+  + [Intel NUC?][intel_nuc]
+  + [Raspberry Pi 3?][rpi3]
+
++ [How do I write a flutter module?][flutter_module]
+
 
-+ [How do I write a flutter module?](https://fuchsia.googlesource.com/modular/+/master/examples/HOWTO_FLUTTER.md)
+[magenta]: https://fuchsia.googlesource.com/magenta/+/master/README.md "Magenta"
+[getting_started]: getting_started.md "Getting started"
+[build_system]: build_system.md "Build system"
+[acer_12]: https://fuchsia.googlesource.com/magenta/+/master/docs/targets/acer12.md "Acer 12"
+[intel_nuc]: https://fuchsia.googlesource.com/magenta/+/master/docs/targets/nuc.md "Intel NUC"
+[rpi3]: https://fuchsia.googlesource.com/magenta/+/master/docs/targets/rpi3.md "Rasperry Pi 3"
+[flutter_module]: https://fuchsia.googlesource.com/modular/+/master/examples/HOWTO_FLUTTER.md "Flutter modules"
diff --git a/build_system.md b/build_system.md
new file mode 100644
index 0000000000000000000000000000000000000000..b37e6c69da60ebe485f73fa95db6b8f5ef762958
--- /dev/null
+++ b/build_system.md
@@ -0,0 +1,65 @@
+
+# Fuchsia Build Notes
+
+You should probably use the [standard build instructions](https://fuchsia.googlesource.com/fuchsia/+/HEAD/README.md) instead of using the instructions here.
+
+These are notes on using the `gen.py` script and `ninja` directly for builds, and the `scripts/run-magenta-*` scripts to launch QEMU. The functions in `env.sh` should cover all the functionality described here and use these commands under-the-hood.
+
+### Build Magenta and the sysroot
+
+First, you need to [build the Magenta kernel](https://fuchsia.googlesource.com/magenta/+/HEAD/docs/getting_started.md) and the sysroot:
+
+```
+(cd magenta; make -j32 magenta-pc-x86-64)
+./scripts/build-sysroot.sh
+```
+### Building Fuchsia
+
+Build Fuchsia using these commands:
+
+```
+./packages/gn/gen.py
+./buildtools/ninja -C out/debug-x86-64
+```
+
+Optionally if you have ccache installed and configured (i.e. the CCACHE_DIR
+environment variable is set to an existing directory), use the following command
+for faster builds:
+
+```
+./packages/gn/gen.py --ccache
+./buildtools/ninja -C out/debug-x86-64
+```
+
+[Googlers only] If you have goma installed, prefer goma over ccache and use these
+alternative commands for faster builds:
+
+```
+./packages/gn/gen.py --goma
+./buildtools/ninja -j1000 -C out/debug-x86-64
+```
+
+The gen.py script takes an optional parameter '--target\_cpu' to set the target
+architecture. If not supplied, it defaults to x86-64.
+
+```
+./packages/gn/gen.py --target_cpu=aarch64
+./buildtools/ninja -C out/debug-aarch64
+```
+
+You can configure the set of modules that `gen.py` uses with the `--modules`
+argument. After running `gen.py` once, you can do incremental builds using
+`ninja`.
+
+### Running Fuchsia
+
+These commands will create an `out/debug-{arch}/user.bootfs` file. To run the
+system with this filesystem attached in QEMU, pass the user.bootfs path as the
+value of the '-x' parameter in Magenta's start command script, for example:
+
+```
+./scripts/run-magenta-x86-64 -x out/debug-x86-64/user.bootfs -m 2048
+./scripts/run-magenta-arm64 -x out/debug-aarch64/user.bootfs -m 2048
+```
+
+See the [standard build instructions](https://fuchsia.googlesource.com/fuchsia/+/HEAD/README.md) for other flags you can pass to QEMU.
diff --git a/getting_started.md b/getting_started.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d949d02fe92b2a48ffac6ca53d30c48ac98860c
--- /dev/null
+++ b/getting_started.md
@@ -0,0 +1,160 @@
+# Fuchsia
+
+Pink + Purple == Fuchsia (a new Operating System)
+
+Welcome to Fuchsia! This is a top-level entry point for the project. From here
+we try to link to everything you need to get started, use, and develop for
+Fuchsia.
+
+## Getting the source
+Get the Fuchsia source by following these two steps and then return to this document:
+  * [Install prerequisites](https://fuchsia.googlesource.com/manifest/+/HEAD/README.md#Prerequisites) for Jiri, a tool for multi-repo development.
+  * [Create a new checkout](https://fuchsia.googlesource.com/manifest/+/HEAD/README.md#Creating-a-new-checkout) of Fuchsia.
+
+## Prerequisites
+
+### Magenta Prerequisites
+
+The Fuchsia source  includes [Magenta](https://fuchsia.googlesource.com/magenta), the core platform which underpins Fuchsia. Follow this step to install the Magenta build prerequisites and then return to this document. (You can ignore the toolchain installation instructions unless you want to build your own; the Fuchsia manifest will automatically obtain a prebuilt toolchain.)
+
+* [Preparing the Magenta build environment](https://fuchsia.googlesource.com/magenta/+/master/docs/getting_started.md#Preparing-the-build-environment).
+
+### [Googlers only] Goma
+
+Ensure `goma` is installed on your machine for faster builds.
+
+## Build Fuchsia
+### Setup Build Environment
+
+Source the `env.sh` script, which provides helpful shell functions for Fuchsia development. The following command also changes the command prompt and sets up for a x86-64 build.
+
+```
+source scripts/env.sh && envprompt && fset x86-64
+```
+
+Run `envhelp` to see other useful shell functions, and `envhelp <function>` for specific usage information.
+
+[optional] You might find it useful to add a shell function `fuchsia` as a shortcut to setup the build environment. For that, add this your shell startup script (e.g. `~/.bashrc`):
+
+```
+export FUCHSIA_ROOT=/path/to/my/fuchsia/source
+function fuchsia() {
+  source $FUCHSIA_ROOT/scripts/env.sh && envprompt && fgo && fset x86-64 "$@"
+}
+```
+
+
+### [optional] Customize Build Environment
+
+By default you will get a x86-64 debug build, and you can skip this step unless you want something else.
+
+[Googlers only: If you have `goma` installed, it will also be used by default. Prefer `goma` over `ccache`]
+
+Run `fset-usage` to see a list of build options. Some examples:
+
+```
+fset x86-64           # x86-64 debug build, no goma, no ccache
+fset arm64            # arm64 debug build, no goma, no ccache
+fset x86-64 --release # x86-64 release build, no goma, no ccache
+fset x86-64 --ccache  # x86-64 debug build, ccache enabled
+```
+
+Note: to use `ccache` or `goma` you must install them first.
+
+### Build Fuchsia
+
+Once you have setup your build environment, simply run:
+```
+fbuild
+```
+
+This builds Magenta, the sysroot, and the default Fuchsia build.
+
+After Fuchsia is built, you will have a Magenta (`magenta.bin`) image and a `user.bootfs` file in `out/debug-{arch}/`.
+
+### Run Fuchsia in QEMU
+
+You can run Fuchsia under emulation using [QEMU](https://fuchsia.googlesource.com/magenta/+/HEAD/docs/qemu.md).
+Fuchsia includes prebuilt binaries for QEMU under `buildtools/qemu`.
+
+The `frun` command will launch Magenta within QEMU, using the locally built
+`user.bootfs`:
+
+```
+frun
+```
+
+There are various flags for `frun` to control QEMU's configuration. The `-m`
+flag sets QEMU's memory size in MB, while `-g` and `-N` enable graphics and
+networking, respectively (see below). Use `frun -h` to see all available
+options.
+
+When Fuchsia has booted and started an MXCONSOLE, you can run programs!
+
+For example, to receive deep wisdom, run:
+
+```
+fortune
+```
+
+#### Working with Fuchsia system components
+
+The `bootstrap` utility sets up the environment and system services required
+to use and develop Fuchsia applications. You can run individual Fuchsia
+applications invoking their url:
+
+    @ bootstrap [args...] <app url> <app args...>
+
+Bootstrap can also be run without any initial apps for debugging purposes.
+
+    @ bootstrap -
+
+You can run additional Fuchsia applications within an existing bootstrap
+environment by specifying the `boot` scope:
+
+    @boot <app url> <app args...>
+
+More information on bootstrap and its uses can be found [here](https://fuchsia.googlesource.com/modular/+/HEAD/src/bootstrap/)
+
+#### Enabling Graphics
+
+To enable graphics, add the `-g` flag to `frun`:
+
+```
+frun -g
+```
+
+Run graphical applications (using [mozart](https://fuchsia.googlesource.com/mozart))
+in `/system/apps` like this:
+
+```
+@ bootstrap launch spinning_square_view
+```
+
+Some more mozart example apps are [here](https://fuchsia.googlesource.com/mozart/+/HEAD/examples/).
+
+#### Enabling Network
+
+Note: Networking support within QEMU is only available under x86_64.
+
+First, [configure](https://fuchsia.googlesource.com/magenta/+/master/docs/qemu.md#Enabling-Networking-under-Qemu-x86_64-only)
+a virtual interface for QEMU's use.
+
+Once this is done you can add the -N flag to `frun`:
+
+```
+frun -N
+```
+
+### Run Fuchsia on hardware
+
+* [Acer Switch Alpha 12](https://fuchsia.googlesource.com/magenta/+/master/docs/targets/acer12.md)
+* [Intel NUC](https://fuchsia.googlesource.com/magenta/+/master/docs/targets/nuc.md)
+* [Raspberry Pi 3](https://fuchsia.googlesource.com/magenta/+/master/docs/targets/rpi3.md)
+
+## Additional helpful documents
+
+
+* [Fuchsia documentation](https://fuchsia.googlesource.com/docs) hub.
+* [Contributing changes](https://fuchsia.googlesource.com/manifest/+/HEAD/README.md#Submitting-changes).
+* More about the [build commands](https://fuchsia.googlesource.com/fuchsia/+/HEAD/BUILD_NOTES.md) called under-the-hood by `fbuild`.