What FOSS Documentation Needs to Thrive in the Age of AI Search

Search behaviour is evolving in ways that matter for everyone who writes for open source software. Developers increasingly reach for AI tools mid-workflow to make decisions and/or to get unstuck. They ask specific questions and get synthesized answers. If your documentation, README, or technical blog post are not the sources that answers come from, you've most likely lost a moment of visibility.

This talk is about what it means for FOSS documentation and technical writing to get cited rather than just indexed. This talk looks at what specific, well-scoped, and deeply useful writing actually looks like across the formats open source projects produce: README files, API references, tutorials, contributor guides, and technical blog posts.

• Documentation that is vague or thin makes your project invisible in AI-assisted developer workflows

• What content that is written to be cited actually looks like

• How these structural and editorial content properties apply across formats: READMEs, tutorials, API docs, and technical blog posts