floorsProject 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
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
Paste it before </body> in your docs template. Works with Docusaurus, VitePress, Starlight, MkDocs, or any static site generator.