Use Case

floors.js for Documentation

Developers get stuck on your docs pages every day. They re-read the same paragraph, scroll back and forth, and eventually give up. floors.js lets you see exactly where they are and help them before they abandon your tool.

Get started — from $14/mo See how it works

The problem every docs maintainer faces

Developers read your documentation, get stuck, and either open a GitHub issue hours later or abandon your tool entirely. You have no visibility into who's struggling or where. By the time someone files an issue, they've already wasted an hour and they're frustrated.

Support channels are async. Discord messages go unanswered for hours. Stack Overflow questions take days. The developer who needed help 10 minutes ago has already moved on to a competing library.

What floors.js does for docs sites

Every documentation page becomes a room. You can see developers reading your getting-started guide, your API reference, your troubleshooting page. When someone lingers on a page, you know they might need help — and you can jump in and assist them in real-time.

Where docs teams use it

Getting started guides
Help new users through setup step by step. See when they're stuck on installation and walk them through it live.
API reference
Clarify confusing endpoints, explain parameter types, and share working examples in real-time conversation.
Troubleshooting pages
Fix issues in real-time. When a developer lands on your error reference, they need help now — not in 24 hours.
Migration guides
Walk developers through version upgrades together. Breaking changes are less painful with someone to guide you.

Real-time support, right on the docs page

The biggest documentation problem isn't bad writing — it's that help is disconnected from context. A developer reads your API reference, gets confused, switches to Discord, describes the problem from scratch, waits for a reply. By then they've lost 30 minutes and all their momentum.

floors.js puts help where the context already is. When a developer is stuck on your authentication guide, they can see other people on that same page. Maybe another developer who just figured it out. Maybe a maintainer who can clarify the confusing paragraph. The conversation happens right there.

For open-source projects especially, this reduces GitHub issue noise. Questions that would become issues get answered live by community members or maintainers. Faster for the developer, less backlog for you.

One line to install

<script src="https://floorsjs.com/embed.js" data-key="flr_..."></script>

Paste it before </body> in your docs layout. Works with Docusaurus, GitBook, VitePress, Mintlify, Nextra, MkDocs, or plain HTML. Every page becomes a room automatically. No configuration, no plugins, no build step changes.

Frequently asked questions

Does it work with Docusaurus?
Yes. Add the script tag to your docusaurus.config.js using the scripts array, or paste it in a custom layout wrapper. Each docs page becomes a room automatically.
What about VitePress or GitBook?
VitePress: add the script in your .vitepress/config.js head configuration. GitBook: use custom code injection if available on your plan. Any platform that allows custom HTML works.
Will it slow down docs page loads?
No. The script loads asynchronously after your page content. Three.js only initializes when someone opens the widget. Zero impact on documentation load times.
Can maintainers be identified?
Maintainers can set their display name via the data-name attribute on the script tag. This way, visitors know when a maintainer is in the room.
Is the chat indexed by search engines?
No. Chat messages are real-time and ephemeral — they're not stored in the DOM or indexed by crawlers. Your docs SEO is unaffected.

Alternatives & Comparisons

Intercom Alternative Crisp Alternative Tidio Alternative tawk.to Alternative vs Gather vs SpatialChat