Browzer

Developer relations teams and solo engineers are responsible for producing demo videos, blog posts, changelogs, cookbooks, quickstarts, and API documentation to support their codebase. Today this content is written manually, and as the underlying code changes, methods get renamed and features ship, causing samples and docs to go stale or out of sync with the source. Someone has to notice the drift, rewrite the affected content, and manually publish updates. For DevRel leads without a full content team, OSS maintainers running projects at night, and solo DX engineers, this ongoing maintenance competes with actually shipping code.

Browzer connects to a GitHub repository and reads its source, comments, and structure without requiring config files or setup scripts. From that source it drafts demo videos (scripted, voiced, and captioned), SEO blog posts with structured data, cookbooks and sample scripts, quickstarts, changelogs generated from merged PRs, and a full SDK/API reference docs site. When code is merged to main, Browzer detects drift, such as a renamed method, and drafts corrected content across docs, cookbooks, and blog posts, as well as new content to announce shipped features. Users review drafted changes in a review inbox and approve and publish, or enable auto-publish for trusted fixes; content can be published to the user's own site (e.g. via PRs) or generated as a hosted docs site.