Merge pull request #9686 from habitat-sh/im/origins

Update docs about creating origins

Author: IanMadd

components/docs-chef-io/content/habitat/builder_origins.md

@@ -1,6 +1,7 @@
 +++
 title = "Get Started with Chef Habitat"
 gh_repo = "habitat"
+draft = true
 
 [menu]
   [menu.habitat]
@@ -134,7 +135,7 @@ Use the Habitat Studio to generate a Habitat package and preview the running Nod
 
 ## Manage the Service with Habitat Builder
 
-[Chef Habitat Builder]({{< relref "/habitat/builder_overview" >}}) acts as the core of Chef’s Application Delivery Enterprise hub. The Chef Habitat Builder SaaS stores plan files where they can be viewed and accessed by the Chef Habitat community and then deployed by the Chef Habitat Supervisor.
+[Chef Habitat Builder]({{< relref "/habitat/builder_overview" >}}) acts as the core of Chef's Application Delivery Enterprise hub. The Chef Habitat Builder SaaS stores plan files where they can be viewed and accessed by the Chef Habitat community and then deployed by the Chef Habitat Supervisor.
 
 Add your package to your Builder origin and then connect that package to your clone of the sample-node-app repository. Any changes made to your clone of the sample-node-app will trigger the Chef Habitat Builder to rebuild the package.
 

components/docs-chef-io/content/habitat/get_started.md

@@ -1,57 +1,37 @@
 +++
-title = "Create an Origin"
-description = "Create an Origin on Chef Habitat Builder"
+title = "Overview of Chef Habitat Builder origins"
 gh_repo = "habitat"
 
 [menu]
   [menu.habitat]
-    title = "Create an Origin"
-    identifier = "habitat/origins Create an Origin"
+    title = "Overview"
+    identifier = "habitat/origins/overview"
     parent = "habitat/origins"
     weight = 10
 +++
 
-An origin is a space on Chef Habitat Builder where you can store, share, and build packages. It is a unique namespace within Chef Habitat Builder, and while you can delete or transfer an origin, you can't rename an origin after it is created. One example of an origin is the "core" origin, which is the set of foundational packages managed and versioned by the core Chef Habitat maintainers.
+{{< readfile file="/habitat/reusable/md/builder_origins.md" >}}
 
-You can join existing origins by invitation and you can create your own origins.
-For more on invitations, see [origin membership and RBAC]({{< relref "origin_rbac.md#origin-membership" >}}).
+## Chef-owned origins
 
-### Create an Origin
+Progress Chef maintains the following origins:
 
-![Chef Habitat Builder without origins](/images/habitat/create-origin.png)
+- **core**: Hosts packages for common dependencies and compilers maintained by Progress Chef.
+- **chef**: Hosts packages for Chef products like Chef Infra Client, Chef InSpec, and Chef Automate.
+- **chef-platform**: Hosts packages for Chef 360 Platform skills.
+- **habitat**: Hosts packages required for an on-prem Habitat Builder deployment.
 
-To create an origin, select the **Create origin** button on the _My Origins_ page which opens the _Create New Origin_ form. (Chef Habitat Builder > My Origins )
+## Where can I create an origin
 
-![Creating an origin](/images/habitat/create-origin-form.png)
+You can create origins in an on-prem Habitat Builder deployment.
+[Chef's public Habitat Builder](https://bldr.habitat.sh) doesn't support creating new origins.
 
-First, enter a unique name that you want to associate with your packages.  Chef Habitat will only let you create an origin with a unique name. Some examples that you'll see in Chef Habitat Builder are team names, user names, and abstract concepts.
+## Create an origin
 
-Next, choose a privacy setting to set as the default for new packages. You can override this setting when uploading individual packages from the CLI or by connecting a plan file that declares a package as private. The difference between public and private packages is:
+{{< readfile file="/habitat/reusable/md/create_origins_builder.md" >}}
 
-- Anyone can find and use public packages
-- Only users with origin membership can find and use private packages
+### Create an origin with the Chef Habitat CLI
 
-When you select **Save and Continue**, Chef Habitat Builder:
+{{< readfile file="/habitat/reusable/md/create_origins_cli.md" >}}
 
-1. Creates your origin
-1. Creates an [origin key pair]({{< relref "origin_keys.md" >}})
-1. Redirects Chef Habitat Builder to the origin page
-
-![Origin successfully created](/images/habitat/create-origin-done.png)
-
-#### Create an Origin with the Chef Habitat CLI
-
-Use the [hab origin]({{< relref "habitat_cli.md#hab-origin" >}}) commands to manage your origins from the command line.
-
-Create an origin from the command line with the [hab origin create]({{< relref "habitat_cli.md#hab-origin-create" >}}) command
-
-```bash
-hab origin create <origin>
-```
-
-The results of this command differ slightly from creating an origin on the Chef Habitat Builder site. The CLI command:
-
-1. Creates an origin on the Chef Habitat Builder site
-1. Does _not_ generate an origin key pair
-
-For more information, see the [`hab origin create`]({{< relref "habitat_cli.md#hab-origin-create" >}}) CLI documentation.
+To create key pair for your origin, see the [origin keys]({{< relref "/habitat/origin_keys/#generate-origin-keys" >}}) documentation.

components/docs-chef-io/content/habitat/origins.md

@@ -0,0 +1,5 @@
+An origin is a unique namespace in Chef Habitat Builder where you can store, share, and build packages.
+Once created, an origin cannot be renamed, but it can be deleted or transferred.
+For example, the _core_ origin contains foundational packages managed and versioned by the core Chef Habitat maintainers.
+
+You can join existing origins by invitation or create your own origins in an on-prem Habitat Builder deployment. For details about invitations, see [origin membership and RBAC]({{< relref "origin_rbac.md#origin-membership" >}}).

components/docs-chef-io/content/habitat/reusable/md/builder_origins.md

@@ -0,0 +1,25 @@
+
+To create an origin in Chef Habitat Builder, follow these steps:
+
+1. In Habitat Builder, select **My Origins** in the left navigation menu.
+
+1. On the **My Origins** page, select **Create origin** which opens the **Create New Origin** form.
+
+1. Enter a unique name that you want to associate with your packages.  Chef Habitat will only let you create an origin with a unique name. Some examples that you'll see in Chef Habitat Builder are team names, user names, and abstract concepts.
+
+1. Choose a privacy setting to set as the default for new packages. You can override this setting when uploading individual packages from the CLI or by connecting a plan file that declares a package as private.
+
+   The difference between public and private packages is:
+
+   - Anyone can find and use public packages.
+   - Only users with origin membership can find and use private packages.
+
+1. Select **Save and Continue**
+
+    Habitat Builder does the following:
+
+    - Creates your origin.
+    - Creates an [origin key pair]({{< relref "/habitat/origin_keys" >}}).
+    - Redirects Chef Habitat Builder to the origin page.
+
+   ![Origin successfully created](/images/habitat/create-origin-done.png)

components/docs-chef-io/content/habitat/reusable/md/create_origins_builder.md

@@ -0,0 +1,8 @@
+
+To create an origin with the hab CLI, use the [`hab origin create`]({{< relref "habitat_cli.md#hab-origin-create" >}}) command. For example:
+
+- ```bash
+  hab origin create <ORIGIN>
+  ```
+
+  Habitat creates an origin on the Chef Habitat Builder site.