Skip to content

Add an account-free temporary preview link #623

Description

@huangdun

Is your feature request related to a problem? Please describe.

After generating a page, users can open the preview in a local browser tab or download the code, but there is no quick way to send the working preview to someone else. A blob: URL only works in the current browser, while downloading the HTML shifts the hosting step to the recipient.

Describe the solution you'd like

Add an explicit Publish temporary preview action beside Download Code in the preview toolbar.

The action would:

  • publish only the currently selected, completed HTML preview;
  • require no account, API key, repository, or deployment configuration;
  • return a public URL that the user can copy or open;
  • clearly identify the preview as temporary and show its expiry;
  • update the same URL on later publishes from the same local project when its scoped update capability is still available;
  • never upload anything until the user clicks the action.

The existing normalized preview HTML appears to be a natural input, so the initial implementation should remain frontend-only and avoid changing the generation pipeline or backend configuration.

Describe alternatives you've considered

  • Open in New Tab is useful for local inspection, but its blob: URL cannot be shared.
  • Download Code is useful for ownership and editing, but the recipient still needs to run or host it.
  • A permanent Vercel/Netlify-style deployment would introduce authentication and project setup for what is often a short review cycle.
  • CodePen-style sharing is useful for editing, but it creates a platform-specific workspace rather than a neutral preview of the generated result.

Additional context

I maintain temp.md, which provides anonymous, expiring static preview URLs and scoped update/revoke capabilities. I would be happy to implement and test this integration if the workflow fits the project.

The proposed PR would include the toolbar state, upload client, locally persisted capability handling, error/loading/success UX, and frontend tests. The integration would be clearly labeled as a third-party temporary publishing action.

Would you be open to a PR with this scope?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions