tinydot renders markdown into a template. It does not do that to your HTML. An .html file is served as its own document, byte for byte, with your styles and your layout and nothing of ours around it.
So if you want to hand-write a site — or have an agent generate one — the folder is the whole deployment.
How it works
Put your files in the folder:
index.html
about.html
styles.css
script.js
photo.jpgindex.htmlbecomes the home page. It replaces the file listing entirelyabout.htmlis at both/aboutand/about.html— link it either waystyles.css,script.jsand images are served with the right content type, so relative links like<link rel="stylesheet" href="styles.css">work unchanged- an
index.htmlinside any folder becomes that folder's page the same way
Every save publishes. There is no build step and nothing to configure.
Mixing HTML and markdown
You do not have to pick one. A folder can hold both: markdown pages get your site's design, HTML pages get whatever you wrote. Use markdown for writing and drop to HTML for the one page that needs to be different — a landing page, an interactive demo, a custom index.
What you still get
Even though the page is yours, the site around it keeps working:
- custom domains and SSL
- access control
- version history for every file
/rss.xml,/sitemap.xmland/llms.txtfrom the markdown pages
What you do not get
Deliberately, because the page is yours:
- no injected CSS, fonts, analytics or footer
- customization settings — colours, menus, logo — do not apply, since there is no template to apply them to
- no markdown processing: no wikilinks, content blocks or syntax highlighting inside an HTML file
Good reasons to do this
- you already have a static site and want somewhere to put it
- one page needs to be interactive and the rest is writing
- you want an agent to build the page and a folder is the simplest thing to hand it
Start free: tinydot.com