# floors.js for _Open Source_

A developer just found your project on GitHub and clicked through to your docs. They have a question. Without floors.js, they'll open an issue. With it, someone in the community answers them live.

## Project sites feel abandoned

Open-source project sites are static. Contributors check the docs, get confused, and either open GitHub issues (slow) or give up entirely. Discord and Slack are separate silos. **The project website itself — where new users land first — feels dead.**

## What floors.js does differently

floors.js turns your project site into a community space. Documentation pages become rooms. Contributors on the same doc page see each other. Maintainers can provide real-time help right where the content lives.

- **On-page help** — newcomers get answers right on the docs page, not in a separate chat app
- **Community building** — contributors discover each other naturally on the project site
- **Fewer issues** — questions get answered live instead of becoming GitHub issues
- **Maintainer presence** — show the community that maintainers are active and reachable

## Where OSS projects use it

- **Getting started guide**: Newcomers help each other through setup. Someone who just got it working helps the next person.
- **API reference**: Developers discuss edge cases and share code snippets right on the API docs page.
- **Contributing guide**: Maintainers onboard new contributors live, walking them through the codebase and PR process.
- **Release announcements**: Community gathers on the changelog page to discuss new versions, ask questions, and share feedback.

## Reduce issue noise, increase contributor happiness

Open-source maintainers drown in GitHub issues that are actually just questions. "How do I configure X?" or "Does this work with Y?" — these don't need issues, they need a 30-second conversation. But there's nowhere on the docs site to have one.

floors.js creates that space. A developer stuck on your getting-started guide can see that two other people are on the same page. One of them might have the answer. A maintainer might drop in. **The question gets resolved in minutes instead of days.**

For growing projects, this creates a community flywheel. Early contributors who got help on the docs site stick around to help newcomers. The project website goes from documentation repository to community hub — without the overhead of managing yet another Discord server.

## One line to install

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

Paste it before `</body>` in your docs template. Works with Docusaurus, VitePress, Starlight, MkDocs, or any static site generator.

## Frequently asked questions

**Is floors.js itself open-source?**  
The embed widget code is visible and unminified. The server component is not open-source. The product is $14/month or $99 lifetime for a site key.

**Does it work with Docusaurus?**  
Yes. Add the script to your docusaurus.config.js via the scripts configuration. Each docs page becomes a room automatically.

**What about VitePress or Starlight?**  
VitePress: add the script in .vitepress/config.js head. Astro Starlight: add it in astro.config.mjs head. Both work out of the box.

**Will it add load time to my docs?**  
No. The script loads asynchronously after page content. Three.js only initializes when someone opens the widget. Documentation load times are completely unaffected.

**Can community members moderate chat?**  
Chat is rate-limited (1 message per second) and input-sanitized. For heavy moderation needs, keep using Discord. floors.js is designed for casual, helpful conversations.