chore: move 'foundations' to 'core concepts'

jyecusch · jyecusch · commit 9d8c550546b1 · 2025-11-12T09:56:25.000+11:00
diff --git a/docs/core/deployment.mdx b/docs/core/deployment.mdx
@@ -394,7 +394,7 @@ terraform plan
 ## Learn More
 
 <CardGroup cols={2}>
-  <Card title="Infrastructure Generation" icon="hammer" href="/foundations/infrastructure-generation">
+  <Card title="Infrastructure Generation" icon="hammer" href="/core/infrastructure-generation">
     Understand how Terraform is generated
   </Card>
 
@@ -406,7 +406,7 @@ terraform plan
     Best practices for Terraform configuration
   </Card>
 
-  <Card title="Local Development" icon="laptop" href="/foundations/local-development">
+  <Card title="Local Development" icon="laptop" href="/core/local-development">
    How to develop applications locally with Suga
   </Card>
 </CardGroup>
diff --git a/docs/core/infrastructure-generation.mdx b/docs/core/infrastructure-generation.mdx
@@ -180,7 +180,7 @@ terraform plan  # Review before apply
 ## Learn More
 
 <CardGroup cols={2}>
-  <Card title="Deployment Guide" icon="rocket" href="/foundations/deployment">
+  <Card title="Deployment Guide" icon="rocket" href="/core/deployment">
     Understand the deployment process
   </Card>
 
diff --git a/docs/core/local-development.mdx b/docs/core/local-development.mdx
@@ -324,7 +324,7 @@ For features that can't be emulated:
 2. **Mock externals** - Use mocks for cloud-specific APIs
 3. **Integration tests** - Test cloud features in CI/CD pipelines
 
-<Card title="Deployment Guide" icon="rocket" href="/foundations/deployment" horizontal>
+<Card title="Deployment Guide" icon="rocket" href="/core/deployment" horizontal>
   Learn how to deploy to cloud environments for testing
 </Card>
 
@@ -343,7 +343,7 @@ For features that can't be emulated:
     Configure databases and connection strings
   </Card>
 
-  <Card title="Deployment" icon="cloud" href="/foundations/deployment">
+  <Card title="Deployment" icon="cloud" href="/core/deployment">
     Deploy to cloud after local testing
   </Card>
 </CardGroup>
diff --git a/docs/core/overview.mdx b/docs/core/overview.mdx
@@ -1,9 +1,9 @@
 ---
-title: "Foundations Overview"
+title: "Core Concepts Overview"
 description: "Understanding Suga's architecture and core concepts"
 ---
 
-Suga is built on a clear separation of concerns that enables both developer productivity and platform governance. Understanding these foundations will help you make the most of the platform.
+Suga is built on a clear separation of concerns that enables both developer productivity and platform governance. Understanding these core concepts will help you make the most of the platform.
 
 ## The Suga Architecture
 
@@ -23,7 +23,7 @@ graph TB
 
 ### 1. Projects: What You Want
 
-[Projects](/foundations/projects) are your application specifications - declarative YAML files that describe what your application needs:
+[Projects](/core/projects) are your application specifications - declarative YAML files that describe what your application needs:
 
 - **Services** - Application containers that run your code
 - **Buckets** - Cloud storage for files and assets
@@ -54,7 +54,7 @@ entrypoints:
 
 ### 2. Platforms: How to Build It
 
-[Platforms](/foundations/platforms) are blueprints that map your project's abstract resources to specific cloud implementations. They define:
+[Platforms](/core/platforms) are blueprints that map your project's abstract resources to specific cloud implementations. They define:
 
 - Which cloud services to use (Lambda vs Fargate, S3 vs Cloud Storage)
 - How to configure those services (memory, CPU, networking)
@@ -65,7 +65,7 @@ Platform teams create and publish platforms to enforce organizational standards
 
 ### 3. Plugins: Cloud Resources
 
-[Plugins](/foundations/plugins) are the lowest-level building blocks - reusable Terraform modules that provision specific cloud resources. Each plugin contains:
+[Plugins](/core/plugins) are the lowest-level building blocks - reusable Terraform modules that provision specific cloud resources. Each plugin contains:
 
 - **Terraform module** - Infrastructure-as-code for a specific cloud service
 - **Input schema** - Configuration properties the module accepts
