openclaw - 💡(How to fix) Fix [Feature]: Documentation map file for LLM navigation

Why: OpenClaw has deep docs (https://docs.openclaw.ai/) across automation/, channels/, cli/, concepts/, gateway/, install/, nodes/, plugins/, providers/, tools/, web/, and more. An LLM currently has to discover this tree through trial and error. A single map fixes that. Example: code.claude.com/docs/en/claude_code_docs_map.md OpenClaw has deep docs (https://docs.openclaw.ai/) across automation/, channels/, cli/, concepts/, gateway/, install/, nodes/, plugins/, providers/, tools/, web/, and more. An LLM currently has to discover this tree through trial and error. A single map fixes that. Example: code.claude.com/docs/en/claude_code_docs_map.md

TL;DR

Create a single docs_map.md file with a nested outline of every doc page's H2/H3/H4 headings to enable AI agents to easily discover and reference OpenClaw documentation.

Guidance

• Consider using GitHub Actions to auto-generate the docs_map.md file on every push to docs/** to keep the map up-to-date.
• The docs_map.md file should be a sibling of the existing llms.txt file, providing a complementary resource for AI agents.
• Review the example claude_code_docs_map.md file for inspiration on how to structure the docs_map.md file.
• Ensure the docs_map.md file includes a clear and consistent heading hierarchy to facilitate easy parsing by AI agents.

Example

No code snippet is provided as the issue focuses on documentation structure rather than code implementation.

Notes

The proposed solution relies on the existence of a consistent heading structure across OpenClaw documentation pages. If this structure is not already in place, additional work may be required to standardize headings before generating the docs_map.md file.

Recommendation

Apply the proposed solution of auto-generating a docs_map.md file via GitHub Actions, as it provides a clear and efficient way to enable AI agents to discover and reference OpenClaw documentation.