Brian guide fix

assets/scss/common/_custom.scss

@@ -11,10 +11,6 @@ Put CSS for custom HTML components here.
   }
 }
 
-body {
-  // line-height: 1.5em;
-}
-
 $code-block-bg: #032332;
 $border-color: #a9b2bc88;
 $background-color: $edgeneutral-05;
@@ -30,14 +26,13 @@ $tab-content-bg: #f5f6f7;
 
 .edgeworx-card-container {
   display: flex;
-  flex-flow: row wrap;
+  flex-direction: row;
   gap: 1.5rem;
-  justify-content: space-around;
+  justify-content: center;
   align-items: stretch;
 
   .no-hover-link {
-    width: 48%;
-    min-width: 300px;
+    max-width: 400px;
   }
 
   & .edgeworx-card {
@@ -185,7 +180,7 @@ $tab-content-bg: #f5f6f7;
         padding-top: 2rem;
         display: grid;
         grid-auto-flow: row;
-        gap: 1.5rem;
+        gap: 2rem;
 
         & .link {
           text-align: left;
@@ -198,14 +193,10 @@ $tab-content-bg: #f5f6f7;
   }
 }
 
-@media screen and (min-width: 768px) {
+@media screen and (max-width: 768px) {
   .edgeworx-card-container {
-    grid-auto-flow: column;
-
-    .edgeworx-card {
-      // TODO: The below is what makes the card on the front page massive. Commenting out to resize card.
-      // max-width: unset;
-    }
+    flex-direction: column;
+    align-items: center;
   }
 
   .home {

content/en/_index.md

@@ -7,18 +7,25 @@ aliases:
   - /edgeworx/contact-us
 cards:
 
-  - title: Get started - Edgeworx Cloud Portal
-    subtitle: Create your Edgeworx Cloud account.
-    action: Build
+  - title: Get started, set up your first edge project.
+    subtitle: Create your Edgeworx Cloud account and your first project.
+    action: Create project
     time: Easy
-    link: '/docs/guides/start-portal/'
-    image: /images/guides/guide-thumb-deploy.jpg
+    link: '/docs/cloud/start-portal/'
+    image: /images/guides/Guide—thumb-create-account.jpg
 
-  - title: Deploy an app to the edge in under 10 minutes
-    subtitle: Package and deploy your app in the real world on different edge devices without changing the code.
-    action: Deploy
+  - title: Add an edge node in under 10 minutes.
+    subtitle: Add a node (or virtual node) to the edge in just a few minutes.
+    action: Add a node
     time: Easy
-    link: '/docs/guides/deploy/'
-    image: /images/guides/guide-thumb-deploy.jpg
+    link: '/docs/cloud/adding-nodes/add-node/'
+    image: /images/guides/Guide—thumb-addnode.jpg
+
+  - title: Deploy an app to the edge in under 10 minutes.
+    subtitle: Package your app and deploy it to your edge node.
+    action: Deploy an app
+    time: Easy
+    link: '/docs/apps/deploy/'
+    image: /images/guides/Guide—thumb-deployapp.jpg
 
 ---

content/en/docs/apps/_index.md

@@ -5,7 +5,7 @@ linkTitle: "Building edge apps"
 ---
 
 [Apps](../more/terminology#application) are groups of [microservices](./microservices.md) bundled to work together. They are defined using YAML files and can
-be deployed and updated by uploading those YAML files through [Edgeworx Cloud](/docs/guides/start-portal) or through
+be deployed and updated by uploading those YAML files through [Edgeworx Cloud](/docs/cloud/start-portal) or through
 [edgectl]({{<ref "/docs/cloud/adding-nodes/add-node.md">}}). An app can consist of an arbitrary
 number of interacting or standalone microservices that are deployed on one or may nodes.
 

content/en/docs/apps/demo-apps/heart-rate.md

@@ -7,7 +7,7 @@ aliases:
 
 ![Heart Rate Demo App](/images/15done.png)
 
-The Heart Rate app provided on the [Edgeworx Cloud](docs/guides/start-portal) platform simulates a wearable device
+The Heart Rate app provided on the [Edgeworx Cloud](docs/cloud/start-portal) platform simulates a wearable device
 transmitting a person's heartbeat at the edge. The Wearable sends heart rate data over bluetooth to
 a data collector [microservice](/docs/apps/microservices) located on the primary [node](../../cloud/adding-nodes/_index.md). The Data collector microservice then
 communicates with another microservice running a web server on the secondary node to display the

content/en/docs/guides/deploy.md → content/en/docs/apps/deploy.md

@@ -37,7 +37,7 @@ from Docker after following those steps.
 
 ### Add your devices to Edgeworx Cloud
 
-[Edgeworx Cloud](/docs/guides/start-portal) gives you management of all your [edge devices](/docs/cloud/adding-nodes) and [edge applications](/docs/more/terminology/#application) in one place.
+[Edgeworx Cloud](/docs/cloud/start-portal) gives you management of all your [edge devices](/docs/cloud/adding-nodes) and [edge applications](/docs/more/terminology/#application) in one place.
 You can open a SSH shell session on demand, deploy applications, and see the health and status for
 every device. All of this functionality works no matter where your edge devices are physically
 located, even when they are behind NAT layers and firewalls.

content/en/docs/apps/docker-to-edgeworx.md

@@ -8,7 +8,7 @@ aliases:
 There are several
 possible [docker run](https://docs.docker.com/engine/reference/commandline/run/) command line
 options that can be used when spinning up a Docker container. The following docker run commands can
-be directly mapped from a `docker run` command to a [Edgeworx Cloud](/docs/guides/start-portal) YAML configuration file:
+be directly mapped from a `docker run` command to a [Edgeworx Cloud](/docs/cloud/start-portal) YAML configuration file:
 
 1. Volumes
 2. Environment Variables

content/en/docs/apps/microservices.md

@@ -23,7 +23,7 @@ smaller pieces. Key characteristics of microservices:
 
 This definition encapsulate the logic we encourage you to use when deploying edge applications on
 your [nodes](../cloud/adding-nodes/_index.md). But we would add a couple of points to really
-nail the [Edgeworx Cloud](/docs/guides/start-portal) Application
+nail the [Edgeworx Cloud](/docs/cloud/start-portal) Application
 Microservice:
 
 - It is a [docker container](https://www.docker.com/resources/what-container) that runs on your node

content/en/docs/apps/registries.md

@@ -5,7 +5,7 @@ aliases:
   - /edgeworx/edgeworx-cloud/applications-doc/registries
 ---
 
-When configuring an [Edgeworx Cloud](/docs/guides/start-portal) [application](../more/terminology#application) YAML file, it is necessary to specify the registry of
+When configuring an [Edgeworx Cloud](/docs/cloud/start-portal) [application](../more/terminology#application) YAML file, it is necessary to specify the registry of
 each [microservice](./microservices.md) container image. The field for this specification
 is `spec.microservices.image.registry`, and the registry tells the [node](../cloud/adding-nodes/_index.md) the microservice is being
 deployed to how to access the image container.

content/en/docs/apps/yaml-definition.md

@@ -6,7 +6,7 @@ aliases:
   - /docs/cloud/portal/ai-explorer-app/app-yaml/
 ---
 
-[Edgeworx Cloud](/docs/guides/start-portal) uses [Eclipse ioFog](https://iofog.org) under the covers to deploy and manage
+[Edgeworx Cloud](/docs/cloud/start-portal) uses [Eclipse ioFog](https://iofog.org) under the covers to deploy and manage
 [applications](../more/terminology#application), and all Edgeworx applications are deployed to edge [node(s)](../cloud/adding-nodes/_index.md) via a YAML configuration file.
 
 We directly use the ioFog YAML specifications for defining different resource `Kinds`. For

content/en/docs/cloud/adding-nodes/_index.md

@@ -12,7 +12,7 @@ Edge devices are the final point of contact for data from the
 cloud to the end user. An edge node is a physical device with a Linux or equivalent operating system
 that can serve data to an end user from the edge.
 
-In [Edgeworx Cloud](/docs/guides/start-portal), nodes are edge devices that run Edgeworx Agents. Ultimately, we want to deploy
+In [Edgeworx Cloud](/docs/cloud/start-portal), nodes are edge devices that run Edgeworx Agents. Ultimately, we want to deploy
 apps to these nodes to put them to work.
 
 ## AI performance

content/en/docs/cloud/deploy-an-app.md

@@ -10,7 +10,7 @@ Deploy apps using the Edgeworx Portal UI or terminal commands via [edgectl](../c
 
 #### Prerequisites
 
-To deploy your custom app, you will need a [Edgeworx Cloud](/docs/guides/start-portal) account with at least one [node](../cloud/adding-nodes/_index.md) accessible
+To deploy your custom app, you will need a [Edgeworx Cloud](/docs/cloud/start-portal) account with at least one [node](../cloud/adding-nodes/_index.md) accessible
 and `ONLINE`. You will need a basic understanding
 of [how to structure app YAML]({{<ref "/docs/apps/yaml-definition.md">}}) for Edgeworx Cloud.
 

content/en/docs/cloud/edgectl/_index.md

@@ -11,7 +11,7 @@ aliases:
 ---
 
 
-_edgectl_ is [Edgeworx Cloud's](/docs/guides/start-portal) command line interface (CLI). It can be used to manage Edgeworx
+_edgectl_ is [Edgeworx Cloud's](/docs/cloud/start-portal) command line interface (CLI). It can be used to manage Edgeworx
 Cloud
 [accounts, organizations,](/docs/more/terminology/#account--org) [projects](/docs/more/terminology#project), [nodes](/docs/cloud/adding-nodes),
 and [applications](/docs/more/terminology#application).
@@ -22,7 +22,7 @@ deploy some live [microservices](/docs/apps/microservices) to the edge.
 ## Create a Edgeworx Cloud Account
 
 Before installing and using _edgectl_, we must first create an account
-via [Edgeworx Cloud Portal](https://cloud.Edgeworx.io) (see [docs](/docs/guides/start-portal)).
+via [Edgeworx Cloud Portal](https://cloud.Edgeworx.io) (see [docs](/docs/cloud/start-portal)).
 
 Navigate to [Cloud Portal](https://cloud.Edgeworx.io) and click the `Create Account` button in the top
 right.

content/en/docs/cloud/node-remote-access.md

@@ -3,7 +3,7 @@ title: "Remotely access your node"
 weight: 700
 ---
 
-Once your [node](../cloud/adding-nodes/_index.md) is installed and connected to [Edgeworx Cloud](/docs/guides/start-portal), you'll be able to remotely access it using
+Once your [node](../cloud/adding-nodes/_index.md) is installed and connected to [Edgeworx Cloud](/docs/cloud/start-portal), you'll be able to remotely access it using
 the Edgeworx Cloud portal and/or [edgectl]({{<ref "/docs/cloud/edgectl">}}).
 
 ## Prerequisites

layouts/index.html

@@ -38,7 +38,7 @@ <h2>Start Here</h2>
     <section>
       <h2>What is Edgeworx Cloud?</h2>
       <div class="gray-section">
-        <div class="img-fluid-container"><img src="/images/home/map.png" alt="Edgeworx Map" class="img-fluid"/></div>
+        <div class="img-fluid-container"><img src="/images/home/arch-3@2x.png" alt="Edgeworx Map" class="img-fluid"/></div>
         <div class="img-label">
           <div class="title">Edgeworx Cloud is a platform for deploying and managing edge apps and devices</div>
           <div class="subtitle">Build apps in your local environment, deploy them to the edge to Linux devices, and run everything from anywhere using Edgeworx Cloud. </div>