Update phoenix guide

Author: bryanjos

content/guide/using-with-phoenix.md

@@ -5,15 +5,15 @@ title = "using with phoenix"
 
 This guide will walk through setting up a Phoenix project with Elixirscript. This guide assumes you have already created a Phoenix project
 
-**NOTE**: This guide covers Phoenix 1.2. It will be updated when Phoenix 1.3 is released
+**Update: 2017-08-15**: This guide has been updated to cover both ElixirScript 0.30 and Phoenix 1.3
 
 Update your mix.exs file to add the current version of elixirscript to your dependencies:
 
 ```elixir
   defp deps do
     [
       #other deps
-     {:elixir_script, "~> x.x.x"}
+     {:elixir_script, "~> x.x"}
     ]
 ```
 
@@ -31,58 +31,51 @@ def project do
     version: "0.0.1",
     elixir: "~> 1.2",
     elixirc_paths: elixirc_paths(Mix.env),
-    compilers: [:phoenix, :gettext, :elixir_script] ++ Mix.compilers,
+    compilers: [:phoenix, :gettext] ++ Mix.compilers ++ [:elixir_script],
     build_embedded: Mix.env == :prod,
     start_permanent: Mix.env == :prod,
     deps: deps(),
     elixir_script: [
-      input: "web/static/elixirscript",
-      output: "web/static/js/build"
+      input: MyApp.App,
+      output: "assets/js/build"
     ]
   ]
 end
 ```
 
-Elixirscript by default will looks for input in the `lib/elixirscript` directory. It will also by default output to `priv/elixirscript`. Update the input directory to `web/static/elixirscript`. Update the output directory to `web/static/js/build`. This lets it tie into Brunch's pipeline.
+Make the `input` the entry point module of your ElixirScript App. Here is will be `MyApp.App` which we will
+define later. Next, add the `output` to the configuration and make it `"assets/js/build"`. By default the output
+goes to `priv/elixir_script/build`, but we want to place our output somewhere that our asset compilation process can pick it up and bundle it with any other JavaScript.
 
-Next, update the watcher configuration to use the Elixirscript watcher:
-
-```elixir
-  watchers: [node: ["node_modules/brunch/bin/brunch", "watch", "--stdin",
-                    cd: Path.expand("../", __DIR__)], mix: ["elixirscript.watch"]]
-```
-
-Whenever your Elixirscript code changes, the elixirscript compiler will recompile it.
-
-Create `app.ex` in the `web/static/elixirscript` directory
+Create `app.ex` in the `lib/my_app_frontend` directory
 
 ```bash
-touch web/static/elixirscript/app.ex
+touch lib/my_app_frontend/app.ex
 ```
 
 For this example, write a simple module that will write `Hello, world` to the console on start:
 
 ```elixir
-defmodule App do
+defmodule MyApp.App do
 
   def start(_type, _args) do
-    :console.log("Hello, world")
+    IO.puts("Hello, world")
   end
 
 end
 ```
 
-Finally, update `web/static/js/app.js` to start your Elixirscript app:
+Finally, update `assets/js/app.js` to start your Elixirscript app:
 
 ```javascript
-import Elixir from './build/Elixir.App';
-Elixir.start(Elixir.App, [])
+import Elixir from './build/elixirscript.build.js';
+Elixir.start(Elixir.MyApp.App, [])
 ```
 
 The empty array is list of initial arguments for your app.
 
 
-If you run `mix compile`, you should see a JavaScript file, `Elixir.App.js` in your `web/static/js/build` directory. 
+If you run `mix compile`, you should see a JavaScript file, `elixirscript.build.js` in your `assets/js/build` directory.
 
-If you run `mix phoenix.server`, open your browser, and then open your console, you should see `Hello, world`. Any changes should cause a reload
+If you run `mix phx.server`, open your browser, and then open your console, you should see `Hello, world`. Any changes should cause a recompilation of your ElixirScript code and a reload of the browser
 

content/post/elixirscript-0.30.0-released.md

@@ -1,14 +1,16 @@
 +++
 title = "ElixirScript 0.30.0 Released"
-date = 2017-08-09T00:29:03-05:00
+date = 2017-08-15T00:29:03-05:00
 draft = true
 +++
 
-ElixirScript 0.30 is a large release with lots of changes. It includes a rewrite of the compiler, a change in JavaScript interoperability and much more. This is also the first version to require Erlang 20 and Elixir 1.5, compiled with Erlang 20. Writing ElixirScript projects feel more like writing a normal Elixir project. These changes make this the best release of ElixirScript so far! This is a great point to give ElixirScript a try for yourself. This post will describe the major changes in this version.
+ElixirScript 0.30 is a large release with lots of changes. It includes a rewrite of the compiler, a change in JavaScript interoperability and much more. This is also the first version to require Erlang 20 and Elixir 1.5, compiled with Erlang 20. ElixirScript can compile your Elixir code and dependencies into JavaScript, with some [limitations](#limitations). These changes make this the best release of ElixirScript so far! This is a great point to give ElixirScript a try for yourself. This post will describe the major changes.
 
 ## Foreign Function Interface (FFI)
 
-JavaScript interoperability has changed in this version. ElixirScript now interacts with JavaScript using an FFI. This allows for a stricter barrier between Elixir code and JavaScript. It also allows for the ability to make packages designed to work with ElixirScript. Another benefit is that there are far fewer warnings during compilation time. As an example let's create an FFI module for some HTTP specific functions we want to use from JavaScript. An FFI module has 2 parts: the Elixir module and the corresponding JavaScript module.
+JavaScript interoperability has changed. ElixirScript now interacts with JavaScript using an FFI. This means there is a stricter barrier between Elixir and JavaScript. The FFI allows the ability to make packages designed to work with ElixirScript. Another benefit is that there are far fewer warnings during compilation time. As an example let's create an FFI module for some HTTP specific functions we want to use from JavaScript.
+
+An FFI module has 2 parts: the Elixir module and the corresponding JavaScript module.
 
 Our Elixir module, `MyApp.Http`
 ```elixir
