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

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

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

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

what

• Disable telemetry in Atmos default settings

why

• We do not want to collect internal executions events

what

• Added css to support datadog logo light/dark themes

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#811

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#811

what

• Use atmos instead of makefile

why

• build-harness deprecated. Use atmos instead

what

• Add Atmos installation step in GitHub Action

why

• Use atmos for readme generation

what

• Update the confusing wording in the ArgoCD GitHub Apps documentation.
• Make it clear that ArgoCD apps only need the ability to bypass branch protection rules.
• Simplify and clarify the explanation to improve readability.

why

• A lot of the content here was unnecessary and confusing. This came from a specific customer use-case, so we can remove a lot for the general usage.

references

• DEV-3535
• Depends on #805

what

• Fix the indentation on the account deployment steps

why

• Fix this:

references

#815

what

• Update account limit increase service quota code
• Add note for enabling cost explorer

why

• These are both issues that came up for recent quickstart customers

references

• https://github.com/orgs/cloudposse/discussions/96
• https://github.com/orgs/cloudposse/discussions/95

what

• Fix typo in quickstart

why

• Fix typo

what

• add codeowners to offboarding

• reformat GitHub sections for offboarding

why

• crucial when transitioning repo maintainers

what

• docs(best-practices): all resource attributes

why

• Use a stop gap or an escape hatch to expose all attributes of a resource in a module where those attributes haven't been explicitly exposed with their own output yet

references

• Slack thread https://sweetops.slack.com/archives/G014YEKDH4K/p1747447711003559?thread_ts=1747354666.579409&cid=G014YEKDH4K

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#801

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#801

what

• Refactoring documentation for improved developer experience
• Updating workflows for new paths in refarch
• Validating refarch end-to-end
• Deprecated Spacelift and OpsGenie

why

• Staging release validation

references

• DEV-3549

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#800

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#800

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#799

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#799

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#798

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#798

what

• Point all Atmos workflows to a copy of the workflow directory

why

• When we merge the staging branch of refarch-scaffold, all workflows will be changed. That means they will break all paths on docs (here). Therefore, we can create a temporary copy of them all in this directory, point to the copy, and then update the staging branch here to point to the new path

references

• https://github.com/cloudposse/refarch-scaffold/tree/staging

Summary

• clarify that Leapp is required with the reference architecture
• fix identity deployment table and add steps for vendoring and Identity Center setup
• remove the SAML provider step per review feedback

Testing

• npm install --ignore-scripts
• npx docusaurus-mdx-checker --cwd docs (fails: Error: canceled)

https://chatgpt.com/codex/tasks/task_b_68825b29b5b0832ba5498ba8ea27aa8e

what

• Update AWS SSO docs.
  • Update Microsoft since it changed to be Entra
  • Removing wording for "handoff to cloudposse" which was from an older period of our reference architecture
  • Fixes issue with code block on identity/deploy.mdx

why

• More Clear instructions hopefully

This pull request introduces several changes across different areas of the codebase, including dependency updates, documentation enhancements, and component refactoring. The key highlights are the downgrade of the Node.js version, the addition of a new documentation guide for self-hosted runners, and the complete refactoring of the EmbedFile component to improve modularity and styling.

Dependency Updates:

• .nvmrc: Downgraded Node.js version from v21.7.3 to v20.12.0 to align with compatibility requirements.

Documentation Enhancements:

• docs/layers/github-actions/runs-on.mdx: Added a comprehensive guide on setting up and managing self-hosted runners, including step-by-step instructions, configuration examples, and troubleshooting tips.

Component Refactoring:

• src/components/EmbedFile/index.js: Removed the EmbedFile component, which dynamically loaded and displayed file content, to simplify the codebase and improve maintainability.
• src/components/File/index.tsx: Introduced a new File component in TypeScript, encapsulating file display functionality with improved structure and modularity.
• src/components/File/index.css: Added new styles for the File component, including enhancements for line numbering, tabs, and viewport design, with support for light and dark themes.

what

• Update heading level for account setup completion step

why

• Incorrect header level

references

• .

what

• Added set up step for validating the root account name
• Updated the tutorials for created or deleting accounts

why

• This has come up a few times in github discussions and in slack

references

• https://github.com/orgs/cloudposse/discussions/82
• https://github.com/orgs/cloudposse/discussions/20

what

• Alternative PR to #782

what

• fix various spelling mistakes throughout documentation

https://chatgpt.com/codex/tasks/task_b_6852ebf32a2883329869bdcf7a564aea

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#767

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#767

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#764

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#764

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#763

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#763

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#761

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#761

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#759

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#759

what

• Update community/contribute/automated-testing.mdx with atmos tests running locally instructions

why

• build-harness deprecated and replaced with Atmos custom commands

references

• DEV-325 Update docs.cloudposse.com with new instructions

This pull request updates import paths in the spacelift.mdx file to reflect a reorganization of example snippets into a legacy folder.

File updates:

• docs/layers/spacelift/spacelift.mdx: Changed import paths for PartialSpaceliftRootStack and PartialSpaceliftTenantStack to point to the legacy/snippets directory instead of examples/snippets.

what

• Use separate key

why

• All data was flowing to our marketing site