Publishing
Take your site live or offline, and choose whether edits publish on save or when you click Publish.
Actualizado el 19 nov 20263 min de lectura
Two settings control what readers see: site status decides whether your site is up at all, and deploy mode decides when edits reach it. Both are in Settings > Publishing, which only the project owner can change.
Site status
| Status | What visitors see |
|---|---|
| Live | Your documentation |
| Offline | A "Documentation coming soon" page with your project name, logo, and primary color |
New projects start offline
A new project starts offline, so you can write and organize before anyone sees it. Your URL is reserved in the meantime.
When you're ready, click Go live in Settings > Publishing. The editor also shows a Go live button while your site is offline.
Taking a site offline
Click Take offline in the same place. Nothing is deleted: your pages, navigation, and settings stay as they are, and the editor keeps working. While a site is offline, its Markdown pages, llms.txt, and MCP server don't serve your content either.
Deploy mode
Auto-deploy (default)
In Settings this is Publish on save. Every save publishes. Typemark commits the page, compiles it in the background, and your live site updates a few seconds later.
Manual deploy
In Settings this is Publish when you choose. Saves are committed to your repo, but readers keep seeing the last published version until you publish. Use it when you're reworking several pages and don't want readers to see them half-done.
Switch to manual
In Settings > Publishing, under When changes go live, select Publish when you choose.
Edit and save
Change as many pages as you like. The editor shows "Manual deploy — you have unpublished changes" while edits are waiting, marks each page that isn't live yet with a dot in the page list, and shows how many there are on Publish. A page is marked when its translation has edits waiting too. The project overview counts them under Pages.
Publish
Click Publish in the editor's top bar, or Publish all changes in Settings > Publishing. Every page with unpublished changes goes live at once, along with its Markdown version and search results.
In the editor's top bar, the site's state changes from Not published to Publishing to Live. In both places, a message then says how long publishing took and how many pages changed, with Open site and Copy link.
Manual mode holds back page content only. Some changes go live right away:
- A page's title and description update when you save.
- Creating, renaming, or deleting pages, reordering navigation, and changing settings rebuild the site and publish straight away. Pages with unpublished edits stay as they are until you publish them.
- On a connected repo, pushes to your deployment branch rebuild the site and publish the pages they change.
- A
typemark pushfrom the CLI publishes the pages it changes.
New and updated AI translations are held back like your edits, so Publish is where you review them.
Switching modes
- Auto to manual: nothing changes on your site. It's already up to date.
- Manual to auto: if you have unpublished changes, Typemark asks you to publish them first. Click Publish and switch to publish everything and switch.
Status and mode together
| Site status | Deploy mode | What happens |
|---|---|---|
| Live | Auto | Every save publishes. |
| Live | Manual | Your site is up. Edits wait until you publish. |
| Offline | Auto | Visitors see "coming soon". Saves publish to the hidden site, ready for when you go live. |
| Offline | Manual | Visitors see "coming soon". Edits wait until you publish. |
Deleting a project
The project owner can delete a project in Settings > Delete project: type the project's slug to confirm.
- The published site goes offline at once, at its typemark.dev address and any custom domain.
- Its pages, deployment history, analytics and members are deleted, along with the repository Typemark hosts. You can't undo this.
- A connected GitHub repository isn't changed or deleted.
Want to keep the content? Connect a GitHub repository or typemark pull a copy first.
When a build fails
If a page fails to compile, readers keep seeing the last version that built, and the editor shows the error. If a full build fails, for example because typemark.json isn't valid JSON, your live site keeps serving the previous build and the error shows on your project's overview page.
Settings > Deployments lists your 20 most recent deployments with their status, commit, and page count.