From 60546893304b0172b0b8f1bc96a43bcaf564717a Mon Sep 17 00:00:00 2001 From: workprentice <257153108+workprentice@users.noreply.github.com> Date: Sat, 25 Jul 2026 12:27:04 +0000 Subject: [PATCH] docs(blog): enable FAQPage schema on 14 blog posts with qualifying Q&A headers These posts already contain genuine question-form H2/H3 sections (5-25 each) but were missing the faq_schema: true front-matter flag required by layouts/partials/schema/collectors/faq-entity.html to emit FAQPage JSON-LD. Enabling FAQPage schema on these pages supports both traditional rich-result eligibility and AI answer-engine citation (GEO), consistent with the pattern already shipped on prior comparison/guide pages this week. --- .../index.md | 1 + content/blog/aws-lambda-container-support/index.md | 1 + content/blog/azure-container-solutions/index.md | 1 + .../index.md | 1 + content/blog/developer-experience-business-critical/index.md | 1 + content/blog/embrace-kubernetes-part1/index.md | 1 + content/blog/fast-docker-image-builds-with-pulumi/index.md | 1 + .../generative-ai-apps-devops-talks-pulumi-user-group/index.md | 1 + .../index.md | 1 + .../kubernetes-best-practices-i-wish-i-had-known-before/index.md | 1 + content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md | 1 + content/blog/serverless-api/index.md | 1 + .../index.md | 1 + content/blog/why-switch-to-pulumi/index.md | 1 + 14 files changed, 14 insertions(+) diff --git a/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md b/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md index 88917b1ab780..98e533d4039a 100644 --- a/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md +++ b/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md @@ -7,6 +7,7 @@ authors: ["joe-duffy"] tags: - features category: product +faq_schema: true --- {{% notes type="warning" %}} diff --git a/content/blog/aws-lambda-container-support/index.md b/content/blog/aws-lambda-container-support/index.md index bd9013303dff..f83c613dd72b 100644 --- a/content/blog/aws-lambda-container-support/index.md +++ b/content/blog/aws-lambda-container-support/index.md @@ -14,6 +14,7 @@ tags: - containers - serverless category: tutorials +faq_schema: true --- **TL;DR** — To run a container image in AWS Lambda, build an OCI image that implements the [Lambda Runtime API](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-api.html) (most teams start from an [AWS-provided base image](https://gallery.ecr.aws/lambda/)), push it to Amazon ECR, and create a Lambda function with `packageType: "Image"` pointing at the image URI. Lambda containers support images up to 10 GB, up to 10 GB of memory, up to 10 GB of `/tmp` ephemeral storage, and a 15-minute execution ceiling. Pulumi automates the build, push, and function wiring in a single program. Pick Lambda containers when your workload is event-driven and bursty but your dependencies (binaries, ML models, system libraries) outgrow the 250 MB ZIP limit; pick [AWS Fargate or ECS](/docs/iac/guides/clouds/aws/) when you need long-running tasks, persistent connections, or multi-container pods. diff --git a/content/blog/azure-container-solutions/index.md b/content/blog/azure-container-solutions/index.md index 14e8f5ba2fc9..616dfb75fb88 100644 --- a/content/blog/azure-container-solutions/index.md +++ b/content/blog/azure-container-solutions/index.md @@ -10,6 +10,7 @@ tags: - azure - containers category: general +faq_schema: true --- Containers have emerged as one of the de facto standards for running software. When adopted with the right mindset, they can drastically improve the development lifecycle and help to close the loop between local development and running your applications in the cloud. diff --git a/content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md b/content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md index 9f892f69689d..bc645d4b488d 100644 --- a/content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md +++ b/content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md @@ -41,6 +41,7 @@ social: Read my full analysis of why infrastructure-first platform engineering delivers better outcomes. #PlatformEngineering #Backstage #Pulumi #InfrastructureAsCode #DevOps #CloudNative #InternalDeveloperPlatform +faq_schema: true --- Developers are losing days every month to infrastructure bottlenecks, compliance hurdles, and inconsistent environments. diff --git a/content/blog/developer-experience-business-critical/index.md b/content/blog/developer-experience-business-critical/index.md index 3787de90c058..5384772e20d2 100644 --- a/content/blog/developer-experience-business-critical/index.md +++ b/content/blog/developer-experience-business-critical/index.md @@ -15,6 +15,7 @@ tags: category: general aliases: - /blog/software-developer-experience-devex-devx-devops-culture +faq_schema: true --- "Developer experience is hard to sell," said Cleve Littlefield, Engineering Manager at Pulumi, during a casual meeting. With experience as both an end-user developer and a lead in self-service platform implementation, Cleve's observation stuck with me. diff --git a/content/blog/embrace-kubernetes-part1/index.md b/content/blog/embrace-kubernetes-part1/index.md index 715c93bd1e09..48a6b51d105e 100644 --- a/content/blog/embrace-kubernetes-part1/index.md +++ b/content/blog/embrace-kubernetes-part1/index.md @@ -9,6 +9,7 @@ tags: - kubernetes category: best-practices series: embrace-kubernetes +faq_schema: true --- When you’re considering whether or not to implement Kubernetes, perhaps the first question to ask yourself is do you need it at all? diff --git a/content/blog/fast-docker-image-builds-with-pulumi/index.md b/content/blog/fast-docker-image-builds-with-pulumi/index.md index 2762141c43c8..54d5aafe98a2 100644 --- a/content/blog/fast-docker-image-builds-with-pulumi/index.md +++ b/content/blog/fast-docker-image-builds-with-pulumi/index.md @@ -14,6 +14,7 @@ tags: - providers - features category: best-practices +faq_schema: true --- **How do I speed up Docker image builds with Pulumi?** Use [BuildKit](https://docs.docker.com/build/buildkit/) (the default since Docker 23), enable a registry or layer cache so repeated builds reuse work, write a multi-stage Dockerfile so production images skip build-time dependencies, and reach for the dedicated [Docker Build provider](/registry/packages/docker-build/) when you need buildx features like multi-platform images, build secrets, or Docker Build Cloud. With these techniques together, repeat builds in a Pulumi program commonly drop from minutes to seconds. diff --git a/content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md b/content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md index da2ae942e24a..8b52bf4b6972 100644 --- a/content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md +++ b/content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md @@ -14,6 +14,7 @@ tags: - langchain - ml category: community +faq_schema: true --- The emergence of DevOps revolutionized software development. Now, with AI powered tools like LangChain, these transformations are being accelerated. Unsurprisingly, our distinguished speaker at the launch of Pulumi's in-person AI Talks, Patrick Debois, who coined the term "DevOps," has recently tuned into LLM and GenAI Ops using the Langchain framework. diff --git a/content/blog/helm-release-resource-for-kubernetes-generally-available/index.md b/content/blog/helm-release-resource-for-kubernetes-generally-available/index.md index 0c6cead675d6..a20bea5bbc5a 100644 --- a/content/blog/helm-release-resource-for-kubernetes-generally-available/index.md +++ b/content/blog/helm-release-resource-for-kubernetes-generally-available/index.md @@ -36,6 +36,7 @@ category: product # See the blogging docs at https://github.com/pulumi/docs/blob/master/BLOGGING.md. # for additional details, and please remove these comments before submitting for review. +faq_schema: true --- Back in September 2021 we announced [public preview](/blog/full-access-to-helm-features-through-new-helm-release-resource-for-kubernetes/) for the Helm Release resource in Pulumi's Kubernetes provider. Over the last few months, we have had a very encouraging uptake in usage and several meaningful discussions with users in the community that have helped shape improvements to this resource. Thanks to this collaboration, we are now pleased to announce that the [Helm Release](/registry/packages/kubernetes/api-docs/helm/v3/release/) resource is now **GA** (generally available) starting in [v3.15.0](https://github.com/pulumi/pulumi-kubernetes/releases/tag/v3.15.0) of the Pulumi Kubernetes Provider and SDK in all Pulumi supported languages. We are excited to offer yet another tool to Pulumi users to effectively manage their Kubernetes footprint. diff --git a/content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md b/content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md index c36cfdf4daeb..c869955a99da 100644 --- a/content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md +++ b/content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md @@ -27,6 +27,7 @@ social: Whether you're just starting or looking to refine your Kubernetes setup, these insights will help you navigate the complexities and harness the full power of Kubernetes. +faq_schema: true --- **Kubernetes best practices** are the production-tested rules that keep clusters reliable, secure, and affordable: set resource requests and limits on every container, isolate workloads with namespaces and NetworkPolicies, enforce least-privilege RBAC, automate health checks, ship via GitOps, validate every change with policy-as-code, generate an SBOM for every image, and manage Kubernetes itself with infrastructure as code instead of hand-rolled YAML. The 20 practices below cover what production teams actually do in 2026 — not what tutorials suggest. diff --git a/content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md b/content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md index 453694c3998c..fc8a100f54e5 100644 --- a/content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md +++ b/content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md @@ -39,6 +39,7 @@ social: OpenAI-compatible API access from your existing tooling Read the full guide: +faq_schema: true ---