@@ -263,30 +263,30 @@ Enable teams to work independently while maintaining consistency:
 
 ## Next Steps
 
-Now that you understand Suga's foundations, dive deeper into each component:
+Now that you understand Suga's core concepts, dive deeper into each component:
 
 <CardGroup cols={2}>
-  <Card title="Projects" icon="file-code" href="/foundations/projects">
+  <Card title="Projects" icon="file-code" href="/core/projects">
     Learn how to define application requirements
   </Card>
 
-  <Card title="Platforms" icon="layers" href="/foundations/platforms">
+  <Card title="Platforms" icon="layers" href="/core/platforms">
     Understand platform blueprints and governance
   </Card>
 
-  <Card title="Plugins" icon="puzzle" href="/foundations/plugins">
+  <Card title="Plugins" icon="puzzle" href="/core/plugins">
     Explore the building blocks of infrastructure
   </Card>
 
-  <Card title="Infrastructure Generation" icon="cog" href="/foundations/infrastructure-generation">
+  <Card title="Infrastructure Generation" icon="cog" href="/core/infrastructure-generation">
     See how Suga transforms projects into Terraform
   </Card>
 
-  <Card title="Local Development" icon="laptop" href="/foundations/local-development">
+  <Card title="Local Development" icon="laptop" href="/core/local-development">
     Master local development workflow
   </Card>
 
-  <Card title="Deployment" icon="rocket" href="/foundations/deployment">
+  <Card title="Deployment" icon="rocket" href="/core/deployment">
     Understand deployment and operations
   </Card>
 </CardGroup>
diff --git a/docs/core/platforms.mdx b/docs/core/platforms.mdx
@@ -3,7 +3,7 @@ title: "Platforms"
 description: "Understanding Suga's platforms and ecosystem"
 ---
 
-Platforms in Suga solve a critical challenge: delivering the seamless developer experience of modern deployment platforms while maintaining enterprise control and flexibility. They're blueprints that transform application specifications ([Projects](/foundations/projects)) into deployable infrastructure by generating Terraform HCL and providing runtime adapters that translate abstract resource operations into cloud-specific API calls.
+Platforms in Suga solve a critical challenge: delivering the seamless developer experience of modern deployment platforms while maintaining enterprise control and flexibility. They're blueprints that transform application specifications ([Projects](/core/projects)) into deployable infrastructure by generating Terraform HCL and providing runtime adapters that translate abstract resource operations into cloud-specific API calls.
 
 Platform teams can create, customize, and govern these distributed packages to provide developers with instant deployments, automatic scaling, and zero-configuration infrastructure, while maintaining full control over security, compliance, and infrastructure standards.
 
@@ -68,7 +68,7 @@ Platforms operate through two key mechanisms: **Infrastructure Generation** and
 
 ### Infrastructure Generation
 
-When you run `suga build`, Suga uses your target platform to transform your [Project](/foundations/projects) specification into cloud-specific Terraform HCL (called stacks). This process:
+When you run `suga build`, Suga uses your target platform to transform your [Project](/core/projects) specification into cloud-specific Terraform HCL (called stacks). This process:
 
 1. **Maps abstract resources** - Takes your high-level resource definitions (services, buckets, databases) and selects appropriate cloud implementations
 2. **Generates Terraform modules** - Creates infrastructure-as-code that provisions actual cloud resources with proper networking, security, and permissions
diff --git a/docs/core/plugins.mdx b/docs/core/plugins.mdx
@@ -269,7 +269,7 @@ Organizations can create custom plugins for:
     Create custom plugins for your needs
   </Card>
 
-  <Card title="Infrastructure Generation" icon="cog" href="/foundations/infrastructure-generation">
+  <Card title="Infrastructure Generation" icon="cog" href="/core/infrastructure-generation">
     See how plugins generate Terraform
   </Card>
 
diff --git a/docs/core/projects.mdx b/docs/core/projects.mdx
@@ -7,7 +7,7 @@ Projects in Suga are application specifications that define your cloud architect
 
 ## What is a Project?
 
-A Suga project is defined by a `suga.yaml` file that describes your application's infrastructure requirements using cloud-agnostic resource types. When combined with a [Platform](/foundations/platforms), this specification gets transformed into deployable cloud infrastructure.
+A Suga project is defined by a `suga.yaml` file that describes your application's infrastructure requirements using cloud-agnostic resource types. When combined with a [Platform](/core/platforms), this specification gets transformed into deployable cloud infrastructure.
 
 <Tabs>
   <Tab title="Suga Project Editor" icon="monitor-cog">
diff --git a/docs/deploy/aws.mdx b/docs/deploy/aws.mdx
@@ -36,6 +36,6 @@ terraform init
 terraform apply
 ```
 
-<Card title="Complete Deployment Guide" icon="rocket" href="/foundations/deployment" horizontal>
+<Card title="Complete Deployment Guide" icon="rocket" href="/core/deployment" horizontal>
   See the full deployment workflow
 </Card>
diff --git a/docs/deploy/gcp.mdx b/docs/deploy/gcp.mdx
@@ -35,6 +35,6 @@ terraform init
 terraform apply
 ```
 
-<Card title="Complete Deployment Guide" icon="rocket" href="/foundations/deployment" horizontal>
+<Card title="Complete Deployment Guide" icon="rocket" href="/core/deployment" horizontal>
   See the full deployment workflow
 </Card>
diff --git a/docs/deploy/overview.mdx b/docs/deploy/overview.mdx
@@ -5,8 +5,8 @@ description: "Overview of deploying Suga applications to cloud providers"
 
 Deploying with Suga means running standard Terraform commands on infrastructure generated by `suga build`.
 
-<Card title="Complete Deployment Guide" icon="rocket" href="/foundations/deployment" horizontal>
-  See the comprehensive deployment guide in Foundations
+<Card title="Complete Deployment Guide" icon="rocket" href="/core/deployment" horizontal>
+  See the comprehensive deployment guide in Core Concepts
 </Card>
 
 ## Quick Links
diff --git a/docs/develop/access-control.mdx b/docs/develop/access-control.mdx
@@ -86,7 +86,7 @@ When using the standard Suga AWS Platforms (`suga/aws`), here is an example of t
 ```
 
 <Note>
-  If you use your own Suga [resource plugins](/foundations/plugins), you're free to construct the IAM, roles, etc. as you see fit.
+  If you use your own Suga [resource plugins](/core/plugins), you're free to construct the IAM, roles, etc. as you see fit.
 </Note>
 
 ## Best Practices
diff --git a/docs/develop/buckets.mdx b/docs/develop/buckets.mdx
@@ -139,7 +139,7 @@ You can:
 - Seed buckets by placing files there
 - Test bucket operations without cloud access
 
-<Card title="Local Development" icon="laptop" href="/foundations/local-development" horizontal>
+<Card title="Local Development" icon="laptop" href="/core/local-development" horizontal>
   Learn how to develop applications locally with Suga
 </Card>
 
@@ -158,7 +158,7 @@ You can:
     Deploy static websites
   </Card>
 
-  <Card title="Local Development" icon="laptop" href="/foundations/local-development">
+  <Card title="Local Development" icon="laptop" href="/core/local-development">
     Test buckets locally
   </Card>
 </CardGroup>
diff --git a/docs/develop/databases.mdx b/docs/develop/databases.mdx
@@ -255,7 +255,7 @@ suga dev
 
 Your services receive `DATABASE_URL` (or your custom `env_var_key`) automatically, making the same code work in both local development and production.
 
-<Card title="Local Development Guide" icon="laptop" href="/foundations/local-development" horizontal>
+<Card title="Local Development Guide" icon="laptop" href="/core/local-development" horizontal>
   Learn more about local development with databases
 </Card>
 
@@ -270,7 +270,7 @@ Your services receive `DATABASE_URL` (or your custom `env_var_key`) automaticall
     Schema management
   </Card>
 
-  <Card title="Local Development" icon="laptop" href="/foundations/local-development">
+  <Card title="Local Development" icon="laptop" href="/core/local-development">
     Local PostgreSQL during suga dev
   </Card>
 
diff --git a/docs/develop/entrypoints.mdx b/docs/develop/entrypoints.mdx
@@ -43,7 +43,7 @@ Routes are evaluated in order - most specific first.
 ## Custom Domains
 
 <Note>
-  Most entrypoints support custom domains, however, this functionality is [platform](/foundations/platforms.mdx) specific.
+  Most entrypoints support custom domains, however, this functionality is [platform](/core/platforms.mdx) specific.
 
   For example, the `suga/aws` platform will generate Terraform Variables during `suga build`, which allow you to specify a custom domain per entrypoint.
 </Note>
diff --git a/docs/develop/overview.mdx b/docs/develop/overview.mdx
@@ -129,7 +129,7 @@ entrypoints:
     subtype: cloudfront   # AWS CloudFront
 ```
 
