Add Resource Library section

archetypes/resources/index.md

@@ -0,0 +1,52 @@
+---
+title: "{{ replace .Name "-" " " | title }}"
+date: {{ .Date }}
+draft: false
+
+# SEO and social
+meta_desc: ""
+meta_image: meta.png
+title_tag: ""
+
+# Resource library taxonomy
+solution_areas:
+    # - infrastructure-unification
+    # - security-compliance
+    # - ai-ready-infrastructure
+
+content_type: ""
+    # ecosystem-overview | comparison-guide | solution-guide
+
+capabilities:
+    # - ai-and-automation
+    # - policy-as-code
+    # - secrets-management
+    # - multi-cloud
+    # - kubernetes
+    # - internal-developer-platforms
+    # - drift-detection
+    # - compliance
+
+funnel_stage: ""
+    # problem-aware | solution-aware | evaluation
+
+target_personas:
+    # - platform-engineer
+    # - security-compliance-lead
+    # - devops-engineer
+    # - engineering-leader
+
+# Editorial
+authors:
+    - ""
+tags:
+    - ""
+featured: false
+featured_weight: 0
+
+# AEO metadata
+last_reviewed: {{ .Date }}
+faq:
+    - question: ""
+      answer: ""
+---

content/resources/_index.md

@@ -0,0 +1,7 @@
+---
+title: Resource Library
+meta_desc: "Guides, comparisons, and solutions for infrastructure as code, cloud security, compliance, and platform engineering."
+type: resources
+---
+
+Explore in-depth guides comparing infrastructure as code platforms, evaluating cloud security tools, and scaling platform engineering with Pulumi. Whether you're choosing your first IaC tool or migrating from Terraform, these resources help you make informed decisions.

content/resources/infrastructure-unification/_index.md

@@ -0,0 +1,59 @@
+---
+title: "Infrastructure Unification"
+meta_desc: "Guides, comparisons, and evaluations for unifying cloud infrastructure management across teams, tools, and clouds with Pulumi."
+meta_image: /images/docs/meta-images/docs-meta.png
+type: resources
+tagline: "One platform for all your clouds, tools, and teams"
+last_reviewed: 2026-03-11
+related_capabilities:
+  - ai-and-automation
+  - multi-cloud
+  - kubernetes
+related_areas:
+  - security-compliance
+  - ai-ready-infrastructure
+cta:
+  text: "Get started with Pulumi"
+  url: "/docs/get-started/"
+faq:
+  - question: "What is infrastructure unification?"
+    answer: "Infrastructure unification is the practice of managing all cloud resources, regardless of provider or deployment target, through a single platform and workflow. Rather than maintaining separate tools for AWS, Azure, GCP, and Kubernetes, teams use one consistent approach for defining, deploying, and managing infrastructure everywhere."
+  - question: "Why do teams struggle with multi-cloud infrastructure management?"
+    answer: "Most organizations accumulate multiple infrastructure tools over time: Terraform for some resources, CloudFormation for AWS-specific workloads, Helm for Kubernetes, and custom scripts for everything else. Each tool has its own language, state management, and workflows. This fragmentation creates knowledge silos, slows deployment velocity, and makes it difficult to enforce consistent policies across environments."
+  - question: "How does Pulumi help unify infrastructure management?"
+    answer: "Pulumi lets teams define infrastructure for any cloud provider using general-purpose programming languages like Python, TypeScript, Go, C#, Java, or even HCL and YAML. With support for over 180 providers and native integrations for AWS, Azure, GCP, and Kubernetes, teams can manage everything from a single platform with consistent state management, policy enforcement, and deployment workflows."
+  - question: "Can I use Pulumi alongside existing Terraform configurations?"
+    answer: "Yes. Pulumi Cloud can manage Terraform and OpenTofu state directly, and Pulumi Insights provides visibility across resources managed by any IaC tool. Teams can adopt Pulumi incrementally, keeping existing configurations while migrating workloads at their own pace."
+---
+
+Infrastructure unification is the practice of managing all your cloud resources through a single platform and workflow, regardless of which cloud providers or deployment targets you use. For platform engineering teams supporting dozens or hundreds of developers, unifying infrastructure management eliminates the tool sprawl and knowledge silos that slow delivery.
+
+## The challenge: infrastructure fragmentation
+
+If you manage infrastructure across multiple clouds, you've likely experienced this firsthand. AWS workloads run through CloudFormation or Terraform. Kubernetes clusters have their own Helm charts and manifests. Azure resources use ARM templates or a separate Terraform workspace. Each tool brings its own language, state backend, and operational model.
+
+This fragmentation hits platform teams hardest. A small infrastructure group (typically 2 to 10 engineers) supports 50 to 500+ developers, and every tool boundary creates a context switch. When only one or two people understand each toolchain, knowledge becomes concentrated, reviews become bottlenecks, and deployment velocity collapses. What should take hours takes days.
+
+The problem compounds at scale. As resource counts grow into the thousands, state management becomes unwieldy, drift goes undetected, and enforcing consistent security policies across disparate tools becomes nearly impossible.
+
+## How Pulumi addresses infrastructure unification
+
+Pulumi approaches this problem by letting teams choose their preferred programming language for all infrastructure, across all clouds, in a single platform.
+
+**Language flexibility across any cloud.** Pulumi supports Python, TypeScript, Go, C#, Java, HCL, and YAML. With over 180 cloud providers, including native support for AWS, Azure, GCP, and Kubernetes, teams can manage every resource from one place. The same language, testing framework, and CI/CD pipeline work whether you're provisioning an S3 bucket, an AKS cluster, or a Cloudflare Worker.
+
+**Software engineering for infrastructure.** Because Pulumi uses general-purpose languages, teams get the full power of software engineering: loops, conditionals, functions, classes, package managers, unit tests, and IDE support. Reusable components can be shared as libraries across teams, turning proven patterns into organizational standards.
+
+**AI-native and agent-ready.** AI coding agents already understand Python and TypeScript. Pulumi's language-native approach means infrastructure can participate in the same AI-assisted development workflows as application code, with agents that can preview changes, check policies, and open pull requests in tight feedback loops. [Pulumi Neo](/product/neo/) brings this capability directly into your infrastructure workflow.
+
+**Unified visibility and governance.** [Pulumi Insights](/product/pulumi-insights/) provides search and visibility across all cloud resources, regardless of which IaC tool manages them. Combined with [Pulumi Policies](/product/pulumi-policies/) for policy as code, teams get consistent governance across every environment.
+
+For a detailed comparison of the tools available for unifying infrastructure management, see our [Infrastructure as Code Tools Guide](/resources/infrastructure-unification/infrastructure-as-code-tools/). To understand how AI is changing infrastructure automation, explore our [AI Infrastructure Tools Guide](/resources/infrastructure-unification/ai-infrastructure-tools/).
+
+## Key capabilities
+
+**Multi-cloud management.** Define and deploy resources across AWS, Azure, GCP, Kubernetes, and 180+ providers from a single program. No need for provider-specific tooling or separate workflows.
+
+**Kubernetes integration.** Pulumi provides native Kubernetes support with full access to the Kubernetes API, including CRDs. Manage clusters, workloads, and cloud resources together in the same program.
+
+**AI-powered automation.** Pulumi Neo can analyze existing infrastructure, suggest improvements, enforce policies, and accelerate migrations from tools like Terraform, CloudFormation, and CDK. Teams using Pulumi have reduced infrastructure change cycles from weeks to hours.