@@ -35,15 +37,15 @@ export default {
 }
 ```
 
-ElixirScript depends on the JavaScript module being at a certain path. It will look for the JavaScript module either at `priv/elixir_script/my_app/http.js` or `priv/elixir_script/my_app.http.js`. If your code uses the FFI module, during compilation ElixirScript copies the js file along side the compilation output. The generated output imports the js file.
+ElixirScript depends on the JavaScript module being at a certain path. It will look for the JavaScript module either at `priv/elixir_script/my_app/http.js` or `priv/elixir_script/my_app.http.js`. If your code uses the FFI module, during compilation ElixirScript copies the js file along side the compilation output. The generated output imports the js file. The JavaScript module must be an ES module that exports a default object containing the functions you want to use.
 
 With the above in place, you can call functions on `MyApp.Http` as you would any other Elixir module.
 
 For more information, check the documentation for `ElixirScript.FFI`.
 
 ## Dependencies
 
-ElixirScript can compile your project's dependencies to JavaScript. This means you can use many of your favorite Hex packages in ElixirScript code. It is also now possible to create packages that ElixirScript code can use. These are normal mix projects which may or may not have FFI modules with their corresponding JavaScript files.
+ElixirScript can compile your project's dependencies to JavaScript. This means you can use many of the packages available in Hex. It is also possible to create ElixirScript-specific packages. These are normal mix projects which may or may not have FFI modules with their corresponding JavaScript files.
 
 If creating a Hex package for ElixirScript, please prepend `elixir_script` to your package name. This is so that it is clear your package is to be use with ElixirScript. For example, a React package would be named `elixir_script_react`. [Here is an example](https://github.com/elixirscript/elixirscript_react).
 
@@ -55,14 +57,16 @@ Calls to Erlang functions that the Elixir standard library make have to be reimp
 
 ElixirScript now only works as a mix compiler. This means there will no longer be an escript for download and plugins for Brunch and Webpack will no longer work with this and future versions.
 
-ElixirScript now only supports output of ES modules. This is mainly so that there is no confusion about how to implement the JavaScript portion of FFI modules.
+ElixirScript now only supports output of ES modules.
 
 ## Limitations
 
 `receive` is still not supported. When ElixirScript encounters a `receive` call during compilation, the compiler will show a warning, but will continue. During runtime these calls will throw an error. With `receive` not yet supported, this also means most of OTP is not supported as well.
 
 ## Conclusion
 
+Finally, I want to give a great big thanks to the Elixir Core Team! Thanks for making the updates in Erlang and Elixir that allowed ElixirScript's progress to continue. And thank you for being available to answer questions and to give great advice!
+
 For more information regarding changes, please check the [changelog](https://github.com/elixirscript/elixirscript/blob/master/CHANGELOG.md).
 
 For more on getting started with ElixirScript, check the [ElixirScript documentation](https://hexdocs.pm/elixir_script/ElixirScript.html)
@@ -72,5 +76,3 @@ For more on FFI, and other things, check out the [FFI documentation](https://hex
 For more on JavaScript Interoperability, check out the [JavaScript interoperability documentation](https://hexdocs.pm/elixir_script/JavaScriptInterop.md)
 
 For an example of an ElixirScript app, check out the [Todo Example App](https://github.com/elixirscript/todo-elixirscript)
-
-Finally, I want to give a great big thanks to the Elixir Core Team! Thanks for making the updates in Erlang and Elixir that allowed ElixirScript's progress to continue. And thank you for being available to answer questions and to give great advice!