-The available subtypes depend on your target [platform](/foundations/platforms):
+The available subtypes depend on your target [platform](/core/platforms):
 - `suga/aws@1` - Lambda, Fargate, S3, CloudFront
 - `suga/gcp@1` - Cloud Run, Cloud Storage, Cloud CDN
 - `you/custom@1` - Any other cloud or resources you like, including cross-cloud deployments
diff --git a/docs/develop/services.mdx b/docs/develop/services.mdx
@@ -211,7 +211,7 @@ Services interact with resources like buckets using generated Suga client librar
     Grant resource access
   </Card>
 
-  <Card title="Local Development" icon="laptop" href="/foundations/local-development">
+  <Card title="Local Development" icon="laptop" href="/core/local-development">
     Test services locally
   </Card>
 
diff --git a/docs/develop/suga-client.mdx b/docs/develop/suga-client.mdx
@@ -236,7 +236,7 @@ You can mix both approaches - use Suga clients for common operations and native
     Complete API documentation
   </Card>
 
-  <Card title="Local Development" icon="laptop" href="/foundations/local-development">
+  <Card title="Local Development" icon="laptop" href="/core/local-development">
     Learn about local development workflow
   </Card>
 
diff --git a/docs/docs.json b/docs/docs.json
@@ -22,15 +22,15 @@
             "pages": ["introduction", "why-suga", "installation", "quickstart"]
           },
           {
-            "group": "Foundations",
+            "group": "Core Concepts",
             "pages": [
-              "foundations/overview",
-              "foundations/projects",
-              "foundations/platforms",
-              "foundations/plugins",
-              "foundations/infrastructure-generation",
-              "foundations/local-development",
-              "foundations/deployment"
+              "core/overview",
+              "core/projects",
+              "core/platforms",
+              "core/plugins",
+              "core/infrastructure-generation",
+              "core/local-development",
+              "core/deployment"
             ]
           },
           {
@@ -42,7 +42,6 @@
               "develop/buckets",
               "develop/databases",
               "develop/suga-client",
-              "develop/environment-variables",
               "develop/access-control"
             ]
           },
@@ -211,11 +210,11 @@
   "redirects": [
     {
       "source": "/projects",
-      "destination": "/foundations/projects"
+      "destination": "/core/projects"
     },
     {
       "source": "/platforms",
-      "destination": "/foundations/platforms"
+      "destination": "/core/platforms"
     }
   ]
 }
diff --git a/docs/faq.mdx b/docs/faq.mdx
@@ -113,7 +113,7 @@ Yes! Suga works with Express, FastAPI, Django, Go HTTP, and any other framework
 
 ### How do I debug services locally?
 
-Use your language's standard debugger with `suga dev`. See the [Local Development](/foundations/local-development) guide.
+Use your language's standard debugger with `suga dev`. See the [Local Development](/core/local-development) guide.
 
 ### Can services communicate with each other?
 
diff --git a/docs/guides/build-platform.mdx b/docs/guides/build-platform.mdx
diff --git a/docs/guides/plugin-development.mdx b/docs/guides/plugin-development.mdx
diff --git a/docs/guides/static-website-hosting.mdx b/docs/guides/static-website-hosting.mdx
diff --git a/docs/quickstart.mdx b/docs/quickstart.mdx
diff --git a/docs/support.mdx b/docs/support.mdx
diff --git a/docs/why-suga.mdx b/docs/why-suga.mdx
