Add llms.txt for AI assistant context

[AntTheLimey]

Summary

• Add llms.txt file following the emerging convention for providing LLMs with structured context about a website
• Includes overview of pgEdge products, deployment options, extensions, AI toolkit, and documentation links

Why

As an AI-forward company with an AI Toolkit, having an llms.txt helps AI assistants provide accurate information about pgEdge products when users ask questions.

Test plan

• Verify file is accessible at https://docs.pgedge.com/llms.txt after deployment

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added comprehensive documentation covering pgEdge capabilities, deployment options, core extensions, AI toolkit components, operations tools, and resources with relevant links and technical information.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Adds a new documentation file detailing pgEdge's capabilities, including deployment options, core extensions, AI toolkit components, and operations tools with relevant URLs and technical stack information organized into structured sections.

Changes

Cohort / File(s)	Summary
Documentation docs/llms.txt	New documentation file covering pgEdge platform features, deployment options, core extensions, AI toolkit components, operations tools, and resources with associated links and tech stack details (+95 lines)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'Add llms.txt for AI assistant context' accurately describes the main change: adding a new llms.txt documentation file designed to provide structured context for AI assistants.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@docs/llms.txt`:
- Line 7: Update the sentence text to hyphenate the compound adjective: change
"100% standard, open source PostgreSQL" to "100% standard, open-source
PostgreSQL" so "open-source" correctly modifies "PostgreSQL" as a compound
adjective.
- Around line 1-95: The two broken links under the "Kubernetes (Containers)" and
"VMs & Bare Metal" sections (currently pointing to
https://docs.pgedge.com/container-images/ and https://docs.pgedge.com/ansible/)
must be corrected: locate those URLs in docs/llms.txt (look for the "Kubernetes
(Containers)" and "VMs & Bare Metal" headings and the lines containing
container-images and ansible) and replace each with the correct documentation
page (or a valid parent path such as the main docs root) after verifying the
canonical URLs on the docs site; ensure the updated links match existing docs
pages and test they no longer return 404.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Extract and test all HTTPS URLs from docs/llms.txt

urls=$(grep -oP 'https://[^\s]+' docs/llms.txt | sort -u)

echo "Testing URL accessibility..."
echo "=========================================="

failed_urls=()
passed_urls=()

for url in $urls; do
  # Remove any trailing markdown characters
  url_clean=$(echo "$url" | sed 's/[`\)\]\*]*$//')
  
  status=$(curl -s -o /dev/null -w "%{http_code}" -L --connect-timeout 5 "$url_clean" 2>/dev/null)
  
  if [ "$status" -eq 200 ]; then
    echo "✓ $url_clean (HTTP $status)"
    passed_urls+=("$url_clean")
  else
    echo "✗ $url_clean (HTTP $status)"
    failed_urls+=("$url_clean")
  fi
done

echo "=========================================="
echo "Summary:"
echo "Passed: ${`#passed_urls`[@]}"
echo "Failed: ${`#failed_urls`[@]}"

if [ ${`#failed_urls`[@]} -gt 0 ]; then
  echo ""
  echo "Failed URLs:"
  for url in "${failed_urls[@]}"; do
    echo "  - $url"
  done
fi

Repository: pgEdge/pgedge-docs

Length of output: 1368

---

Fix broken documentation URLs.

Two documentation links return HTTP 404 errors:

• Line 23: https://docs.pgedge.com/container-images/
• Line 24: https://docs.pgedge.com/ansible/

These URLs need to be corrected or replaced to ensure all documentation links are accessible.

🧰 Tools

🪛 LanguageTool

[grammar] ~7-~7: Use a hyphen to join words.
Context: ...r clusters. Built on 100% standard, open source PostgreSQL. **Key Capabilities:*...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

In `@docs/llms.txt` around lines 1 - 95, The two broken links under the
"Kubernetes (Containers)" and "VMs & Bare Metal" sections (currently pointing to
https://docs.pgedge.com/container-images/ and https://docs.pgedge.com/ansible/)
must be corrected: locate those URLs in docs/llms.txt (look for the "Kubernetes
(Containers)" and "VMs & Bare Metal" headings and the lines containing
container-images and ansible) and replace each with the correct documentation
page (or a valid parent path such as the main docs root) after verifying the
canonical URLs on the docs site; ensure the updated links match existing docs
pages and test they no longer return 404.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Hyphenate compound adjective.

When "open source" modifies a noun as a compound adjective, it should be hyphenated as "open-source".

📝 Proposed fix

-pgEdge delivers hardened, production-grade PostgreSQL with a seamless path from single database deployments to globally distributed multi-master clusters. Built on 100% standard, open source PostgreSQL.
+pgEdge delivers hardened, production-grade PostgreSQL with a seamless path from single database deployments to globally distributed multi-master clusters. Built on 100% standard, open-source PostgreSQL.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	pgEdge delivers hardened, production-grade PostgreSQL with a seamless path from single database deployments to globally distributed multi-master clusters. Built on 100% standard, open source PostgreSQL.
	pgEdge delivers hardened, production-grade PostgreSQL with a seamless path from single database deployments to globally distributed multi-master clusters. Built on 100% standard, open-source PostgreSQL.

🧰 Tools

🪛 LanguageTool

[grammar] ~7-~7: Use a hyphen to join words.
Context: ...r clusters. Built on 100% standard, open source PostgreSQL. **Key Capabilities:*...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

In `@docs/llms.txt` at line 7, Update the sentence text to hyphenate the compound
adjective: change "100% standard, open source PostgreSQL" to "100% standard,
open-source PostgreSQL" so "open-source" correctly modifies "PostgreSQL" as a
compound adjective.