Static by default
How to publish a MkDocs site
MkDocs turns a folder of Markdown into a finished documentation site. The output folder is called site, which is the detail people get wrong.
- Build command
- mkdocs build
- Folder to upload
- site
Free plan, free SSL, no credit card.
-
Build the project
Run mkdocs build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build.
-
Find the output folder
The build writes a finished site to site. That folder, not the project folder, is what gets uploaded.
-
Drag it in
Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL.
Worth knowing about MkDocs
The folder to upload is
site, notdocs.docsholds your Markdown source, and uploading that publishes your source rather than your site.site_dirin mkdocs.yml changes the output folder. Read it before assuming the default.Set
site_urlto the address the site will live at. The search index and the canonical tags in Material for MkDocs both read it.Use
mkdocs build, notmkdocs gh-deploy. The second one commits to a gh-pages branch, which is a different destination entirely.
Did an AI tool build this project?
Hosting an AI-generated website covers the question that comes before the build command: whether what you are holding is a single file or a project, and which of the two every tool actually hands back.