Tools for crafting product release content (changelogs, docs, blogs), announcements, and feedback.
Learn more »
💬 Discord
·
🌐 Website
·
🐛 Bugs
·
🗺️ Roadmap
ℹ️ Floe is currently in alpha. You will probably experience bugs, and in the interest of moving quickly I may introduce breaking changes.
- ✅ Write changelogs, blogs, and docs (coming soon) in Markdoc
- ✅ Git-backed
- ✅ Open source
- ✅ Reactions
- ✅ Multi-repo support (co-locate content with code)
- ✅ React Primitives
- 🔜 Feedback forms
- 🔜 Emails
- 🔜 Slack integration
- 🔜 AI writer
- 🔜 Analytics
Check out the Roadmap for more.
Examples:
- 🚢 Changelog
- ✍️ Blog
- 📖 Docs (coming soon)
Check out the tutorial in the (temporary) docs to get started.
Product release comms are hard. Beamer, Canny, Product Board and a dozen other companies offer some great solutions for rolling content for a release, annoucements, and getting feedback. But when it comes to control and customization, they fall flat. Not only that, but these tools don't enforce a single source of truth; instead your changelogs, blogs, and docs get spread across multiple services.
That's where Floe comes in:
-
Open source Great products are built through collaboration and feedback. That's why Floe is completely open source.
-
Single source of truth Floe is backed by git. Use your codebase as your single source of truth.
-
Content <> UI de-coupling Treat your content for what it really is: data. Co-locate your data with code across multiple repositories. Plus, there's no need to redeploy your templates everytime you ship a data change.
-
Built on React Get started quickly with a pre-built Floe template. Or use Floe's Primitives library to create your own.
Floe is in alpha. While in alpha, you can expect bugs, and breaking changes to the API may occur. That being said, the project is starting to reach a point of stability. If you need more stability, I would recommend waiting for the beta. Check the changelog for status updates.
To contribute check out the guidelines here.