diff --git a/docs/getting_started.md b/docs/getting_started.md
new file mode 100644
index 000000000..ceb5e04d6
--- /dev/null
+++ b/docs/getting_started.md
@@ -0,0 +1,26 @@
+---
+layout: default
+title: Getting Started
+---
+## Installation
+
+Vagrant is packaged as a [RubyGem](http://rubyforge.org/projects/rubygems). Note that
+vagrant is _not limited to just ruby-based projects_. On the contrary, vagrant does not
+care what tools or language your project uses, but the vagrant tool itself is written
+in Ruby and can be installed simply:
+
+{% highlight bash %}
+$ gem install vagrant
+{% endhighlight %}
+
+## Initialize Your Project
+
+Once you've got vagrant installed, you'll want to initialize it for your project or
+projects. To do this, go to the root directory of your project, and do the following:
+
+{% highlight bash %}
+$ vagrant init
+{% endhighlight %}
+
+This will create an initial `Vagrantfile` in that directory, which is used not only
+to mark the root directory of your project but also to control every aspect of vagrant.
\ No newline at end of file
diff --git a/index.md b/index.md
index f46965289..2c8f86d72 100644
--- a/index.md
+++ b/index.md
@@ -1,8 +1,37 @@
---
layout: default
+title: Welcome
---
-Coming soon! For now, take a look at these pictures:
+Vagrant is a tool set out to **change the way web developers work**.
-
-
-
+Vagrant quickly and seamlessly builds and provisions virtual machines for
+development using [Sun's VirtualBox](http://www.virtualbox.org). Using vagrant,
+developers can continue to manage project files using their own system and editors,
+but all the servers, processes, etc. actually run within a virtualized environment.
+Vagrant allows ports to be forwarded so you can still test a web service, for example,
+by forwarding the virtual machine's port 80 to some port on the host machine and
+visiting it in any browser.
+
+## Why Use Vagrant?
+
+* **Get up and running without worrying about server setup** - Instead of spending
+ hours setting up a development environment for a project, simply run
+ `vagrant up` and get coding!
+* **Continue using your own editor and browser** - With shared folders and port forwarding,
+ it feels exactly as if nothing has changed. You can still edit files using your favorite
+ editor, and test the site using your favorite local tools.
+* **Avoid dependency hell** - Every project which uses vagrant has its own _unique and isolated virtual environment_,
+ so the dependencies and configurations of multiple projects never collide.
+* **Cleanup when you're done** - When you're done working for the day, execute
+ `vagrant down` and remove the virtual machine! No more web server, database, etc.
+ processes running when they're not needed!
+* **Add developers quickly and easily** - For teams, adding developers to new projects
+ is often a pain, since the new developer needs to learn how to setup all the
+ different pieces of the application to get it running on his development machine.
+ Forget about it! Just tell him to pull the latest code base from version control
+ and run `vagrant up` and you're in business!
+
+## Get Started!
+
+Are you ready to use vagrant to revolutionize the way you work? Check out
+the [getting started guide](/docs/getting_started.html).
\ No newline at end of file
-
-
+Vagrant quickly and seamlessly builds and provisions virtual machines for
+development using [Sun's VirtualBox](http://www.virtualbox.org). Using vagrant,
+developers can continue to manage project files using their own system and editors,
+but all the servers, processes, etc. actually run within a virtualized environment.
+Vagrant allows ports to be forwarded so you can still test a web service, for example,
+by forwarding the virtual machine's port 80 to some port on the host machine and
+visiting it in any browser.
+
+## Why Use Vagrant?
+
+* **Get up and running without worrying about server setup** - Instead of spending
+ hours setting up a development environment for a project, simply run
+ `vagrant up` and get coding!
+* **Continue using your own editor and browser** - With shared folders and port forwarding,
+ it feels exactly as if nothing has changed. You can still edit files using your favorite
+ editor, and test the site using your favorite local tools.
+* **Avoid dependency hell** - Every project which uses vagrant has its own _unique and isolated virtual environment_,
+ so the dependencies and configurations of multiple projects never collide.
+* **Cleanup when you're done** - When you're done working for the day, execute
+ `vagrant down` and remove the virtual machine! No more web server, database, etc.
+ processes running when they're not needed!
+* **Add developers quickly and easily** - For teams, adding developers to new projects
+ is often a pain, since the new developer needs to learn how to setup all the
+ different pieces of the application to get it running on his development machine.
+ Forget about it! Just tell him to pull the latest code base from version control
+ and run `vagrant up` and you're in business!
+
+## Get Started!
+
+Are you ready to use vagrant to revolutionize the way you work? Check out
+the [getting started guide](/docs/getting_started.html).
\ No newline at end of file