diff --git a/docs/getting-started.md b/docs/getting-started.md
index c7dd54a8c..2e0104591 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -44,6 +44,49 @@ In order to better understand Pilosa's capabilities, we will create a sample pro
Although Pilosa doesn't keep the data in a tabular format, we still use the terms "columns" and "rows" when describing the data model. We put the primary objects in columns, and the properties of those objects in rows. For example, the Star Trace project will contain an index called "repository" which contains columns representing Github repositories, and rows representing properties like programming languages and tags. We can better organize the rows by grouping them into sets called Fields. So the "repository" index might have a "languages" field as well as a "tags" field. You can learn more about indexes and fields in the [Data Model](../data-model/) section of the documentation.
+#### Create the Environment
+
+While we can create indexes and query directly in the terminal, it is more conventional to do so in a client library. Pilosa supports Go, Java, and Python, though you will have to install the library for compatibility.
+
+For Go users, open a terminal (one other than the one running pilosa) and download the library in your `GOPATH` using:
+```
+go get github.com/pilosa/go-pilosa
+```
+
+For Java users, add the following dependency in your `pom.xml`:
+```
+
+
+ com.pilosa
+ pilosa-client
+ 1.3.1
+
+
+```
+
+For Python users, open a terminal (one other than the one running pilosa) and install the library using:
+```
+pip install pilosa
+```
+
+For simplicity, we reccomend that you create a separate folder for this project. In the terminal, create a new folder as follows:
+```
+mkdir GettingStarted
+cd GettingStarted
+```
+
+In this folder, we will download two CSV files to provide data to our fields later on. Download the stargazer.csv and language.csv files here:
+```
+curl -O https://raw.githubusercontent.com/pilosa/getting-started/master/stargazer.csv
+curl -O https://raw.githubusercontent.com/pilosa/getting-started/master/language.csv
+```
+
+We will also create a file called StarTrace.go (for Go users), StarTrace.java (for Java users), or StarTrace.py (for Python users) as follows:
+```
+touch StarTrace.go
+```
+This file will be used in the following section.
+
#### Create the Schema
Note:
@@ -55,184 +98,220 @@ curl localhost:10101/schema
``` response
{"indexes":null}
```
+##### Go Users
-Before we can import data or run queries, we need to create our indexes and the fields within them. Let's create the repository index first:
-``` request
-curl localhost:10101/index/repository -X POST
+Before we can import data or run queries, we need to create our indexes and the fields within them. Let's create the repository index first. Copy the following into the StarTrace.go file:
+```
+package main
+
+import (
+ "bytes"
+ "fmt"
+ "github.com/pilosa/go-pilosa"
+ "github.com/pilosa/go-pilosa/csv"
+ "io/ioutil"
+ "log"
+)
+
+func main() {
+ // Create the Schema
+ client := pilosa.DefaultClient()
+ schema, _ := client.Schema()
+ repository := schema.Index("repository")
+ // This is where the field will go later
+ err := client.SyncSchema(schema)
+ if err != nil {
+ log.Fatal(err)
+ }
+}
```
-``` response
-{"success":true}
-```
-The index name must be 64 characters or less, start with a letter, and consist only of lowercase alphanumeric characters or `_-`.
+The index name must be 64 characters or less, start with a letter, and consist only of lowercase alphanumeric characters or `_-`. The same goes for field names.
Let's create the `stargazer` field which has user IDs of stargazers as its rows:
-``` request
-curl localhost:10101/index/repository/field/stargazer \
- -X POST \
- -d '{"options": {"type": "time", "timeQuantum": "YMD"}}'
```
-``` response
-{"success":true}
+ stargazer := repository.Field("stargazer")
```
-Since our data contains time stamps which represent the time users starred repos, we set the field type to `time`. Time quantum is the resolution of the time we want to use, and we set it to `YMD` (year, month, day) for `stargazer`.
-
Next up is the `language` field, which will contain IDs for programming languages:
-``` request
-curl localhost:10101/index/repository/field/language \
- -X POST
```
-``` response
-{"success":true}
+ language := repository.Field("language")
```
-The `language` is a `set` field, but since the default field type is `set`, we didn't specify it in field options.
+Your StarTrace.go file should look like:
+```
+package main
+
+import (
+ "bytes"
+ "fmt"
+ "github.com/pilosa/go-pilosa"
+ "github.com/pilosa/go-pilosa/csv"
+ "io/ioutil"
+ "log"
+)
+
+func main() {
+ // Create the Schema
+ client := pilosa.DefaultClient()
+ schema, _ := client.Schema()
+ repository := schema.Index("repository")
+ stargazer := repository.Field("stargazer")
+ language := repository.Field("language")
+ err := client.SyncSchema(schema)
+ if err != nil {
+ log.Fatal(err)
+ }
+}
+```
+
+##### Java and Python Users
+
+
+
Java and Python support will be uploaded shortly.
+
-
For demonstration purposes, we're using Pilosa's built in utility to import specially formatted CSV files. For more general usage, see how the various client libraries expose the bulk import functionality in Go, Java, and Python.
+
Java and Python support will be uploaded shortly.
+
If you are using a Docker container for Pilosa (with name `pilosa`), you should instead copy the `*.csv` file into the container and then import them:
```
docker cp stargazer.csv pilosa:/stargazer.csv
docker exec -it pilosa /pilosa import -i repository -f stargazer /stargazer.csv
docker cp language.csv pilosa:/language.csv
docker exec -it pilosa /pilosa import -i repository -f language /language.csv
```
+
+
Java and Python support will be uploaded shortly.
+