Update repo README

Author: mikesir87

README.md

@@ -1,48 +1,48 @@
-# Labspace starter
+# Labspace - Container Getting Started
 
-This repository is intended to server as a template to help bootstrap a new Labspace.
+Learn Docker fundamentals by running containers, exploring the container lifecycle, and packaging a real Node.js app into your own custom image.
 
-## Instructions
+## What You'll Do
 
-1. Create a new repository using this repo as the template ([docs here](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)).
+- Run your first container
+- Build your first container image
+- Run that newly created container image
+- Push the new image to Docker Hub to share with others
 
-    **NOTE:** After creating the repo, a GHA workflow will run to do some additional bootstrapping. The bootstrapping workflow file will be removed during bootstrapping.
+## Launch the Labspace
 
-2. Clone your newly created repo to your local machine
+To launch the Labspace, run the following command:
 
-3. Start the local development mode:
+```bash
+docker compose -f oci://dockersamples/labspace-container-getting-started up -d
+```
 
-    ```bash
-    # On Mac/Linux
-    CONTENT_PATH=$PWD docker compose up --watch
+And then open your browser to http://localhost:3030.
 
-    # On Windows with PowerShell
-    $Env:CONTENT_PATH = (Get-Location).Path; docker compose up --watch
-    ```
-
-4. Update the `labspace/labspace.yaml` with your Labspace's title and description
+### Using the Docker Desktop extension
 
-5. Write your Labspace! Being in dev mode, your changes should be visible in the interface without a restart. Feel free to edit either on your host machine or in the Labspace itself!
+If you have the Labspace extension installed (`docker extension install dockersamples/labspace-extension` if not), you can also [click this link](https://open.docker.com/dashboard/extension-tab?extensionId=dockersamples/labspace-extension&location=dockersamples/labspace-container-getting-started&title=Container%20getting%20started) to launch the Labspace.
 
-    Add any supporting application files or resources directly into the Labspace. This repo will be cloned into the Labspace at startup.
-
-    Be sure to check out the [docs](https://github.com/dockersamples/labspace-infra/tree/main/docs) for additional information and guidelines.
+## Contributing
 
+If you find something wrong or something that needs to be updated, feel free to submit a PR. If you want to make a larger change, feel free to fork the repo into your own repository.
 
+**Important note:** If you fork it, you will need to update the GHA workflow to point to your own Hub repo.
 
-### Setting up the deployment pipeline
+1. Clone this repo
 
-The template repo contains a workflow file to make it easy to publish your Labspace.
+2. Start the Labspace in content development mode:
 
-1. Add GitHub Action Secrets in your new repo for the following:
+    ```bash
+    # On Mac/Linux
+    CONTENT_PATH=$PWD docker compose up --watch
 
-    - `DOCKERHUB_USERNAME` - the username to authenticate to Docker Hub with
-    - `DOCKERHUB_TOKEN` - a personal or organization access token to use for authentication
+    # On Windows with PowerShell
+    $Env:CONTENT_PATH = (Get-Location).Path; docker compose up --watch
+    ```
 
-2. In the `.github/workflows/publish-labspace.yaml.temp` file, update the `DOCKERHUB_REPO` with the name of the Docker Hub repo you want to publish to.
+3. Open the Labspace at http://dockerlabs.xyz.
 
-3. Rename the workflow file to remove the `.temp` extension.
+4. Make the necessary changes and validate they appear as you expect in the Labspace
 
-    ```bash
-    mv .github/workflows/publish-labspace.yaml.temp .github/workflows/publish-labspace.yaml
-    ```
+    Be sure to check out the [docs](https://github.com/dockersamples/labspace-infra/tree/main/docs) for additional information and guidelines.