v1.41.0

Add component deprecation and archival process documentation @osterman (#827)

Summary

• Added comprehensive deprecation and archival process documentation to the community section
• Created blog post announcing the new documentation
• Documents the 7-step process for transparently deprecating and archiving repositories

Details

This PR adds structured documentation for how Cloud Posse handles component deprecation and archival. The process includes:

1. Announce Deprecation via Pull Request - Communicate the plan with clear timelines
2. Add Deprecation Notice to README - Using GitHub warning admonitions
3. Update README.yaml - Add the deprecated field with notice text
4. Create and Pin GitHub Issue - Comprehensive issue with migration guidance
5. Link Issue in Deprecation Notice - Ensure visibility
6. Wait for Deprecation Date - Typically 90+ days grace period
7. Archive Repository - Update .github/settings.yml to set archived: true

The documentation is added to /community/contribute/our-github#deprecation-and-archival-process which seemed like the natural fit given the existing content about GitHub maintenance and archival.

A blog post has been added to announce this new documentation to the community.

Test Plan

• Documentation renders correctly in MDX
• All links are valid
• Code examples are properly formatted
• Blog post follows existing format

🤖 Generated with Claude Code

Add blog post: Why We Recommend Managed Node Groups Over Fargate for EKS Add-Ons @osterman (#826)

Summary

• New blog post explaining why managed node groups are recommended over Fargate for EKS add-ons
• Covers bootstrap deadlock issues, high availability challenges, and cost/flexibility benefits
• Written in Cloud Posse voice: technically grounded, lightly opinionated, and story-driven

Test plan

• Review blog post content for technical accuracy
• Verify MDX formatting and component usage
• Check that the post renders correctly on the website
• Confirm date format matches existing posts
• Validate author attribution in frontmatter

🤖 Generated with Claude Code

Add Conductor workspace configuration @osterman (#825)

Summary

• Adds conductor.json configuration file for automated workspace setup
• Includes conductor-setup.sh script that validates Node.js/npm and installs dependencies
• Enables one-click development server launching via Conductor

What's included

conductor.json

• setup script: Runs workspace initialization (dependency installation, cache clearing)
• run script: Starts Docusaurus dev server on Conductor-assigned port
• nonconcurrent mode: Ensures only one dev server runs at a time

conductor-setup.sh

• Validates Node.js ≥20.10 is installed
• Validates npm is available
• Clears cached build artifacts (.docusaurus, build)
• Installs npm dependencies
• Provides clear error messages if requirements are missing

Test plan

• Tested setup script successfully in workspace
• Verified Node.js version checking works
• Confirmed dependencies install correctly
• Test run script launches dev server (can be tested after merge)

🤖 Generated with Claude Code

Add LLM-friendly documentation (llms.txt) @goruha (#824)

what

• Add support for llms.txt standard using docusaurus-plugin-llms
• Generate two LLM-friendly documentation files:
  • /llms.txt - Compact link list
  • /llms-full.txt - Full documentation content
• Configure plugin to prioritize core documentation sections
• Include blog content in generated files

why

• LLMs need structured documentation: The llms.txt standard (https://llmstxt.org/) provides a standardized way for LLMs to efficiently understand website documentation
• Address context window limitations: Instead of crawling entire websites, LLMs can access curated, structured content optimized for their understanding
• Improve AI assistance: Tools like Claude, ChatGPT, and other AI assistants can provide better answers about Atmos by referencing these files
• Follow emerging standards: Similar to robots.txt for search engines, llms.txt is becoming a standard for AI-friendly documentation
• Better developer experience: Users asking AI assistants will get more accurate, up-to-date responses

references

• https://llmstxt.org/ - llms.txt standard specification
• https://github.com/rachfop/docusaurus-plugin-llms - Docusaurus plugin used
• Live files will be available at:
  • https://docs.cloudposse.com/llms.txt
  • https://docs.cloudposse.com/llms-full.txt

Add telemetry settings to atmos.yaml @goruha (#823)

what

• Disable telemetry in Atmos default settings

why

• We do not want to collect internal executions events