Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optional Share Temporary Preview action for HTML exports

Open
  • Is something wrong?
#2,738 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, html, markdown
Domain
api, desktop, security

Research direction

Start with VNote's existing HTML export flow and the temp.md documentation linked in the issue; identify the export entry point and asset collection path. Review the proposed tests for asset collection, failed uploads, stable-URL updates, and revocation. Done means the opt-in action supports temporary previews without changing local export behavior and keeps service secrets out of notes and bundles.

Written by the indexing model from the issue text.

Description

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

VNote can export a note or notebook as browser-ready HTML, but sharing that result for short-lived review still requires the user to configure hosting, send an archive, or use a permanent publishing workflow. This adds friction when the goal is simply to let someone open the rendered result in a browser and review it.

Describe the solution you'd like

Add an optional Share Temporary Preview action alongside the existing HTML export flow.

The action could:

  1. Reuse VNote's existing HTML export pipeline rather than introducing another Markdown renderer.
  2. Upload the generated HTML and all referenced exported assets to temp.md.
  3. Return a temporary, unlisted URL that VNote can copy or open.
  4. Allow a later export to update the same URL, or let the user create a new preview.
  5. Show the preview's status and expiration, with an option to revoke it permanently.

This should be explicitly opt-in and separate from local HTML/PDF export. Before uploading, the UI should clearly state that anyone with the URL can view it, that it is unlisted rather than private, and that it expires. Any update/revoke capability returned by the service should be treated as a secret and never written into the note or exported bundle.

temp.md accepts static files or directories, keeps one URL stable across updates, reports lifecycle state and expiration, and supports permanent revocation: https://temp.md/docs

Describe alternatives you've considered

  • Continue exporting HTML and require users to configure a separate host.
  • Send the exported directory or archive directly, which is less convenient for browser review and makes revisions harder to track.
  • Use a permanent publishing provider, which is a larger ownership and configuration commitment than a disposable preview.

Additional context

I work on temp.md and am happy to prepare a focused PR if this direction fits VNote. I would keep the integration isolated from the current export behavior and include tests for asset collection, failed uploads, updating an existing URL, and revocation.

Dominant language
C++
Stars
13k
Forks
1.3k
Avg merge
1d 22h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vnotex/vnote

All issues in vnotex/vnote

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.