fix: add truncation markers to blog posts

osterman · claude · osterman · commit 6bf9d9261021 · 2026-01-06T16:32:35.000-06:00
Add  markers after the intro section in all blog posts that were missing them to eliminate Docusaurus build warnings. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
diff --git a/blog/2024-11-12-terraform-repo-move.mdx b/blog/2024-11-12-terraform-repo-move.mdx
@@ -13,6 +13,8 @@ import Steps from '@site/src/components/Steps';
 The GitHub repository for Cloud Posse's Terraform components has migrated to a dedicated GitHub organization. All documentation remains here, but all future updates, contributions, and issue tracking for the source code should now be directed to the respective repositories in the new organization.
 </Intro>
 
+<!--truncate-->
+
 # Hello, Cloud Posse Community!
 
 We're excited to announce that starting on November 12, 2024, we will begin migrating each component in the `cloudposse/terraform-aws-components` repository to individual repositories under a new GitHub organization. This change aims to improve the stability, maintainability, and usability of our components.
diff --git a/blog/2025-03-21-automated-component-testing.mdx b/blog/2025-03-21-automated-component-testing.mdx
@@ -12,6 +12,8 @@ import Intro from '@site/src/components/Intro';
 We're excited to announce the completion of the second phase of our Component Testing project, which has added automated testing for 27 components. This milestone follows our successful migration of 160+ Terraform Components from a monorepo to individual repositories, making them more maintainable and testable.
 </Intro>
 
+<!--truncate-->
+
 Hello SweetOps!
 
 A few months ago, we embarked on a MASSIVE project to enable Component Testing.
diff --git a/blog/2025-06-01-platform-advisory.mdx b/blog/2025-06-01-platform-advisory.mdx
@@ -9,9 +9,11 @@ import FeatureList from '@site/src/components/FeatureList';
 import Intro from '@site/src/components/Intro';
 
 <Intro>
-We’re excited to announce our new **Platform Advisory** service—now available to Cloud Posse customers. Private access to Cloud Posse engineers.
+We're excited to announce our new **Platform Advisory** service—now available to Cloud Posse customers. Private access to Cloud Posse engineers.
 </Intro>
 
+<!--truncate-->
+
 Many of our larger customers—especially in **fintech, health tech**—who operate in regulated industries have asked for a way to get **private, real-time access** to senior Cloud Posse engineers for their most critical projects.
 
 These teams often run into scenarios where:
diff --git a/blog/2025-10-15-deprecation-process.mdx b/blog/2025-10-15-deprecation-process.mdx
@@ -12,6 +12,8 @@ import Intro from '@site/src/components/Intro';
 We've documented our formal process for deprecating and archiving components to ensure transparency and give our community adequate notice when repositories are being sunset.
 </Intro>
 
+<!--truncate-->
+
 Hello SweetOps!
 
 As part of our commitment to maintaining [300+ open source projects](https://github.com/cloudposse/) across Terraform modules, [components](https://github.com/cloudposse-terraform-components), and other tooling, we occasionally need to deprecate repositories that are no longer actively maintained or have been superseded by better alternatives.
diff --git a/blog/2025-10-15-fargate-vs-managed-node-groups.mdx b/blog/2025-10-15-fargate-vs-managed-node-groups.mdx
@@ -12,6 +12,8 @@ import Intro from '@site/src/components/Intro';
 When simplicity meets automation, sometimes it's the hidden complexity that bites back.
 </Intro>
 
+<!--truncate-->
+
 For a while, running Karpenter on AWS Fargate sounded like a perfect solution. No nodes to manage, automatic scaling, and no EC2 lifecycle headaches. The [AWS EKS Best Practices Guide](https://aws.github.io/aws-eks-best-practices/karpenter/#run-the-karpenter-controller-on-eks-fargate-or-on-a-worker-node-that-belongs-to-a-node-group) and [Karpenter's official documentation](https://karpenter.sh/docs/getting-started/getting-started-with-karpenter/) both present Fargate as a viable option for running the Karpenter controller.
 
 But in practice, that setup started to cause problems for certain EKS add-ons. Over time, those lessons led us — and our customers — to recommend using a small managed node group (MNG) instead of relying solely on Fargate.
diff --git a/blog/2025-10-17-llms-txt.mdx b/blog/2025-10-17-llms-txt.mdx
@@ -12,6 +12,8 @@ import Intro from '@site/src/components/Intro';
 We've implemented the llms.txt standard to make our documentation more accessible to AI assistants, ensuring better responses when you ask ChatGPT, Claude, or other LLMs about Cloud Posse tools and best practices.
 </Intro>
 
+<!--truncate-->
+
 Hello SweetOps!
 
 As AI assistants become increasingly integrated into developer workflows, we're excited to announce support for the [llms.txt standard](https://llmstxt.org/) across our documentation site.
diff --git a/blog/2025-12-19-deprecate-account-map.mdx b/blog/2025-12-19-deprecate-account-map.mdx
@@ -12,6 +12,8 @@ import Steps from '@site/src/components/Steps';
 We're releasing Version 2 of the Cloud Posse Reference Architecture, which removes the `account-map` component and related identity components in favor of a simpler, more flexible approach using Atmos Auth profiles and static configuration.
 </Intro>
 
+<!--truncate-->
+
 ## What's Changing
 
 Version 2 of the Reference Architecture removes several components that were central to Version 1:
