From 2d0b4a7dcb4a34cd1ba175f9d677627e2617af49 Mon Sep 17 00:00:00 2001 From: Solomon Hykes Date: Wed, 16 Jun 2021 16:54:28 +0000 Subject: [PATCH] Docs: 102: group initial setup Signed-off-by: Solomon Hykes --- docs/learn/102-dev.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/learn/102-dev.md b/docs/learn/102-dev.md index 1f03eca3..d0ed3d8d 100644 --- a/docs/learn/102-dev.md +++ b/docs/learn/102-dev.md @@ -27,8 +27,6 @@ An environment is made of 3 parts: We will first develop our environment's *plan*, then configure its initial inputs, then finally run it to verify that it works. -## Developing your plan - ### Anatomy of a plan A _plan_ specifies, in code, how to deliver a particular application in a particular way. @@ -60,12 +58,14 @@ steps to get started, and give you resources to learn more. In technical terms, our plan is a [Cue Package](https://cuelang.org/docs/concepts/packages/#packages). In this tutorial we will develop a new Cue package from scratch for our plan; but you can use any Cue package as a plan. +## Initial setup + ### Install Cue Although not strictly necessary, for an optimal development experience we recommend [installing a recent version of Cue](https://github.com/cuelang/cue/releases/). -### (optional) Prepare Cue learning resources +### Prepare Cue learning resources If you are new to Cue, we recommend keeping the following resources in browser tabs: @@ -88,6 +88,8 @@ Make sure that all commands are run from the `todoapp` directory: cd examples/todoapp ``` +## Develop the plan + ### Initialize a Cue module Developing for Dagger takes place in a [Cue module](https://cuelang.org/docs/concepts/packages/#modules). @@ -100,7 +102,7 @@ In this guide we will use the same directory as the root of the Dagger workspace cue mod init ``` -### Organize your package +### Create a Cue package Now we start developing our Cue package at the root of our Cue module.