Last updated: 13 Dec 25 13:58:21 (UTC)

2025-12-13_JoplinForum_Thank you for your rapid reaction.

Thank you for your rapid reaction.

I understand my proposed use-case wasn’t properly described.

Let me 1st confirm I have well seen all the 4 means of structuring notes WITHIN Joplin; I started to make use of them. No problem and no Request4Feature about that.

See here attached screenshots, and, below, the proposed methodology :
how I need Joplin to relate to web pages / bookmarks in web browser :


AlhambraScreen in FirefoxWithLateralBookmarks.jpg

AlhambraScreen in FirefoxWithLateralBookmarks


2 Bookmarks To TouristicPage+BM to Joplin related Note.jpg

Bookmarks To TouristicPage+BM to Joplin trelatyed Note



Properties of theBookmarkToJoplinNote.jpg

Properties of theBookmarkToJoplinNote


PropertiesOfTheThematicFolderAlhambra.jpg

PropertiesOfTheThematicFolderAlhambra

Folder : Alhambra (Grenade-Andalousie) - 2025-11

  • Bookmark : [JOPLIN Note] Alhambra __F.A.Q. - Patronato de la Alhambra y Generalife - Joplin Cloud

  • Bookmark : Alhambra y Generalife

  • Bookmark : etc

  • Bookmark : etc

  • Bookmark : etc ( all bookmarks in the theme “Folder : Alhambra (Grenade-Andalousie) - 2025-11” )

You find attached as well abig bookmarks File :
2025-12-14_10-55-21 Partial Bookmarks Export_ Autres marque-pages.html

<!DOCTYPE NETSCAPE-Bookmark-file-1>
<!DOCTYPE NETSCAPE-Bookmark-file-1>

2025-12-14_10-55-21 Partial Bookmarks Export_ Autres marque-pages.html (4.3 MB)

Pictures above, and the bookmarks collection file (html) show that, for longterm and multithematic weknowledge management (professional and private life), one should consider :

  1. Joplin can’t be a 100% “replacement” of Bookmarks collection in navigator,
    and that for many reasons :
  • Information fetching on the web is multi topics, is progressive; collecting bookmarks is often temporary storage while searching, and you never know in advance which info should be selected and stored for middel or long term…

  • Bookmarks will be much more numerous than Notes, and shoudn’t be obfuscating in Joplin

  • Important : avoiding duplication (of URLs/bookmarks) is very important : just like in a database, maintenance and consultation would be difficult

  1. Therefore, in the perspective of lightweight, flexible Knowledge Management, we need to keep the main workspace in the navigator,
  • As in a RDBMS ( databases system), let’s consider the supplementary information stored in Joplin just as a subTable in a database: relation Many to one, not all bookmarks need a note, BUT every Note is by vocation related to a URL
  1. While working in the navigator context, I need to easily see if I already have a Note, or not, related to any specific bookmark.
  • The easy proposed solution is to add a bookmark, sibling to the original one (Alhambra weebpage), and leading to the Joplin Cloud stored note

  • Typically, the label of the link is the same as the original, but prefixed “[JOPLIN Note]”, this is artisanal but easy and straightforward.

  1. The ‘Thematic Folder’ issue
  • As the navigator remains responsible for global bookmarks storage, it remains responsible for structuring the knowledge

  • Structuring does happen via folders / subfolders

  • So, the structure of folders is in itself an important part of the knowledge assets: the levels, sublevels, and the vocabulary used for subcategorizing

  • Therefore, it is good-design to allow for note-taking (Joplin), dedicated to a folder as well as for bookmarks.

  • Typical example : consider a Google Search task like ‘explore note-taking apps offers’, or ‘must have visits in Granada - Andalusia’ : it is often interesting (preferable) to keep together small notes about various pages visited , and - in a second stage if justified - to create a substancial note dedicated to areally important webPage.

  • The easy proposed solution is to add a bookmark, as a ‘child’ item, just UNDER the folder , and leading to the Joplin Cloud stored note wich is dedicated to the thema (‘Granada’), and not to a specific page (‘tickets for Alhambra’)

  • This method is well illustrated in the snapshots, notably these showing the properties of the tree items( UTRLS and folder)

I hope it is a bit clearer; for sure the explanation is long already.

I suppose that other navigator plugins approaches would be interesting, notably working on enriched metadata in the bookmarks files and including URLs to Joplin Notes in the properties (metadata of the bookmarks and folders, but this is heavy and hypothetic scenario.

Awaiting for your feed-back,
I thank you very much on forward.

⚙️