FluidDocs
Interactive HTML docs that answer questions and report back
245 followers
Interactive HTML docs that answer questions and report back
245 followers
FluidDocs are interactive HTML documents that keep working after you hit send. A proposal that reprices itself, an offer with live equity math, an API reference that rewrites its examples around the reader's key. Every document answers questions from its own content, and reader analytics come out of the box. The open source Deck Builder that launched here lives on as part of the platform, and the template gallery at fluiddocs.ai/templates is the fastest way in.
This is the 3rd launch from FluidDocs. View more
FluidDocs CLI
Launched this week
FluidDocs CLI turns your prompts into interactive documents that answer questions and report back. You see who opened it, how far they got, and what they asked. Pitch decks, proposals, reports, board updates. One line installs the CLI and one command publishes. Edit later by prompt, and the same link updates. Viewer-side AI-enabled Q&A and analytics come built in.
Free Options
Launch Team / Built With
FluidDocs
Hey Product Hunt, we are thrilled to launch the FluidDocs CLI. 🎉
FluidDocs are interactive documents that keep doing their job after you hit send: readers ask them questions and get answers from the document itself, and you see who opened them, how far they got, and what they asked.
The reason we built a CLI is that more than half of the 1,000+ documents created on FluidDocs, were created programmatically, by coding agents working through our MCP, not by a person clicking in the app. Our users' agents were already writing the documents. They needed a first-class way to publish and maintain them.
So now one line installs fld, and from there everything runs in the terminal:
✅ Publish a file, a zip, or a whole directory as an interactive document
✅ Turn on reader Q&A with one command
✅ Pull reader analytics back into the terminal
✅ Edit the live document later, and the same link updates
✅ --json on every command, so your coding agent can run the whole flow unattended
The best way in: install, run fld login, and publish something you already have. Or try the SpaceX S-1 as a FluidDoc at https://share.fluiddocs.ai/spacex-s1 and ask it a question a static document could never answer.
We are taking command and workflow requests all week. Tell us what your publishing flow needs and we will build it.
@nishant_aggarwal When I send someone a doc, do they need an account or an app to ask it questions, or does the link just work in their browser? My clients will not sign up for anything, so this is the whole decision for me.
FluidDocs
@abhiranjan_mehta, that is a great question. Your clients don't need to sign up for an account. They can just ask a question right away from the moment they receive the document from you. Feel free to try asking questions from the SpaceX S-1 (a 300-page static document otherwise) here just as an example: https://share.fluiddocs.ai/spacex-s1
@nishant_aggarwal Not a terminal person at all, is there a way to do this without the command line, or is that the whole point?
FluidDocs
@suyash_kr, we just launched our CLI today. But we have a full web app that you can try by signing up for a free account at https://fluiddocs.ai, and you won't need to use the terminal at all. The terminal is just one of the ways to use it.
One of the cool things about the CLI (vs MCP) is that it's a lot faster, and you get a very readable trace of the commands that the agent executed, then you can use it to build especialized document skills with greater control.
For example a very simple loop that I use when I publish a fluid doc, is to use claudecode + cli to get the questions that the users have asked on the document's QNA chat to improve the document itself.
FluidDocs
@ricardo_david_pacheco being an active MCP user myself, I feel that difference so much as well :)
ProductBridge
Really interesting approach to making documents interactive instead of static. The built-in Q&A and engagement analytics could be especially useful for pitches and proposals.
How does FluidDocs handle AI-generated answers when viewers ask questions that go beyond the original document?
FluidDocs
@hareesh_vemasani FluidDocs is essentially a file system, so for context beyond the document, a user can point the AI Q&A chat to any other document in the file system. That is a feature available out of the box. Additionally, we offer advanced features to be extended to documents/context outside of FluidDocs as well (e.g., Google Drive, OneDrive, etc.). Would be very happy to give you a demo :)
Lancepilot
FluidDocs
@priyankamandal that's one of my favorite parts too. You can try it free at https://fluiddocs.ai
I'm looking forward to digging in to see how I could use it with the Kithli pitch deck as we prepare to raise a pre-seed round. But, even before that with the Revenue Leakage research project we're running with ASCs.
FluidDocs
@lydia_sugarman those are great use cases - would be very happy to give you a demo/help answer any questions at all :)