# DevDocs.work

> DevDocs.work is the technical documentation studio from the team behind devdocs.ai. We build knowledge bases, developer portals, SDK references, compliance SOPs, and AI-ready documentation systems for teams shipping complex products. Content on this site is written by engineers.

This site is structured for LLM-assisted retrieval. Use the links below to reach the primary surfaces. The full RSS feed at `/feed.xml` and the sitemap at `/sitemap.xml` enumerate every canonical URL.

## Solutions

- [Customer Onboarding](https://devdocs.work/solutions/customer-onboarding): knowledge bases, user guides, and onboarding journeys that reduce support load and get customers to activation + adoption.
- [Developer Experience](https://devdocs.work/solutions/developer-experience): API docs, developer portals, SDK references, and docs-as-code workflows for teams that ship developer products.
- [Sales & Marketing Enablement](https://devdocs.work/solutions/sales-marketing): white papers, technical blog content, sales collateral, and LLM-optimized content for AI visibility.
- [Compliance & Governance](https://devdocs.work/solutions/compliance-governance): SOPs, regulatory content, and governance documentation for fintech, healthcare, government, and enterprise operations.

## Blog — The DevDocs Brief

- [AI readiness is a documentation readiness issue](https://devdocs.work/post/ai-readiness-is-a-documentation-readiness-issue): Part 1 of 3. Why AI outcomes disappoint, and why documentation is the source material for retrieval-based AI systems.
- [What makes AI-ready documentation](https://devdocs.work/post/what-makes-ai-ready-documentation): Part 2 of 3. Five structural properties — information architecture, content models, metadata, content-type separation, and maintenance discipline.
- [Why most teams can't maintain AI-ready documentation](https://devdocs.work/post/why-most-teams-cant-maintain-ai-ready-documentation): Part 3 of 3. Four maintenance responsibilities, ownership patterns that fail, and the skill set the role actually requires.

## Company

- [About DevDocs](https://devdocs.work/about)
- [How we work](https://devdocs.work/how-we-work)
- [Case studies](https://devdocs.work/work)
- [Talk to us](https://devdocs.work/contact)

## Feeds

- [RSS](https://devdocs.work/feed.xml)
- [Sitemap](https://devdocs.work/sitemap): Human-readable index of public pages.
- [XML Sitemap](https://devdocs.work/sitemap.xml)

## Notes for retrieval

- Every blog post uses the slug-based route `https://devdocs.work/post/<slug>`.
- Posts in a series share a `series` field in their frontmatter (see `/feed.xml` for canonical order).
- Structured data (JSON-LD `BlogPosting`) is embedded on every post detail page.
- This file follows the llms.txt convention. A longer mirror with full expansions is available at `/llms-full.txt`.