Now that you've got a grasp on the structure of a pod, we can jump into changing configs, writing content, and working on templates. All of this is easily possible using Grow's built-in development server, which you can start using the
grow run ./my-codelab/
When you start the development server, Grow checks for updates to the SDK, tests your pod, compiles translations, and runs preprocessors. If any of these tasks fail, the test server will fail to start. Here's what it looks like when you start your development server:
$ grow run ~/my-codelab/ Checking for updates to the Grow SDK... Your Grow SDK is the latest version: 0.X.X Compiled /source/sass/main.sass -> /static/css/main.min.css Serving pod /Users/me/git/growsdk.org => http://localhost:8080
Your development server is now running, and by default, your web browser will open to your project's root, ready for you to preview.
Changes to content (in
content), templates (in
views), or static files are immediately reflected, and a quick refresh of any page allows you to see your changes immediately.
Grow watches for changes to files that require preprocessing (such as files in
translations). Changes to those files will cause Grow to kick off a preprocessor to build the generated files, and your changes will be reflected in the live preview almost immediately.
http://localhost:8080 in your browser and navigate through the site. This entire site is built by your codelab pod.