How to publish a Quarto HTML report
Guides ·
A Quarto report combines the analysis and its explanation in one document. To share it with a reader, first render the document into files their browser can open. Publidock can give those files a URL while you keep the source project in your normal workflow.
The publishing decision is whether to send one HTML document or a complete rendered folder. That depends on the report's resources and whether it belongs to a larger website.
Render one report to HTML
For a single document, use Quarto's HTML output:
quarto render report.qmd --to html
Check the rendered file before uploading it. If it relies on a supporting directory, keep that directory beside the HTML when you publish. Uploading only the page can leave its styles, images or scripts behind.
For a report you want to package as one file, add this to its YAML header:
---
title: "Example quarterly report"
format:
html:
embed-resources: true
---
Render the document again. This option embeds linked resources into the HTML. Some features can still load resources dynamically, so test the result rather than assuming every dependency has disappeared. Quarto's HTML basics explains self-contained output and its limits.
For a website, upload the rendered output
A report with several linked pages is often better kept as a website. In a Quarto website project, run a full render:
quarto render
The default website output directory is _site; use the configured output directory if your project changes it. Upload that rendered folder, or ZIP its contents with the entry page and assets together. Include generated page and resource files, rather than the source .qmd files or the temporary preview server.
The Quarto website guide describes the output directory and recommends a full render before deployment, including after previewing edits.
Review what the export contains
Read the rendered report as a recipient. Confirm the reporting period, units and source notes are visible. Check navigation, footnotes and images, including a narrow browser window.
For an internal analysis, review tables and chart data before publishing. Collapsing a section or hiding code in the page does not make the information private if it remains in the delivered files. Remove material the audience should not receive at the source, then render again.
A conventional HTML export contains the results produced during rendering. Publidock does not run an R or Python server for later calculations. If a control expects a live backend, host that backend separately and verify its authentication, or share a report that already contains the required results.
Publish with the intended sharing rule
Upload the rendered report to Publidock, check the preview and choose who can open it before Go Live. Use link sharing only for content anyone with the address may read. Company-domain, named-people and password rules depend on the plan; the access guide explains how to check them as a viewer.
API and MCP uploads can publish immediately with the site's current rule. Configure a restricted audience before sending confidential exports through an automated route. Search-engine exclusion does not make a public link private.
Re-render and publish the next version
For the next reporting period, update the source, render again and upload the complete result as a new version of the same site. Verify the live page before announcing the refresh. Its URL and sharing rule stay in place.
If the page looks right locally but loses styling after upload, compare the requested paths with the files you published. The missing images and CSS guide walks through that check. For the broader handoff, see sharing HTML reports with your team.