FluidDocs Templates - Create HTML docs that answer and report back, in minutes

FluidDocs templates are interactive HTML documents for what you already write: resumes, proposals, term sheets, offers, investor updates, API docs. Every template is the real document, live at a real URL: pick a package and the proposal reprices itself, paste a key and the API reference rewrites every example. Q&A and reader analytics come out of the box. One click and a simple prompt make any of them yours. If the documents you send are still static, you are not leveraging what AI can do.

Add a comment

Replies

Best
Hey Product Hunt, we are thrilled to launch our revamped template gallery today: interactive HTML documents for resumes, proposals, term sheets, decks, and API docs that answer questions and report back, in minutes šŸŽ‰ Every document we used to send, we would export, attach, and hear nothing the moment it left us. Slack shows replies. Figma shows comments. Loom tells you who watched and how far they got. The document that actually mattered told us nothing. So we started building ours as interactive HTML instead, and this gallery is the fastest way to feel the difference. Pick the template for the document you were about to write, copy it with one click, and a simple prompt makes it yours. Every template ships with: āœ… Hosted at a real URL āœ… Answers reader questions from the document and any knowledge you attach āœ… Reader analytics: visits, locations, interactions, questions asked āœ… Reader decisions captured: acceptances, sign-offs, ticked steps The best way in: open the API reference in the screenshots, paste any key, and watch as every example is rewritten. Open the gallery (), try a template, and tell us which document you keep rebuilding from scratch. We are taking template requests all day.

One of my favorite templates here, that we kind of built for ourselves, is the interactive API doc template, We typically use a branded version of this template to personalise it for our customers, having examples of exactly the parts of our API that they care about for their documents.

I used to use the more dry traditional API documentation generators, but making this kind of documents actually interactive and personalised can really help you close a technical sale.

It's this one here: , let us know if you remix it and try it out!