Add llms.txt implementation for improved AI/LLM visibility #16656
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement llms.txt standard to improve Pulumi's visibility in AI-generated content and responses. Changes: - Add static llms.txt file with curated Pulumi documentation structure - Configure Hugo to generate llms.txt dynamically via new output format - Create Hugo template for future dynamic llms.txt generation - Add AI bot tracking JavaScript to measure experiment effectiveness - Update AGENTS.md with llms.txt guidance for AI assistants - Track known AI bots: ClaudeBot, Amazonbot, ChatGPT-User, OAI-SearchBot, PerplexityBot The blockquote summary uses Pulumi's Entry Segment Messaging emphasizing: - Real programming languages vs YAML - IDE support, type safety, automated testing - Multi-cloud support (AWS, Azure, GCP, Kubernetes, 150+ providers) - 3x faster deployment with 90% fewer configuration errors Bot detection based on actual traffic data from pulumi.com analytics.
Remove '3x faster with 90% fewer configuration errors' from the blockquote summary to keep the messaging focused on core value propositions rather than specific metrics.
This comment was marked as resolved.
This comment was marked as resolved.
Collaborator
|
Your site preview for commit e9bc8ab is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16656-e9bc8abc.s3-website.us-west-2.amazonaws.com. |
- Add trailing newlines to all new files (llms.txt, index.llmstxt.txt, ai-bot-tracking.js) - Clarify AGENTS.md documentation: .md URLs are a future enhancement, not currently implemented - Remove Hugo template comment that was generating unwanted blank line in output - Add clarification to JavaScript that bot detection is supplemental client-side tracking (primary measurement is via server-side access logs) These changes address all required fixes from the documentation review and improve code clarity per reviewer suggestions.
sicarul
reviewed
Nov 24, 2025
sicarul
reviewed
Nov 24, 2025
sicarul
reviewed
Nov 24, 2025
Collaborator
|
Your site preview for commit de16f46 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16656-de16f463.s3-website.us-west-2.amazonaws.com. |
sicarul
reviewed
Nov 24, 2025
Based on PR review feedback: 1. Move blog content out of 'Optional' section - Created new 'Blog & Resources' section with higher priority - Blog posts are valuable for LLMs to understand recent features and best practices - Case studies remain with blog as related resources 2. Clarify JavaScript/HTML separation - Added clear comments explaining ai-bot-tracking.js is ONLY for HTML pages - Emphasized that JavaScript does NOT interact with llms.txt file - llms.txt is served as plain text, completely separate from website JS 3. Improve blog template visibility - Added example blog posts to static llms.txt to show intended output - Added comment explaining Hugo dynamically generates blog posts - Template filters for high-value posts (IaC, Terraform, Kubernetes topics) These changes address confusion about file purposes and improve content organization.
Collaborator
|
Your site preview for commit fc48377 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16656-fc483771.s3-website.us-west-2.amazonaws.com. |
- Remove AI bot tracking JavaScript entirely - Remove script reference from assets.html - Simplify Hugo template by removing complex blog post generation logic - Update static llms.txt to match simplified structure - Keep blog section as simple link without specific posts This addresses PR review feedback about unnecessary complexity and confusion around the JavaScript tracking
Collaborator
|
Your site preview for commit 45acecb is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16656-45acecb0.s3-website.us-west-2.amazonaws.com. |
- Merge Tutorials & Examples and Blog & Resources into unified Resources section - Remove Optional section (What Is Pulumi?, Community) - Remove CrossGuard reference from IaC section - Rename Hugo template from index.llmstxt.txt to index.llms.txt - Update output format name from LLMSTXT to llms in config
Collaborator
|
Your site preview for commit 2bc1e34 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16656-2bc1e34a.s3-website.us-west-2.amazonaws.com. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the
llms.txtstandard to improve Pulumi's visibility and inclusion in AI-generated summaries and responses.The
llms.txtfile provides a structured, markdown-based index of Pulumi's documentation that LLMs can efficiently consume within their context windows. This follows the proposed standard from llmstxt.org that's gaining adoption for making websites more AI-friendly.Key changes:
The blockquote summary uses messaging from Pulumi's Entry Segment document, emphasizing real programming languages vs YAML, IDE support, type safety, and multi-cloud capabilities.
Bot detection is based on actual traffic data from pulumi.com analytics, tracking known AI crawlers like ClaudeBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, and Amazonbot.
This is part of a growth experiment to test if llms.txt improves brand citations and organic traffic from AI-driven discovery channels. Success metrics will be tracked via server logs and analytics over 4-6 weeks.