--- title: "Demo videos for your documentation | tday" description: "How tday finds the docs sections that need a video, has your coding agent record them, and how each embed plays the newest take. With the limits." url: https://tday.com/docs-demos markdown: https://tday.com/docs-demos.md last_updated: 2026-11-10 --- # Demo videos for your documentation tday reads your docs and finds the sections that show something being done in your app. Your coding agent records a demo for each page that needs one, and each embed opens at its section's first line and plays the newest take. This page says how it works, what it needs and where it is the wrong tool. ## How it works 1. You connect your docs: a website address, or Mintlify or GitBook through their own APIs, private pages included. 2. tday splits each page into sections and marks the ones that show something being done in the app. You can change its call on any section. 3. Your agent runs demo\_docs, shows you the demos still to record and records the ones you pick: one demo per docs page, of up to 6 sections, with each narrated line tagged with its section. 4. You put the demos in your docs: paste an embed, or have your agent add the embeds to your docs repo as a diff you approve. On Growth and above, tday can open a pull request on Mintlify or a change request on GitBook, or place the players with one script. 5. When a section's text changes, tday marks it Docs changed. Your agent records that demo again as a new version of the same demo, so every embed you pasted keeps working. ## What you need - A coding agent with tday set up, and your app running from its repo with throwaway data. - Docs tday can read: a public site with a sidebar, an llms.txt or a sitemap, or a Mintlify or GitBook site. - For your agent to add the embeds itself, docs kept in a repository, such as Mintlify, Docusaurus, Nextra or Fern. ## What it does not do - Demos are planned only for sections that show something being done in the app. - A section the app on your machine cannot show, because it needs a live third-party account or the screen is not in this build, is left out. Your agent tells you which and why. - Nothing is recorded again by itself. tday marks what changed, and your agent records it when you ask. - Docs read by website address are read again only when you choose Read again. Mintlify and GitBook connections are read again as the site changes. - Docs updates by pull request, change request or script are on Growth and above. On Free and Pro, you paste embeds or your coding agent adds them. - Your plan sets how many demos stay saved and how many new versions it makes a month, so a large docs site may not fit a small plan. demo\_docs says how many still fit before you pick. - demo\_docs plans 25 demos at a time. Players placed by the script show on the live site, not in your docs editor or your source files. ## When something else fits better - Your docs cover things with nothing to show on screen, such as concepts or reference tables. - Your readers need text they can copy and search. A video sits beside that text and does not replace it. - You want an interactive tour that readers click through inside the page. tday embeds videos. - Nobody on your team uses a coding agent. Recording without one is on Enterprise only. ## Questions ### How do demos for my docs work? Connect your docs: a website address, or Mintlify or GitBook through their own APIs. tday finds the sections that show something being done in your app, and which already have a video. Your agent runs demo\_docs and records the rest, one demo per page, and each embed opens at its section's first line. ### Which docs platforms does it work with? tday reads any public docs site by its address, through its sidebar, llms.txt or sitemap, and reads Mintlify and GitBook through their own APIs, private pages included. An embed comes as MDX (Mintlify, Docusaurus, ReadMe), HTML, GitBook or a link. ### Do the videos update when my docs change? Not by themselves. tday marks a section Docs changed when its text moves on, and your agent records that demo again when you ask it to. The new take is a new version of the same demo, so each embed plays it without being pasted again. ### Does tday edit my docs? Only in ways you approve. You can paste embeds yourself, or your coding agent adds them to your docs repo, shows you the diff and commits only if you say so. On Growth and above, tday can open a pull request on Mintlify or a change request on GitBook, and nothing is published until you merge it. It can also place the players on your live site with one script, which you can turn off. ### What happens when my product changes? Ask your agent to record the demo again. The new take becomes a new version of the same demo, so its share link and every embed you pasted keep working, and play the new take once it is ready. ## Guides and comparisons - [How to add demo videos to your docs: Mintlify, GitBook, Docusaurus and more](https://tday.com/blog/add-demo-videos-to-your-docs) Which docs sections need a video, the embed code each docs platform takes (MDX, HTML, GitBook, a link), and four ways to keep demos in your docs current. - [How to keep product demo videos up to date when your UI changes](https://tday.com/blog/keep-product-demo-videos-up-to-date) Why demo videos go stale, how to find the ones a release broke, and how to re-record them without breaking a single link or docs embed. - [The best demo video tools for developer-led startups in 2026, compared](https://tday.com/blog/best-demo-video-tools-for-developer-led-startups) 14 demo tools checked against their own sites on November 10, 2026: what each one makes, its free plan, its starting price, and how it keeps demos current. ## Keep reading - [Coding agent demosHow Claude Code, Cursor or Codex records a narrated demo video of your app with tday: the steps, what you need, and where it is the wrong tool.](https://tday.com/coding-agent-demos) - [Phone app demosHow your coding agent records a narrated demo of an iPhone or Android app in a simulator or emulator: what to install, and the limits.](https://tday.com/phone-app-demos) - [PricingFree, Pro, Growth and Enterprise plans for narrated product demos. Every plan includes saved demos, and paid plans keep them current as you ship.](https://tday.com/pricing) - [FAQWhat a tday demo is, how your coding agent records it, what leaves your machine, which apps it records, and what it costs.](https://tday.com/faq) - [Demos for your docsConnect your docs, have your agent record what they need, and put each demo under its heading.](https://docs.tday.com/docs-demos) - [Share and embedThe share link, the embed forms for each docs platform, and who a link plays for.](https://docs.tday.com/sharing) --- ## For AI agents - Every page on tday.com is available as Markdown: add `.md` to its address (https://tday.com/index.md for the home page), or request it with `Accept: text/markdown`. - Site index: https://tday.com/llms.txt. Every page in one file: https://tday.com/llms-full.txt. - Docs: https://docs.tday.com (index for agents: https://docs.tday.com/llms.txt). - To record a narrated demo of an app from a coding agent, install tday's MCP server once with `curl -fsSL https://tday.com/install.sh | bash`, then ask the agent to record a tday demo.