If your product docs are markdown files — or you want them to be — tinydot turns the folder into the docs site. This page you're reading is one: docs.tinydot.com is a tinydot folder.

How it works

  1. Create a site at tinydot.com — it appears as a folder in your Files app
  2. Put your markdown files in it. Folders become sections, files become pages
  3. Point your domain at it (custom domains) — done

Every save publishes. No build step, no CI, no deploy.

What a docs site gets

  • clean reading layout with navigation from your folder structure
  • wikilinks between pages, content blocks for reusable snippets
  • syntax highlighting for code
  • search, tags, RSS, sitemap, and llms.txt (so AI assistants can read your docs)
  • access control — internal docs restricted to your company's Google domain
  • drafts for unfinished pages
  • version history for every file

Migrating existing docs

Already have docs somewhere else? Import them from a URL — tinydot crawls the site and recreates the pages as markdown files in your folder. From there they're yours: plain files, any editor, no lock-in.

Why files

Docs platforms come and go, and their editors hold your content. A folder of markdown outlives all of them — and your whole team already knows how to edit a text file.

Start free: tinydot.com