Update docs for Epiphany

docs/getting-started/creating-a-place.md

@@ -0,0 +1,64 @@
+To use Rojo to build a place, you'll need to create a new project file, which tells Rojo how your project is structured on-disk and in Roblox.
+
+Create a new folder, then run `rojo init` inside that folder to initialize an empty project.
+
+```sh
+mkdir my-new-project
+cd my-new-project
+
+rojo init
+```
+
+Rojo will make a small project file in your directory, named `roblox-project.json`. It'll make sure that any code in the directory `src` will get put into `ReplicatedStorage.Source`.
+
+Speaking of, let's make sure we create a directory named `src`, and maybe a Lua file inside of it:
+
+```sh
+mkdir src
+echo 'print("Hello, world!")' > src/hello.lua
+```
+
+## Building Your Place
+Now that we have a project, one thing we can do is build a Roblox place file for our project. This is a great way to get started with a project quickly with no fuss.
+
+All we have to do is call `rojo build`:
+
+```sh
+rojo build -o MyNewProject.rbxl
+```
+
+If you open `MyNewProject.rbxl` in Roblox Studio now, you should see a `Folder` containing a `ModuleScript` under `ReplicatedStorage`!
+
+!!! info
+    To generate an XML place file instead, like if you're checking the place file into version control, just use `rbxlx` as the extension on the output file instead.
+
+## Live-Syncing into Studio
+Building a place file is great for the initial build, but for actively working on your place, you'll want something quicker.
+
+In Roblox Studio, make sure the Rojo plugin is installed. If you need it, check out [the installation guide](installation) to learn how to install it.
+
+To expose your project to the plugin, you'll need to _serve_ it from the command line:
+
+```sh
+rojo serve
+```
+
+This will start up a web server that tells Roblox Studio what instances are in your project and sends notifications if any of them change.
+
+Note the port number, then switch into Roblox Studio and press the Rojo **Connect** button in the plugins tab. Type in the port number, if necessary, and press **Start**.
+
+If everything went well, you should now be able to change files in the `src` directory and watch them sync into Roblox Studio in real time!
+
+## Uploading Your Place
+Aimed at teams that want serious levels of automation, Rojo can upload places to Roblox.com automatically.
+
+You'll need an existing place on Roblox.com as well as the `.ROBLOSECURITY` cookie of an account that has write access to that place.
+
+!!! warning
+    It's recommended that you set up a Roblox account dedicated to deploying your place instead of your personal account in case your security cookie is compromised.
+
+Generating and uploading your place file is as simple as:
+
+```sh
+rojo upload --place_id [PLACE ID] --cookie "[SECURITY COOKIE]"
+```

docs/getting-started/creating-a-project.md

@@ -1,77 +0,0 @@
-# Creating a Project
-To use Rojo, you'll need to create a new project file, which tells Rojo what your project is, and how to load it into Roblox Studio.
-
-## New Project
-Create a new folder, then run `rojo init` inside that folder to initialize an empty project.
-
-```sh
-mkdir my-new-project
-cd my-new-project
-
-rojo init
-```
-
-Rojo will create an empty project file named `rojo.json` in the directory.
-
-The default configuration doesn't do anything. We need to tell Rojo where our code is on the filesystem, and where we want to put it in the Roblox tree.
-
-To do that, open up `rojo.json` and add an entry to the `partitions` table:
-
-```json
-{
-    "name": "your-project-name-here",
-    "servePort": 8000,
-    "partitions": {
-        "src": {
-            "path": "src",
-            "target": "ReplicatedStorage.Project"
-        }
-    }
-}
-```
-
-!!! warning
-    Make sure that the `src` directory exists in your project, or Rojo will throw an error!
-
-!!! warning
-    Any objects contained in the `target` of a partition will be destroyed by Rojo if not found on the filesystem!
-
-A Rojo project has one or more *partitions*. Partitions define how code should be transferred between the filesystem and Roblox by mapping directories and files to Roblox objects.
-
-Each partition has:
-
-* A name (the key in the `partitions` object), which is used for debugging
-* `path`, the location on the filesystem relative to `rojo.json`
-* `target`, the location in Roblox relative to `game`
-
-## Syncing into Studio
-
-Once you've added your partition to the project file, you can start the Rojo dev server by running a command in your project's directory:
-
-```sh
-rojo serve
-```
-
-If your project is in the right place, Rojo will let you know that it was found and start an HTTP server that the plugin can connect to.
-
-In Roblox Studio, open the plugins tab and find Rojo's buttons.
-
-![Location of Rojo's plugin buttons in Roblox Studio](/images/plugin-buttons.png)
-{: align="center" }
-
-Press **Test Connection** to verify that the plugin can communicate with the dev server. Watch the Output panel for the results.
-
-!!! info
-    If you see an error message, return to the previous steps and make sure that the Rojo dev server is running.
-
-    ![Rojo error in Roblox Studio Output](/images/connection-error.png)
-    {: align="center" }
-
-After your connection was successful, press **Sync In** to move code from the filesystem into Studio, or use **Toggle Polling** to have Rojo automatically sync in changes as they happen.
-
-## Importing an Existing Project
-Rojo will eventually support importing an existing Roblox project onto the filesystem for use with Rojo.
-
-Rojo doesn't currently support converting an existing project or syncing files from Roblox Studio onto the filesystem. In the mean time, you can manually copy your files into the structure that Rojo expects.
-
-Up-to-date information will be available on [issue #5](https://github.com/LPGhatguy/rojo/issues/5) as this is worked on.

docs/getting-started/installation.md

@@ -1,4 +1,3 @@
-# Installation
 Rojo has two components:
 
 * The server, a binary written in Rust