Merge pull request akash-network#76 from HoomanHQ/dharamveer

Refactor hero section and add advert section
zachhorn · Mar 19, 2024 · 4424a62 · 4424a62
2 parents e881f70 + 2a7b38b
commit 4424a62
Show file tree

Hide file tree

Showing 11 changed files with 288 additions and 124 deletions.
diff --git a/src/components/header/hamburger-menu.tsx b/src/components/header/hamburger-menu.tsx
@@ -90,13 +90,13 @@ const Panel = ({ currentPath, open }: { currentPath: string; open: any }) => {
             </a>
 
             <div className="flex items-center gap-5">
-              <Disclosure.Button
+              {/* <Disclosure.Button
                 as="a"
                 href={"/#getting-started"}
                 className="flex items-center justify-center rounded-[4px] bg-[#FF414C] px-[11px] py-[7px] text-xs text-white"
               >
                 Get Started
-              </Disclosure.Button>
+              </Disclosure.Button> */}
 
               <Disclosure.Button className="inline-flex items-center justify-center">
                 <span className="sr-only">Open main menu</span>

diff --git a/src/components/home/hero/hero.astro b/src/components/home/hero/hero.astro
@@ -1,5 +1,11 @@
 ---
 import Button from "@/components/ui/button-link.astro";
+import type { CollectionEntry } from "astro:content";
+
+interface Props {
+  heroSection: CollectionEntry<"Homepage">["data"]["heroSection"];
+}
+
 const { heroSection } = Astro.props;
 ---
 
@@ -20,44 +26,29 @@ const { heroSection } = Astro.props;
     </p>
     <!-- buttons -->
 
-    <div class="mx-auto mt-12 flex w-fit flex-row gap-x-3 md:hidden">
-      <Button
-        aria-label={heroSection.primaryButton.label}
-        link={heroSection.primaryButton.link}
-        variant="secondary"
-        size="lg"
-      >
-        {heroSection.primaryButton.label}
-      </Button>
-
-      <Button
-        aria-label={heroSection.secondaryButton.label}
-        link={heroSection.secondaryButton.link}
-        size="lg"
-        target="_blank"
-      >
-        {heroSection.secondaryButton.label}
-      </Button>
-    </div>
-
-    <div class="mx-auto mt-8 hidden w-fit flex-row gap-x-5 md:flex">
-      <Button
-        aria-label={heroSection.primaryButton.label}
-        link={heroSection.primaryButton.link}
-        variant="secondary"
-        size="xl"
-      >
-        {heroSection.primaryButton.label}
-      </Button>
-
-      <Button
-        aria-label={heroSection.secondaryButton.label}
-        target="_blank"
-        link={heroSection.secondaryButton.link}
-        size="xl"
-      >
-        {heroSection.secondaryButton.label}
-      </Button>
+    <div
+      class="mx-auto mt-20 grid w-fit gap-6 sm:grid-cols-2 md:mt-16 lg:grid-cols-3"
+    >
+      {
+        heroSection.cards.map((card, index) => (
+          <div class="flex flex-col gap-2 rounded-lg border bg-background2 p-6 md:rounded-xl">
+            <h1 class="font-base font-bold">{card.title}</h1>
+            <p class="text-sm ">{card.description}</p>
+            <div class="mt-auto flex flex-wrap gap-2 pt-2">
+              {card.buttons.map((button, index) => (
+                <Button
+                  aria-label={button.label}
+                  link={button.link}
+                  variant={button.type}
+                  size="lg"
+                >
+                  {button.label}
+                </Button>
+              ))}
+            </div>
+          </div>
+        ))
+      }
     </div>
   </div>
 </section>
diff --git a/src/content/Docs/providers/build-a-cloud-provider/gpu-resource-enablement/index.md b/src/content/Docs/providers/build-a-cloud-provider/gpu-resource-enablement/index.md
@@ -13,7 +13,7 @@ The steps involved in enabling your Akash Provider to host GPU resources are cov
 - [Apply NVIDIA Runtime Engine](#apply-nvidia-runtime-engine)
 - [Update Akash Provider](#update-akash-provider)
 - [GPU Test Deployments](#gpu-test-deployments)
-- [GPU Provider Troubleshooting](../../../../providers/akash-provider-troubleshooting/gpu-provider-troubleshooting)
+- [GPU Provider Troubleshooting](/docs/providers/provider-faq-and-guide/#gpu-provider-troubleshooting)
 
 ## GPU Provider Configuration
 

diff --git a/...nt/Docs/providers/build-a-cloud-provider/ip-leases-provider-enablement/index.md b/...nt/Docs/providers/build-a-cloud-provider/ip-leases-provider-enablement/index.md
@@ -41,9 +41,9 @@ In this guide we present paths to install MetalLB both via Helm Charts and Kubes
 
 Sections within this guide:
 
-- [New MetalLB Deployment via Helm](metallb-install.md#option-1-deploy-metallb-with-helm)
-- [New MetalLB Deployment via Kubespray](metallb-install.md#option-2-deploy-metallb-using-kubespray)
-- [Migration of MetalLB Version 0.12.X to 0.13.x](metallb-install.md#migrating-metallb-0.12.x-to-0.13.x)
+- [New MetalLB Deployment via Helm](#option-1-deploy-metallb-with-helm)
+- [New MetalLB Deployment via Kubespray](#option-2-deploy-metallb-using-kubespray)
+- [Migration of MetalLB Version 0.12.X to 0.13.x](#migrating-metallb-012x-to-013x)
 
 ### Option 1: Deploy MetalLB with Helm
 

diff --git a/...ovider/kubernetes-cluster-for-akash-providers/additional-k8s-resources/index.md b/...ovider/kubernetes-cluster-for-akash-providers/additional-k8s-resources/index.md
@@ -12,31 +12,45 @@ linkTitle: "Additional K8s Resources"
 
 The Kubespray hosts.yaml inventory file is composed of 3 groups:
 
-* **kube\_node**: list of Kubernetes nodes where the pods will run.
-* **kube\_control\_plane**: list of servers where Kubernetes control plane components (apiserver, scheduler, controller) will run.
-* **etcd**: list of servers to compose the etcd server. You should have at least 3 servers for failover purpose.
+- **kube_node**: list of Kubernetes nodes where the pods will run.
+- **kube_control_plane**: list of servers where Kubernetes control plane components (apiserver, scheduler, controller) will run.
+- **etcd**: list of servers to compose the etcd server. You should have at least 3 servers for failover purpose.
 
 Please following these links for YAML examples and depending on your preferred topology:
 
-* [All-In-One Node](kubespray-hosts.yaml-examples.md#all-in-one-node)
-* [One Control Plane Node with Multiple Worker Nodes](kubespray-hosts.yaml-examples.md#one-control-plane-node-with-multiple-worker-nodes)
-* [Multiple Control Plane Nodes with Multiple Work Nodes](kubespray-hosts.yaml-examples.md#multiple-control-plane-nodes-with-multiple-work-nodes)
+- [Kubespray Hosts.Yaml Examples](#kubespray-hostsyaml-examples)
+  - [Hosts.Yaml Overview](#hostsyaml-overview)
+- [All-In-One Node](#all-in-one-node)
+  - [Topology](#topology)
+  - [ Pros](#-pros)
+  - [Cons](#cons)
+  - [Example Hosts.yaml File](#example-hostsyaml-file)
+- [One Control Plane Node with Multiple Worker Nodes](#one-control-plane-node-with-multiple-worker-nodes)
+  - [Topology](#topology-1)
+  - [Pros](#pros)
+  - [Cons](#cons-1)
+  - [Example Hosts.yaml File](#example-hostsyaml-file-1)
+- [Multiple Control Plane Nodes with Multiple Work Nodes](#multiple-control-plane-nodes-with-multiple-work-nodes)
+  - [Topology](#topology-2)
+  - [Pros](#pros-1)
+  - [Cons](#cons-2)
+  - [Example Hosts.yaml File](#example-hostsyaml-file-2)
 
 ## All-In-One Node
 
 ### Topology
 
-* node1 - is a single control plane + etcd node
-* node1 - is also running the pods
+- node1 - is a single control plane + etcd node
+- node1 - is also running the pods
 
 ### &#x20;Pros
 
-* Easy to manage
+- Easy to manage
 
 ### Cons
 
-* Single point of failure for K8s/etcd/pods;
-* Thinner security barrier since pods are running on control plane / etcd nodes;
+- Single point of failure for K8s/etcd/pods;
+- Thinner security barrier since pods are running on control plane / etcd nodes;
 
 ### Example Hosts.yaml File
 
@@ -63,17 +77,17 @@ Please following these links for YAML examples and depending on your preferred t
 
 ### Topology
 
-* node1 - single control plane + etcd node
-* node2..N - kube nodes where the pods will run
+- node1 - single control plane + etcd node
+- node2..N - kube nodes where the pods will run
 
 ### Pros
 
-* Better security barrier since pods aren't running on control plane / etcd nodes
-* Can scale by adding either more control plane nodes or worker nodes
+- Better security barrier since pods aren't running on control plane / etcd nodes
+- Can scale by adding either more control plane nodes or worker nodes
 
 ### Cons
 
-* Single point of failure only for K8s/etcd but not the pods
+- Single point of failure only for K8s/etcd but not the pods
 
 ### Example Hosts.yaml File
 
@@ -101,18 +115,18 @@ Please following these links for YAML examples and depending on your preferred t
 
 ### Topology
 
-* Nodes 1.-3 -  the control plane + etcd nodes; (This makes K8s High Available)
-* Node 4.-N -  the kube nodes on which the Pods will run
+- Nodes 1.-3 - the control plane + etcd nodes; (This makes K8s High Available)
+- Node 4.-N - the kube nodes on which the Pods will run
 
 ### Pros
 
-* Highly available control plane / etcd
-* Better security barrier since pods aren't running on control plane / etcd nodes
-* Can scale by adding either more control plane nodes or worker nodes
+- Highly available control plane / etcd
+- Better security barrier since pods aren't running on control plane / etcd nodes
+- Can scale by adding either more control plane nodes or worker nodes
 
 ### Cons
 
-* More complex environment makes its configuration & management more difficult
+- More complex environment makes its configuration & management more difficult
 
 ### Example Hosts.yaml File
 
@@ -139,4 +153,4 @@ Please following these links for YAML examples and depending on your preferred t
         kube_node:
     calico_rr:
       hosts: {}
-```
+```