Resolve merge conflicts: update documentation links and structure

- Remove obsolete Project Structure section from README.md
- Update link paths in infrastructure setup guides to match new directory structure
- Keep updated paths for configuration-setup.mdx, npm-registry-setup.mdx, and project-setup.mdx

Author: cvarma2

CODEOWNERS

@@ -0,0 +1 @@
+* @docusign/1fe

README.md

@@ -52,32 +52,6 @@ yarn dev
 yarn build
 ```
 
-## Project Structure
-
-Inside of this Astro documentation project, you'll see the following folders and files:
-
-```text
-/
-├── public/
-│   ├── favicon.svg
-│   └── robots.txt
-├── src/
-│   ├── content/
-│   │   ├── docs/           # Documentation content
-│   │   │   ├── start-here/
-│   │   │   ├── tutorials/
-│   │   │   ├── learning/
-│   │   │   ├── how-to-guides/
-│   │   │   ├── infrastructure/
-│   │   │   ├── reference/
-│   │   │   └── ...
-│   │   └── config.ts       # Content collections config
-│   ├── components/         # Reusable Astro components
-│   ├── layouts/           # Page layouts
-│   └── assets/            # Images and other assets
-├── astro.config.mjs       # Astro configuration
-└── package.json
-```
 
 Documentation content is written in MDX format and stored in the `src/content/docs/` directory. Each file automatically becomes a page based on its file path.
 

public/robots.txt

@@ -1,2 +1,8 @@
+# 1fe Documentation Site Robots.txt
+# https://1fe.com
+
 User-agent: *
-Disallow: /
+Allow: /
+
+# Crawl delay for respectful crawling (for bots that support it)
+Crawl-delay: 1

src/assets/playground.png

@@ -13,12 +13,12 @@ const { nomargin } = Astro.props;
     "max-w-4xl mx-auto flex flex-col items-center justify-center",
     !nomargin && "mt-24",
   ]}>
-  <Badge color="purple">The 1fe Runtime is alive!</Badge>
+  <Badge color="purple">🚀 Next-Gen Micro-Frontend</Badge>
   <h2 class="text-4xl lg:text-5xl font-bold lg:tracking-tight mt-4 text-center">
-    A Dynamic Runtime
+    Micro-Frontend That <br/><span class="text-purple-600">Actually Works</span>
   </h2>
   <p class="text-lg mt-4 text-slate-600 text-center [text-wrap:pretty]">
-    1fe's configuration-driven runtime pulls and orchestrates widgets independently to stitch together dynamic pages. A living and breathing Ecosystem, when deployed, does not need to be restarted when widgets release.
+    1fe revolutionizes micro-frontend architecture with <strong>live configuration management</strong>. Deploy widgets independently, update instantly, and scale without limits—all while your app keeps running. No restarts. No rebuilds. Just pure dynamic power.
   </p>
 </div>
 
@@ -34,31 +34,28 @@ const { nomargin } = Astro.props;
 
   <div class="grid place-items-center">
     <div class="max-w-lg">
-      <Badge color="purple" class="-ml-px">A Unified App Shell</Badge>
+      <Badge color="purple" class="-ml-px">⚡ Live Configuration Magic</Badge>
       <h3 class="text-2xl font-medium mt-4 [text-wrap:balance]">
-        Standardize Web Utilities Across Products
+        Deploy Once, Update Forever
       </h3>
       <p class="mt-4 text-slate-600 [text-wrap:balance]">
-        The Runtime provides contextual data and configurable web helper utilities to widgets to help them render and interact with the page.
+        Unlike traditional module federation, 1fe's dynamic runtime orchestrates micro-frontends through live configs. Change widget versions, update features, or rollback instantly—all without touching your main app.
       </p>
 
       <ul class="grid mt-6 text-left gap-y-4">
         <li class="flex items-center gap-3 text-neutral-800">
-          <Icon name="ph:check-circle-fill" class="w-5 h-5" aria-hidden="true" />
-
-          <span class="text-sm">Browser Storage</span>
+          <Icon name="ph:check-circle-fill" class="w-5 h-5 text-green-600" aria-hidden="true" />
+          <span class="text-sm"><strong>Zero-Downtime Deployments</strong> - Update widgets while users browse</span>
         </li>
 
         <li class="flex items-center gap-3 text-neutral-800">
-          <Icon name="ph:check-circle-fill" class="w-5 h-5" aria-hidden="true" />
-
-          <span class="text-sm">Event Bus</span>
+          <Icon name="ph:check-circle-fill" class="w-5 h-5 text-green-600" aria-hidden="true" />
+          <span class="text-sm"><strong>Live Config Updates</strong> - No rebuilds, no restarts required</span>
         </li>
 
         <li class="flex items-center gap-3 text-neutral-800">
-          <Icon name="ph:check-circle-fill" class="w-5 h-5" aria-hidden="true" />
-
-          <span class="text-sm">Performance Metrics</span>
+          <Icon name="ph:check-circle-fill" class="w-5 h-5 text-green-600" aria-hidden="true" />
+          <span class="text-sm"><strong>Independent Teams</strong> - Deploy at your own pace, no coordination</span>
         </li>
       </ul>
     </div>

src/components/feature-alt.astro

@@ -1,14 +1,9 @@
 ---
-title: 'CDN Setup for Widget Bundles'
-description: 'Configure CDN hosting for your 1fe widget bundles and static assets'
+title: "CDN Setup for Widget Bundles"
+description: "Configure CDN hosting for your 1fe widget bundles and static assets"
 ---
 
-import {
-  FcFlashOn,
-  FcSettings,
-  FcDeployment,
-  FcGlobe,
-} from "react-icons/fc";
+import { FcFlashOn, FcSettings, FcDeployment, FcGlobe } from "react-icons/fc";
 import {
   FaCloud,
   FaDatabase,
@@ -19,12 +14,7 @@ import {
   FaAws,
   FaGoogle,
 } from "react-icons/fa";
-import {
-  SiAkamai,
-  SiCloudflare,
-  SiFastly,
-  SiJsdelivr,
-} from "react-icons/si";
+import { SiAkamai, SiCloudflare, SiFastly, SiJsdelivr } from "react-icons/si";
 
 <div className="infrastructure-header">
 
@@ -52,9 +42,10 @@ We use Akamai NetStorage to host our widget bundles and static assets, but your
 **Official Documentation:** [Akamai NetStorage User Guide](https://techdocs.akamai.com/netstorage/docs)
 
 :::note[Key Concepts]
+
 - **Storage Group**: A logical container for your content that defines its storage location and replication settings.
 - **Upload Directory**: A specific directory within a Storage Group where you upload your files. Each directory is assigned a unique CP Code (Content Provider Code) which is used to link it to your CDN configuration.
-:::
+  :::
 
 :::note
 NetStorage serves as the origin for your CDN. All widget bundles, assets, and manifests will be stored here and served globally through Akamai's edge network.
@@ -196,7 +187,7 @@ With the storage configured, you can now upload your content using rsync over SS
    Ensure the key file has proper permissions (`chmod 600`).
 
 6. **Store Key Securely**  
-   Store the key securely for CI/CD use. For guidance on adding secrets to your CI/CD pipeline, see the [Secrets Management section](/infrastructure/project-setup/#11-secrets-management).
+   Store the key securely for CI/CD use. For guidance on adding secrets to your CI/CD pipeline, see the [Secrets Management section](/how-to-guides/infrastructure%20setup/project-setup/#11-secrets-management).
 
 </section>
 
@@ -205,7 +196,7 @@ The rsync command uses specific flags for secure, efficient file transfers to Ne
 
 - **[1fe-ci-cd Repository](https://github.com/docusign/1fe-ci-cd)** - Complete CI/CD workflows and deployment scripts
 - **[mock-cdn-assets Repository](https://github.com/docusign/mock-cdn-assets)** - Example asset structures and upload configurations
-:::
+  :::
 
 :::tip[Complete Examples Available]
 For complete rsync command examples and production-ready scripts, see the **[1fe-ci-cd repository](https://github.com/docusign/1fe-ci-cd)** which contains tested deployment workflows.
@@ -215,7 +206,7 @@ For complete rsync command examples and production-ready scripts, see the **[1fe
 
 #### <SiAkamai style={{ display: 'inline', marginRight: '0.5rem', verticalAlign: 'middle', color: '#0096D6' }} /> Step 4: Configure an Akamai CDN Property
 
-The final step is to create a CDN property to serve content from your NetStorage origin. 
+The final step is to create a CDN property to serve content from your NetStorage origin.
 
 **Setup Instructions:**
 
@@ -272,7 +263,8 @@ The final step is to create a CDN property to serve content from your NetStorage
 
 </section>
 
-**Official Documentation:** 
+**Official Documentation:**
+
 - [Property Manager User Guide](https://techdocs.akamai.com/property-mgr/docs)
 - [Creating a New Property](https://techdocs.akamai.com/property-mgr/docs/create-a-new-property)
 
@@ -301,15 +293,17 @@ We have setup two environments for our CDN:
 
 :::note[Environment Separation]
 However, you may setup as many environments as you need. Different environments are used to separate different versions of your widget bundles and static assets, ensuring safe testing and reliable production delivery.
-::: 
+:::
 
 ## Additional Resources
 
 ### 1fe Implementation Resources
+
 - **[1fe-ci-cd Repository](https://github.com/docusign/1fe-ci-cd)** - Complete CI/CD workflows and deployment automation
 - **[mock-cdn-assets Repository](https://github.com/docusign/mock-cdn-assets)** - Example asset structures and configurations
 
 ### Akamai Resources
+
 - **[Akamai Control Center](https://control.akamai.com/)** - Main management interface
 - **[Akamai Developer Portal](https://developer.akamai.com/)** - APIs and automation tools
 - **[Akamai CLI](https://github.com/akamai/cli)** - Command-line interface for automation
@@ -320,22 +314,82 @@ However, you may setup as many environments as you need. Different environments
 While this guide focuses on Akamai CDN setup, you can use other CDN providers for hosting your 1fe widget bundles:
 
 **Cloud Provider CDNs:**
-- <FaAws style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#FF9900' }} /> Amazon CloudFront (AWS)
-- <FaMicrosoft style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#0078D4' }} /> Azure CDN
-- <FaGoogle style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#4285F4' }} /> Google Cloud CDN
+
+- <FaAws
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#FF9900",
+    }}
+  /> Amazon CloudFront (AWS)
+- <FaMicrosoft
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#0078D4",
+    }}
+  /> Azure CDN
+- <FaGoogle
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#4285F4",
+    }}
+  /> Google Cloud CDN
 
 **Modern CDN Services:**
-- <SiCloudflare style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#F38020' }} /> Cloudflare
-- <SiFastly style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#FF282D' }} /> Fastly
-- <FaCloud style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#00AAFF' }} /> KeyCDN
+
+- <SiCloudflare
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#F38020",
+    }}
+  /> Cloudflare
+- <SiFastly
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#FF282D",
+    }}
+  /> Fastly
+- <FaCloud
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#00AAFF",
+    }}
+  /> KeyCDN
 
 **Specialized Solutions:**
-- <SiJsdelivr style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#E84D3D' }} /> JSDelivr
-- <FaNpm style={{ display: 'inline-block', marginRight: '0.5rem', verticalAlign: 'middle', color: '#CB3837' }} /> UnPkg
+
+- <SiJsdelivr
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#E84D3D",
+    }}
+  /> JSDelivr
+- <FaNpm
+    style={{
+      display: "inline-block",
+      marginRight: "0.5rem",
+      verticalAlign: "middle",
+      color: "#CB3837",
+    }}
+  /> UnPkg
 
 ## Next Steps
 
 After setting up your CDN:
-1. [Configure Configuration Service](/infrastructure/configuration-setup/)
-2. [Set up NPM Registry](/infrastructure/npm-registry-setup/)
-3. [Implement CI/CD Integration](/infrastructure/project-setup/) 
+
+1. [Configure Configuration Service](/how-to-guides/infrastructure%20setup/configuration-setup/)
+2. [Set up NPM Registry](/how-to-guides/infrastructure%20setup/npm-registry-setup/)
+3. [Implement CI/CD Integration](/how-to-guides/infrastructure%20setup/project-setup/)