Browzer
Put your technical content on autopilot
Start new thread

Browzer - Put your technical content on autopilot

by
•
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.

Add a comment

Replies

Best

How well does it support monorepos? I imagine a scenario where there are a dozen microservices and am curious if the healing code is service-oriented or treats the entire repository as one entity.

Congrats #makers! How does it better from competitors? And what will be the best usp of browzer?
Maker
thanks! Most competitors today focus on docs only - Mintlify, fern, stainless, gitbook. We focus not only on docs but also on technical content. Our pricing structure is also different, in many cases a lot more cost effective than competitors. Usp - most customers today love our video generation capabilities. Technical content workflows is our wedge, but video content is what makes people stay

very interesting project! i'm curious: how long did it take u to built it?

Nice features, I have seen teams spend hours updating examples and changelogs manually. Automating that repetitive work could be a real time saver.

Maker
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

am curious how this performs with a messy or older codebase. thats usually where documentation tools get seriously tested.

Maker
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

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?

Maker
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

  That split is what mine are missing. Docs drift into release notes and then neither one reads like it was written for anyone.

the self-heal on merge part is the interesting bit to me - how granular is the trigger? like if I rename a variable that shows up in a code snippet inside a guide but the surrounding explanation is still 100% accurate, does Browzer regenerate the whole page or just patch the snippet? asking because I've used doc tools before where "auto-heal" ended up meaning "rewrite everything every time," which creates its own review burden even if nothing important actually changed.

Maker
great question. Self healing wouldn’t regenerate the whole thing. Only updates whatever is necessary - nothing more, nothing less. You’d also be able to view a “diff”-based view of every doc or piece of content that self heals to see what portions of the docs are being updated.

How much human review is expected before this stuff goes live? Fully autopilot content makes me a little nervous for anything customer-facing.

Maker
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.

heals them on every merge is the interesting claim and also the hardest one to keep true. a merge tells you the code changed. it does not tell you whether the doc was describing the behaviour or the reason behind it, and only one of those survives a refactor that keeps the behaviour identical.

First
Previous
12