# Blog

Arguments, not announcements. Why Publidock is this shape — sharing, publishing, pricing, review, and self-hosting.

Source: https://publidock.com/blog

- [How to let Claude, ChatGPT or Cursor publish to a link](https://publidock.com/blog/connect-ai-assistant-to-publidock/index.md): Connect Publidock over MCP once, choose what the assistant may do, and ask it to publish what it made. Steps for Claude, ChatGPT, Claude Code, Cursor and more.
- [How to share a Claude artifact with people who don't use Claude](https://publidock.com/blog/share-claude-artifact-outside-claude/index.md): Shared Claude artifacts need a Claude account to open. Publish the artifact to its own link instead, from Claude itself or by hand, and choose who can open it.
- [How to turn a ChatGPT canvas into a shareable web page](https://publidock.com/blog/chatgpt-canvas-to-web-page/index.md): Move a page from ChatGPT's canvas to a lasting address: publish through the connector or copy the code into a file, keep secrets out, and update at the same link.
- [How to password-protect an HTML page](https://publidock.com/blog/password-protect-html-page/index.md): Why a password in JavaScript protects nothing, how to have the host check it before the page is sent, and when a sign-in rule is the better choice.
- [How to share an HTML file with someone](https://publidock.com/blog/how-to-share-an-html-file/index.md): Attachments break and cloud drives no longer render HTML. Give the file its own address, choose who can open it, and fix the paths that commonly break.
- [Canvases: shape it with the team, then publish](https://publidock.com/blog/canvases/index.md): A private canvas for a project's pages, screens, decks and design system. Send work in from your AI tool, change it in place, review it on the frame, and publish when it's right.
- [How to share a Jupyter notebook as an HTML report](https://publidock.com/blog/share-jupyter-notebook-as-html/index.md): Export saved notebook results to HTML, review code and data exposure, and publish a report your audience can read without Jupyter.
- [How to publish a Quarto HTML report](https://publidock.com/blog/publish-quarto-html-report/index.md): Render a Quarto document or website, package embedded or separate resources, and publish revisions at the same report URL.
- [How to restrict access to a published HTML site](https://publidock.com/blog/restrict-access-to-published-html/index.md): Choose link, company-domain, named-people or password sharing, save the rule before publishing, and test access as a recipient.
- [How to fix missing images and CSS after publishing HTML](https://publidock.com/blog/fix-missing-images-and-css-in-html-uploads/index.md): Trace failed asset requests, fix relative paths and build settings, and publish the complete corrected export without changing its URL.
- [How to share HTML reports with your team](https://publidock.com/blog/share-html-reports-with-your-team/index.md): Publish an HTML report with its images and charts, check who can open it, and refresh it at the same URL.
- [How to share interactive Plotly charts with a link](https://publidock.com/blog/share-interactive-plotly-charts/index.md): Export a self-contained Plotly HTML chart, publish it for your audience, and update the figure without changing its address.
- [How to publish a Vite build for team review](https://publidock.com/blog/publish-a-vite-build-for-review/index.md): Share the compiled frontend, keep its assets intact, enable SPA fallback when needed, and check external API access.
- [Share a vibe-coded prototype with your team](https://publidock.com/blog/share-a-vibe-coded-prototype/index.md): If it runs in the browser, it can have a live link your team signs in to see. What works, what does not, and the one setting a single-page app needs.
- [Rendering is not sharing](https://publidock.com/blog/rendering-is-not-sharing/index.md): Slack now shows an HTML attachment inside the channel. That fixes looking at one file. It does not give the file an address, a door, or a current version.
- [There is no repo to connect](https://publidock.com/blog/there-is-no-repo-to-connect/index.md): Git-connected hosting assumes a repository and a build. The people who produce these files have an export.
- [One rule, set by the person who published it](https://publidock.com/blog/one-rule-per-site/index.md): A bucket policy is a ticket. A project-wide lock is an admin setting. A dashboard needs a door of its own.
- [Mark the chart they mean](https://publidock.com/blog/mark-the-chart/index.md): Feedback in a separate thread is how the dashboard dies in a DM. Comments belong on the artifact.
- [Priced by sites, never by people](https://publidock.com/blog/priced-by-sites-never-by-people/index.md): Seat math punishes the moment someone publishes. Viewers and members are unlimited. You pay for live URLs.
- [No Kubernetes. No exceptions.](https://publidock.com/blog/no-kubernetes-no-exceptions/index.md): The identical product is one Go binary against your Postgres and your bucket. The files never leave your network.
- [The assistant that built it can ship it](https://publidock.com/blog/the-assistant-ships-it/index.md): If an agent just wrote the artifact, handing you a zip is the old Slack problem. The tool result should be a live URL.