Browzer lets users connect their codebases to auto-generate docs that self heal and technical content (blogs, quickstarts, cookbooks, videos) that are human & agent friendly. We automate all technical output of a DevRel so that DevRel teams can focus more on community, growth & events. Try it out at - https://trybrowzer.com
Connect your GitHub repo and Browzer drafts your docs, guides, changelogs, cookbooks, quickstarts, and SEO & AEO friendly blog posts, and then heals them on every merge. We automate all technical output of a DevRel so that DevRel teams can focus more on community, growth & events.
@yangliu44 you’re free to configure Browzer to your liking. We’ve seen some teams be okay with it being a full autopilot scenario. But some teams turn off autopilot mode, so that they can review the content. In these cases, people usually spend 5-10 mins reviewing the content & making minor edits, as opposed to spending a few hours to create the entire content from scratch.
Report
The SEO and AEO content support is a nice addition alongside the developer docs. Curious how much control users have over the writing style.
@johnnie_kuvalis the AI takes the first pass at writing things up. After the writes the content, you can either allow it to auto publish, or you could review the content before it’s published. By default, auto approvals are turned off, so humans are required to review content, and in the process you can also update things as needed. Additionally, before any content is written, you can configure a brand voice/tone in the “Configurations” tab
@adams_parker we haven’t heard any complaints so far about our docs not working on a codebase. But that doesn’t mean there couldn’t be an issue. From what we have heard and seen, our docs are accurate in almost all cases. However, if you have an older codebase, I’d love for you to try us out & let us know of your thoughts. If something’s not working, would love to get your feedback and be happy to fix things as needed
@yelyzaveta_kibets it keeps the human phrasing. But we also have a separate section where you can activate changelog entries. So with every code update you have docs that self heal and maintain human & agent phrasing + you also get changelog entries to show how your product evolves over time
@sansa_grey thank you! And yes, that’s the goal. Make lives of trans handling docs & technical content easier, so they have time to focus on other critical things
How much human review is expected before this stuff goes live? Fully autopilot content makes me a little nervous for anything customer-facing.
Browzer
The SEO and AEO content support is a nice addition alongside the developer docs. Curious how much control users have over the writing style.
Browzer
Bababot
am curious how this performs with a messy or older codebase. thats usually where documentation tools get seriously tested.
Browzer
Softorino 💻📲
Docs on the site I do SEO for go stale within a week of a release. Does auto-updating keep the human phrasing, or does it read like a changelog?
Browzer
Softorino 💻📲
@rahulkumaran4 That split is what mine are missing. Docs drift into release notes and then neither one reads like it was written for anyone.
Buffup.AI
Nice features, I have seen teams spend hours updating examples and changelogs manually. Automating that repetitive work could be a real time saver.
Browzer