I’d like to export a notebook to standalone HTML, which could then be hosted on a website. However, although both images and files work in the exported code, links between notes don’t work. Currently, when I serve the exported files using e.g. Python’s HTTP server, or http-server from node, the links don’t point anywhere.
I would also love to see this feature implemented. I expect it would not require a ton of effort, and would massively increase joplin's accessibility by allowing export of whole notebooks into a format browsable by someone without joplin.
I would personally find this very useful, as a way of publishing my (inter-linked) lab notebook to a local website for others in my lab (who don't have joplin) to reference.
This feature would put Joplin at the top of the chart, imo.
So far, I haven't seen any wiki-building apps that can actually export to HTML and build a web wiki with, besides Joplin, but the internal links don't work right now.
Obsidian's Publish is the only other way to easily create a Wiki-type collection of notes and make them accessible online as-is without hassle. (EDIT: I found a guide that describes how to convert .md to a usable html, but requires more technical knowledge to do)
Besides Publish being expensive, this has limitations like no deeper site design. I wouldn't need to frequently update posted Wikis so I wouldn't mind the step of actually hosting a collection of pages, as long as they can link between each other without needing to re-write the articles.
I previously achieved a similar effect with vuepress/docsify exported by joplin-blog, which exports joplin's notes as hierarchical markdown notes, which are then rendered as a website via a third-party framework. refer to:
The latest I am creating is mami, which is no longer limited to joplin export by design, but connects multiple markdown-based note-taking, blog or wiki tools, already supports exporting to joplin => hugo/hexo/obsidian, but obsidian => joplin currently Still in progress, reference:
Re-opening this issue as I've encountered it in a new context. Feel free to let me know if this isn't warranted
Relative paths are already implemented in markdown "export all"; any Joplin Note ID formatted as an "inline link" is automatically converted to the relative path of the target export directory. Works very well! However, when Note ID's are formatted with "reference link" syntax (as per CommonMark), they aren't parsed in the same way. Instead, they're exported as unaltered Joplin Note ID's.
This limits Joplin's capacity to be a "future-proof" & "portable" application. Reason being, for anyone using the (much neater) "reference link" syntax in their markdown, Joplin doesn't actually preserve note links in plaintext exports. This is because, as outlined above, the relative local path of the note is ignored & only the app-dependent Joplin Note ID is exported.
This issue can be reproduced with the following steps:
Create two new Notes within Joplin & name them "referrer" & "referee", respectively.
Paste the "referee's" Joplin ID into the "referrer" Note, formatted as a Reference Link AND then as an Inline Link.
"Taskbar--->Export All" as either "MD-Markdown" or "MD-Markdown+Front Matter".
Open the exported "referrer" Note with any plaintext editor & you will notice...
4a. The Inline Link to the "referree" Note has been succesfully parsed as the relative filepath.
4b. The Reference Link to the "referree" Note hasn't been parsed the same way. It remains a Joplin Note ID, which doesn't refer to anything unless used within Joplin.
Example Syntax:
[Reference Link syntax][ID-Ref]
[ID-Ref]: :/"Joplin-Note-ID"
[Inline Link syntax](:/"Joplin-Note-ID")
All this to say, I'm adding my voice to the crowd asking for deeper implementation of 'relative paths' when exporting Notebooks. Could this feature be within scope for 2024?
I just stumbled upon this after exporting my Notebooks to HTML and wondering why Joplin opens when I click on a link in one of the HTML files.
I just realized on Export, Joplin creates a joplin:// Link instead of let's say a ./other_note.html. This is for links I created within Joplin by right-clicking on a Note --> Copy Markdown Link and putting it into another note.
I did not find a Export Plugin that may have helped and I am now wondering if I am doing something wrong or how I can make sure that all the stuff I put into Joplin is future proof for migrations I might need to do later.
I guess this statement is still valid for HTML export:
However, Markdown export should convert note links properly. I would already consider Markdown as future proof. If you need HTML specifically, maybe there is a Markdown-to-HTML converter that preserves links.
Yes, Markdown export does seem to work... made it possible for me to export it and import it in Obsidian. There, due to a Plugin, is a very good HTML export available. But the mermaid rendering compared to Joplin looks ugly to me in Obsidian. You can't have everything I guess? Still switching between both to find out which one fits me better. On the other hand, a correct Markdown export is more important than PDF, since markdown fits better as an export / import format.
