In the desktop, the action "Save as Markdown" (via menu) uses a Tauri dialog to choose a target folder that defaults to folder inside the project, but the user can select a different folder in the OS filesystem. That folder will have a .md file and optionally a .bib file with reference(s) used in the document.

For the web, we have two issues:

1. Where should we have the action to trigger the action?
2. What should be the UX for the action.

My considerations:

1. Can be implemented in the command palette and also as a context context menu action in the files explorer.
2. We don't need an alternative to the Tauri dialog, saving the export in an export folder inside the project (maybe under a folder named after the file we want to export so that we can have multiple files / exports). Then we can implement a download feature of files/folder to access these files from web.
   a. Should we implement the same behaviour for the desktop version?

This is a follow-up after #425