# ScopeDocs sitemap

> Machine-readable twin of [sitemap.xml](https://scopedocs.ai/sitemap.xml). Prefer [llms.txt](https://scopedocs.ai/llms.txt) for curated agent paths.

Last generated: 2026-09-01. 81 published blog posts.

## Core pages

- [Home](https://scopedocs.ai/)
- [Product](https://scopedocs.ai/product)
- [Features](https://scopedocs.ai/features)
- [Solutions](https://scopedocs.ai/solutions)
- [Pricing](https://scopedocs.ai/pricing)
- [About](https://scopedocs.ai/about)
- [About us](https://scopedocs.ai/about-us)
- [Team](https://scopedocs.ai/team)
- [Vivian Nguyen Lin](https://scopedocs.ai/team/vivian-nguyen-lin)
- [Thao Ha](https://scopedocs.ai/team/thao-ha)
- [Radha Parikh](https://scopedocs.ai/team/radha-parikh)
- [Docs hub](https://scopedocs.ai/docs)
- [Quickstart](https://scopedocs.ai/docs/quickstart)
- [MCP for agents](https://scopedocs.ai/docs/mcp)
- [Blog](https://scopedocs.ai/blog)
- [Blog RSS](https://scopedocs.ai/blog/rss.xml)
- [Privacy](https://scopedocs.ai/privacy)
- [Terms of service](https://scopedocs.ai/terms-of-service)
- [What is generative documentation?](https://scopedocs.ai/guides/what-is-generative-documentation)
- [What is living documentation?](https://scopedocs.ai/guides/what-is-living-documentation)
- [What is source-linked documentation?](https://scopedocs.ai/guides/what-is-source-linked-documentation)
- [Wiki vs living documentation](https://scopedocs.ai/guides/wiki-vs-living-documentation)
- [Generative documentation vs wikis](https://scopedocs.ai/guides/generative-documentation-vs-wikis)
- [MCP for engineering documentation](https://scopedocs.ai/guides/mcp-for-engineering-documentation)
- [AI documentation for engineering teams](https://scopedocs.ai/guides/ai-documentation-for-engineering-teams)
- [llms.txt](https://scopedocs.ai/llms.txt)
- [llms-full.txt](https://scopedocs.ai/llms-full.txt)
- [AGENTS.md](https://scopedocs.ai/AGENTS.md)
- [MCP discovery](https://scopedocs.ai/.well-known/mcp.json)
- [pricing.md](https://scopedocs.ai/pricing.md)
- [product.md](https://scopedocs.ai/product.md)
- [features.md](https://scopedocs.ai/features.md)
- [index.md](https://scopedocs.ai/index.md)

## Blog tag hubs

- [Generative Documentation](https://scopedocs.ai/blog/tag/generative-documentation)
- [AI Documentation](https://scopedocs.ai/blog/tag/ai-documentation)
- [Developer Productivity](https://scopedocs.ai/blog/tag/developer-productivity)
- [Knowledge Management](https://scopedocs.ai/blog/tag/knowledge-management)
- [Engineering Workflows](https://scopedocs.ai/blog/tag/engineering-workflows)
- [Documentation Automation](https://scopedocs.ai/blog/tag/documentation-automation)
- [Onboarding Documentation](https://scopedocs.ai/blog/tag/onboarding-documentation)
- [On-Call Documentation](https://scopedocs.ai/blog/tag/on-call-documentation)
- [API Documentation](https://scopedocs.ai/blog/tag/api-documentation)
- [Technical Writing](https://scopedocs.ai/blog/tag/technical-writing)
- [Documentation Best Practices](https://scopedocs.ai/blog/tag/documentation-best-practices)
- [Team Collaboration](https://scopedocs.ai/blog/tag/team-collaboration)
- [Information Silos](https://scopedocs.ai/blog/tag/information-silos)
- [Slack Integration](https://scopedocs.ai/blog/tag/slack-integration)
- [Jira Integration](https://scopedocs.ai/blog/tag/jira-integration)
- [Notion Integration](https://scopedocs.ai/blog/tag/notion-integration)
- [Supabase Integration](https://scopedocs.ai/blog/tag/supabase-integration)
- [Google Drive Integration](https://scopedocs.ai/blog/tag/google-drive-integration)
- [Fathom Integration](https://scopedocs.ai/blog/tag/fathom-integration)
- [Datadog Integration](https://scopedocs.ai/blog/tag/datadog-integration)
- [Confluence Integration](https://scopedocs.ai/blog/tag/confluence-integration)
- [Project Coordination](https://scopedocs.ai/blog/tag/project-coordination)
- [SOPs and Runbooks](https://scopedocs.ai/blog/tag/sops-and-runbooks)
- [Tribal Knowledge](https://scopedocs.ai/blog/tag/tribal-knowledge)
- [Documentation Debt](https://scopedocs.ai/blog/tag/documentation-debt)

## Blog posts

- [Where Tribal Knowledge Lives Inside ERP and CRM Implementations](https://scopedocs.ai/blog/where-tribal-knowledge-lives-inside-erp-and-crm-implementations)
- [CRM Implementation Handoff Checklist: Requirements, Decisions, Workflows, and Custom Work](https://scopedocs.ai/blog/crm-implementation-handoff-checklist-requirements-decisions-workflows-and-custom-work)
- [Why CRM Implementation Projects Lose Requirements Between Discovery and Go-Live](https://scopedocs.ai/blog/why-crm-implementation-projects-lose-requirements-between-discovery-and-go-live)
- [When ERP Practices Should Use Living Delivery Records Instead of Client Wikis](https://scopedocs.ai/blog/when-erp-practices-should-use-living-delivery-records-instead-of-client-wikis)
- [How ERP Consultancies Reduce Implementation Knowledge Debt Across Client Accounts](https://scopedocs.ai/blog/how-erp-consultancies-reduce-implementation-knowledge-debt-across-client-accounts)
- [From Discovery Call to Living CRM Implementation Record](https://scopedocs.ai/blog/from-discovery-call-to-living-crm-implementation-record)
- [When AI Writes the Docs, Who Checks the Work?](https://scopedocs.ai/blog/when-ai-writes-the-docs-who-checks-the-work)
- [Why Did We Customize That Field? Tracing Jira Ticket Context in ERP and CRM Implementations](https://scopedocs.ai/blog/why-did-we-customize-that-field-tracing-jira-ticket-context-in-erp-and-crm-implementations)
- [Why CRM and ERP Firms Abandon Client Wikis: Documentation Fatigue in Delivery](https://scopedocs.ai/blog/why-crm-and-erp-firms-abandon-client-wikis-documentation-fatigue-in-delivery)
- [How to Set Up a Source-Linked Delivery Record for a New CRM Rollout](https://scopedocs.ai/blog/how-to-set-up-a-source-linked-delivery-record-for-a-new-crm-rollout)
- [From PRs to Living Docs: How to Build a Workflow That Actually Keeps Documentation Current](https://scopedocs.ai/blog/from-prs-to-living-docs-how-to-build-a-workflow-that-actually-keeps-documentation-current)
- [How Generative Documentation Reduces Documentation Debt for Engineering Teams](https://scopedocs.ai/blog/how-generative-documentation-reduces-documentation-debt-for-engineering-teams)
- [When the Auditor Asks, the Wiki Lies](https://scopedocs.ai/blog/when-the-auditor-asks-the-wiki-lies)
- [When the Docs Say One Thing and the Product Does Another](https://scopedocs.ai/blog/when-the-docs-say-one-thing-and-the-product-does-another)
- [When Confluence Says Yes and GitHub Says No](https://scopedocs.ai/blog/when-confluence-says-yes-and-github-says-no)
- [How to Build an Engineering Knowledge Base That Updates Itself](https://scopedocs.ai/blog/how-to-build-an-engineering-knowledge-base-that-updates-itself)
- [How to Link Linear Ticket Context to Your Documentation (Before It Gets Lost)](https://scopedocs.ai/blog/how-to-link-linear-ticket-context-to-your-documentation-before-it-gets-lost)
- [Documentation Debt Is Draining Your Engineers. Here Is What the Data Shows.](https://scopedocs.ai/blog/documentation-debt-is-draining-your-engineers-here-is-what-the-data-shows)
- [Why Engineering Teams Abandon Their Wikis: Research on Documentation Fatigue](https://scopedocs.ai/blog/why-engineering-teams-abandon-their-wikis-research-on-documentation-fatigue)
- [Where Tribal Knowledge Lives: What Engineering Team Surveys Actually Show](https://scopedocs.ai/blog/where-tribal-knowledge-lives-what-engineering-team-surveys-actually-show)
- [How to Capture Architecture Decision Records from GitHub PRs](https://scopedocs.ai/blog/how-to-capture-architecture-decision-records-from-github-prs)
- [Onboarding Documentation Best Practices That Actually Stay Current](https://scopedocs.ai/blog/onboarding-documentation-best-practices-that-actually-stay-current)
- [Architecture Docs That Actually Reflect Your Codebase](https://scopedocs.ai/blog/architecture-docs-that-actually-reflect-your-codebase)
- [On-Call Docs vs. Onboarding Docs: Different Needs, One Source](https://scopedocs.ai/blog/on-call-docs-vs-onboarding-docs-different-needs-one-source)
- [How to Keep Runbooks and ADRs in Sync with Your Codebase](https://scopedocs.ai/blog/how-to-keep-runbooks-and-adrs-in-sync-with-your-codebase)
- [When to Use Generative Docs vs. Traditional Wikis (And When the Wiki Is Already Wrong)](https://scopedocs.ai/blog/when-to-use-generative-docs-vs-traditional-wikis-and-when-the-wiki-is-already-wrong)
- [Source-Linked Documentation Beats Traditional Wikis. Here's the Proof.](https://scopedocs.ai/blog/source-linked-documentation-beats-traditional-wikis-here-s-the-proof)
- [Scaling Engineering Documentation Without Losing the People Who Know the System](https://scopedocs.ai/blog/scaling-engineering-documentation-without-losing-the-people-who-know-the-system)
- [Traceability in Technical Documentation: Why It Matters](https://scopedocs.ai/blog/traceability-in-technical-documentation-why-it-matters)
- [How to Keep Engineering Docs Current by Connecting GitHub, Slack, and Linear](https://scopedocs.ai/blog/how-to-keep-engineering-docs-current-by-connecting-github-slack-and-linear)
- [Adoption of Generative Documentation Tools: Current Landscape and Trends](https://scopedocs.ai/blog/adoption-of-generative-documentation-tools-current-landscape-and-trends)
- [How to Link Implementation to Documentation Using Linear Ticket Context](https://scopedocs.ai/blog/how-to-link-implementation-to-documentation-using-linear-ticket-context)
- [How to Capture Documentation Context from Slack Discussions](https://scopedocs.ai/blog/how-to-capture-documentation-context-from-slack-discussions)
- [How to Reduce Context Switching: Generate Documentation Where Engineers Already Work](https://scopedocs.ai/blog/how-to-reduce-context-switching-generate-documentation-where-engineers-already-work)
- [PR-to-Doc Pipelines: Turning Code Reviews into Living Documentation](https://scopedocs.ai/blog/pr-to-doc-pipelines-turning-code-reviews-into-living-documentation)
- [How to Set Up Source-Linked Documentation for a New Repository](https://scopedocs.ai/blog/how-to-set-up-source-linked-documentation-for-a-new-repository)
- [How to Build an Engineering Knowledge Base Without Manual Writing](https://scopedocs.ai/blog/how-to-build-an-engineering-knowledge-base-without-manual-writing)
- [How RAG and Source-Linking Improve Documentation Accuracy](https://scopedocs.ai/blog/how-rag-and-source-linking-improve-documentation-accuracy)
- [From Slack Threads to Structured Docs: Generative Documentation Workflows](https://scopedocs.ai/blog/from-slack-threads-to-structured-docs-generative-documentation-workflows)
- [How Traceability Improves Trust in AI-Generated Documentation](https://scopedocs.ai/blog/how-traceability-improves-trust-in-ai-generated-documentation)
- [How to Extract Documentation from Code Reviews: What to Capture and What to Skip](https://scopedocs.ai/blog/how-to-extract-documentation-from-code-reviews-what-to-capture-and-what-to-skip)
- [How Documentation Quality Impacts New Engineer Time to Productivity](https://scopedocs.ai/blog/how-documentation-quality-impacts-new-engineer-time-to-productivity)
- [Best Practices for Onboarding Documentation That Stays Current](https://scopedocs.ai/blog/best-practices-for-onboarding-documentation-that-stays-current)
- [Why Teams Abandon Wikis: Research on Documentation Fatigue](https://scopedocs.ai/blog/why-teams-abandon-wikis-research-on-documentation-fatigue)
- [How to Keep Architecture Documentation in Sync with Your Codebase](https://scopedocs.ai/blog/how-to-keep-architecture-documentation-in-sync-with-your-codebase)
- [How to Build Automated Incident Runbooks from PRs and Tickets](https://scopedocs.ai/blog/how-to-build-automated-incident-runbooks-from-prs-and-tickets)
- [How Engineers Verify AI-Generated Documentation: Building Trust Through Traceability](https://scopedocs.ai/blog/how-engineers-verify-ai-generated-documentation-building-trust-through-traceability)
- [Engineering Documentation Integrations: What to Connect First (and What Can Wait)](https://scopedocs.ai/blog/engineering-documentation-integrations-what-to-connect-first)
- [When to Use Generative Documentation vs Traditional Wikis](https://scopedocs.ai/blog/when-to-use-generative-documentation-vs-traditional-wikis)
- [How to Keep Documentation Current: Connecting GitHub, Slack, and Linear](https://scopedocs.ai/blog/how-to-keep-documentation-current-connecting-github-slack-and-linear)
- [Generative Documentation Adoption: Current State of AI-Powered Docs in Engineering Teams](https://scopedocs.ai/blog/generative-documentation-adoption-current-state-of-ai-powered-docs-in-engineering-teams)
- [How to Capture Architecture Decisions and ADRs from GitHub PRs](https://scopedocs.ai/blog/how-to-capture-architecture-decisions-and-adrs-from-github-prs)
- [How to Link Linear Tickets to Documentation for Better Engineering Context](https://scopedocs.ai/blog/how-to-link-linear-tickets-to-documentation-for-better-engineering-context)
- [On-Call Documentation vs Onboarding Documentation: Different Needs, One Source](https://scopedocs.ai/blog/on-call-documentation-vs-onboarding-documentation-different-needs-one-source)
- [How to Build an Engineering Knowledge Base That Updates Automatically](https://scopedocs.ai/blog/how-to-build-an-engineering-knowledge-base-that-updates-automatically)
- [How to Scale Documentation as Your Engineering Team Grows](https://scopedocs.ai/blog/how-to-scale-documentation-as-your-engineering-team-grows)
- [Why Source-Linked Documentation Beats Traditional Wikis for Engineering Teams](https://scopedocs.ai/blog/why-source-linked-documentation-beats-traditional-wikis-for-engineering-teams)
- [Reducing Context Switching: Docs Generated Where Engineers Already Work](https://scopedocs.ai/blog/reducing-context-switching-docs-generated-where-engineers-already-work)
- [Slack Integration for Documentation: Capturing Context from Team Discussions](https://scopedocs.ai/blog/slack-integration-for-documentation-capturing-context-from-team-discussions)
- [Documentation from Code Reviews: What to Capture and What to Skip](https://scopedocs.ai/blog/documentation-from-code-reviews-what-to-capture-and-what-to-skip)
- [Step-by-Step: Setting Up Source-Linked Docs for a New Repo](https://scopedocs.ai/blog/step-by-step-setting-up-source-linked-docs-for-a-new-repo)
- [From PRs to Living Docs: Practical Workflow and Tooling](https://scopedocs.ai/blog/from-prs-to-living-docs-practical-workflow-and-tooling)
- [Traceability and Trust: How Engineers Verify AI-Generated Documentation](https://scopedocs.ai/blog/traceability-and-trust-how-engineers-verify-ai-generated-documentation)
- [Where Tribal Knowledge Lives: Surveys of Engineering Teams](https://scopedocs.ai/blog/where-tribal-knowledge-lives-surveys-of-engineering-teams)
- [Adoption of Generative Documentation Tools: Current Landscape](https://scopedocs.ai/blog/adoption-of-generative-documentation-tools-current-landscape)
- [Linking Implementation to Documentation: Linear Ticket Context](https://scopedocs.ai/blog/linking-implementation-to-documentation-linear-ticket-context)
- [Docs That Stay Current: Connecting GitHub, Slack, and Linear](https://scopedocs.ai/blog/docs-that-stay-current-connecting-github-slack-and-linear)
- [Capturing Architecture Decisions and ADRs from GitHub PRs](https://scopedocs.ai/blog/capturing-architecture-decisions-and-adrs-from-github-prs)
- [Linking Implementation to Documentation: The Power of Linear Ticket Context](https://scopedocs.ai/blog/linking-implementation-to-documentation-the-power-of-linear-ticket-context)
- [Why Traceability Matters in Technical Documentation](https://scopedocs.ai/blog/why-traceability—to a merge in GitHub, a monitor in Datadog, or a ticket in Jira-matters-in-technical-documentation)
- [Scaling Documentation as Your Engineering Team Grows](https://scopedocs.ai/blog/scaling-documentation-as-your-engineering-team-grows)
- [Linking Linear Tickets to Your Documentation: Boost Traceability and Context](https://scopedocs.ai/blog/linking-linear-tickets-to-your-documentation-boost-traceability-and-context)
- [Supercharge Your Documentation with Slack Integration](https://scopedocs.ai/blog/supercharge-your-documentation-with-slack-integration)
- [Why Source-Linked Documentation Beats Traditional Wikis](https://scopedocs.ai/blog/why-source-linked-documentation-beats-traditional-wikis)
- [Architecture Documentation That Stays in Sync with Your Codebase](https://scopedocs.ai/blog/architecture-documentation-that-stays-in-sync-with-your-codebase)
- [Decision Logs: Capturing the 'Why' Behind Code Changes](https://scopedocs.ai/blog/decision-logs-capturing-the-why-behind-changes)
- [Incident Response with Traceability: What Actually Helps](https://scopedocs.ai/blog/incident-response-with-traceability-what-actually-helps)
- [From GitHub PRs to Living Documentation: A Practical Workflow](https://scopedocs.ai/blog/from-prs-to-living-docs-practical-workflow)
- [Onboarding with Context: How Engineering Teams Ramp Faster](https://scopedocs.ai/blog/onboarding-with-context-how-teams-ramp-faster)
- [Generated Documentation: The End of Stale Wikis](https://scopedocs.ai/blog/generated-documentation-end-of-stale-wikis)
- [Why Source-linked Documentation Beats AI Summaries](https://scopedocs.ai/blog/why-source-linked-docs-beat-ai-summaries)
