Blog
Migrate From GitBook or mkdocs in One Command
The single biggest thing standing between a team and switching docs tools is almost never the tool itself - it's the migration. Nobody wants to hand-convert three hundred Markdown files and their nav structure. bxSites migrate exists specifically to remove that excuse, for the two sources I hear about most: GitBook and mkdocs.
Never Lose a Reader: Versions and Translations
Two of the fastest ways to lose a documentation reader: they land on docs for the wrong version of your software, or they land on a page in a language they don't read well and there's no obvious way out. BX Sites handles both the same way it handles most things - a folder convention, no config flag to remember to flip.
Search That Just Works
Search is one of those features that either quietly works or loudly doesn't, and for a static docs site it's easy to end up with the latter - no server to query, so search either gets bolted on as a third-party widget or skipped entirely. BX Sites takes the same approach mkdocs does by default: fully static, fully client-side, no server or external service required.
Pick Your Theme
One question I get a lot after someone runs bxSites new for the first time: "which theme should I actually pick?" The honest answer is that it barely matters at the feature level - all three built-in themes ship the exact same set of capabilities. It's purely a question of which one matches your project's own visual identity.
Get Your Docs Live in 10 Minutes
I've written a lot of documentation tools over the years, and the thing I keep coming back to with BX Sites is how little ceremony is involved in going from nothing to a real, browsable static site. No config wizard, no plugin marketplace to shop through first - just a folder of Markdown and one command.
Categories
- Getting Started (3)
- Migration (1)
- Search (1)
- Themes (1)
- Versioning & i18n (1)