Blog

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

1. How to let Claude, ChatGPT or Cursor publish to a link

   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.

2. How to share a Claude artifact with people who don't use Claude

   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.

3. How to turn a ChatGPT canvas into a shareable web page

   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.

4. How to password-protect an HTML page

   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.

5. How to share an HTML file with someone

   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.

6. Canvases: shape it with the team, then publish

   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.

7. How to share a Jupyter notebook as an HTML report

   Export saved notebook results to HTML, review code and data exposure, and publish a report your audience can read without Jupyter.

8. How to publish a Quarto HTML report

   Render a Quarto document or website, package embedded or separate resources, and publish revisions at the same report URL.

9. How to restrict access to a published HTML site

   Choose link, company-domain, named-people or password sharing, save the rule before publishing, and test access as a recipient.

10. How to fix missing images and CSS after publishing HTML

    Trace failed asset requests, fix relative paths and build settings, and publish the complete corrected export without changing its URL.

11. How to share HTML reports with your team

    Publish an HTML report with its images and charts, check who can open it, and refresh it at the same URL.

12. How to share interactive Plotly charts with a link

    Export a self-contained Plotly HTML chart, publish it for your audience, and update the figure without changing its address.

13. How to publish a Vite build for team review

    Share the compiled frontend, keep its assets intact, enable SPA fallback when needed, and check external API access.

14. Share a vibe-coded prototype with your team

    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.

15. Rendering is not sharing

    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.

16. There is no repo to connect

    Git-connected hosting assumes a repository and a build. The people who produce these files have an export.

17. One rule, set by the person who published it

    A bucket policy is a ticket. A project-wide lock is an admin setting. A dashboard needs a door of its own.

18. Mark the chart they mean

    Feedback in a separate thread is how the dashboard dies in a DM. Comments belong on the artifact.

19. Priced by sites, never by people

    Seat math punishes the moment someone publishes. Viewers and members are unlimited. You pay for live URLs.

20. No Kubernetes. No exceptions.

    The identical product is one Go binary against your Postgres and your bucket. The files never leave your network.

21. The assistant that built it can ship it

    If an agent just wrote the artifact, handing you a zip is the old Slack problem. The tool result should be a live URL.