Skip to content

Build your personal knowledge base with Trilium Notes

client/collections/board: rename "Remove from board" to "Remove from column", fix docs

Adorian Doran5d276a8d93f9
diff --git a/apps/client/src/translations/en/translation.json b/apps/client/src/translations/en/translation.json
index 0bfd37612a..be97ec3eb2 100644
--- a/apps/client/src/translations/en/translation.json
+++ b/apps/client/src/translations/en/translation.json
@@ -3462,7 +3462,7 @@
},
"board_view": {
"delete-note": "Delete note...",
- "remove-from-board": "Remove from board",
+ "remove-from-board": "Remove from column",
"archive-note": "Archive note",
"unarchive-note": "Unarchive note",
"status-header": "Status",
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Kanban Board.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Kanban Board.html
index 173d313cac..5125e78f46 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Kanban Board.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Kanban Board.html
@@ -322,7 +322,7 @@
or colors, deleting them, or archiving them.</p>
<p>You can select multiple cards in the following ways:</p>
<ul>
- <li class="ck-list-marker-bold"><strong>Using a mouse and keyboard:</strong>
+ <li><strong>Using a mouse and keyboard:</strong>
<ul>
<li>To add a card to the selection, hold <kbd>Ctrl</kbd> and click the card.
Repeat this for other cards until all the desired cards are selected. Clicking
@@ -333,7 +333,7 @@
<li>Press <kbd>Esc</kbd> to clear the selection.</li>
</ul>
</li>
- <li class="ck-list-marker-bold"><strong>On mobile:</strong>
+ <li><strong>On mobile:</strong>
<ol>
<li>To enter selection mode, tap the&nbsp;<span class="tn-icon bx bx-select-multiple"></span> button
at the top of the screen. A selection toolbar will appear in the header,
@@ -345,7 +345,7 @@
<li>Use the side toolbar to apply actions to the selected cards.</li>
</ol>
</li>
- <li class="ck-list-marker-bold"><strong>Using only the keyboard:</strong>
+ <li><strong>Using only the keyboard:</strong>
<ul>
<li>To add the currently focused card to the selection, press <kbd>Ctrl</kbd> + <kbd>Space</kbd>.
Repeat this for the other cards you want to select. Pressing <kbd>Ctrl</kbd> + <kbd>Space</kbd> again
@@ -463,7 +463,7 @@ class="admonition warning">
class="tn-icon bx bx-trash"></span> button.</p>
<h4>Removing a card from the board without deleting the note</h4>
<p>To remove a card from the board's columns while keeping its note, open
- the card's context menu and select&nbsp;<span class="tn-icon bx bx-task-x"></span> <strong>Remove from board</strong>,
+ the card's context menu and select&nbsp;<span class="tn-icon bx bx-task-x"></span> <strong>Remove from column</strong>,
or press <kbd>Delete</kbd>. On mobile, hold the card until the side toolbar
appears, and then tap the&nbsp;<span class="tn-icon bx bx-task-x"></span> button.</p>
<p>This command is not available when the inbox column is enabled. Instead,
@@ -644,11 +644,17 @@ class="admonition warning">
</ul>
<p>To use relations for grouping:</p>
<ol>
- <li>Create a Kanban board from scratch rather than from a template.</li>
- <li>Assign <code>#viewType=board #hidePromotedAttributes</code> to emulate the
- default template.</li>
- <li>Set <code>#board:groupBy</code> to the name of a relation, <strong>including the</strong> <code>~</code> <strong>prefix</strong> (for
- example, <code>~status</code>).</li>
+ <li>
+ <p>Create a Kanban board from scratch rather than from a template.</p>
+ </li>
+ <li>
+ <p>Assign <code>#viewType=board #hidePromotedAttributes</code> to emulate the
+ default template.</p>
+ </li>
+ <li>
+ <p>Set <code>#board:groupBy</code> to the name of a relation, <strong>including the</strong> <code>~</code> <strong>prefix</strong> (for
+ example, <code>~status</code>).</p>
+ </li>
<li>
<p>Optionally, use&nbsp;<a class="reference-link" href="#root/_help_OFXdgB2nNk1F">Promoted Attributes</a>&nbsp;to
make changing the status within the note easier:</p><pre><code class="language-text-x-trilium-auto">#relation:status(inheritable)="promoted,alias=Status,single"</code></pre>
diff --git a/docs/Developer Guide/!!!meta.json b/docs/Developer Guide/!!!meta.json
new file mode 100644
index 0000000000..1b3a7e715f
--- /dev/null
+++ b/docs/Developer Guide/!!!meta.json
@@ -0,0 +1,2942 @@
+{
+ "formatVersion": 2,
+ "files": [
+ {
+ "isClone": false,
+ "noteId": "jdjRLhLV3TtI",
+ "notePath": [
+ "jdjRLhLV3TtI"
+ ],
+ "title": "Developer Guide",
+ "notePosition": 1,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "label:shareAlias",
+ "value": "promoted,alias=Slug,single,text",
+ "isInheritable": true,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-code-alt",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "developer-guide",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Developer Guide.md",
+ "attachments": [],
+ "dirFileName": "Developer Guide",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "T2W7WCZrYZBU",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "T2W7WCZrYZBU"
+ ],
+ "title": "Environment Setup",
+ "notePosition": 260,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-cog",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "environment-setup",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Environment Setup.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "ccIoz7nqgDRK",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "ccIoz7nqgDRK"
+ ],
+ "title": "Branching strategy",
+ "notePosition": 270,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-git-merge",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "branching-strategy",
+ "isInheritable": false,
+ "position": 40
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Branching strategy.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "cxfTSHIUQtt2",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "cxfTSHIUQtt2"
+ ],
+ "title": "Project Structure",
+ "notePosition": 280,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bxs-component",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "project-structure",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Project Structure.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "MhwWMgxwDTZL",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL"
+ ],
+ "title": "Architecture",
+ "notePosition": 290,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "architecture",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-arch",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Architecture.md",
+ "attachments": [],
+ "dirFileName": "Architecture",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "dsMq2EIOMOBU",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "dsMq2EIOMOBU"
+ ],
+ "title": "Frontend",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "frontend",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Frontend.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "tsswRlmHEnYW",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "tsswRlmHEnYW"
+ ],
+ "title": "Backend",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "backend",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Backend.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "pRZhrVIGCbMu",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu"
+ ],
+ "title": "Database",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "database",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-data",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Database.md",
+ "attachments": [],
+ "dirFileName": "Database",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "vNMojjUN76jc",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc"
+ ],
+ "title": "Database structure",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "tables",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Database structure",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "e6GnYOXeIWjg",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "e6GnYOXeIWjg"
+ ],
+ "title": "attachments",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "attachments",
+ "isInheritable": false,
+ "position": 50
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "attachments.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "ciL84vNBNi9y",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "ciL84vNBNi9y"
+ ],
+ "title": "attributes",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "attributes",
+ "isInheritable": false,
+ "position": 40
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "attributes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "VIcWnKGs0sMh",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "VIcWnKGs0sMh"
+ ],
+ "title": "blobs",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "blobs",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "blobs.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "GskLPkgY5n6E",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "GskLPkgY5n6E"
+ ],
+ "title": "branches",
+ "notePosition": 50,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "branches",
+ "isInheritable": false,
+ "position": 40
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "branches.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "ohhExR078MPU",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "ohhExR078MPU"
+ ],
+ "title": "entity_changes",
+ "notePosition": 51,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "entity-changes",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "entity_changes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "bRqbIg633nCs",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "bRqbIg633nCs"
+ ],
+ "title": "etapi_tokens",
+ "notePosition": 52,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "etapi-tokens",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "etapi_tokens.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "DSkl8C325tEC",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "DSkl8C325tEC"
+ ],
+ "title": "notes",
+ "notePosition": 53,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "notes",
+ "isInheritable": false,
+ "position": 40
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "notes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "4oeftEmy77Bt",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "4oeftEmy77Bt"
+ ],
+ "title": "options",
+ "notePosition": 54,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "options",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "options.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "VyFirdgAOoh5",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "VyFirdgAOoh5"
+ ],
+ "title": "recent_notes",
+ "notePosition": 55,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "recent-notes",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "recent_notes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "s7ZBiaJVNumK",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "s7ZBiaJVNumK"
+ ],
+ "title": "revisions",
+ "notePosition": 56,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "revisions",
+ "isInheritable": false,
+ "position": 50
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "revisions.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "6DG1au6rgOTl",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "6DG1au6rgOTl"
+ ],
+ "title": "sessions",
+ "notePosition": 66,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "sessions",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "sessions.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "zWY2LKmas9os",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "pRZhrVIGCbMu",
+ "vNMojjUN76jc",
+ "zWY2LKmas9os"
+ ],
+ "title": "user_data",
+ "notePosition": 76,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-table",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "user_data.md",
+ "attachments": []
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "Wxn82Em8B7U5",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "Wxn82Em8B7U5"
+ ],
+ "title": "APIs",
+ "notePosition": 50,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "api",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "APIs.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "Vk4zD1Iirarg",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "Vk4zD1Iirarg"
+ ],
+ "title": "Arhitecture Decision Records",
+ "notePosition": 60,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "adr",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Arhitecture Decision Records.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "RHbKw3xiwk3S",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "MhwWMgxwDTZL",
+ "RHbKw3xiwk3S"
+ ],
+ "title": "Security",
+ "notePosition": 80,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "security",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Security.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "zdQzavvHDl1k",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "zdQzavvHDl1k"
+ ],
+ "title": "Documentation",
+ "notePosition": 300,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "documentation",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-book-open",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Documentation.md",
+ "attachments": [],
+ "dirFileName": "Documentation",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "LjqM0VUL1CrU",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "zdQzavvHDl1k",
+ "LjqM0VUL1CrU"
+ ],
+ "title": "Documentation references in the application",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "doc-references",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Documentation references in the application.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "a0mkxxB4Uvbf",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf"
+ ],
+ "title": "Building",
+ "notePosition": 310,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "building",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-terminal",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Building",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "czgXkoEYwclZ",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf",
+ "czgXkoEYwclZ"
+ ],
+ "title": "Running a development build",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "dev-build",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Running a development build.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "mXFYlhuEr1mZ",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf",
+ "mXFYlhuEr1mZ"
+ ],
+ "title": "Docker",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "docker",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bxl-docker",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Docker.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "aGlhNBEA9wwo",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf",
+ "aGlhNBEA9wwo"
+ ],
+ "title": "Build information",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "build-info",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-info-circle",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Build information.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "fI16A7NrT713",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf",
+ "fI16A7NrT713"
+ ],
+ "title": "Live reload (HMR)",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "live-reload",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Live reload (HMR).md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "PXzm2t3sCdsP",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf",
+ "PXzm2t3sCdsP"
+ ],
+ "title": "Build deliveries locally",
+ "notePosition": 50,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "build-deliveries",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-package",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Build deliveries locally.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "4nwtTJyjNDKd",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "a0mkxxB4Uvbf",
+ "4nwtTJyjNDKd"
+ ],
+ "title": "Releasing a new version",
+ "notePosition": 70,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-rocket",
+ "isInheritable": false,
+ "position": 30
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "releasing",
+ "isInheritable": false,
+ "position": 40
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Releasing a new version.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "qalhAaJoQ7AN",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN"
+ ],
+ "title": "Dependencies",
+ "notePosition": 330,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bxs-component",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "dependencies",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Dependencies",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "fa6hAJ9Ith3A",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "fa6hAJ9Ith3A"
+ ],
+ "title": "Per-dependency checks",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "updating-deps",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Per-dependency checks.md",
+ "attachments": [],
+ "dirFileName": "Per-dependency checks",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "Xfi1ScuBTKJf",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "fa6hAJ9Ith3A",
+ "Xfi1ScuBTKJf"
+ ],
+ "title": "bettersqlite binaries",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "bettersqlite-binaries",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "bettersqlite binaries.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "Jg7clqogFOyD",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "Jg7clqogFOyD"
+ ],
+ "title": "CKEditor",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-package",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "ckeditor",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "CKEditor.md",
+ "attachments": [],
+ "dirFileName": "CKEditor",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "BRhQZHgwaGyw",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "Jg7clqogFOyD",
+ "BRhQZHgwaGyw"
+ ],
+ "title": "Plugin migration guide",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "plugin-migration",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Plugin migration guide.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "5gBYmUqiupBl",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "Jg7clqogFOyD",
+ "5gBYmUqiupBl"
+ ],
+ "title": "Differences from upstream",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "fullContentWidth",
+ "value": "",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "differences-from-upstream",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Differences from upstream.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "lY19SLxUMj3J",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "Jg7clqogFOyD",
+ "lY19SLxUMj3J"
+ ],
+ "title": "ckeditor5-math",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "ckeditor5-math",
+ "isInheritable": false,
+ "position": 40
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "ckeditor5-math.md",
+ "attachments": [
+ {
+ "attachmentId": "UlSZYhYX8Kfj",
+ "title": "image.png",
+ "role": "image",
+ "mime": "image/png",
+ "position": 10,
+ "dataFileName": "ckeditor5-math_image.png"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "dEpZ1pLibs4Z",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "qalhAaJoQ7AN",
+ "dEpZ1pLibs4Z"
+ ],
+ "title": "Compression libraries",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "compression-libraries",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Compression libraries.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "yeqU0zo0ZQ83",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83"
+ ],
+ "title": "Concepts",
+ "notePosition": 340,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "concepts",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-sitemap",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "sorted",
+ "value": "",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Concepts",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "3mz4ZYhi9Cy8",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "3mz4ZYhi9Cy8"
+ ],
+ "title": "Backlinks",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "backlinks",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-link-alt",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Backlinks.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "h8AsuFjSD4fB",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "h8AsuFjSD4fB"
+ ],
+ "title": "Branch prefixes",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "branch-prefix",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Branch prefixes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "6Yms5izbd0GF",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "6Yms5izbd0GF"
+ ],
+ "title": "Cache",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-microchip",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "cache",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Cache.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "oqg9OpK8xfcm",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "oqg9OpK8xfcm"
+ ],
+ "title": "CI",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "ci",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "CI",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "IxkDdjTogO18",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "oqg9OpK8xfcm",
+ "IxkDdjTogO18"
+ ],
+ "title": "Main",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "main",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Main.md",
+ "attachments": [
+ {
+ "attachmentId": "c3aGEk60ZR2Q",
+ "title": "image.png",
+ "role": "image",
+ "mime": "image/png",
+ "position": 10,
+ "dataFileName": "Main_image.png"
+ },
+ {
+ "attachmentId": "q9OGTAguCyWf",
+ "title": "image.png",
+ "role": "image",
+ "mime": "image/png",
+ "position": 10,
+ "dataFileName": "1_Main_image.png"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "tM3rIZQzlum4",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "tM3rIZQzlum4"
+ ],
+ "title": "Deleted notes",
+ "notePosition": 50,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "deleted-notes",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-trash",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Deleted notes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "oLhKpfi2kGON",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "oLhKpfi2kGON"
+ ],
+ "title": "Demo document",
+ "notePosition": 60,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "demo-document",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bxs-file-archive",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Demo document.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "TiUll0Osoaz6",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "TiUll0Osoaz6"
+ ],
+ "title": "Entities",
+ "notePosition": 70,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "entities",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bxs-note",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Entities.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "UzRirf46Xi46",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "UzRirf46Xi46"
+ ],
+ "title": "Hidden notes",
+ "notePosition": 80,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "hidden-notes",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-low-vision",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Hidden notes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "m2W35hwSDUeh",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "m2W35hwSDUeh"
+ ],
+ "title": "Icons",
+ "notePosition": 90,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "icons",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Icons.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "TLXJwBDo8Rdv",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "TLXJwBDo8Rdv"
+ ],
+ "title": "Internationalisation / Translations",
+ "notePosition": 100,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-globe",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "i18n",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Internationalisation Translations.md",
+ "attachments": [],
+ "dirFileName": "Internationalisation Translations",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "ky5zpmxXZhhr",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "TLXJwBDo8Rdv",
+ "ky5zpmxXZhhr"
+ ],
+ "title": "Guidelines",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "guidelines",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Guidelines.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "VTebBD3jZjdp",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "TLXJwBDo8Rdv",
+ "VTebBD3jZjdp"
+ ],
+ "title": "i18n-ally",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "i18n-ally",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "i18n-ally.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "KhDvxPlQQybs",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "TLXJwBDo8Rdv",
+ "KhDvxPlQQybs"
+ ],
+ "title": "Server translations",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "server-translation",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Server translations.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "lXjOyKpUSKgE",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "TLXJwBDo8Rdv",
+ "lXjOyKpUSKgE"
+ ],
+ "title": "Adding a new locale",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "new-locale",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Adding a new locale.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "Usiyzn9C4WFv",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "Usiyzn9C4WFv"
+ ],
+ "title": "Launchers",
+ "notePosition": 110,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "launchers",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Launchers.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "qjQNyaYXSNWu",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "qjQNyaYXSNWu"
+ ],
+ "title": "Note Revisions",
+ "notePosition": 120,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "revisions",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-history",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Note Revisions.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "7RBJMqVz2EsJ",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ"
+ ],
+ "title": "Note Types",
+ "notePosition": 130,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "note-types",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Note Types",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "AdNRgGrYeTCy",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy"
+ ],
+ "title": "Adding a new note type",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "new-note-type",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Adding a new note type",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "UFtOg3sLumZM",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "UFtOg3sLumZM"
+ ],
+ "title": "First steps",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "first-steps",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "First steps.md",
+ "attachments": [],
+ "dirFileName": "First steps",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "aSO1wqK7L1ma",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "UFtOg3sLumZM",
+ "aSO1wqK7L1ma"
+ ],
+ "title": "mind_map.js",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "code",
+ "mime": "application/javascript;env=frontend",
+ "attributes": [],
+ "dataFileName": "mind_map.js",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "lgFwLJT72mdf",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "lgFwLJT72mdf"
+ ],
+ "title": "Note type checklist",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-list-check",
+ "isInheritable": false,
+ "position": 40
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "checklist",
+ "isInheritable": false,
+ "position": 50
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Note type checklist.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "PoxUNujeKJ7T",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "PoxUNujeKJ7T"
+ ],
+ "title": "Saving data via spaced update",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "saving-data",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Saving data via spaced update.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "xYVE7qA3EBwb",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "xYVE7qA3EBwb"
+ ],
+ "title": "Loading data",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "loading-data",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Loading data.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "OGYpAbrmEXbX",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "OGYpAbrmEXbX"
+ ],
+ "title": "SVG rendering",
+ "notePosition": 50,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "svg-rendering",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "SVG rendering.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "Q8hgB8EEen80",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "Q8hgB8EEen80"
+ ],
+ "title": "Copy image reference to the clipboard",
+ "notePosition": 60,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "copy-image-reference",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Copy image reference to the clipboard.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "AwWq8bJRl6XD",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7RBJMqVz2EsJ",
+ "AdNRgGrYeTCy",
+ "AwWq8bJRl6XD"
+ ],
+ "title": "Export diagram as SVG",
+ "notePosition": 70,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "export-to-svg",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Export diagram as SVG.md",
+ "attachments": []
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "6dC7ha5vjqqS",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "6dC7ha5vjqqS"
+ ],
+ "title": "Options",
+ "notePosition": 140,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "options",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-cog",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Options.md",
+ "attachments": [],
+ "dirFileName": "Options",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "NcHcYOEn4ol5",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "6dC7ha5vjqqS",
+ "NcHcYOEn4ol5"
+ ],
+ "title": "Creating a new option",
+ "notePosition": 50,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "new-option",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Creating a new option.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "W0msUwLxm40d",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "W0msUwLxm40d"
+ ],
+ "title": "Printing and exporting to PDF",
+ "notePosition": 150,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "printing",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-printer",
+ "isInheritable": false,
+ "position": 50
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Printing and exporting to PDF.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "UvXpeSqfYc6d",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "UvXpeSqfYc6d"
+ ],
+ "title": "Protected entities",
+ "notePosition": 160,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "protected-entities",
+ "isInheritable": false,
+ "position": 40
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-lock-alt",
+ "isInheritable": false,
+ "position": 50
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Protected entities.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "vphziLmQeQHY",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "vphziLmQeQHY"
+ ],
+ "title": "Share",
+ "notePosition": 170,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-share-alt",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "share",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Share.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "n9wYW9nUTynV",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "n9wYW9nUTynV"
+ ],
+ "title": "Synchronisation",
+ "notePosition": 180,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "sync",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-sync",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Synchronisation.md",
+ "attachments": [],
+ "dirFileName": "Synchronisation",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "wA6tm9xcWWaB",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "n9wYW9nUTynV",
+ "wA6tm9xcWWaB"
+ ],
+ "title": "Content hashing",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "content-hashing",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Content hashing.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "sYnCT0mbst1E",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "n9wYW9nUTynV",
+ "sYnCT0mbst1E"
+ ],
+ "title": "Entity change tombstones",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "entity-change-tombstones",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Entity change tombstones.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "k7RavjuXQt8z",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "k7RavjuXQt8z"
+ ],
+ "title": "Syntax highlighting",
+ "notePosition": 190,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "syntax-highlighting",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-highlight",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Syntax highlighting.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "7BCukQTCm7fv",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "7BCukQTCm7fv"
+ ],
+ "title": "Themes",
+ "notePosition": 200,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "themes",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-palette",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Themes.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "YTAxJMA3uWwn",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "yeqU0zo0ZQ83",
+ "YTAxJMA3uWwn"
+ ],
+ "title": "Web Clipper",
+ "notePosition": 210,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "web-clipper",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-paperclip",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Web Clipper.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "YjerxU7Aii8X",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "YjerxU7Aii8X"
+ ],
+ "title": "Troubleshooting",
+ "notePosition": 380,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-bug",
+ "isInheritable": false,
+ "position": 10
+ },
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "troubleshooting",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Troubleshooting",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "g9nFZ6dRz1Cg",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "YjerxU7Aii8X",
+ "g9nFZ6dRz1Cg"
+ ],
+ "title": "better-sqlite3 was compiled against a different Node.js version",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "better-sqlite3",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "better-sqlite3 was compiled against a different Node.js version.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "QUb0fRhbpT8E",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "YjerxU7Aii8X",
+ "QUb0fRhbpT8E"
+ ],
+ "title": "Error [TransformError]: The package \"@esbuild/linux-x64\" could not be found, and is needed by esbuild.",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "esbuild-error",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Error [TransformError] The package @esbuildlinux-x64 could not be found, and is needed by esbuild.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "trBshtRcNt5X",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "YjerxU7Aii8X",
+ "trBshtRcNt5X"
+ ],
+ "title": "A note is listed in Recent Changes but missing from the tree",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "recent-changes-missing-note",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "A note is listed in Recent Changes but missing from the tree.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "dtKC3FmoWOrv",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "dtKC3FmoWOrv"
+ ],
+ "title": "Testing",
+ "notePosition": 400,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "testing",
+ "isInheritable": false,
+ "position": 20
+ },
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bxs-eyedropper",
+ "isInheritable": false,
+ "position": 30
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Testing.md",
+ "attachments": [],
+ "dirFileName": "Testing",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "ETeT5YO61DAW",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "dtKC3FmoWOrv",
+ "ETeT5YO61DAW"
+ ],
+ "title": "Unit tests",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "unit-tests",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Unit tests.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "C5MUQczZ5R9N",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "dtKC3FmoWOrv",
+ "C5MUQczZ5R9N"
+ ],
+ "title": "Integration testing",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "integration",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Integration testing.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "bIfKwfCnqpeI",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "dtKC3FmoWOrv",
+ "bIfKwfCnqpeI"
+ ],
+ "title": "Test database",
+ "notePosition": 30,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "test-database",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Test database.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "w6gMvKh0UAVT",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "dtKC3FmoWOrv",
+ "w6gMvKh0UAVT"
+ ],
+ "title": "End-to-end tests",
+ "notePosition": 40,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "shareAlias",
+ "value": "running-tests",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "End-to-end tests.md",
+ "attachments": []
+ }
+ ]
+ },
+ {
+ "isClone": false,
+ "noteId": "HMrVxa1lJBKv",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "HMrVxa1lJBKv"
+ ],
+ "title": "Interoperability",
+ "notePosition": 410,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-repost",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "attachments": [],
+ "dirFileName": "Interoperability",
+ "children": [
+ {
+ "isClone": false,
+ "noteId": "dSgzBgbagtYP",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "HMrVxa1lJBKv",
+ "dSgzBgbagtYP"
+ ],
+ "title": "Exported content with extended task states",
+ "notePosition": 10,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-list-check",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Exported content with extended task states.md",
+ "attachments": []
+ },
+ {
+ "isClone": false,
+ "noteId": "Gntibtjmzi7e",
+ "notePath": [
+ "jdjRLhLV3TtI",
+ "HMrVxa1lJBKv",
+ "Gntibtjmzi7e"
+ ],
+ "title": "Trilium Backup Container (.tnbackup) file format",
+ "notePosition": 20,
+ "prefix": null,
+ "isExpanded": false,
+ "type": "text",
+ "mime": "text/html",
+ "attributes": [
+ {
+ "type": "label",
+ "name": "iconClass",
+ "value": "bx bx-history",
+ "isInheritable": false,
+ "position": 20
+ }
+ ],
+ "format": "markdown",
+ "dataFileName": "Trilium Backup Container (.tnbackup) file format.md",
+ "attachments": []
+ }
+ ]
+ }
+ ]
+ }
+ ]
+}
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide.md b/docs/Developer Guide/Developer Guide.md
new file mode 100644
index 0000000000..8f5721b305
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide.md
@@ -0,0 +1,15 @@
+# Developer Guide
+This documentation is intended for developers planning to implement new features or maintain the Trilium Notes application, as it describes the architecture of the application.
+
+For the user-facing documentation, including how to write scripts and the various APIs, consult the [user guide](https://docs.triliumnotes.org/user-guide/) instead.
+
+### Quick links
+
+* <a class="reference-link" href="Developer%20Guide/Environment%20Setup.md">Environment Setup</a>
+* <a class="reference-link" href="Developer%20Guide/Project%20Structure.md">Project Structure</a>
+
+### External links
+
+* The [Trilium Notes website](https://triliumnotes.org/), for a quick presentation of the application.
+* [User Guide](https://docs.triliumnotes.org/user-guide/), to understand the concepts of the application itself.
+* [GitHub Repository (TriliumNext/Trilium)](https://github.com/TriliumNext/Trilium/)
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture.md b/docs/Developer Guide/Developer Guide/Architecture.md
new file mode 100644
index 0000000000..c9b4d858d1
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture.md
@@ -0,0 +1,196 @@
+# Architecture
+Trilium Notes is a hierarchical note-taking application built as a TypeScript monorepo. It supports multiple deployment modes (desktop, server, mobile web) and features advanced capabilities including synchronization, scripting, encryption, and rich content editing.
+
+### Key Characteristics
+
+* **Monorepo Architecture**: Uses pnpm workspaces for dependency management
+* **Multi-Platform**: Desktop (Electron), Server (Node.js/Express), and Mobile Web
+* **TypeScript-First**: Strong typing throughout the codebase
+* **Plugin-Based**: Extensible architecture for note types and UI components
+* **Offline-First**: Full functionality without network connectivity
+* **Synchronization-Ready**: Built-in sync protocol for multi-device usage
+
+### Technology Stack
+
+* **Runtime**: Node.js (backend), Browser/Electron (frontend)
+* **Language**: TypeScript, JavaScript
+* **Database**: SQLite (better-sqlite3)
+* **Build Tools**:
+ * Client: Vite,
+ * Server: ESBuild (bundling)
+ * Package manager: pnpm
+* **UI Framework**: Custom widget-based system (vanilla HTML, CSS & JavaScript + jQuery), in the process of converting to React/Preact.
+* **Rich Text**: CKEditor 5 (customized)
+* **Code Editing**: CodeMirror 6
+* **Desktop**: Electron
+* **Server**: Express.js
+
+## Main architecture
+
+Trilium follows a **client-server architecture** even in desktop mode, where Electron runs both the backend server and frontend client within the same process.
+
+```
+graph TB
+ subgraph Frontend
+ Widgets[Widgets<br/>System]
+ Froca[Froca<br/>Cache]
+ UIServices[UI<br/>Services]
+ end
+
+ subgraph Backend["Backend Server"]
+ Express[Express<br/>Routes]
+ Becca[Becca<br/>Cache]
+ ScriptEngine[Script<br/>Engine]
+ Database[(SQLite<br/>Database)]
+ end
+
+ Widgets -.-> API[WebSocket & REST API]
+ Froca -.-> API
+ UIServices -.-> API
+ API -.-> Express
+ API -.-> Becca
+ API -.-> ScriptEngine
+ Becca --> Database
+ Express --> Database
+ ScriptEngine --> Database
+```
+
+### Deployment Modes
+
+1. **Desktop Application**
+ * Electron wrapper running both frontend and backend
+ * Local SQLite database
+ * Full offline functionality
+ * Cross-platform (Windows, macOS, Linux)
+2. **Server Installation**
+ * Node.js server exposing web interface
+ * Multi-user capable
+ * Can sync with desktop clients
+ * Docker deployment supported
+3. **Mobile Web**
+ * Optimized responsive interface
+ * Accessed via browser
+ * Requires server installation
+
+## Monorepo Structure
+
+Trilium uses **pnpm workspaces** to manage its monorepo structure, with apps and packages clearly separated.
+
+```
+trilium/
+├── apps/ # Runnable applications
+│ ├── client/ # Frontend application (shared by server & desktop)
+│ ├── server/ # Node.js server with web interface
+│ ├── desktop/ # Electron desktop application
+│ ├── web-clipper/ # Browser extension for web content capture
+│ ├── db-compare/ # Database comparison tool
+│ ├── dump-db/ # Database export tool
+│ ├── edit-docs/ # Documentation editing tool
+│ ├── build-docs/ # Documentation build tool
+│ └── website/ # Marketing website
+│
+├── packages/ # Shared libraries
+│ ├── commons/ # Shared interfaces and utilities
+│ ├── ckeditor5/ # Custom rich text editor
+│ ├── codemirror/ # Code editor customizations
+│ ├── highlightjs/ # Syntax highlighting
+│ ├── share-theme/ # Shared note theme
+│ ├── splitjs/ # Split pane library
+│ └── turndown-plugin-gfm/ # Markdown conversion
+│
+├── docs/ # Documentation
+├── scripts/ # Build and utility scripts
+└── patches/ # Package patches (via pnpm)
+```
+
+### Package Dependencies
+
+The monorepo uses workspace protocol (`workspace:*`) for internal dependencies:
+
+```
+desktop → client → commons
+server → client → commons
+client → ckeditor5, codemirror, highlightjs
+ckeditor5 → its in-tree plugins (src/plugins/)
+```
+
+## Security summary
+
+### Encryption System
+
+**Per-Note Encryption:**
+
+* Notes can be individually protected
+* AES-128-CBC encryption for encrypted notes.
+* Separate protected session management
+
+**Protected Session:**
+
+* Time-limited access to protected notes
+* Automatic timeout
+* Re-authentication required
+* Frontend: `protected_session.ts`
+* Backend: `protected_session.ts`
+
+### Authentication
+
+**Password Auth:**
+
+* PBKDF2 key derivation
+* Salt per installation
+* Hash verification
+
+**OpenID Connect:**
+
+* External identity provider support
+* OAuth 2.0 flow
+* Configurable providers
+
+**TOTP (2FA):**
+
+* Time-based one-time passwords
+* QR code setup
+* Backup codes
+
+### Authorization
+
+**Single-User Model:**
+
+* Desktop: single user (owner)
+* Server: single user per installation
+
+**Share Notes:**
+
+* Public access without authentication
+* Separate Shaca cache
+* Read-only access
+
+### CSRF Protection
+
+**CSRF Tokens:**
+
+* Required for state-changing operations
+* Token in header or cookie
+* Validation middleware
+
+### Input Sanitization
+
+**XSS Prevention:**
+
+* DOMPurify for HTML sanitization
+* CKEditor content filtering
+* CSP headers
+
+**SQL Injection:**
+
+* Parameterized queries only
+* Better-sqlite3 prepared statements
+* No string concatenation in SQL
+
+### Dependency Security
+
+**Vulnerability Scanning:**
+
+* Renovate bot for updates
+* npm audit integration
+* Override vulnerable sub-dependencies
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/APIs.md b/docs/Developer Guide/Developer Guide/Architecture/APIs.md
new file mode 100644
index 0000000000..cdd954a610
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/APIs.md
@@ -0,0 +1,72 @@
+# APIs
+### Internal API
+
+**REST Endpoints** (`/api/*`)
+
+Used by the frontend for all operations:
+
+**Note Operations:**
+
+* `GET /api/notes/:noteId` - Get note
+* `POST /api/notes/:noteId/content` - Update content
+* `PUT /api/notes/:noteId` - Update metadata
+* `DELETE /api/notes/:noteId` - Delete note
+
+**Tree Operations:**
+
+* `GET /api/tree` - Get note tree
+* `POST /api/branches` - Create branch
+* `PUT /api/branches/:branchId` - Update branch
+* `DELETE /api/branches/:branchId` - Delete branch
+
+**Search:**
+
+* `GET /api/search?query=...` - Search notes
+* `GET /api/search-note/:noteId` - Execute search note
+
+### ETAPI (External API)
+
+Located at: `apps/server/src/etapi/`
+
+**Purpose:** Third-party integrations and automation
+
+**Authentication:** Token-based (ETAPI tokens)
+
+**OpenAPI Spec:** Auto-generated
+
+**Key Endpoints:**
+
+* `/etapi/notes` - Note CRUD
+* `/etapi/branches` - Branch management
+* `/etapi/attributes` - Attribute operations
+* `/etapi/attachments` - Attachment handling
+
+**Example:**
+
+```
+curl -H "Authorization: YOUR_TOKEN" \
+ https://trilium.example.com/etapi/notes/noteId
+```
+
+### WebSocket API
+
+Located at: `apps/server/src/services/ws.ts`
+
+**Purpose:** Real-time updates and synchronization
+
+**Protocol:** WebSocket (Socket.IO-like custom protocol)
+
+**Message Types:**
+
+* `sync` - Synchronization request
+* `entity-change` - Entity update notification
+* `refresh-tree` - Tree structure changed
+* `open-note` - Open note in UI
+
+**Client Subscribe:**
+
+```typescript
+ws.subscribe('entity-change', (data) => {
+ froca.processEntityChange(data)
+})
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Arhitecture Decision Records.md b/docs/Developer Guide/Developer Guide/Architecture/Arhitecture Decision Records.md
new file mode 100644
index 0000000000..c524642cd9
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Arhitecture Decision Records.md
@@ -0,0 +1,62 @@
+# Arhitecture Decision Records
+## 🚀 Future milestones
+
+* [Mobile](https://github.com/TriliumNext/Trilium/issues/7447)
+* [Multi-user](https://github.com/TriliumNext/Trilium/issues/4956)
+
+## Aug 2025 - present: Port the client to React
+
+- [x] [Type widgets](https://github.com/TriliumNext/Trilium/pull/7044)
+- [x] [Collections](https://github.com/TriliumNext/Trilium/pull/6837)
+- [x] [Various widgets](https://github.com/TriliumNext/Trilium/pull/6830)
+- [x] [Floating buttons](https://github.com/TriliumNext/Trilium/pull/6811)
+- [x] [Settings](https://github.com/TriliumNext/Trilium/pull/6660)
+
+## Aug 2025 - Move away from NX
+
+We took the decision of moving away from the NX monorepo tool, due to:
+
+* Various issues with the cache, especially after an update of the NX dependencies which required periodical `nx reset` to get rid of.
+* Various issues with memory and CPU consumption along the way, due to the NX daemon (including it remaining as a background process after closing the IDE).
+* On Windows, almost always there was a freeze on every second build.
+* Various hacks that were needed to achieve what we needed (especially for artifacts since NX would not copy assets if they were in `.gitignore` for some arbitrary reason and requiring a patch that made it difficult to maintain across updates).
+
+As a result, we decided to switch to… nothing. Why?
+
+* `pnpm` (which we were already using) covers the basic needs of a monorepo via workspaces on its own.
+* Our client-side solution, Vite already supports navigating through projects without requiring built artifacts. This makes the build process slightly faster (especially cold starts) at a slighter bigger RAM consumption.
+* ESBuild, on the server-side, also seems happy to go across projects without an issue.
+
+Apart from this:
+
+* In dev mode, the server now runs directly using `tsx` and not built and then run. This means that it'll run much faster.
+* We're back to an architecture where the `server` and the `desktop` host their own Vite instance as a middleware. What this means that there is no `client:dev` and no separate port to handle.
+ * This makes it possible to easily test on mobile in dev mode, since there's a single port to access.
+ * The downside is that the initial start up time is longer while Vite is spinning up. Nevertheless, it's still slightly faster than it used to be anyway.
+* No more asset copying, which should also improve performance.
+* No more messing around with the native dependency of `better-sqlite3` that caused those dreaded mismatches when running between server and desktop. We have (hopefully) found a permanent solution for it that involves no user input.
+* A decent solution was put in place to allow easier development on NixOS for the desktop application.
+* The desktop version has also gained back the ability to automatically refresh the client when a change is made, including live changes for React components.
+
+Migration steps, as a developer:
+
+1. In VS Code, uninstall the NX Console unless you plan to use it for other projects.
+2. Remove `.nx` at project level.
+3. It's ideal to clean up all your `node_modules` in the project (do note that it's not just the top-level one, but also in `apps/client`, `apps/server`, `apps/desktop`, etc.).
+4. Run a `pnpm i` to set up the new dependencies and the installation
+5. Instead of `nx run server:serve`, now you can simply run `pnpm dev` while in `apps/server`, or `pnpm server:start` while in the root.
+6. When first starting the server, it will take slightly longer than usual to see something on the screen since the dependencies are being rebuilt. Those are later cached so subsequent runs should work better. If you end up with a white screen, simply refresh the page a few times until it shows up correctly.
+
+## Apr 2025: NX-based monorepo
+
+* Goal: Restructure the application from a mix where the client was a subfolder within the server and other dependencies such as <a class="reference-link" href="../Dependencies/CKEditor.md">CKEditor</a> were scattered in various repositories to a monorepo powered by NX.
+* [Initial discussion](https://github.com/TriliumNext/Trilium/issues/4941)
+* [Relevant PR](https://github.com/TriliumNext/Notes/pull/1773)
+
+## Dec 2024: Front-end conversion to TypeScript
+
+* [Relevant PRs on GitHub](https://github.com/TriliumNext/Notes/pulls?q=is%3Apr+is%3Aclosed+%22Port+frontend+to+TypeScript%22)
+
+## Apr 2024: Back-end conversion to TypeScript
+
+* [Relevant PRs on GitHub](https://github.com/TriliumNext/Notes/pulls?q=is%3Apr+%22convert+backend+to+typescript%22)
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Backend.md b/docs/Developer Guide/Developer Guide/Architecture/Backend.md
new file mode 100644
index 0000000000..df0ddf21db
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Backend.md
@@ -0,0 +1,88 @@
+# Backend
+### Application Entry Point
+
+Location: `apps/server/src/main.ts`
+
+**Startup Sequence:**
+
+1. Load configuration
+2. Initialize database
+3. Run migrations
+4. Load Becca cache
+5. Start Express server
+6. Initialize WebSocket
+7. Start scheduled tasks
+
+### Service Layer
+
+Located at: `apps/server/src/services/`
+
+**Core Services:**
+
+* **Notes Management**
+ * `notes.ts` - CRUD operations
+ * `note_contents.ts` - Content handling
+ * `note_types.ts` - Type-specific logic
+ * `cloning.ts` - Note cloning/multi-parent
+* **Tree Operations**
+ * `tree.ts` - Tree structure management
+ * `branches.ts` - Branch operations
+ * `consistency_checks.ts` - Tree integrity
+* **Search**
+ * `search/search.ts` - Main search engine
+ * `search/expressions/` - Search expression parsing
+ * `search/services/` - Search utilities
+* **Sync**
+ * `sync.ts` - Synchronization protocol
+ * `sync_update.ts` - Update handling
+ * `sync_mutex.ts` - Concurrency control
+* **Scripting**
+ * `backend_script_api.ts` - Backend script API
+ * `script_context.ts` - Script execution context
+* **Import/Export**
+ * `import/` - Various import formats
+ * `export/` - Export to different formats
+ * `zip.ts` - Archive handling
+* **Security**
+ * `encryption.ts` - Note encryption
+ * `protected_session.ts` - Session management
+ * `password.ts` - Password handling
+
+### Route Structure
+
+Located at: `apps/server/src/routes/`
+
+```
+routes/
+├── index.ts # Route registration
+├── api/ # REST API endpoints
+│ ├── notes.ts
+│ ├── branches.ts
+│ ├── attributes.ts
+│ ├── search.ts
+│ ├── login.ts
+│ └── ...
+└── custom/ # Special endpoints
+ ├── setup.ts
+ ├── share.ts
+ └── ...
+```
+
+**API Endpoint Pattern:**
+
+```typescript
+router.get('/api/notes/:noteId', (req, res) => {
+ const noteId = req.params.noteId
+ const note = becca.getNote(noteId)
+ res.json(note.getPojoWithContent())
+})
+```
+
+### Middleware
+
+Key middleware components:
+
+* `auth.ts` - Authentication
+* `csrf.ts` - CSRF protection
+* `request_context.ts` - Request-scoped data
+* `error_handling.ts` - Error responses
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database.md b/docs/Developer Guide/Developer Guide/Architecture/Database.md
new file mode 100644
index 0000000000..b8836b56d4
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database.md
@@ -0,0 +1,40 @@
+# Database
+Trilium uses **SQLite** (via `better-sqlite3`) as its embedded database engine, providing a reliable, file-based storage system that requires no separate database server. The database stores all notes, their relationships, metadata, and configuration.
+
+Schema location: `apps/server/src/assets/db/schema.sql`
+
+### Data Access Patterns
+
+**Direct SQL:**
+
+```typescript
+// apps/server/src/services/sql.ts
+sql.getRows("SELECT * FROM notes WHERE type = ?", ['text'])
+sql.execute("UPDATE notes SET title = ? WHERE noteId = ?", [title, noteId])
+```
+
+**Through Becca:**
+
+```typescript
+// Recommended approach - uses cache
+const note = becca.getNote('noteId')
+note.title = 'New Title'
+note.save()
+```
+
+**Through Froca (Frontend):**
+
+```typescript
+// Read-only access
+const note = froca.getNote('noteId')
+console.log(note.title)
+```
+
+### Database Migrations
+
+* The migration system is in `server/src/migrations/migrations.ts` (actual definitions) and `src/services/migration.ts`.
+* Both SQLite and TypeScript migrations are supported.
+ * Small migrations are contained directly in `src/migrations/migrations.ts`.
+ * Bigger TypeScript migrations are sequentially numbered (e.g., `XXXX_migration_name.ts`) and dynamically imported by `migrations.ts`.
+* Automatic execution on version upgrade.
+* Schema version tracked in options table.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/attachments.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/attachments.md
new file mode 100644
index 0000000000..19cfae5da4
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/attachments.md
@@ -0,0 +1,16 @@
+# attachments
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `attachmentId` | Text | Non-null | | Unique ID (e.g. `qhC1vzU4nwSE`) |
+| `ownerId` | Text | Non-null | | The unique ID of a row in <a class="reference-link" href="notes.md">notes</a>. |
+| `role` | Text | Non-null | | The role of the attachment: `image` for images that are attached to a note, `file` for uploaded files. |
+| `mime` | Text | Non-null | | The MIME type of the attachment (e.g. `image/png`) |
+| `title` | Text | Non-null | | The title of the attachment. |
+| `isProtected` | Integer | Non-null | 0 | `1` if the entity is [protected](../../../Concepts/Protected%20entities.md), `0` otherwise. |
+| `position` | Integer | Non-null | 0 | Not sure where the position is relevant for attachments (saw it with values of 10 and 0). |
+| `blobId` | Text | Nullable | `null` | The corresponding `blobId` from the <a class="reference-link" href="blobs.md">blobs</a> table. |
+| `dateModified` | Text | Non-null | | Localized modification date (e.g. `2023-11-08 18:43:44.204+0200`) |
+| `utcDateModified` | Text | Non-null | | Modification date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+| `utcDateScheduledForErasure` | Text | Nullable | `null` | |
+| `isDeleted` | Integer | Non-null | | `1` if the entity is [deleted](../../../Concepts/Deleted%20notes.md), `0` otherwise. |
+| `deleteId` | Text | Nullable | `null` | |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/attributes.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/attributes.md
new file mode 100644
index 0000000000..2a34f46a9c
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/attributes.md
@@ -0,0 +1,84 @@
+# attributes
+<table>
+ <thead>
+ <tr>
+ <th>Column Name</th>
+ <th>Data Type</th>
+ <th>Nullity</th>
+ <th>Default value</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <th><code>attributeId</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td>Unique Id of the attribute (e.g. <code>qhC1vzU4nwSE</code>), can also have a special unique ID for special notes (e.g. <code>_lbToday_liconClass</code>).</td>
+ </tr>
+ <tr>
+ <th><code>noteId</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td>The ID of the <a href="notes.md">note</a> this atttribute belongs to</td>
+ </tr>
+ <tr>
+ <th><code>type</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td>The type of attribute (<code>label</code> or <code>relation</code>).</td>
+ </tr>
+ <tr>
+ <th><code>name</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td>The name/key of the attribute.</td>
+ </tr>
+ <tr>
+ <th><code>value</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td><code>""</code></td>
+ <td><ul><li>For <code>label</code> attributes, a free-form value of the attribute.</li><li>For <code>relation</code> attributes, the ID of the <a href="notes.md">note</a> the relation is pointing to.</li></ul></td>
+ </tr>
+ <tr>
+ <th><code>position</code></th>
+ <td>Integer</td>
+ <td>Non-null</td>
+ <td>0</td>
+ <td>The position of the attribute compared to the other attributes. Some predefined attributes such as <code>originalFileName</code> have a value of 1000.</td>
+ </tr>
+ <tr>
+ <th><code>utcDateModified</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td>Modification date in UTC format (e.g. <code>2023-11-08 16:43:44.204Z</code>)</td>
+ </tr>
+ <tr>
+ <th><code>isDeleted</code></th>
+ <td>Integer</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td><code>1</code> if the entity is <a href="../../../Concepts/Deleted%20notes.md">deleted</a>, <code>0</code> otherwise.</td>
+ </tr>
+ <tr>
+ <th><code>deleteId</code></th>
+ <td>Text</td>
+ <td>Nullable</td>
+ <td><code>null</code></td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><code>isInheritable</code></th>
+ <td>Integer</td>
+ <td>Nullable</td>
+ <td>0</td>
+ <td>&nbsp;</td>
+ </tr>
+ </tbody>
+</table>
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/blobs.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/blobs.md
new file mode 100644
index 0000000000..7273516286
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/blobs.md
@@ -0,0 +1,42 @@
+# blobs
+<table>
+ <thead>
+ <tr>
+ <th>Column Name</th>
+ <th>Data Type</th>
+ <th>Nullity</th>
+ <th>Default value</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <th><code>blobId</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td><p>The unique ID of the blob (e.g. <code>XXbfAJXqWrYnSXcelLFA</code>).</p><aside class="admonition important"><p>The ID is actually a hash of the content, see <code>AbstractBeccaEntity#saveBlob</code>! It is a logic error to modify an existing blob.</p></aside></td>
+ </tr>
+ <tr>
+ <th><code>content</code></th>
+ <td>Text</td>
+ <td>Nullable</td>
+ <td><code>null</code></td>
+ <td><p>The content of the blob, can be either:</p><ul><li>text (for plain text notes or HTML notes).</li><li>binary (for images and other types of attachments)</li></ul></td>
+ </tr>
+ <tr>
+ <th><code>dateModified</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td>Creation date with timezone offset (e.g. <code>2023-11-08 18:43:44.204+0200</code>)</td>
+ </tr>
+ <tr>
+ <th><code>utcDateModified</code></th>
+ <td>Text</td>
+ <td>Non-null</td>
+ <td>&nbsp;</td>
+ <td><p>Creation date in UTC format (e.g. <code>2023-11-08 16:43:44.204Z</code>).</p><p>Blobs cannot be modified, so this timestamp specifies when the blob was created.</p></td>
+ </tr>
+ </tbody>
+</table>
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/branches.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/branches.md
new file mode 100644
index 0000000000..b1baa230bb
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/branches.md
@@ -0,0 +1,12 @@
+# branches
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `branchId` | Text | Non-null | | The ID of the branch, in the form of `a_b` where `a` is the `parentNoteId` and `b` is the `noteId`. |
+| `noteId` | Text | Non-null | | The ID of the [note](notes.md). |
+| `parentNoteId` | Text | Non-null | | The ID of the parent [note](notes.md) the note belongs to. |
+| `notePosition` | Integer | Non-null | | The position of the branch within the same level of hierarchy, the value is usually a multiple of 10. |
+| `prefix` | Text | Nullable | | The [branch prefix](../../../Concepts/Branch%20prefixes.md) if any, or `NULL` otherwise. |
+| `isExpanded` | Integer | Non-null | 0 | Whether the branch should appear expanded (its children shown) to the user. |
+| `isDeleted` | Integer | Non-null | 0 | `1` if the entity is [deleted](../../../Concepts/Deleted%20notes.md), `0` otherwise. |
+| `deleteId` | Text | Nullable | `null` | |
+| `utcDateModified` | Text | Non-null | | Modification date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/entity_changes.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/entity_changes.md
new file mode 100644
index 0000000000..23921f7293
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/entity_changes.md
@@ -0,0 +1,15 @@
+# entity_changes
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `id` | Integer | Non-null | | A sequential numeric index of the entity change. |
+| `entityName` | Text | Non-null | | The type of entity being changed (`attributes`, `branches`, `note_reordering`, etc.) |
+| `entityId` | Text | Non-null | | The ID of the entity being changed. |
+| `hash` | Text | Nullable (\*) | | TODO: Describe how the hash is calculated |
+| `isErased` | Integer (1 or 0) | Nullable (\*) | | TODO: What does this do? |
+| `changeId` | Text | Nullable (\*) | | TODO: What does this do? |
+| `componentId` | Text | Nullable (\*) | | The ID of the UI component that caused this change. <br> <br>Examples: `date-note`, `F-PoZMI0vc`, `NA` (catch all) |
+| `instanceId` | Text | Nullable (\*) | | The ID of the [instance](#root/pOsGYCXsbNQG/tC7s2alapj8V/Gzjqa934BdH4/c5xB8m4g2IY6) that created this change. |
+| `isSynced` | Integer (1 or 0) | Non-null | | TODO: What does this do? |
+| `utcDateChanged` | Text | Non-null | | Date of the entity change in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+
+Nullable (\*) means all new values are non-null, old rows may contain null values.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/etapi_tokens.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/etapi_tokens.md
new file mode 100644
index 0000000000..0bc852fda0
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/etapi_tokens.md
@@ -0,0 +1,9 @@
+# etapi_tokens
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `etapiTokenId` | Text | Non-null | | A unique ID of the token (e.g. `aHmLr5BywvfJ`). |
+| `name` | Text | Non-null | | The name of the token, as is set by the user. |
+| `tokenHash` | Text | Non-null | | The token itself. |
+| `utcDateCreated` | Text | Non-null | | Creation date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+| `utcDateModified` | Text | Non-null | | Modification date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+| `isDeleted` | Integer | Non-null | 0 | `1` if the entity is [deleted](../../../Concepts/Deleted%20notes.md), `0` otherwise. |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/notes.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/notes.md
new file mode 100644
index 0000000000..192eeaa166
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/notes.md
@@ -0,0 +1,15 @@
+# notes
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `noteId` | Text | Non-null | | The unique ID of the note (e.g. `2LJrKqIhr0Pe`). |
+| `title` | Text | Non-null | `"note"` | The title of the note, as defined by the user. |
+| `isProtected` | Integer | Non-null | 0 | `1` if the entity is [protected](../../../Concepts/Protected%20entities.md), `0` otherwise. |
+| `type` | Text | Non-null | `"text"` | The type of note (i.e. `text`, `file`, `code`, `relationMap`, `mermaid`, `canvas`). |
+| `mime` | Text | Non-null | `"text/html"` | The MIME type of the note (e.g. `text/html`).. Note that it can be an empty string in some circumstances, but not null. |
+| `blobId` | Text | Nullable | `null` | The corresponding ID from <a class="reference-link" href="blobs.md">blobs</a>. Although it can theoretically be `NULL`, haven't found any such note yet. |
+| `isDeleted` | Integer | Nullable | 0 | `1` if the entity is [deleted](../../../Concepts/Deleted%20notes.md), `0` otherwise. |
+| `deleteId` | Text | Non-null | `null` | |
+| `dateCreated` | Text | Non-null | | Localized creation date (e.g. `2023-11-08 18:43:44.204+0200`) |
+| `dateModified` | Text | Non-null | | Localized modification date (e.g. `2023-11-08 18:43:44.204+0200`) |
+| `utcDateCreated` | Text | Non-null | | Creation date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+| `utcDateModified` | Text | Non-null | | Modification date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/options.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/options.md
new file mode 100644
index 0000000000..54b8961704
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/options.md
@@ -0,0 +1,7 @@
+# options
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `name` | Text | Non-null | | The name of option (e.g. `maxContentWidth`) |
+| `value` | Text | Non-null | | The value of the option. |
+| `isSynced` | Integer | Non-null | 0 | `0` if the option is not synchronized and thus can differ between clients, `1` if the option is synchronized. |
+| `utcDateModified` | Text | Non-null | | Modification date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/recent_notes.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/recent_notes.md
new file mode 100644
index 0000000000..536b6cfe49
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/recent_notes.md
@@ -0,0 +1,6 @@
+# recent_notes
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `noteId` | Text | Non-null | | Unique ID of the note (e.g. `yRRTLlqTbGoZ`). |
+| `notePath` | Text | Non-null | | The path (IDs) to the [note](notes.md) from root to the note itself, separated by slashes. |
+| `utcDateCreated` | Text | Non-null | | Creation date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/revisions.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/revisions.md
new file mode 100644
index 0000000000..bcc72303d7
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/revisions.md
@@ -0,0 +1,15 @@
+# revisions
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `revisionId` | Text | Non-null | | Unique ID of the revision (e.g. `0GjgUqnEudI8`). |
+| `noteId` | Text | Non-null | | ID of the [note](notes.md) this revision belongs to. |
+| `type` | Text | Non-null | `""` | The type of note (i.e. `text`, `file`, `code`, `relationMap`, `mermaid`, `canvas`). |
+| `mime` | Text | Non-null | `""` | The MIME type of the note (e.g. `text/html`). |
+| `title` | Text | Non-null | | The title of the note, as defined by the user. |
+| `isProtected` | Integer | Non-null | 0 | `1` if the entity is [protected](../../../Concepts/Protected%20entities.md), `0` otherwise. |
+| `blobId` | Text | Nullable | `null` | The corresponding ID from <a class="reference-link" href="blobs.md">blobs</a>. Although it can theoretically be `NULL`, haven't found any such note yet. |
+| `utcDateLastEdited` | Text | Non-null | | **Not sure how it differs from modification date.** |
+| `utcDateCreated` | Text | Non-null | | Creation date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+| `utcDateModified` | Text | Non-null | | Modification date in UTC format (e.g. `2023-11-08 16:43:44.204Z`) |
+| `dateLastEdited` | Text | Non-null | | **Not sure how it differs from modification date.** |
+| `dateCreated` | Text | Non-null | | Localized creatino date (e.g. `2023-08-12 15:10:04.045+0300`) |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/sessions.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/sessions.md
new file mode 100644
index 0000000000..4d6919a8cb
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/sessions.md
@@ -0,0 +1,8 @@
+# sessions
+Contains user sessions for authentication purposes. The table is almost a direct mapping of the information that `express-session` requires.
+
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `id` | Text | Non-null | | Unique, non-sequential ID of the session, directly as indicated by `express-session` |
+| `data` | Text | Non-null | | The session information, in stringified JSON format. |
+| `expires` | Integer | Non-null | | The expiration date of the session, extracted from the session information. Used to rapidly clean up expired sessions. |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/user_data.md b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/user_data.md
new file mode 100644
index 0000000000..100a7272bb
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Database/Database structure/user_data.md
@@ -0,0 +1,17 @@
+# user_data
+Contains the user information for two-factor authentication. This table is **not** used for multi-user.
+
+Relevant files:
+
+* `apps/server/src/services/encryption/open_id_encryption.ts`
+
+| Column Name | Data Type | Nullity | Default value | Description |
+| --- | --- | --- | --- | --- |
+| `tmpID` | Integer | | | A sequential ID of the user. Since only one user is supported by Trilium, this value is always zero. |
+| `username` | Text | | | The user name as returned from the OAuth operation. |
+| `email` | Text | | | The email as returned from the OAuth operation. |
+| `userIDEncryptedDataKey` | Text | | | An encrypted hash of the user subject identifier from the OAuth operation. |
+| `userIDVerificationHash` | Text | | | A salted hash of the subject identifier from the OAuth operation. |
+| `salt` | Text | | | The verification salt. |
+| `derivedKey` | Text | | | A random secure token. |
+| `isSetup` | Text | | `"false"` | Indicates that the user has been saved (`"true"`). |
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Frontend.md b/docs/Developer Guide/Developer Guide/Architecture/Frontend.md
new file mode 100644
index 0000000000..9ef0acbdfb
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Frontend.md
@@ -0,0 +1,61 @@
+# Frontend
+### Application Entry Point
+
+**Desktop:** `apps/client/src/desktop.ts` **Web:** `apps/client/src/index.ts`
+
+### Service Layer
+
+Located at: `apps/client/src/services/`
+
+Key services:
+
+* `froca.ts` - Frontend cache
+* `server.ts` - API communication
+* `ws.ts` - WebSocket connection
+* `tree_service.ts` - Note tree management
+* `note_context.ts` - Active note tracking
+* `protected_session.ts` - Encryption key management
+* `link.ts` - Note linking and navigation
+* `export.ts` - Note export functionality
+
+### UI Components
+
+**Component Locations:**
+
+* `widgets/containers/` - Layout containers
+* `widgets/buttons/` - Toolbar buttons
+* `widgets/dialogs/` - Modal dialogs
+* `widgets/ribbon_widgets/` - Tab widgets
+* `widgets/type_widgets/` - Note type editors
+
+### Event System
+
+**Application Events:**
+
+```typescript
+// Subscribe to events
+appContext.addBeforeUnloadListener(() => {
+ // Cleanup before page unload
+})
+
+// Trigger events
+appContext.trigger('noteTreeLoaded')
+```
+
+**Note Context Events:**
+
+```typescript
+// NoteContextAwareWidget automatically receives:
+- noteSwitched()
+- noteChanged()
+- refresh()
+```
+
+### State Management
+
+Trilium uses **custom state management** rather than Redux/MobX:
+
+* `note_context.ts` - Active note and context
+* `froca.ts` - Entity cache
+* Component local state
+* URL parameters for shareable state
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Architecture/Security.md b/docs/Developer Guide/Developer Guide/Architecture/Security.md
new file mode 100644
index 0000000000..f1ef4da771
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Architecture/Security.md
@@ -0,0 +1,464 @@
+# Security
+Trilium implements a **defense-in-depth security model** with multiple layers of protection for user data. The security architecture covers authentication, authorization, encryption, input sanitization, and secure communication.
+
+## Security Principles
+
+1. **Data Privacy**: User data is protected at rest and in transit
+2. **Encryption**: Per-note encryption for sensitive content
+3. **Authentication**: Multiple authentication methods supported
+4. **Authorization**: Single-user model with granular protected sessions
+5. **Input Validation**: All user input sanitized
+6. **Secure Defaults**: Security features enabled by default
+7. **Transparency**: Open source allows security audits
+
+## Threat Model
+
+### Threats Considered
+
+1. **Unauthorized Access**
+ * Physical access to device
+ * Network eavesdropping
+ * Stolen credentials
+ * Session hijacking
+2. **Data Exfiltration**
+ * Malicious scripts
+ * XSS attacks
+ * SQL injection
+ * CSRF attacks
+3. **Data Corruption**
+ * Malicious modifications
+ * Database tampering
+ * Sync conflicts
+4. **Privacy Leaks**
+ * Unencrypted backups
+ * Search indexing
+ * Temporary files
+ * Memory dumps
+
+### Out of Scope
+
+* Nation-state attackers
+* Zero-day vulnerabilities in dependencies
+* Hardware vulnerabilities (Spectre, Meltdown)
+* Physical access with unlimited time
+* Quantum computing attacks
+
+## Authentication
+
+### Password Authentication
+
+**Implementation:** `apps/server/src/services/password.ts`
+
+### TOTP (Two-Factor Authentication)
+
+**Implementation:** `apps/server/src/routes/api/login.ts`
+
+### OpenID Connect
+
+**Implementation:** `apps/server/src/routes/api/login.ts`
+
+**Supported Providers:**
+
+* Any OpenID Connect compatible provider
+* Google, GitHub, Auth0, etc.
+
+**Flow:**
+
+```typescript
+// 1. Redirect to provider
+GET /api/login/openid
+
+// 2. Provider redirects back with code
+GET /api/login/openid/callback?code=...
+
+// 3. Exchange code for tokens
+const tokens = await openidClient.callback(redirectUri, req.query)
+
+// 4. Verify ID token
+const claims = tokens.claims()
+
+// 5. Create session
+req.session.loggedIn = true
+```
+
+### Session Management
+
+**Session Storage:** SQLite database (sessions table)
+
+**Session Configuration:**
+
+```typescript
+app.use(session({
+ secret: sessionSecret,
+ resave: false,
+ saveUninitialized: false,
+ rolling: true,
+ cookie: {
+ maxAge: 7 * 24 * 60 * 60 * 1000, // 7 days
+ httpOnly: true,
+ secure: isHttps,
+ sameSite: 'lax'
+ },
+ store: new SqliteStore({
+ db: db,
+ table: 'sessions'
+ })
+}))
+```
+
+**Session Invalidation:**
+
+* Automatic timeout after inactivity
+* Manual logout clears session
+* Server restart invalidates all sessions (optional)
+
+## Authorization
+
+### Single-User Model
+
+**Desktop:**
+
+* Single user (owner of device)
+* No multi-user support
+* Full access to all notes
+
+**Server:**
+
+* Single user per installation
+* Authentication required for all operations
+* No user roles or permissions
+
+### Protected Sessions
+
+**Purpose:** Temporary access to encrypted (protected) notes
+
+**Implementation:** `apps/server/src/services/protected_session.ts`
+
+**Workflow:**
+
+```typescript
+// 1. User enters password for protected notes
+POST /api/protected-session/enter
+Body: { password: "protected-password" }
+
+// 2. Derive encryption key
+const protectedDataKey = deriveKey(password)
+
+// 3. Verify password (decrypt known encrypted value)
+const decrypted = decrypt(testValue, protectedDataKey)
+if (decrypted === expectedValue) {
+ // 4. Store in memory (not in session)
+ protectedSessionHolder.setProtectedDataKey(protectedDataKey)
+
+ // 5. Set timeout
+ setTimeout(() => {
+ protectedSessionHolder.clearProtectedDataKey()
+ }, timeout)
+}
+```
+
+**Protected Session Timeout:**
+
+* Default: 10 minutes (configurable)
+* Extends on activity
+* Cleared on browser close
+* Separate from main session
+
+### API Authorization
+
+**Internal API:**
+
+* Requires authenticated session
+* CSRF token validation
+* Same-origin policy
+
+**ETAPI (External API):**
+
+* Token-based authentication
+* No session required
+* Rate limiting
+
+## Encryption
+
+### Note Encryption
+
+**Encryption Algorithm:** AES-256-CBC
+
+**Key Hierarchy:**
+
+```
+User Password
+ ↓ (scrypt)
+Data Key (for protected notes)
+ ↓ (AES-128)
+Protected Note Content
+```
+
+**Protected Note Metadata:**
+
+* Content IS encrypted
+* Type and MIME are NOT encrypted
+* Attributes are NOT encrypted
+
+### Data Key Management
+
+**Key Rotation:**
+
+* Not currently supported
+* Requires re-encrypting all protected notes
+
+### Transport Encryption
+
+**HTTPS:**
+
+* Recommended for server installations
+* TLS 1.2+ only
+* Strong cipher suites preferred
+* Certificate validation enabled
+
+**Desktop:**
+
+* Local communication (no network)
+* No HTTPS required
+
+### Backup Encryption
+
+**Database Backups:**
+
+* Protected notes remain encrypted in backup
+* Backup file should be protected separately
+* Consider encrypting backup storage location
+
+## Input Sanitization
+
+### XSS Prevention
+
+* **HTML Sanitization**
+* **CKEditor Configuration:**
+
+ ```
+ // apps/client/src/widgets/type_widgets/text_type_widget.ts
+ ClassicEditor.create(element, {
+ // Restrict allowed content
+ htmlSupport: {
+ allow: [
+ { name: /./, attributes: true, classes: true, styles: true }
+ ],
+ disallow: [
+ { name: 'script' },
+ { name: 'iframe', attributes: /^(?!src$).*/ }
+ ]
+ }
+ })
+ ```
+* Content Security Policy
+
+### SQL Injection Prevention
+
+**Parameterized Queries:**
+
+```typescript
+const notes = sql.getRows(
+ 'SELECT * FROM notes WHERE title = ?',
+ [userInput]
+)
+```
+
+**ORM Usage:**
+
+```typescript
+// Entity-based access prevents SQL injection
+const note = becca.getNote(noteId)
+note.title = userInput // Sanitized by entity
+note.save() // Parameterized query
+```
+
+### CSRF Prevention
+
+**CSRF Token Validation:**
+
+Location: `apps/server/src/routes/csrf_protection.ts`
+
+Stateless CSRF using [Double Submit Cookie Pattern](https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#double-submit-cookie) via [`csrf-csrf`](https://github.com/Psifi-Solutions/csrf-csrf).
+
+### File Upload Validation
+
+**Validation:**
+
+```typescript
+// Validate file size
+const maxSize = 100 * 1024 * 1024 // 100 MB
+if (file.size > maxSize) {
+ throw new Error('File too large')
+}
+```
+
+## Network Security
+
+### HTTPS Configuration
+
+**Certificate Validation:**
+
+* Require valid certificates in production
+* Self-signed certificates allowed for development
+* Certificate pinning not implemented
+
+### Rate Limiting
+
+**Login Rate Limiting:**
+
+```typescript
+const loginLimiter = rateLimit({
+ windowMs: 15 * 60 * 1000,
+ max: 10, // 10 failed attempts
+ skipSuccessfulRequests: true
+})
+
+app.post('/api/login/password', loginLimiter, loginHandler)
+```
+
+## Data Security
+
+### Secure Data Deletion
+
+**Soft Delete:**
+
+```typescript
+// Mark as deleted (sync first)
+note.isDeleted = 1
+note.deleteId = generateUUID()
+note.save()
+
+// Entity change tracked for sync
+addEntityChange('notes', noteId, note)
+```
+
+**Hard Delete (Erase):**
+
+```typescript
+// After sync completed
+sql.execute('DELETE FROM notes WHERE noteId = ?', [noteId])
+sql.execute('DELETE FROM branches WHERE noteId = ?', [noteId])
+sql.execute('DELETE FROM attributes WHERE noteId = ?', [noteId])
+
+// Mark entity change as erased
+sql.execute('UPDATE entity_changes SET isErased = 1 WHERE entityId = ?', [noteId])
+```
+
+**Blob Cleanup:**
+
+```typescript
+// Find orphaned blobs (not referenced by any note/revision/attachment)
+const orphanedBlobs = sql.getRows(`
+ SELECT blobId FROM blobs
+ WHERE blobId NOT IN (SELECT blobId FROM notes WHERE blobId IS NOT NULL)
+ AND blobId NOT IN (SELECT blobId FROM revisions WHERE blobId IS NOT NULL)
+ AND blobId NOT IN (SELECT blobId FROM attachments WHERE blobId IS NOT NULL)
+`)
+
+// Delete orphaned blobs
+for (const blob of orphanedBlobs) {
+ sql.execute('DELETE FROM blobs WHERE blobId = ?', [blob.blobId])
+}
+```
+
+### Memory Security
+
+**Protected Data in Memory:**
+
+* Protected data keys stored in memory only
+* Cleared on timeout
+* Not written to disk
+* Not in session storage
+
+## Dependency Security
+
+### Vulnerability Scanning
+
+**Tools:**
+
+* Renovate bot - Automatic dependency updates
+* `pnpm audit` - Check for known vulnerabilities
+* GitHub Dependabot alerts
+
+**Process:**
+
+```
+# Check for vulnerabilities
+npm audit
+
+# Fix automatically
+npm audit fix
+
+# Manual review for breaking changes
+npm audit fix --force
+```
+
+### Dependency Pinning
+
+**package.json:**
+
+```
+{
+ "dependencies": {
+ "express": "4.18.2", // Exact version
+ "better-sqlite3": "^9.2.2" // Compatible versions
+ }
+}
+```
+
+**pnpm Overrides:**
+
+```
+{
+ "pnpm": {
+ "overrides": {
+ "lodash@<4.17.21": ">=4.17.21", // Force minimum version
+ "axios@<0.21.2": ">=0.21.2"
+ }
+ }
+}
+```
+
+### Patch Management
+
+**pnpm Patches:**
+
+```
+# Create patch
+pnpm patch @ckeditor/ckeditor5
+
+# Edit files in temporary directory
+# ...
+
+# Generate patch file
+pnpm patch-commit /tmp/ckeditor5-patch
+
+# Patch applied automatically on install
+```
+
+## Security Auditing
+
+### Logs
+
+**Security Events Logged:**
+
+* Login attempts (success/failure)
+* Protected session access
+* Password changes
+* ETAPI token usage
+* Failed CSRF validations
+
+**Log Location:**
+
+* Desktop: Console output
+* Server: Log files or stdout
+
+### Monitoring
+
+**Metrics to Monitor:**
+
+* Failed login attempts
+* API error rates
+* Unusual database changes
+* Large exports/imports
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Branching strategy.md b/docs/Developer Guide/Developer Guide/Branching strategy.md
new file mode 100644
index 0000000000..e302f4ee15
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Branching strategy.md
@@ -0,0 +1,30 @@
+# Branching strategy
+## Main branch
+
+The main development branch is conveniently called `main`. This branch contains all the merged features and is considered semi-stable.
+
+## Development
+
+Every new development must be done in a separate branch (usually prefixed with `feature/`). The PR must then be reviewed.
+
+## Reviewing
+
+Each PR must be tested manually and reviewed by a maintainer. For PRs that are made by the maintainers themselves, an LLM review from Copilot or Gemini are also accepted.
+
+After a PR is approved, it is merged into the `main` branch and the change log draft is updated.
+
+## Releasing
+
+[Releasing a new version](Building/Releasing%20a%20new%20version.md) is done straight from the `main` branch once it's deemed stable enough for production.
+
+## Hot-fixing
+
+After releasing a new version, it's sometimes desirable to create a hotfix in order to fix some issues with the production version without introducing many changes that might have already been merged in `main`.
+
+To do so, the procedure is as follows:
+
+1. A `hotfix` branch is created, from the tag of the release.
+2. If fixes/features from the `main` branch are needed, they are cherry-picked directly onto the branch.
+3. New fixes/features are either developed directly on the `hotfix` branch or an a PR that targets this branch, depending on the complexity.
+4. A new version is released from the `hotfix` version.
+5. The `hotfix` version is merged back into `main`, via a PR.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Building/Build deliveries locally.md b/docs/Developer Guide/Developer Guide/Building/Build deliveries locally.md
new file mode 100644
index 0000000000..80bb6471c9
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Building/Build deliveries locally.md
@@ -0,0 +1,36 @@
+# Build deliveries locally
+## Building the desktop
+
+Go to `apps/desktop`, and:
+
+* To generate the packages, run `pnpm electron-forge:make`.
+* To only build the Flatpak, run `pnpm electron-forge:make-flatpak`.
+* To only build without packaging it, run `pnpm electron-forge:package`.
+
+On macOS, packaging compiles the Icon Composer app icons (`app-icon/icon.icon`, `icon-dev.icon`) with `actool`, so it requires macOS 26 and Xcode 26 or newer. On older versions `@electron/packager` fails with an `actool` error rather than falling back to the `.icns` icon.
+
+## Building the server
+
+Go to `apps/server` and run `pnpm package` to run the build script. The built artifacts will appear in `apps/server/dist`, whereas the packaged build will be available in `apps/server/out`.
+
+## On NixOS
+
+Under NixOS the following `nix-shell` is needed:
+
+```
+nix-shell -p jq
+```
+
+For Linux builds:
+
+```
+nix-shell -p jq fakeroot dpkg
+```
+
+To test the Linux builds, use `steam-run`:
+
+```javascript
+$ NIXPKGS_ALLOW_UNFREE=1 nix-shell -p steam-run
+[nix-shell] cd dist/trilium-linux-x64
+[nix-shell] steam-run ./trilium
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Building/Build information.md b/docs/Developer Guide/Developer Guide/Building/Build information.md
new file mode 100644
index 0000000000..4d900aaec0
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Building/Build information.md
@@ -0,0 +1,5 @@
+# Build information
+* Provides context about when the build was made and the corresponding Git revision.
+* The information is displayed to the client when going in the about dialog.
+* The build information is hard-coded in `packages/trilium-core/src/services/build.ts`. This file is generated automatically via `chore:update-build-info` which itself is run automatically whenever making a build in the CI.
+* Passing `--from-commit` stamps the commit's date instead of the current time, so that two builds of the same source agree. The Flathub build uses it, since it rebuilds published tags.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Building/Docker.md b/docs/Developer Guide/Developer Guide/Building/Docker.md
new file mode 100644
index 0000000000..ea5782ad2b
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Building/Docker.md
@@ -0,0 +1,8 @@
+# Docker
+To build the server for Docker:
+
+* Go to `apps/server` and run:
+ * `pnpm docker-build-debian` or
+ * `pnpm docker-build-alpine`.
+* Similarly, to build the rootless versions: `pnpm docker-build-rootless-debian` or `pnpm docker-build-rootless-alpine`.
+* To not only build but also run the Docker container, simply replace `docker-build` with `docker-start` (e.g. `pnpm docker-start-debian`).
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Building/Live reload (HMR).md b/docs/Developer Guide/Developer Guide/Building/Live reload (HMR).md
new file mode 100644
index 0000000000..8ae38f99a5
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Building/Live reload (HMR).md
@@ -0,0 +1,10 @@
+# Live reload (HMR)
+Trilium uses Vite's HMR (hot module reloading) mechanism.
+
+## Server live reload
+
+If running the server using `pnpm server:start`, the server will watch for changes. For React components, they will be hot-reloaded without requiring a refresh. For other services, it will reload the page.
+
+## Desktop live reload
+
+`pnpm desktop:start` acts the same as `pnpm server:start` with hot-reloading for client-side changes. Changes on the desktop side require a complete re-run of the `pnpm desktop:start` command.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Building/Releasing a new version.md b/docs/Developer Guide/Developer Guide/Building/Releasing a new version.md
new file mode 100644
index 0000000000..dc6793a025
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Building/Releasing a new version.md
@@ -0,0 +1,19 @@
+# Releasing a new version
+Releasing is mostly handled by the CI:
+
+* The version on GitHub is published automatically, including the description with the change log which is taken from the documentation.
+* A PR is created automatically on the Winget repository to update to the new version.
+
+Releases are usually made directly from the `main` branch. For hot-fixes the process is the same but with a different branch, consult the <a class="reference-link" href="../Branching%20strategy.md">Branching strategy</a> for more information.
+
+The process is as follows:
+
+1. Edit the <a class="reference-link" href="../Documentation.md">Documentation</a> to add a corresponding entry in the _Release notes_ section.
+2. In the root `package.json`, set `version` to the new version to be released.
+3. Run `chore:update-version` to automatically update the version of the rest of the `package.json` files.
+4. Run `pnpm i` to update the package lock as well.
+5. Commit the changes to the `package.json` files and the `package-lock.json`. The commit message is usually `chore(release): prepare for v1.2.3`.
+6. Tag the newly created commit: `git tag v1.2.3`
+7. Push the commit and the newly created tag: `git push; git push --tags`.
+8. Wait for the CI to finish.
+9. When the release is automatically created in GitHub, download it to make sure it works OK.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Building/Running a development build.md b/docs/Developer Guide/Developer Guide/Building/Running a development build.md
new file mode 100644
index 0000000000..c69e19d50b
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Building/Running a development build.md
@@ -0,0 +1,33 @@
+# Running a development build
+First, follow the <a class="reference-link" href="../Environment%20Setup.md">Environment Setup</a>.
+
+## Client
+
+The client is not meant to be run by itself, despite being described as an app. See the documentation on the server instead.
+
+## Server
+
+* To run the server in development mode, run `server:start`. The dev port is `8080`.
+* To run the server in production mode (with its own copy of the assets), run `server:start-prod`.
+* To build for Docker, see <a class="reference-link" href="Docker.md">Docker</a>.
+
+To run with a custom port, change the `TRILIUM_PORT` environment variable from the `package.json`.
+
+## Desktop
+
+* To run in development mode, use `pnpm desktop:start`.
+* To run in production mode, use `pnpm desktop:start-prod`.
+
+## Safe mode
+
+Safe mode is off by default, to enable it temporarily on a Unix shell, prepend the environment variable setting:
+
+```
+pnpm cross-env TRILIUM_SAFE_MODE=1 pnpm server:start
+```
+
+## Running on NixOS
+
+When doing development, the Electron binary retrieved from NPM is not going to be compatible with NixOS, resulting in errors when trying to run it. However Trilium handles it automatically when running `pnpm desktop:start`.
+
+If there's no `electron` the system path it will attempt to use `nix-shell` to obtain it.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Backlinks.md b/docs/Developer Guide/Developer Guide/Concepts/Backlinks.md
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Branch prefixes.md b/docs/Developer Guide/Developer Guide/Concepts/Branch prefixes.md
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/docs/Developer Guide/Developer Guide/Concepts/CI/1_Main_image.png b/docs/Developer Guide/Developer Guide/Concepts/CI/1_Main_image.png
new file mode 100644
index 0000000000..5eacee569a
Binary files /dev/null and b/docs/Developer Guide/Developer Guide/Concepts/CI/1_Main_image.png differ
diff --git a/docs/Developer Guide/Developer Guide/Concepts/CI/Main.md b/docs/Developer Guide/Developer Guide/Concepts/CI/Main.md
new file mode 100644
index 0000000000..7025bf2f08
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/CI/Main.md
@@ -0,0 +1,38 @@
+# Main
+The main workflow of the CI:
+
+* Builds the Docker image and publishes in the GitHub Docker registry.
+* Builds using a portion of the [delivery script](../../Building/Build%20deliveries%20locally.md) artifacts for the following platforms:
+ * Windows `x86_64` as .zip file
+ * Windows `x86_64` installer (using Squirrel)
+ * macOS `x86_64` and `aarch64`.
+ * Linux `x86_64`
+ * Linux server `x86_64`.
+
+The main workflow of the CI runs on `develop` branches as well as any branch that starts with `feature/update_`.
+
+## Downloading the artifacts from the main branch
+
+Simply go to the [`develop` branch on GitHub](https://github.com/TriliumNext/Trilium) and look at the commit bar:
+
+<figure class="image"><img src="Main_image.png"></figure>
+
+Press the green checkmark (or red cross if something went bad). Then look at the list of jobs and their status:
+
+<figure class="image"><img src="1_Main_image.png"></figure>
+
+Then look for any of the entires that starts with “Main” and press the “Details” link next to it. It doesn't really matter which platform you'll choose as the artifacts are available on the same page.
+
+## Preview deployments
+
+Three workflows publish a Cloudflare Pages preview for every pull request: `deploy-app.yml` (the standalone app, `trilium-app`), `deploy-docs.yml` (`trilium-docs`) and `website.yml` (`trilium-homepage`). Each preview lands at `https://pr-<number>.<project>.pages.dev` and a bot comment on the pull request carries the link.
+
+Those workflows do not deploy the preview themselves. A `pull_request` run started from a fork receives neither secrets nor repository variables, so it cannot reach Cloudflare and `vars.REPO_MAIN` reads as empty. Instead the run builds, `.github/actions/upload-cloudflare-preview` uploads the built directory and the pull request number as artifacts, and the completed run raises a `workflow_run` event. `deploy-previews.yml` answers that event and calls `cloudflare-preview.yml`, which downloads the artifacts, deploys with `wrangler` and posts the comment. A `workflow_run` run always executes the default branch's copy of the workflow with the base repository's secrets.
+
+Two consequences are worth knowing:
+
+* `cloudflare-preview.yml` must never check out the pull request's head or install its dependencies. It holds the Cloudflare credentials, and running fork-authored code beside them would hand those credentials away. Its only fork-controlled input is a directory of static files passed to `wrangler`.
+* A pull request can edit the workflow that writes the artifacts, so the pull request number it claims is checked against `workflow_run.head_sha` before it is used.
+* The build is served as static files, but Cloudflare Pages runs a `functions/` directory and `_worker.js` server-side, where the project's bindings are reachable. None of the three sites uses them, so a build carrying one fails the deploy rather than publishing it. `_headers` and `_redirects` are published as usual; `apps/standalone/public/_headers` sets the cross-origin isolation the app needs.
+
+Because GitHub only triggers `workflow_run` from workflow files on the default branch, changes to `deploy-previews.yml` and `cloudflare-preview.yml` take effect once they are merged into `main` and cannot be exercised from a branch.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/CI/Main_image.png b/docs/Developer Guide/Developer Guide/Concepts/CI/Main_image.png
new file mode 100644
index 0000000000..2f13f1647f
Binary files /dev/null and b/docs/Developer Guide/Developer Guide/Concepts/CI/Main_image.png differ
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Cache.md b/docs/Developer Guide/Developer Guide/Concepts/Cache.md
new file mode 100644
index 0000000000..91a6f8b6d3
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Cache.md
@@ -0,0 +1,111 @@
+# Cache
+### Three-Layer Cache System
+
+Trilium implements a sophisticated **three-tier caching system** to optimize performance and enable offline functionality:
+
+#### 1\. Becca (Backend Cache)
+
+Located at: `apps/server/src/becca/`
+
+```typescript
+// Becca caches all entities in memory
+class Becca {
+ notes: Record<string, BNote>
+ branches: Record<string, BBranch>
+ attributes: Record<string, BAttribute>
+ attachments: Record<string, BAttachment>
+ // ... other entity collections
+}
+```
+
+**Responsibilities:**
+
+* Server-side entity cache
+* Maintains complete note tree in memory
+* Handles entity relationships and integrity
+* Provides fast lookups without database queries
+* Manages entity lifecycle (create, update, delete)
+
+**Key Files:**
+
+* `becca.ts` - Main cache instance
+* `becca_loader.ts` - Loads entities from database
+* `becca_service.ts` - Cache management operations
+* `entities/` - Entity classes (BNote, BBranch, etc.)
+
+#### 2\. Froca (Frontend Cache)
+
+Located at: `apps/client/src/services/froca.ts`
+
+```typescript
+// Froca is a read-only mirror of backend data
+class Froca {
+ notes: Record<string, FNote>
+ branches: Record<string, FBranch>
+ attributes: Record<string, FAttribute>
+ // ... other entity collections
+}
+```
+
+**Responsibilities:**
+
+* Frontend read-only cache
+* Lazy loading of note tree
+* Minimizes API calls
+* Enables fast UI rendering
+* Synchronizes with backend via WebSocket
+
+**Loading Strategy:**
+
+* Initial load: root notes and immediate children
+* Lazy load: notes loaded when accessed
+* When note is loaded, all parent and child branches load
+* Deleted entities tracked via missing branches
+
+#### 3\. Shaca (Share Cache)
+
+Located at: `apps/server/src/share/`
+
+**Responsibilities:**
+
+* Optimized cache for shared/published notes
+* Handles public note access without authentication
+* Performance-optimized for high-traffic scenarios
+* Separate from main Becca to isolate concerns
+
+### Cache Invalidation
+
+**Server-Side:**
+
+* Entities automatically update cache on save
+* WebSocket broadcasts changes to all clients
+* Synchronization updates trigger cache refresh
+
+**Client-Side:**
+
+* WebSocket listeners update Froca
+* Manual reload via `froca.loadSubTree(noteId)`
+* Full reload on protected session changes
+
+### Cache Consistency
+
+**Entity Change Tracking:**
+
+```typescript
+// Every entity modification tracked
+entity_changes (
+ entityName: 'notes',
+ entityId: 'note123',
+ hash: 'abc...',
+ changeId: 'change456',
+ utcDateChanged: '2025-11-02...'
+)
+```
+
+**Sync Protocol:**
+
+1. Client requests changes since last sync
+2. Server returns entity\_changes records
+3. Client applies changes to Froca
+4. Client sends local changes to server
+5. Server updates Becca and database
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Deleted notes.md b/docs/Developer Guide/Developer Guide/Concepts/Deleted notes.md
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Demo document.md b/docs/Developer Guide/Developer Guide/Concepts/Demo document.md
new file mode 100644
index 0000000000..90429bdb18
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Demo document.md
@@ -0,0 +1,22 @@
+# Demo document
+The demo document is an exported .zip that resides in `apps/server/src/assets/db/demo.zip`.
+
+During on-boarding, if the user selects that they are a new user then the `demo.zip` is imported into the root note.
+
+## Modifying the document
+
+1. In the Git root, run `pnpm edit-docs:edit-demo`.
+2. Wait for the desktop application to show up with the docs.
+3. Simply make the needed modifications.
+4. Wait for a few seconds for the change to be processed in the background.
+5. Commit the change in Git.
+
+## Testing the changes
+
+1. Run:
+
+ ```
+ rm -r data
+ pnpm server:start
+ ```
+2. And then do the on-boarding again.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Entities.md b/docs/Developer Guide/Developer Guide/Concepts/Entities.md
new file mode 100644
index 0000000000..faac90af75
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Entities.md
@@ -0,0 +1,109 @@
+# Entities
+### Entity System
+
+Trilium's data model is based on five core entities:
+
+```
+graph TD
+ Note[Note<br/>BNote]
+ Branch[Branch<br/>BBranch]
+ Attribute[Attribute<br/>BAttribute]
+ Revision[Revision<br/>BRevision]
+ Attachment[Attachment<br/>BAttachment]
+
+ Note -->|linked by| Branch
+ Note -.->|metadata| Attribute
+ Branch -->|creates| Revision
+ Note -->|has| Attachment
+
+ style Note fill:#e1f5ff
+ style Branch fill:#fff4e1
+ style Attribute fill:#ffe1f5
+ style Revision fill:#f5ffe1
+ style Attachment fill:#ffe1e1
+```
+
+#### Entity Definitions
+
+**1\. BNote** (`apps/server/src/becca/entities/bnote.ts`)
+
+* Represents a note with title, content, and metadata
+* Type can be: text, code, file, image, canvas, mermaid, etc.
+* Contains content via blob reference
+* Can be protected (encrypted)
+* Has creation and modification timestamps
+
+**2\. BBranch** (`apps/server/src/becca/entities/bbranch.ts`)
+
+* Represents parent-child relationship between notes
+* Enables note cloning (multiple parents)
+* Contains positioning information
+* Has optional prefix for customization
+* Tracks expansion state in tree
+
+**3\. BAttribute** (`apps/server/src/becca/entities/battribute.ts`)
+
+* Key-value metadata attached to notes
+* Two types: labels (tags) and relations (links)
+* Can be inheritable to child notes
+* Used for search, organization, and scripting
+* Supports promoted attributes (displayed prominently)
+
+**4\. BRevision** (`apps/server/src/becca/entities/brevision.ts`)
+
+* Stores historical versions of note content
+* Automatic versioning on edits
+* Retains title, type, and content
+* Enables note history browsing and restoration
+
+**5\. BAttachment** (`apps/server/src/becca/entities/battachment.ts`)
+
+* File attachments linked to notes
+* Has owner (note), role, and mime type
+* Content stored in blobs
+* Can be protected (encrypted)
+
+**6\. BBlob** (`apps/server/src/becca/entities/bblob.ts`)
+
+* Binary large object storage
+* Stores actual note content and attachments
+* Referenced by notes, revisions, and attachments
+* Supports encryption for protected content
+
+### Widget-Based UI
+
+The frontend uses a **widget system** for modular, reusable UI components.
+
+Located at: `apps/client/src/widgets/`
+
+```typescript
+// Widget Hierarchy
+BasicWidget
+├── NoteContextAwareWidget (responds to note changes)
+│ ├── RightPanelWidget (displayed in right sidebar)
+│ └── Type-specific widgets
+├── Container widgets (tabs, ribbons, etc.)
+└── Specialized widgets (search, calendar, etc.)
+```
+
+**Base Classes:**
+
+1. **BasicWidget** (`basic_widget.ts`)
+ * Base class for all UI components
+ * Lifecycle: construction → rendering → events → destruction
+ * Handles DOM manipulation
+ * Event subscription management
+ * Child widget management
+2. **NoteContextAwareWidget** (`note_context_aware_widget.ts`)
+ * Extends BasicWidget
+ * Automatically updates when active note changes
+ * Accesses current note context
+ * Used for note-dependent UI
+3. **RightPanelWidget**
+ * Widgets displayed in right sidebar
+ * Collapsible sections
+ * Context-specific tools and information
+
+**Type-Specific Widgets:**
+
+Each note type has a dedicated widget, which are located in `apps/client/src/widgets/type_widgets`.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Hidden notes.md b/docs/Developer Guide/Developer Guide/Concepts/Hidden notes.md
new file mode 100644
index 0000000000..6b9f718eb6
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Hidden notes.md
@@ -0,0 +1,6 @@
+# Hidden notes
+## Disallow adding child notes
+
+1. To enforce at server level go to `services/notes.ts` and look for the `getAndValidateParent` method.  Look for the `params.ignoreForbiddenParents` if statement and add it there.
+2. To hide the plus button in the note tree, go to `widgets/note_tree` in the client and look for `enhanceTitle`. Look for the if statement which starts with `!["search", "launcher"].includes(note.type)`.
+3. To disable it from the contextual menu, go to `tree_context_menu` and look for the `getMenuItems` method. There look for the `insertNoteAfter` and `insertChildNote` actions and look at their `enabled` conditions. If adding a big note type with lots of child notes, see the pattern of optinos & help (rename and augment the `notOptionsOrHelp` variable.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Icons.md b/docs/Developer Guide/Developer Guide/Concepts/Icons.md
new file mode 100644
index 0000000000..07d075a13c
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Icons.md
@@ -0,0 +1,74 @@
+# Icons
+Icons are stored in `images` and in `images/app-icons`.
+
+## Favicon
+
+The favicon is served dynamically via `serve-favicon`, using the icon in `images/app-icons/win/icon.ico`.
+
+## Declarative generation of icons
+
+All the icons are now built off of the SVGs in the `images` directory using the `bin/create-icons.sh` script.
+
+## Main images
+
+These are stored in `images`:
+
+| Name | Resolution | Description |
+| --- | --- | --- |
+| `icon-black.svg` | 53x40 | Used by the global menu button when not hovered. |
+| `icon-color.svg` | 53x40 | Used by the global menu when hovered. |
+| `icon-grey.svg` | 53x40 | Used by the dark theme, in place of `icon-black.svg`. |
+
+## App icons
+
+<table>
+ <thead>
+ <tr>
+ <th>Name</th>
+ <th>Resolution</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code>ios/apple-touch-icon.png</code></td>
+ <td>180x180</td>
+ <td>Used as <code>apple-touch-icon</code>, but only in <code>login.ejs</code> and <code>set_password.ejs</code> for some reason.</td>
+ </tr>
+ <tr>
+ <td><code>mac/icon.icns</code></td>
+ <td>512x512</td>
+ <td>Provided as <code>--icon</code> to <code>electron-packager</code> for <code>mac-arm64</code> and <code>mac-x64</code> <a href="../Building/Build%20deliveries%20locally.md">builds</a>.</td>
+ </tr>
+ <tr>
+ <td><code>png/128x128.png</code></td>
+ <td>128x128</td>
+ <td>Used in <code>linux-x64</code> <a href="../Building/Build%20deliveries%20locally.md">build</a>, to provide an <code>icon.png</code>.</td>
+ </tr>
+ <tr>
+ <td><code>png/256x256-dev.png</code></td>
+ <td>256x256</td>
+ <td>Used by the Electron window icon, if in dev mode.</td>
+ </tr>
+ <tr>
+ <td><code>png/256x256.png</code></td>
+ <td>Used by the Electron window icon, if not in dev mode.</td>
+ </tr>
+ <tr>
+ <td><code>win/icon.ico</code></td>
+ <td><ul><li>ICO 16x16</li><li>ICO 32x32</li><li>ICO 48x48</li><li>ICO 64x64</li><li>ICO 128x128</li><li>PNG 256x256</li></ul></td>
+ <td><ul><li>Used by the <code>win-x64</code> <a href="../Building/Build%20deliveries%20locally.md">build</a>.</li><li>Used by Squirrel Windows installer for: setup icon, app icon, control panel icon</li><li>Used as the favicon.</li></ul></td>
+ </tr>
+ <tr>
+ <td><code>win/setup-banner.gif</code></td>
+ <td>640x480</td>
+ <td>Used by the Squirrel Windows installer during the installation process. Has only one frame.</td>
+ </tr>
+ </tbody>
+</table>
+
+## Additional locations where the branding is used
+
+* In the client, more specifically in `src/public/app/widgets/buttons/global_menu.js`, where the SVG content of the icon is directly embedded to allow styling via CSS.
+* In the <a class="reference-link" href="Demo%20document.md">Demo document</a>, as an attachment.
+* In the <a class="reference-link" href="../Dependencies/CKEditor.md">CKEditor</a> build, look for `packages/ckeditor5-build-balloon-block/src/icons/trilium.svg`. Make sure not to have any `fill` overrides in the SVG as the wrong color will be used.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations.md b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations.md
new file mode 100644
index 0000000000..f420ff7ada
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations.md
@@ -0,0 +1,90 @@
+# Internationalisation / Translations
+During the initial development of Trilium Notes, internationalisation was not considered as it was meant to be an English-only product.
+
+As the application and the user base grows, it makes sense to be able to reach out as many people as possible by providing translations in their native language.
+
+The library used is [i18next](https://www.i18next.com/).
+
+## Where are the translations?
+
+The translations are formatted as JSON files and they are located in `src/public/translations`. For every supported locale, there is a subdirectory in which there is a `translation.json` file (e.g. `src/public/translations/en/translation.json`).
+
+### Message keys
+
+One important aspect is the fact that we are using a key-based approach. This means that each message is identified by an ID rather than a natural-language message (such as the default approach in gettext).
+
+The key-based approach allows a hierarchical structure. For example, a key of `about.title` would be added in `translation.json` as follows:
+
+```json
+{
+ "about": {
+ "title": "About Trilium Notes"
+ }
+}
+```
+
+Follow the <a class="reference-link" href="Internationalisation%20%20Translations/Guidelines.md">Guidelines</a> when creating a new message.
+
+### Adding a new locale
+
+See <a class="reference-link" href="Internationalisation%20%20Translations/Adding%20a%20new%20locale.md">Adding a new locale</a>.
+
+### Changing the language
+
+Since the internationalisation process is in its early stages, there is no user-facing way to switch the language.
+
+To change the language manually, edit `src/public/app/services/i18n.js` and look for the line containing `lng: "en"`. Replace `en` with the desired language code (from the ones available in `src/public/translations`).
+
+## Client-side translations
+
+### Component-level translations
+
+Most of the client translations are present in the various widgets and layouts.
+
+Translation support has to be added manually for every file.
+
+The first step is to add the translation import with a relative import. For example, if we are in the `src/public/app/widgets/dialogs` directory, the import would look as follows:
+
+```javascript
+import { t } from "../../services/i18n.js";
+```
+
+Afterwards, simply replace the hard-coded message with:
+
+```javascript
+${t("msgid")}
+```
+
+where `msgid` is the key of the message being translated.
+
+### Variables
+
+In the translation, enclose the variables with `{{` and `}}`:
+
+```
+{
+ "key": "{{what}} is {{how}}"
+}
+```
+
+Then pass the arguments when reading the translation:
+
+```
+t('key', { what: 'i18next', how: 'great' })
+```
+
+### Template-level translations
+
+Templates are `.ejs` files present in `src/views`, these are used to prepare the root layout for desktop, mobile applications as well as setup (onboarding) and the shared notes view.
+
+Due to using a different approach, it is not possible yet to translate those files.
+
+## Server-side translations
+
+Currently the server-side messages are not translatable. They will be added as a separate step.
+
+## Locale/language selection
+
+The language is stored as an option which is synchronized across all devices and the user is able to adjust it via Options → Appearance → Locale.
+
+The options shown to the user are currently hard-coded in `src/routes/api/options.ts`, where there is a `getSupportedLocales()` function. The `id` field must match the corresponding directory in `src/public/translations` and the `name` must be the localized name of the language (so the name must be in that language, not in English).
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Adding a new locale.md b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Adding a new locale.md
new file mode 100644
index 0000000000..c895702083
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Adding a new locale.md
@@ -0,0 +1,27 @@
+# Adding a new locale
+Once the Weblate translations for a single language have reached ~50% in coverage, it's time to add it to the application.
+
+To do so:
+
+1. In `packages/commons` look for `i18n.ts` and add a new entry to `UNSORTED_LOCALES` for the language.
+2. In `packages/commons` look for `dayjs.ts` and add a mapping for the new language in `DAYJS_LOADER`. Sort the entire list.
+3. In `apps/client`, look for `collections/calendar/index.tsx` and modify `LOCALE_MAPPINGS` to add support to the new language.
+4. In `apps/client`, look for `widgets/type_widgets/canvas/i18n.ts` and modify `LANGUAGE_MAPPINGS`. A unit test ensures that the language is actually loadable.
+5. In `packages/ckeditor5`, look for `i18n.ts` and modify `LOCALE_MAPPINGS`. The import validation should already check if the new value is supported by CKEditor, and there's also a test to ensure it. The test in `i18n.spec.ts` pins every locale by hand rather than iterating them, so add the new one there as well.
+6. In `apps/client`, look for `widgets/type_widgets/spreadsheet/locales.ts` and modify `UNIVER_LOCALES`, either with a source (if Univer ships a bundle for the language) or with an explicit `null` to fall back to English. Every preset in `SPREADSHEET_PRESET_PACKAGES` must have a bundle for the locale, which `locales.spec.ts` checks.
+7. Locale mappings for PDF.js might need adjustment. To do so, in `packages/pdfjs-viewer/scripts/build.ts` there is `LOCALE_MAPPINGS`. No entry is needed when the locale's `electronLocale` already names a directory under `packages/pdfjs-viewer/viewer/locale`.
+
+Steps 1 to 6 are keyed by `DISPLAYABLE_LOCALE_IDS`, so `pnpm typecheck` reports each one still missing after step 1.
+
+## The website
+
+The website tracks its own Weblate component and its own list, so a locale added to the application above is not offered on [triliumnotes.org](https://triliumnotes.org) until it is added there too.
+
+1. In `apps/website`, look for `locales.ts` and add an entry to `LOCALES`, using the language's own name and setting `rtl` where it applies. The id must match the folder under `apps/website/src/translations`, which Weblate creates.
+2. A locale carrying a region, such as `pt-BR`, is resolved by `mapLocale()` in `i18n.ts` by matching `LOCALES`, so it needs no further mapping. Chinese is the exception: it is selected by script, which browsers report only through the region, and `mapLocale()` special-cases it.
+
+## The coverage gate
+
+`scripts/translation/check-translation-coverage.ts` fails CI once Weblate reports a language above 50% that is missing from either list. It runs on the `weblate:*` branches, so the pull request that brings the translations in is where it fires.
+
+The gate only catches a language that is translated but not offered. It does not notice one that is offered and has since fallen behind, and it does not check that the locale renders — only that the id is listed.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Guidelines.md b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Guidelines.md
new file mode 100644
index 0000000000..cadf4e61a7
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Guidelines.md
@@ -0,0 +1,9 @@
+# Guidelines
+* Use hierarchy whenever appropriate, try to group the messages by:
+ * Modals (e.g. `about.foo`, `jump_to_note.foo`)
+* Don't duplicate messages that are very widely used.
+ * One such example is `aria-label="Close"` which should go to a single message such as `modal.close` instead of being duplicated in every modal.
+* On the other hand, don't overly generalise messages. A `close` message that is used whenever the “Close” word is encountered is not a good approach since it can potentially cause issues due to lack of context.
+* Use [variable interpolation](https://www.i18next.com/translation-function/interpolation) whenever appropriate.
+ * If you see multiple messages joined together only to apply add a variable such as a user-inputted value, try to join those messages together into a single message containing a variable.
+ * So instead of `“Number of updates: “ + numUpdates + “.”` use `$(t("number_updates", { numUpdates }))` where the message translation would appear as `Number of updates: {{numUpdates}}.`
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Server translations.md b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Server translations.md
new file mode 100644
index 0000000000..4b8de1e46d
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/Server translations.md
@@ -0,0 +1,19 @@
+# Server translations
+* Server-side translations are managed by the same library as the client, i18next.
+* The translation files reside in the `/translations` directory, following the same convention as the client (`translations/{{lng}}/{{ns}}.json`), where the namespace is `server.json`. So for the Spanish translations we have `translations/es/server.json`.
+* Loading of translations is managed by [i18next-fs-backend](https://github.com/i18next/i18next-fs-backend) which loads the translations directly from the file system (unlike HTTP requests like the client), at the path mentioned previously (relative to `package.json`).
+
+## How to translate a string
+
+Unlike the client which uses a dedicated client service, the i18next library on the server is used directly, as such:
+
+```javascript
+import { t } from "i18next";
+
+const translatedString = t("message.id");
+```
+
+## What should be translated
+
+* Avoid translating server-side logs, as those are supposed to be for debugging and as such there is no benefit in translating them.
+* Translate any user-facing message that comes from the server, such as error messages shown in the Electron application, or information such as keyboard shortcuts, note titles, etc.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/i18n-ally.md b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/i18n-ally.md
new file mode 100644
index 0000000000..3c8c447626
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Internationalisation Translations/i18n-ally.md
@@ -0,0 +1,15 @@
+# i18n-ally
+[`i18n-ally`](https://github.com/lokalise/i18n-ally) is a VS Code extension that aids in internationalization.
+
+It is currently integrated in the project and offers features such as:
+
+* Highlight, autocomplete translations.
+* Display translations inline.
+* Extract messages into translation.
+
+### Extracting messages into translation
+
+1. Open any .js file and select an untranslated string inside a template (`TPL`).
+2. Press Ctrl+P and look for “i18n Ally: Extract text into i18n messages”
+3. Select the first template.
+4. Select the path of translation, taking into consideration the  <a class="reference-link" href="Guidelines.md">Guidelines</a> (e.g. `jump_to_note.search-for-note-by-its-name`).
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Launchers.md b/docs/Developer Guide/Developer Guide/Concepts/Launchers.md
new file mode 100644
index 0000000000..aac16ae912
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Launchers.md
@@ -0,0 +1,13 @@
+# Launchers
+Launchers are items that are displayed in the launcher bar (left side of the screen). They are of two different types:
+
+* Visible launchers: are displayed by default to the user, can be moved to the available launchers section to hide them.
+* Available launchers: can be manually added by the user from settings into the list of visible launchers.
+
+## Adding a new launcher
+
+Regardless of the type, new launchers are added at server level, inside `hidden_subtree.ts` file.
+
+* To add a new available launcher, look for `_lbAvailableLaunchers` and add a new item to its `children`.
+* Similarly, to add a visible launcher, look for `_lbVisibleLaunchers`.
+ * If you add a visible launcher, it will be available for both new and old users, since the application will identify that there is a new launcher to be added regardless of the user preference.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Revisions.md b/docs/Developer Guide/Developer Guide/Concepts/Note Revisions.md
new file mode 100644
index 0000000000..7624b1d78e
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Revisions.md
@@ -0,0 +1,2 @@
+# Note Revisions
+The revision API on the server side is managed by `apps/server/src/routes/api/revisions.ts`
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Copy image reference to the clipboard.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Copy image reference to the clipboard.md
new file mode 100644
index 0000000000..bff7c9caf7
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Copy image reference to the clipboard.md
@@ -0,0 +1,6 @@
+# Copy image reference to the clipboard
+This function is handled by `src/public/app/widgets/floating_buttons/copy_image_reference_button.js` and it supports multiple note types out of the box.
+
+To enable the display of the button, simply modify `isEnabled` to add support for the new note type.
+
+No other modifications should be necessary.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Export diagram as SVG.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Export diagram as SVG.md
new file mode 100644
index 0000000000..9ee27ec994
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Export diagram as SVG.md
@@ -0,0 +1,33 @@
+# Export diagram as SVG
+This mechanism is handled by `src/public/app/widgets/floating_buttons/svg_export_button.js`.
+
+## Step 1. Enable the button
+
+Modify the  `isEnabled` method in `svg_export_button.js` to add support for the new note type.
+
+## Step 2. Add support for exporting the image
+
+The SVG export needs to be handled inside the note type implementation. 
+
+The first goal is to create a method to handle the <a class="reference-link" href="SVG%20rendering.md">SVG rendering</a>. Make sure to deduplicate the code if the SVG rendering is already handled.
+
+```
+async renderSvg() {
+ return await this.mind.exportSvg().text();
+}
+```
+
+Then create an event handler to manage the SVG export:
+
+```
+async exportSvgEvent({ntxId}) {
+ if (!this.isNoteContext(ntxId) || this.note.type !== "mindMap") {
+ return;
+ }
+
+ const svg = await this.renderSvg();
+ utils.downloadSvg(this.note.title, svg);
+}
+```
+
+Make sure to modify the note type assertion at the beginning of the method. This is very important, otherwise there can be errors when navigating through multiple note types that support this button.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/First steps.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/First steps.md
new file mode 100644
index 0000000000..fa860fe591
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/First steps.md
@@ -0,0 +1,54 @@
+# First steps
+> **Note**: When adding or updating step titles/order, don't forget to update the corresponding list in <a class="reference-link" href="Note%20type%20checklist.md">Note type checklist</a>.
+
+## Step 1. Register the note type in the server
+
+Go to `src\services\note_types.ts` and add a new entry in `noteTypes` with the type ID and the default MIME type.
+
+## Step 2. Register the note type in the client context menu
+
+The client lists the available note types in `src\public\app\services\note_types.ts`.
+
+## Step 3. Create a type widget
+
+Go to `src\public\app\widgets\type_widgets` directory and create a new file corresponding to the new note type.
+
+A blank implementation looks something like this:
+
+## Step 4. Register the type widget
+
+The type widget needs to go in `src\public\app\widgets\note_detail.ts`where there is a `typeWidgetClasses` map, mapping the type IDs with the corresponding type widget that was created at the previous step.
+
+## Step 5. Add the default icon mapping
+
+To set a default icon for this note type, go to `src\public\app\entities\fnote.ts` and add it to `NOTE_TYPE_ICONS`.
+
+## Step 6. Add to note type selector
+
+Go to `src/public/app/widgets/note_type.ts` and register the new note type in `NOTE_TYPES`.
+
+## Step 7. Add the note to server allowed note types
+
+This is required in order to make imports possible, otherwise they will be imported as plain text.
+
+Go to `src/becca/entities/rows.ts` and add the new note type to `ALLOWED_NOTE_TYPES`.
+
+## Additional changes
+
+* If the widget requires a full height, it must be configured in `src\public\app\widgets\note_detail.ts` (look for `checkFullHeight`) then a `height: 100%` style can be applied to the containers to make them fit.
+* To make the note always full width (ignoring the user's content width), go to `note_wrapper` and look for the `refresh` method. There is a `toggleClass` for `full-content-width` based on the note type.
+* To allow the note source to be viewed, go to `src/public/app/widgets/buttons/note_actions.ts` and look for `this.toggleDisabled(this.$showSourceButton` in `refreshVisibility`.
+
+## Final steps
+
+* Update the <a class="reference-link" href="../../Demo%20document.md">Demo document</a> to showcase the new note type.
+
+## Troubleshooting
+
+### Content does not appear, however it appears as hidden in the DOM
+
+Type widgets do a check whenever a note is selected to determine whether the widget needs to be displayed or not, based on the note type. Make sure `getType()` is well implemented in the newly added type widget (take great care that the value is returned but also that the note type ID matches the ones registered in the previous steps):
+
+```
+static getType() { return "foo"; }
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/First steps/mind_map.js b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/First steps/mind_map.js
new file mode 100644
index 0000000000..9e33e54d9b
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/First steps/mind_map.js
@@ -0,0 +1,27 @@
+import TypeWidget from "./type_widget.js";
+
+const TPL = `
+<div class="note-detail-mind-map note-detail-printable">
+</div>
+`;
+
+export default class MindMapWidget extends TypeWidget {
+ static getType() { return "mindMap"; }
+
+ doRender() {
+ this.$widget = $(TPL);
+
+ super.doRender();
+ }
+
+ async doRefresh(note) {
+ this.$widget.html("<p>Hello</p>");
+ this.$widget.show();
+ }
+
+ async entitiesReloadedEvent({loadResults}) {
+ if (loadResults.isNoteReloaded(this.noteId)) {
+ this.refresh();
+ }
+ }
+}
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Loading data.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Loading data.md
new file mode 100644
index 0000000000..6710454379
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Loading data.md
@@ -0,0 +1,9 @@
+# Loading data
+Data loading can be done in `doRefresh()` since it gets a reference to the note:
+
+```
+const blob = await note.getBlob();
+const content = blob.getJsonContent();
+```
+
+Note that `doRefresh` can sometimes be called by <a class="reference-link" href="Saving%20data%20via%20spaced%20update.md">Saving data via spaced update</a> when the user makes a changes, this has to be accounted for.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Note type checklist.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Note type checklist.md
new file mode 100644
index 0000000000..e872359144
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Note type checklist.md
@@ -0,0 +1,49 @@
+# Note type checklist
+The goal of this checklist is to ensure a good implementation or re-test of a note type.
+
+## Implementation checklist
+
+The note type widget must be created according to <a class="reference-link" href="First%20steps.md">First steps</a>:
+
+* Register the note type in the server
+* Register the note type in the client context menu
+* Create a type widget
+* Register the type widget
+* Add the default icon mapping
+* Add to note type selector
+* Add the note to server allowed note types
+* Update demo document to include this new note type
+* Increase server sync version (otherwise an older instance turns notes of the new type into file notes on sync).
+
+## Validation checklist
+
+### Ensure that the note renders properly
+
+* When refreshing to a note that is already displayed
+* When going to another note and then going back
+* When creating a new note of the given type
+* Have two tabs of the same note type and switch between them
+
+### Ensure data persistence
+
+* Save data when modifying changes via spaced update
+
+### Ensure data retrieval
+
+* Go on a note of this type and refresh the page
+* Create a new note of this type while on another note of this type and ensure that the content is set properly.
+
+### Set up a note preview
+
+For an implementation reference, see <a class="reference-link" href="SVG%20rendering.md">SVG rendering</a>.
+
+* Note preview rendering (go to parent and see note list).
+* Include note
+* Share
+* Note revisions
+
+### Import/export
+
+* Export & Import, making sure no data is lost in the process.
+* Remove the data folder entirely to test that the demo document is well imported on first setup.
+ * Ensure that the preview also works (check the preview in the root note).
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/SVG rendering.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/SVG rendering.md
new file mode 100644
index 0000000000..847594de63
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/SVG rendering.md
@@ -0,0 +1,72 @@
+# SVG rendering
+For diagrams and similar note types, it makes sense to cache an SVG rendering of the content so that it can be used for:
+
+* Content preview in note lists (when viewing the list of notes from the parent note).
+* Note inclusion
+* Share
+
+## Step 1. Save the SVG content as an attachment
+
+The first step is to obtain the SVG from the custom widget used. For example, for Mind Elixir there is an `exportSvg` method.
+
+If the returned value is a `Blob`, then the underlying text can be obtained via `await blob.text()`.
+
+To save the SVG as an attachment alongside the content, simply modify `getData()`:
+
+```
+async getData() {
+ const mind = this.mind;
+ if (!mind) {
+ return;
+ }
+
+ const svgContent = await this.mind.exportSvg().text();
+ return {
+ content: mind.getDataString(),
+ attachments: [
+ {
+ role: "image",
+ title: "mindmap-export.svg",
+ mime: "image/svg+xml",
+ content: svgContent,
+ position: 0
+ }
+ ]
+ };
+}
+```
+
+You can test this step by making a change to the note and then using the “Note attachments” option from the note menu.
+
+## Step 2. Adapting the server to serve SVG attachment
+
+The `src/routes/api/image.ts` route is in charge for serving the image previews of image notes, but also of custom note types such as canvases.
+
+Alter the `returnImageInt` method as follows:
+
+1. Add the image type to the guard condition which returns 400 for unsupported note types.
+2. Add an `if` statement to render the attachment using the correct name:
+
+```
+if (image.type === "mindMap") {
+ renderSvgAttachment(image, res, 'mindmap-export.svg');
+}
+```
+
+## Step 3. Serve the SVG attachment for note preview
+
+The client also needs tweaking to allow it to render SVG attachments by calling the previously modified server route.
+
+The `src/public/app/services/content_renderer.js` file is in charge of handling the previews. To render using the image route, modify `getRenderedContent` to add the new note type to the `if` which calls `renderImage`.
+
+## Step 4. Serve SVG for share
+
+By default, `Note type cannot be displayed` will be displayed when trying to access the given note via a share.
+
+To serve the SVG, open `src/share/content_renderer.ts` and look for `getContent`. Then add to the `if` containing `renderImage` the new note type.
+
+This is not enough, as attempting to access the shared note will result in a broken image that fails with `Requested note is not a shareable image`. To solve this one, go to `src/share/routes.ts` and add a `renderImageAttachment` statement to `router.get('/share/api/images/[…])`.
+
+## Step 5. Serve SVG for revisions
+
+In the revisions list, to display the SVG, go to `src/public/app/widgets/dialogs/revisions.js` and look for the `renderContent` method. Simply add the note type to one of the already existing `if`s, such as the one for `canvas` and `mindMap` or `mermaid` (if the text content of the diagram should also be displayed).
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Saving data via spaced update.md b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Saving data via spaced update.md
new file mode 100644
index 0000000000..06911c8315
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Note Types/Adding a new note type/Saving data via spaced update.md
@@ -0,0 +1,27 @@
+# Saving data via spaced update
+The data persistence is achieved via the spaced update mechanism which is already present and needs to be integrated within the newly created type widgets.
+
+First, the class must implement `getData`, in order to retrieve the data from the custom widget in a serialized form. As an example from the mind map implementation:
+
+```
+async getData() {
+ const mind = this.mind;
+ if (!mind) {
+ return;
+ }
+
+ return {
+ content: mind.getDataString()
+ };
+}
+```
+
+Here the content is a string containing a JSON. It is also possible to provide attachments here as well, such as <a class="reference-link" href="SVG%20rendering.md">SVG rendering</a> to provide a preview of the content.
+
+Then to trigger an update, register a listener within the custom widget that calls the spaced update, for example:
+
+```
+mind.bus.addListener("operation", (operation) => {
+ this.spacedUpdate.scheduleUpdate();
+});
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Options.md b/docs/Developer Guide/Developer Guide/Concepts/Options.md
new file mode 100644
index 0000000000..ce0d348f53
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Options.md
@@ -0,0 +1,43 @@
+# Options
+## Read an option
+
+Add the import to the service (make sure the relative path is correct):
+
+```javascript
+import options from "../../services/options.js";
+```
+
+Them simply read the option:
+
+```javascript
+this.firstDayOfWeek = options.getInt("firstDayOfWeek");
+```
+
+## Adding new options
+
+### Checkbox option
+
+Refer to this example in `backup.tsx`:
+
+```javascript
+export function AutomaticBackup() {
+ const [ dailyBackupEnabled, setDailyBackupEnabled ] = useTriliumOptionBool("dailyBackupEnabled");
+
+ return (
+ <OptionsSection title={t("backup.automatic_backup")}>
+ <FormMultiGroup label={t("backup.automatic_backup_description")}>
+ <FormCheckbox
+ name="daily-backup-enabled"
+ label={t("backup.enable_daily_backup")}
+ currentValue={dailyBackupEnabled} onChange={setDailyBackupEnabled}
+ />
+ </FormMultiGroup>
+
+ <FormText>{t("backup.backup_recommendation")}</FormText>
+ </OptionsSection>
+ )
+}
+```
+
+> [!TIP]
+> To trigger a UI refresh (e.g. `utils#reloadFrontendApp`), simply pass a `true` as the second argument to `useTriliumOption` methods.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Options/Creating a new option.md b/docs/Developer Guide/Developer Guide/Concepts/Options/Creating a new option.md
new file mode 100644
index 0000000000..95c80f84b2
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Options/Creating a new option.md
@@ -0,0 +1,5 @@
+# Creating a new option
+1. Go to `options_interface.ts` and add the option to `OptionDefinitions`, specifying its intended data type (boolean, string, number). Note that in the end the option will still be stored as a string, but this aids in type safety across the application.
+2. To add a new option with a set default, go to `options_init.ts` in the server and add a new entry in the `defaultOptions`.
+3. **Make the option adjustable by the client**
+ By default options are not adjustable or visible to the client. To do so, modify `routes/api/options.ts` to add the newly added option to `ALLOWED_OPTIONS`.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Printing and exporting to PDF.md b/docs/Developer Guide/Developer Guide/Concepts/Printing and exporting to PDF.md
new file mode 100644
index 0000000000..ad057206bb
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Printing and exporting to PDF.md
@@ -0,0 +1,18 @@
+# Printing and exporting to PDF
+Note printing is handled by `note_detail.js`, in the `printActiveNoteEvent` method. Exporting to PDF works similarly.
+
+## How it works
+
+Both printing and exporting as PDF use the same mechanism: a note is rendered individually in a separate webpage that is then sent to the browser or the Electron application either for printing or exporting as PDF.
+
+The webpage that renders a single note can actually be accessed in a web browser. For example `http://localhost:8080/#root/WWRGzqHUfRln/RRZsE9Al8AIZ?ntxId=0o4fzk` becomes `http://localhost:8080/?print#root/WWRGzqHUfRln/RRZsE9Al8AIZ`.
+
+Accessing the print note in a web browser allows for easy debugging to understand why a particular note doesn't render well. The mechanism for rendering is similar to the one used in <a class="reference-link" href="#root/0ESUbbAxVnoK">Note List</a>.
+
+## Syntax highlighting
+
+Syntax highlighting for code blocks is supported as well:
+
+* It works by injecting a Highlight.js stylesheet into the print.
+* The theme used is hard-coded (the _Visual Studio Light theme_, at the time of writing) in order not to have a dark background in print.
+* <a class="reference-link" href="Syntax%20highlighting.md">Syntax highlighting</a> is handled by the content renderer.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Protected entities.md b/docs/Developer Guide/Developer Guide/Concepts/Protected entities.md
new file mode 100644
index 0000000000..31d5250c0d
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Protected entities.md
@@ -0,0 +1,6 @@
+# Protected entities
+The following entities can be made protected, via their `isProtected` flag:
+
+* <a class="reference-link" href="../Architecture/Database/Database%20structure/attachments.md">attachments</a>
+* <a class="reference-link" href="../Architecture/Database/Database%20structure/notes.md">notes</a>
+* <a class="reference-link" href="../Architecture/Database/Database%20structure/revisions.md">revisions</a>
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Share.md b/docs/Developer Guide/Developer Guide/Concepts/Share.md
new file mode 100644
index 0000000000..701621077c
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Share.md
@@ -0,0 +1,61 @@
+# Share
+## Share theme
+
+The share theme represents the layout, styles and scripts behind the Share notes functionality. The current implementation is a heavy adaptation of [trilium.rocks](https://trilium.rocks/) which is a third-party share theme.
+
+* The theme resides in `packages/share-theme`.
+* The HTML is defined in `src/templates` using EJS templating.
+* The `src/scripts` and `src/styles` subdirectories house the rest of the theme.
+
+## Building the share theme
+
+* In `packages/share-theme`, run `pnpm build` to trigger a build. This will generate `dist` which will then be used by the server.
+* Alternatively, use `pnpm dev` to watch for changes.
+* `pnpm dist` is the same build, minified. It is what the app builds run, so a release ships the minified assets while local development keeps readable ones.
+
+Both scripts clear `dist` first, since esbuild writes into it without removing what an earlier build left there — a minified release build would otherwise be copied alongside the unminified files `pnpm install` produces. A `--module=` build (`build-scripts`, `build-styles`) builds one entry point and deliberately does not clear, so it leaves the other's output alone.
+
+## Where the code lives
+
+The share subsystem is in `packages/trilium-core/src/share`, so that every runtime that carries core can serve it:
+
+* `shaca` is the read-only cache of the `_share` subtree, loaded from raw rows.
+* `content_renderer.ts` renders one of its notes into a page.
+* `handlers.ts` holds the routes as transport-neutral handlers: each takes a `ShareRequest` and returns a `ShareReply` (status, headers, body or redirect), touching no Express type. `route_paths.ts` lists the URL patterns on their own, free of imports, so a router can register them without loading the renderer behind them.
+
+What differs per platform goes through the `ShareProvider` (`share_provider.ts`): where the rows come from, where the EJS templates come from, and whether a note is allowed to supply its own template.
+
+| | Server / desktop | Standalone / mobile |
+| --- | --- | --- |
+| Rows | a second, read-only `better-sqlite3` connection (`apps/server/src/share/sql.ts`) | the one sqlite-wasm connection, shared with every other route |
+| Templates | read from disk | bundled into the build with `?raw` |
+| A note's own EJS template | allowed when backend scripting is enabled | never — this build has no backend scripting |
+
+## Integration with the server for the share functionality
+
+The server renders the templates using EJS templating from the share theme and hosts the assets.
+
+* In dev mode, the templates and assets are served directly from `packages/share-theme/dist`.
+ * Modifications to the assets (scripts or styles) will reflect without having to restart the server. However the share theme needs to be built first (see previous section).
+ * Changes to the template will require a restart of the server, since they are cached. Simply press Enter in the console with `pnpm server:start` to quickly trigger a restart.
+* In production mode, the share theme is automatically built by the server build script and copied to `dist/share-theme`.
+
+`apps/server/src/share/routes.ts` is the Express adapter over the core handlers, and `apps/server/src/share/share_provider.ts` registers the provider above.
+
+## Integration with the standalone (in-browser) build
+
+`apps/standalone` serves the same pages from the browser. A `/share/` request is claimed by the service worker, forwarded to the tab that owns the database, and answered by the worker's `BrowserRouter` (`apps/standalone/src/lightweight/browser_routes.ts`); `share_provider.ts` beside it supplies the rows and the bundled templates. Nothing outside the browser can reach these pages — there is no server listening — so this is for working on the share feature and for reading published notes locally, not for publishing.
+
+* The subsystem is loaded by a dynamic `import()` on the first `/share/` request, which keeps EJS, the share theme and the syntax highlighter (~950 KB together) out of the worker's startup bundle. That only holds while nothing in the eager graph imports `share/index.ts`, which is why it is not re-exported from the `@triliumnext/core` barrel.
+* `ejs` is aliased to its own browser build in `vite.config.mts`: the package's ESM entry imports `node:fs` and `node:path`, which it only needs when no `includer` is passed, and the renderer always passes one.
+* The share theme's assets are copied into the build at the paths `content_renderer.ts` writes into the page (`share/assets`, `assets/v<version>/images`), in place of the `express.static` routes the server registers.
+* The pages are rendered by the tab holding the database, so at least one app tab must be open for a `/share/` URL to resolve.
+
+## Exporting to static HTML files
+
+The static export lives in `packages/trilium-core/src/services/export/zip/share_theme.ts`, so both the server and the standalone build offer it. It works quite similar to the normal sharing functionality, but it uses `BNote` instead of `SNote` (and so on for other entity types), in order to work regardless of whether a note is shared or not.
+
+The same templates are used, except that the rendered pages are stored in the archive instead of served to web clients. The theme's built files and the built-in icon fonts reach the provider through `ShareThemeExportAssets`, which each platform fills in its zip export factory:
+
+* The server reads them from disk (`apps/server/src/services/export/zip/share_theme.ts`).
+* The standalone build fetches them from `share/assets`, where it already copies them for the share pages. The file names come from the `virtual:share-theme-assets` module, which `vite.config.mts` generates from `packages/share-theme/dist` for both the page and the worker bundle.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Synchronisation.md b/docs/Developer Guide/Developer Guide/Concepts/Synchronisation.md
new file mode 100644
index 0000000000..45a520cb68
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Synchronisation.md
@@ -0,0 +1,484 @@
+# Synchronisation
+Trilium implements a **bidirectional synchronization system** that allows users to sync their note databases across multiple devices (desktop clients and server instances). The sync protocol is designed to handle:
+
+* Concurrent modifications across devices
+* Simple conflict resolution (without “merge conflict” indication).
+* Partial sync (only changed entities)
+* Protected note synchronization
+* Efficient bandwidth usage
+
+## Sync Architecture
+
+```
+graph TB
+ Desktop1[Desktop 1<br/>Client]
+ Desktop2[Desktop 2<br/>Client]
+
+ subgraph SyncServer["Sync Server"]
+ SyncService[Sync Service<br/>- Entity Change Management<br/>- Conflict Resolution<br/>- Version Tracking]
+ SyncDB[(Database<br/>entity_changes)]
+ end
+
+ Desktop1 <-->|WebSocket/HTTP| SyncService
+ Desktop2 <-->|WebSocket/HTTP| SyncService
+ SyncService --> SyncDB
+```
+
+## Core Concepts
+
+### Entity Changes
+
+Every modification to any entity (note, branch, attribute, etc.) creates an **entity change** record:
+
+```
+entity_changes (
+ id, -- Auto-increment ID
+ entityName, -- 'notes', 'branches', 'attributes', etc.
+ entityId, -- ID of the changed entity
+ hash, -- Content hash for integrity
+ isErased, -- If entity was erased (deleted permanently)
+ changeId, -- Unique change identifier
+ componentId, -- Unique component/widget identifier
+ instanceId, -- Process instance identifier
+ isSynced, -- Whether synced to server
+ utcDateChanged -- When change occurred
+)
+```
+
+**Key Properties:**
+
+* **changeId**: Globally unique identifier (UUID) for the change
+* **componentId**: Unique identifier of the component/widget that generated to change (can be used to avoid refreshing the widget being edited).
+* **instanceId**: Unique per process (changes on restart)
+* **hash**: SHA-256 hash of entity data for integrity verification
+
+### Sync Versions
+
+Each Trilium installation tracks:
+
+* **Local sync version**: Highest change ID seen locally
+* **Server sync version**: Highest change ID on server
+* **Entity versions**: Last sync version for each entity type
+
+### Change Tracking
+
+**When an entity is modified:**
+
+```typescript
+// apps/server/src/services/entity_changes.ts
+function addEntityChange(entityName, entityId, entity) {
+ const hash = calculateHash(entity)
+ const changeId = generateUUID()
+
+ sql.insert('entity_changes', {
+ entityName,
+ entityId,
+ hash,
+ changeId,
+ componentId: config.componentId,
+ instanceId: config.instanceId,
+ isSynced: 0,
+ utcDateChanged: now()
+ })
+}
+```
+
+**Entity modification triggers:**
+
+* Note content update
+* Note metadata change
+* Branch creation/deletion/reorder
+* Attribute addition/removal
+* Options modification
+
+## Sync Protocol
+
+### Sync Handshake
+
+**Step 1: Client Initiates Sync**
+
+```typescript
+// Client sends current sync version
+POST /api/sync/check
+{
+ "sourceId": "client-component-id",
+ "maxChangeId": 12345
+}
+```
+
+**Step 2: Server Responds with Status**
+
+```typescript
+// Server checks for changes
+Response:
+{
+ "entityChanges": 567, // Changes on server
+ "maxChangeId": 12890, // Server's max change ID
+ "outstandingPushCount": 23 // Client changes not yet synced
+}
+```
+
+**Step 3: Decision**
+
+* If `entityChanges > 0`: Pull changes from server
+* If `outstandingPushCount > 0`: Push changes to server
+* Both can happen in sequence
+
+### Pull Sync (Server → Client)
+
+**Client Requests Changes:**
+
+```typescript
+POST /api/sync/pull
+{
+ "sourceId": "client-component-id",
+ "lastSyncedChangeId": 12345
+}
+```
+
+**Server Responds:**
+
+```typescript
+Response:
+{
+ "notes": [
+ { noteId: "abc", title: "New Note", ... }
+ ],
+ "branches": [...],
+ "attributes": [...],
+ "revisions": [...],
+ "attachments": [...],
+ "entityChanges": [
+ { entityName: "notes", entityId: "abc", changeId: "...", ... }
+ ],
+ "maxChangeId": 12890
+}
+```
+
+**Client Processing:**
+
+1. Apply entity changes to local database
+2. Update Froca cache
+3. Update local sync version
+4. Trigger UI refresh
+
+### Push Sync (Client → Server)
+
+**Client Sends Changes:**
+
+```typescript
+POST /api/sync/push
+{
+ "sourceId": "client-component-id",
+ "entities": [
+ {
+ "entity": {
+ "noteId": "xyz",
+ "title": "Modified Note",
+ ...
+ },
+ "entityChange": {
+ "changeId": "change-uuid",
+ "entityName": "notes",
+ ...
+ }
+ }
+ ]
+}
+```
+
+**Server Processing:**
+
+1. Validate changes
+2. Check for conflicts
+3. Apply changes to database
+4. Update Becca cache
+5. Mark as synced
+6. Broadcast to other connected clients via WebSocket
+
+**Conflict Detection:**
+
+```typescript
+// Check if entity was modified on server since client's last sync
+const serverEntity = becca.getNote(noteId)
+const serverLastModified = serverEntity.utcDateModified
+
+if (serverLastModified > clientSyncVersion) {
+ // CONFLICT!
+ resolveConflict(serverEntity, clientEntity)
+}
+```
+
+## Conflict Resolution
+
+### Conflict Types
+
+**1\. Content Conflict**
+
+* Both client and server modified same note content
+* **Resolution**: Last-write-wins based on `utcDateModified`
+
+**2\. Structure Conflict**
+
+* Branch moved/deleted on one side, modified on other
+* **Resolution**: Tombstone records, reconciliation
+
+**3\. Attribute Conflict**
+
+* Same attribute modified differently
+* **Resolution**: Last-write-wins
+
+### Conflict Resolution Strategy
+
+**Last-Write-Wins:**
+
+```typescript
+if (clientEntity.utcDateModified > serverEntity.utcDateModified) {
+ // Client wins, apply client changes
+ applyClientChange(clientEntity)
+} else {
+ // Server wins, reject client change
+ // Client will pull server version on next sync
+}
+```
+
+**Tombstone Records:**
+
+* Deleted entities leave tombstone in `entity_changes`
+* Prevents re-sync of deleted items
+* `isErased = 1` for permanent deletions
+
+### Protected Notes Sync
+
+**Challenge:** Encrypted content can't be synced without password
+
+**Solution:**
+
+1. **Encrypted sync**: Content synced in encrypted form
+2. **Hash verification**: Integrity checked without decryption
+3. **Lazy decryption**: Only decrypt when accessed
+
+## Sync States
+
+### Connection States
+
+* **Connected**: WebSocket connection active
+* **Disconnected**: No connection to sync server
+* **Syncing**: Actively transferring data
+* **Conflict**: Sync paused due to conflict
+
+### Entity Sync States
+
+Each entity can be in:
+
+* **Synced**: In sync with server
+* **Pending**: Local changes not yet pushed
+* **Conflict**: Conflicting changes detected
+
+### UI Indicators
+
+```typescript
+// apps/client/src/widgets/sync_status.ts
+class SyncStatusWidget {
+ showSyncStatus() {
+ if (isConnected && allSynced) {
+ showIcon('synced')
+ } else if (isSyncing) {
+ showIcon('syncing-spinner')
+ } else {
+ showIcon('not-synced')
+ }
+ }
+}
+```
+
+## Performance Optimizations
+
+### Incremental Sync
+
+Only entities changed since last sync are transferred:
+
+```
+SELECT * FROM entity_changes
+WHERE id > :lastSyncedChangeId
+ORDER BY id ASC
+LIMIT 1000
+```
+
+### Batch Processing
+
+Changes sent in batches to reduce round trips:
+
+```typescript
+const BATCH_SIZE = 1000
+const changes = getUnsyncedChanges(BATCH_SIZE)
+await syncBatch(changes)
+```
+
+### Hash-Based Change Detection
+
+```typescript
+// Only sync if hash differs
+const localHash = calculateHash(localEntity)
+const serverHash = getServerHash(entityId)
+
+if (localHash !== serverHash) {
+ syncEntity(localEntity)
+}
+```
+
+### Compression
+
+Large payloads compressed before transmission:
+
+```typescript
+// Server sends compressed response
+res.setHeader('Content-Encoding', 'gzip')
+res.send(gzip(syncData))
+```
+
+## Error Handling
+
+### Network Errors
+
+Reported to the user and the sync will be retried after the interval passes.
+
+### Sync Integrity Checks
+
+**Hash Verification:**
+
+```typescript
+// Verify entity hash matches
+const calculatedHash = calculateHash(entity)
+const receivedHash = entityChange.hash
+
+if (calculatedHash !== receivedHash) {
+ throw new Error('Hash mismatch - data corruption detected')
+}
+```
+
+**Consistency Checks:**
+
+* Orphaned branches detection
+* Missing parent notes
+* Invalid entity references
+* Circular dependencies
+
+## Sync Server Configuration
+
+### Server Setup
+
+**Required Options:**
+
+```javascript
+{
+ "syncServerHost": "https://sync.example.com",
+ "syncServerTimeout": 60000,
+ "syncProxy": "" // Optional HTTP proxy
+}
+```
+
+**Authentication:**
+
+* Username/password or
+* Sync token (generated on server)
+
+## Sync API Endpoints
+
+Located at: `apps/server/src/routes/api/sync.ts`
+
+## WebSocket Sync Updates
+
+Real-time sync via WebSocket:
+
+```typescript
+// Server broadcasts change to all connected clients
+ws.broadcast('frontend-update', {
+ lastSyncedPush,
+ entityChanges
+})
+
+// Client receives and processed the information.
+```
+
+## Sync Scheduling
+
+### Automatic Sync
+
+**Desktop:**
+
+* Sync on startup
+* Periodic sync (configurable interval, default: 60s)
+
+**Server:**
+
+* Sync on entity modification
+* WebSocket push to connected clients
+
+### Manual Sync
+
+User can trigger:
+
+* Full sync
+* Sync now
+* Sync specific subtree
+
+## Troubleshooting
+
+### Common Issues
+
+**Sync stuck:**
+
+```
+-- Reset sync state
+UPDATE entity_changes SET isSynced = 0;
+DELETE FROM options WHERE name LIKE 'sync%';
+```
+
+**Hash mismatch:**
+
+* Data corruption detected
+* Re-sync from backup
+* Check database integrity
+
+**Conflict loop:**
+
+* Manual intervention required
+* Export conflicting notes
+* Choose winning version
+* Re-sync
+
+## Security Considerations
+
+### Encrypted Sync
+
+* Protected notes synced encrypted
+* No plain text over network
+* Server cannot read protected content
+
+### Authentication
+
+* Username/password over HTTPS only
+* Sync tokens for token-based auth
+* Session cookies with CSRF protection
+
+### Authorization
+
+* Users can only sync their own data
+* No cross-user sync support
+* Sync server validates ownership
+
+## Performance Metrics
+
+**Typical Sync Performance:**
+
+* 1000 changes: ~2-5 seconds
+* 10000 changes: ~20-50 seconds
+* Initial full sync (100k notes): ~5-10 minutes
+
+**Factors:**
+
+* Network latency
+* Database size
+* Number of protected notes
+* Attachment sizes
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Synchronisation/Content hashing.md b/docs/Developer Guide/Developer Guide/Concepts/Synchronisation/Content hashing.md
new file mode 100644
index 0000000000..2d95f8ab27
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Synchronisation/Content hashing.md
@@ -0,0 +1,17 @@
+# Content hashing
+Entity hashing is done in `content_hash#getEntityHashes`.
+
+* It works by looking at the `entity_changes` table and going through each of the entity names/types:
+ * `blobs`
+ * `attributes`
+ * `revisions`
+ * `attachments`
+ * `notes`
+ * `branches`
+ * `etapi_tokens`
+ * `options`
+* For some reason `note_reordering` entities are ignored specifically.
+* All the rows in `entity_changes` are then ordered alphabetically, based on their `entityId`.
+* Every entity row is then grouped by `entityName` and then by sector. The sector is defined as the first character of the `id`.
+* The hash is altered to add the `isErased` value as well since the hash of deleted entries is not updated.
+* For each sector, the hash is calculated using `utils.hash`, using SHA1 encoded as Base64.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Synchronisation/Entity change tombstones.md b/docs/Developer Guide/Developer Guide/Concepts/Synchronisation/Entity change tombstones.md
new file mode 100644
index 0000000000..9beca53e07
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Synchronisation/Entity change tombstones.md
@@ -0,0 +1,48 @@
+# Entity change tombstones
+When an entity is erased, its row in `entity_changes` is **not** deleted — it is flagged. `erase#setEntityChangesAsErased` sets `isErased = true`, refreshes `utcDateChanged` and re-pushes the row through `putEntityChangeWithForcedChange`. The tombstone is what tells every peer "this entity is gone"; without it, a peer that still holds the entity would simply push it back.
+
+## Tombstones are never collected
+
+There is no garbage collection for them. There is no cluster-wide acknowledged-id watermark, no TTL, and no compaction pass. The `entity_changes` table therefore grows monotonically with **lifetime deletion activity**, not with the amount of data a user currently has.
+
+Two things amplify this:
+
+* **Deletions cascade.** Erasing a note tombstones its branches, attributes and revisions too (`erase#eraseNotes`), so the count tracks edit-and-delete volume rather than note count.
+* **Full initial sync replays the entire history.** A fresh client pulls every row, tombstones included. There is no snapshot or bootstrap path that would let it start from the current state.
+
+A real database observed in 2026 held ~165 000 entity changes against only ~12 000 live entities (1 954 notes, 7 200 attributes, 644 attachments) — roughly **85 % tombstones**.
+
+## Why they cannot simply be deleted
+
+`content_hash#getEntityHashes` folds the flag into the per-sector hash:
+
+```
+entityHashMap[sector] = (entityHashMap[sector] || "") + hash + isErased;
+```
+
+Erased rows are therefore part of the hash a peer compares against. Deleting tombstones on one instance diverges its sector hashes from any peer that still has them, `checkContentHashes` then fails on nearly every sector, and `addEntityChangesForSector` re-pushes **all** rows for those sectors — including the erased ones, because `putEntityChange` preserves `isErased`. The tombstones come back.
+
+A manual `DELETE FROM entity_changes WHERE isErased = 1` only sticks if it is done on every instance at once, or if the server is the sole surviving source and every client is wiped or brand new (a fresh device has no tombstones to push back). Back up first, and only do it with all clients caught up. It is id-safe: `entity_changes` uses an `AUTOINCREMENT` high-water mark, so ids are never reused.
+
+## The built-in options do not help
+
+* **`fillEntityChanges`** runs `DELETE FROM entity_changes WHERE isErased = 0` and rebuilds the live rows. Tombstones are untouched, and the rebuilt rows get new ids, which makes peers re-pull them.
+* **`forceFullSync`** resets `lastSyncedPull`/`lastSyncedPush` to 0 and re-pulls everything, tombstones included. It makes the problem worse.
+
+## Blobs are the one exception
+
+The same wall was already hit for blobs and special-cased in `erase#eraseUnusedBlobs`, which purges their change rows outright instead of tombstoning them:
+
+```
+// blobs are not marked as erased in entity_changes, they are just purged completely
+// this is because technically every keystroke can create a new blob and there would be just too many
+sql.executeMany(`DELETE FROM entity_changes WHERE entityName = 'blobs' AND entityId IN (???)`, unusedBlobIds);
+```
+
+That exception was never generalised, so every other entity type still accumulates.
+
+## Where it actually bites
+
+The cost is invisible on native clients — better-sqlite3 handles a few hundred thousand rows without complaint. It is only fatal on the WASM targets (standalone in the browser, and the Capacitor mobile app built on it), where SQLite runs synchronously and a long transaction blocks the thread. This is latent debt that the newer targets exposed rather than created.
+
+Any real fix has to address the hash coupling above. The plausible directions are a per-instance acknowledged-id watermark that permits coordinated collection, a snapshot/bootstrap path so fresh clients do not replay history, or generalising the blob purge to other high-churn entity types.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Syntax highlighting.md b/docs/Developer Guide/Developer Guide/Concepts/Syntax highlighting.md
new file mode 100644
index 0000000000..841e6699d3
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Syntax highlighting.md
@@ -0,0 +1,93 @@
+# Syntax highlighting
+## Defining the MIME type
+
+The first step to supporting a new language for either code blocks or code notes is to define the MIME type. Go to `mime_type.ts` in `packages/commons` and add a corresponding entry:
+
+```
+{ title: "ABAP (SAP)", mime: "text/x-abap", mdLanguageCode: "abap" }
+```
+
+Where `mdLanguageCode` is a Markdown-friendly name of the language.
+
+## Syntax highlighting for Highlight.js
+
+The Highlight.js instance in Trilium identifies the code to highlight by the mime type mappings defined in `syntax_highlighting.ts` in `packages/highlightjs`.
+
+There are three possible cases, all involving modifying the `byMimeType` record:
+
+### Highlight.js built-in languages:
+
+Simply add a corresponding entry:
+
+```
+"application/dart": () => import("highlight.js/lib/languages/dart"),
+```
+
+### External modules from NPM
+
+1. Install the module as a dependency in `packages/highlight.js`
+2. Import:
+
+ ```
+ "application/x-cypher-query": () => import("highlightjs-cypher")
+ ```
+3. Do this if the npm module is relatively new and it has TypeScript mappings, if not see the last option.
+
+### Modules integrated directly into Trilium
+
+* Allows making small modifications if needed (especially if the module is old).
+* Works well for modules missing type definitions, since types are added directly in code.
+
+Steps:
+
+1. Copy the syntax highlighting file ([example](https://github.com/highlightjs/highlightjs-sap-abap/blob/main/src/abap.js)) into `packages/highlightjs/src/languages/[code].ts`.
+2. Add a link in a comment at the top of the file linking to the original source code.
+3. Replace `module.exports =` by `export default`.
+4. Add types to the method:
+
+ ```
+ import { HLJSApi, Language } from "highlight.js";
+
+ export default function (hljs: HLJSApi): Language {
+ // [...]
+ }
+ ```
+5. Remove any module loading mechanism or shims outside the main highlight function.
+6. Modify `syntax_highlighting.js` to support the new language:
+
+ ```
+ "text/x-abap": () => import("./languages/abap.js"),
+ ```
+
+## Syntax highlighting for CodeMirror
+
+> [!NOTE]
+> Newer versions of Trilium use CodeMirror 6, so the plugin must be compatible with this version.
+
+### Adding the MIME type mapping
+
+Similar to Highlight.js, the mappings for each MIME type are handled in `syntax_highlighting.ts` in `packages/codemirror`, by modifying the `byMimeType` record.
+
+1. Official modules:
+
+ ```
+ async () => (await import('@codemirror/lang-html')).html(),
+ ```
+2. Legacy modules (ported from CodeMirror 5):
+
+ ```
+ "text/turtle": async () => (await import('@codemirror/legacy-modes/mode/turtle')).turtle, 
+ ```
+3. Modules integrated into Trilium:
+
+ ```
+ "application/x-bat": async () => (await import("./languages/batch.js")).batch,
+ ```
+
+### Integrating existing modules
+
+* Add a comment at the beginning indicating the link to the original source code.
+* Some imports might require updating:
+ * Instead of
+ `import { StreamParser, StringStream } from "@codemirror/stream-parser";`, use  
+ `import { StreamParser, StringStream } from "@codemirror/language";`
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Themes.md b/docs/Developer Guide/Developer Guide/Concepts/Themes.md
new file mode 100644
index 0000000000..314c886ccc
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Themes.md
@@ -0,0 +1,17 @@
+# Themes
+## Server-side
+
+* There are three themes embedded in the application:
+ * `light`, located in `src\public\stylesheets\theme-light.css`
+ * `dark`, located in `src\public\stylesheets\theme-dark.css`
+ * `next`, composed from `src\public\stylesheets\theme-next-light.css` and `src\public\stylesheets\theme-next-dark.css`.
+* The default theme is set only once, when the database is created and is managed by `options_init#initNotSyncedOptions`.
+ * In the original implementation: On Electron, the choice between `light` and `dark` is done based on the OS preference. Otherwise, the theme is always `dark`.
+ * Now, we always choose `next` as the default theme.
+* The theme is served via `src\routes\index.ts`, in the `getThemeCssUrl` method.
+
+## Client-side
+
+* The predefined themes are hard-coded in the client in `src\public\app\widgets\type_widgets\options\appearance\theme.js`.
+* The user-defined themes are obtained via a call to the server: `options/user-themes`.
+* The theme retrieval is done via a request.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Concepts/Web Clipper.md b/docs/Developer Guide/Developer Guide/Concepts/Web Clipper.md
new file mode 100644
index 0000000000..dc504658ea
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Concepts/Web Clipper.md
@@ -0,0 +1,42 @@
+# Web Clipper
+The Web Clipper is present in the monorepo in `apps/web-clipper`. It's based on [WXT](https://wxt.dev/guide/introduction.html), a framework for building web extensions that allows very easy development and publishing.
+
+## Manifest version
+
+Originally the Web Clipper supported only Manifest v2, which made the extension incompatible with Google Chrome. [#8494](https://github.com/TriliumNext/Trilium/pull/8494) introduces Manifest v3 support for Google Chrome, alongside with Manifest v2 for Firefox.
+
+Although Firefox does support Manifest v3, we are still using Manifest v2 for it because WXT dev mode doesn't work for the Firefox / Manifest v3 combination and there were some mentions about Manifest v3 not being well supported on Firefox Mobile (and we plan to have support for it).
+
+## Development
+
+WXT allows easy development of the plugin, with full TypeScript support and live reload. To enter dev mode:
+
+* Run `pnpm --filter web-clipper dev` to enter dev mode for Chrome (with manifest v3).
+* Run `pnpm --filter web-clipper dev:firefox` to enter dev mode for Firefox (with manifest v2).
+
+This will open a separate browser instance in which the extension is automatically injected.
+
+> [!NOTE]
+> On NixOS, the same development commands work just fine. Just make sure the browser is available in the system path:
+>
+> ```sh
+> nix-shell -p chromium
+> ```
+
+## Default port
+
+The default port is:
+
+* `37742` if in development mode. This makes it possible to use `pnpm desktop:start` to spin up a desktop instance to use the Clipper with.
+* `37840` in production, the default Trilium port.
+
+## Building
+
+* Run `build` (Chrome) or `build:firefox` to generate the output files, which will be in `.output/[browser]`.
+* Run `zip` or `zip:firefox` to generate the ZIP files.
+
+## CI
+
+`.github/workflows/web-clipper.yml` handles the building of the web clipper. Whenever the web clipper is modified, it generates the ZIPs and uploads them as artifacts.
+
+There is currently no automatic publishing to the app stores.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/CKEditor.md b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor.md
new file mode 100644
index 0000000000..a1c1902dc4
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor.md
@@ -0,0 +1,6 @@
+# CKEditor
+* We migrated away from the legacy CKEditor builds using Webpack and instead use the prebuilt npm binaries.
+* The role of the `packages/ckeditor5` is to gather the CKEditor for consumption by the client, which includes plugin definitions.
+* The internal Trilium plugins (e.g. cut to note, include note) are present in `packages/ckeditor5/src/plugins`.
+* External CKEditor plugins that needed adjustments are present in `packages/ckeditor5-*`.
+ * To integrate a new plugin, see <a class="reference-link" href="CKEditor/Plugin%20migration%20guide.md">Plugin migration guide</a>.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/Differences from upstream.md b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/Differences from upstream.md
new file mode 100644
index 0000000000..32ffef24c6
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/Differences from upstream.md
@@ -0,0 +1,25 @@
+# Differences from upstream
+* Embeds [`~~isaul32/ckeditor5-math~~`](https://github.com/isaul32/ckeditor5-math)  <a class="reference-link" href="ckeditor5-math.md">ckeditor5-math</a>, which is a third-party plugin for adding math support. CKEditor itself also has a [math plugin](https://ckeditor.com/docs/ckeditor5/latest/features/math-equations.html) with MathType and ChemType but it's premium-only.
+* Zadam left a TODO in `findandreplaceUI`: `// FIXME: keyboard shortcut doesn't work:` [`https://github.com/ckeditor/ckeditor5/issues/10645`](https://github.com/ckeditor/ckeditor5/issues/10645)
+* `packages\ckeditor5-build-balloon-block\src\mention_customization.js` introduces note insertion via `@` character.
+
+| Affected file | Affected method | Changed in | Reason for change |
+| --- | --- | --- | --- |
+| `packages/ckeditor5-mention/src/mentionui.ts` | `createRegExp()` | `6db05043be24bacf9bd51ea46408232b01a1b232` (added back) | Allows triggering the autocomplete for labels and attributes in the attribute editor. |
+| `init()` | `55a63a1934efb9a520fcc2d69f3ce55ac22aca39` | Allows dismissing @-mention permanently after pressing ESC, otherwise it would automatically show up as soon as a space was entered. | |
+
+## Checking the old repo
+
+Use the following command to identify commits from Zadam:
+
+```
+git log --oneline --author="adam" --all
+```
+
+It's best to run the command from zadam's fork of `trilium-ckeditor5` instead of the TriliumNext once since it might not contain all the unmerged branches.
+
+To show a filtered diff of a commit:
+
+```
+git show d42e772783 -- ':!*yarn.lock' ':!*packages/ckeditor5-build-balloon-block/build/*' ':!*package.json'
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/Plugin migration guide.md b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/Plugin migration guide.md
new file mode 100644
index 0000000000..47a4b5e83a
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/Plugin migration guide.md
@@ -0,0 +1,85 @@
+# Plugin migration guide
+This guide walks through the basic steps to take to integrate a CKEditor 5 plugin for use inside the Trilium monorepo, which allows:
+
+* Making modifications to the implementation without having to maintain a new repo.
+* Integrating an older plugin based on the legacy installation method so that it works well with the new one.
+
+> [!IMPORTANT]
+> This guide assumes that the CKEditor plugin is written in TypeScript. If it isn't, then you will have to port it to TypeScript to match the rest of the monorepo.
+
+## Step 1. Creating the project skeleton
+
+First, we are going to generate a project from scratch so that it picks up the latest template for building CKEditor plugins, whereas the plugin which is being integrated might be based on the legacy method.
+
+Outside the `Notes` repository, we are going to use the CKEditor generator to generate the new project structure for us. We are not doing it directly inside `Notes` repository since it's going to use a different package manager (Yarn/NPM vs `pnpm`) and it also creates its own Git repository.
+
+```
+npx ckeditor5-package-generator @triliumnext/ckeditor5-foo --use-npm --lang ts --installation-methods current
+```
+
+Of course, replace `foo` with the name of the plugin. Generally it's better to stick with the original name of the plugin which can be determined by looking at the prefix of file names (e.g. `mermaid` from `mermaidui` or `mermaidediting`).
+
+## Step 2. Copy the new project
+
+1. Go to the newly created `ckeditor5-foo` directory.
+2. Remove `node_modules` since we are going to use `pnpm` to handle it.
+3. Remove `.git` from it.
+4. Copy the folder into the `Notes` repo, as a subdirectory of `packages`.
+
+## Step 3. Updating dependencies
+
+In the newly copied package, go to `package.json` and edit:
+
+1. In `devDependencies`, change `ckeditor5` from `latest` to the same version as the one described in `packages/ckeditor5/package.json` (fixed version, e.g. `43.2.0`).
+2. In `peerDependencies`, change `ckeditor5` to the same version as from the previous step.
+3. Similarly, update `vitest` dependencies to match the monorepo one.
+4. Remove the `prepare` entry from the `scripts` section.
+5. Change `build:dist` to simply `build`.
+6. In `tsconfig.dist.json`, change `typings/types` to `../typings/types.d.ts` to be compatible with the latest TypeScript version.
+
+## Step 4. Install missing dependencies and build errors
+
+Run `pnpm build-dist` on the `Notes` root, and:
+
+1. If there is an error about `Invalid module name in augmentation, module '@ckeditor/ckeditor5-core' cannot be found.`, simply replace `@ckeditor/ckeditor5-core` with `ckeditor5`.
+2. Run the build command again and ensure there are no build errors.
+3. Commit the changes.
+
+## Step 5. Using `git subtree` to pull in the original repo
+
+Instead of copying the files from the existing plugin we are actually going to carry over the history for traceability. To do so, we will use a temporary directory inside the repo:
+
+```
+git subtree add --prefix=_regroup/<name> https://[...]/repo.git <main_branch>
+```
+
+This will bring in all the commits of the upstream repo from the provided branch and rewrite them to be placed under the desired directory.
+
+## Step 6. Integrate the plugin
+
+1. Start by copying each sub-plugin (except the main one such as `FooEditing` and `FooUI`).
+ 1. If they are written in JavaScript, port them to TypeScript.
+ 1. Remove any non-TypeScript type documentation.
+ 2. If they have non-standard imports to CKEditor, such as `'ckeditor5/src/core.js'`, rewrite them to simply `ckeditor`.
+2. Install any necessary dependencies used by the source code (try going based on compilation errors rather than simply copying over all dependencies from `package.json`).
+3. Keep the existing TypeScript files that were generated automatically and integrate the changes into them.
+4. In `tsconfig.json` of the plugin, set `compilerOptions.composite` to `true`.
+5. Add a workspace dependency to the new plugin in `packages/ckeditor5/package.json`.
+6. In `packages/ckeditor5` look for `plugins.ts` and import the top-level plugin in `EXTERNAL_PLUGINS`.
+
+## Handling CSS
+
+Some plugins have custom CSS whereas some don't.
+
+1. `import` the CSS in the `index.ts` of the plugin.
+2. When building the plugin, `dist/index.css` will be updated.
+3. In `plugins.ts` from `packages/ckeditor5`, add an import to the CSS.
+
+## Integrating from another monorepo
+
+This is a more complicated use-case if the upstream plugin belongs to a monorepo of another project (similar to how `trilium-ckeditor5` used to be).
+
+1. Create a fresh Git clone of the upstream monorepo to obtain the plugin from.
+2. Run `git filter-repo --path packages/ckeditor5-foo/` (the trailing slash is very important!).
+3. Run `git subtree add` just like in the previous steps but point to the local Git directory instead (by appending `/.git` to the absolute path of the repository).
+4. Follow same integration steps as normal.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/ckeditor5-math.md b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/ckeditor5-math.md
new file mode 100644
index 0000000000..e47a59f125
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/ckeditor5-math.md
@@ -0,0 +1,16 @@
+# ckeditor5-math
+<figure class="image image-style-align-right"><img src="ckeditor5-math_image.png"><figcaption><code>ckeditor5-math</code> in action.</figcaption></figure>
+
+A fork of [isaul32/ckeditor5-math](https://github.com/isaul32/ckeditor5-math), which is the CKEditor5 plugin which adds the math functionality. We keep our own version to be able to use it on the latest version of CKEditor, alongside some custom improvements.
+
+## Development environment
+
+* Tested on Node.js 20.
+* The package manager is yarn 1 (v1.22.22 is known to be working fine for it at the time of writing).
+
+Important commands:
+
+* To check if the code has any formatting issues: `yarn lint`
+* To start a live preview: `yarn start`
+* To run the tests: `yarn test`
+ * Note that this requires Chromium, on NixOS this can be achieved by running a `nix-shell -p chromium`, and running `CHROME_BIN=$(which chromium) yarn test` inside it.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/ckeditor5-math_image.png b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/ckeditor5-math_image.png
new file mode 100644
index 0000000000..51184b1309
Binary files /dev/null and b/docs/Developer Guide/Developer Guide/Dependencies/CKEditor/ckeditor5-math_image.png differ
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/Compression libraries.md b/docs/Developer Guide/Developer Guide/Dependencies/Compression libraries.md
new file mode 100644
index 0000000000..7152899178
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/Compression libraries.md
@@ -0,0 +1,24 @@
+# Compression libraries
+The repository ships **three** independent ZIP implementations. This looks like an obvious consolidation target and is not one — each is anchored by a constraint the others cannot satisfy. This page exists so the analysis is not repeated.
+
+| Library | Declared by | Used for |
+| --- | --- | --- |
+| `jszip` | `packages/commons` | The XLSX container, via `exceljs`; also `renderSpreadsheetToCsvZip` |
+| `fflate` | `apps/standalone` | The browser note `ZipProvider` (`lightweight/zip_provider.ts`) |
+| `archiver` + `yauzl` | `apps/server` | The Node `ZipProvider` used by server and desktop |
+
+## jszip cannot be removed
+
+`exceljs` — commons' XLSX read/write engine and a genuine runtime dependency — hard-depends on jszip for the XLSX zip container. `pnpm why jszip` resolves it as `jszip → exceljs → @triliumnext/commons`. Any bundle that reads or writes spreadsheets pulls jszip in regardless of what else changes.
+
+`commons/src/lib/spreadsheet/render_to_csv.ts` also uses jszip directly. Switching that one call site to fflate does **not** remove jszip (exceljs still drags it in) and is mildly counterproductive: it would add fflate to the server bundle, where jszip is already present, in a feature that has therefore already paid for jszip.
+
+## fflate is not interchangeable with it either
+
+fflate is the deliberate lighter choice for the browser: roughly 30 KB against jszip's ~95 KB, in a bundle where that matters, with custom CP437 filename handling for the standalone note ZipProvider. Replacing it with jszip would grow the standalone bundle to remove a dependency that cannot be removed anyway.
+
+## A trap if jszip is ever dropped
+
+`packages/commons` is intentionally **browser-pure** — its library `tsconfig` does not include `@types/node`; only the spec `tsconfig` does. jszip's `index.d.ts` carries a `/// <reference types="node" />`, which has been silently supplying the `Buffer` global type to `parse_from_xlsx.ts`.
+
+If jszip ever does leave commons, `bytesToBase64`'s reference to `Buffer` breaks. The fix is to reach it through `globalThis` rather than re-adding `@types/node`, which would undo the browser-purity constraint.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/Per-dependency checks.md b/docs/Developer Guide/Developer Guide/Dependencies/Per-dependency checks.md
new file mode 100644
index 0000000000..0640925536
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/Per-dependency checks.md
@@ -0,0 +1,189 @@
+# Per-dependency checks
+<table class="ck-table-resized">
+ <colgroup>
+ <col>
+ <col>
+ <col>
+ <col>
+ <col>
+ </colgroup>
+ <thead>
+ <tr>
+ <th>Dependency</th>
+ <th>Name in <code>library_loader</code></th>
+ <th>Things to check for a basic sanity check</th>
+ <th>&nbsp;</th>
+ <th>Protected by unit tests</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code>better-sqlite3</code></td>
+ <td>&nbsp;</td>
+ <td>See&nbsp;<a class="reference-link" href="Per-dependency%20checks/bettersqlite%20binaries.md">bettersqlite binaries</a>.</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>jsdom</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Note map</li><li>Clipper</li><li>Note similarity</li></ul></td>
+ <td>Protected by typings, should catch any potential changes in API.</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td><code>async-mutex</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Sync</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>axios</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Can't be directly tested, as it's exposed only via the backend script API.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>sax</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>EverNote imports</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><ul><li><code>ws</code></li><li><code>debounce</code></li></ul></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Check any action is reported from server to client (e.g. delete a note).</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>ejs</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Onboarding / first setup</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>dayjs</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Day notes</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>semver</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Application should start.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>https-proxy-agent</code></td>
+ <td>&nbsp;</td>
+ <td>???</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>sax</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>EverNote import</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>ini</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Affects config, generally if the application starts then it should be OK.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>jsplumb</code></td>
+ <td><code>RELATION_MAP</code></td>
+ <td><ul><li>Relation map note type</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>jquery.mark.es6</code></td>
+ <td><code>MARKJS</code></td>
+ <td><ul><li>In search, when highlighting the text that matched.</li><li>In search in HTML, which might not actually be used since it seems to have been replaced by CKEditor's own find &amp; replace dialog.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>knockout.js</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Used in rendering the login and main layout of the application.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>normalize.min.css</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Used in shared notes.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>wheel-zoom.min.js</code></td>
+ <td><code>WHEEL_ZOOM</code></td>
+ <td><ul><li>When opening a image that is in attachment.</li><li>When opening a stand-alone image note.</li><li>When zooming in a mermaid chart.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>fancytree</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>The note tree should be fully functional.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>bootstrap</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Check mostly the on-boarding pages, when there is no database.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>electron-debug</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Run electron using <code>npm run start-electron</code> and check that the debug hotkeys are still working (Ctrl+Shift+I on Windows/Linux, Cmd+Alt+I for dev tools, Cmd/Ctrl+R for reload).</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>electron-dl</code></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>eslint</code></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><code>marked</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Importing a markdown note.</li></ul></td>
+ <td>&nbsp;</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td><code>force-graph</code></td>
+ <td>&nbsp;</td>
+ <td><ul><li>Note map</li></ul></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ </tbody>
+</table>
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Dependencies/Per-dependency checks/bettersqlite binaries.md b/docs/Developer Guide/Developer Guide/Dependencies/Per-dependency checks/bettersqlite binaries.md
new file mode 100644
index 0000000000..5a473b5e51
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Dependencies/Per-dependency checks/bettersqlite binaries.md
@@ -0,0 +1,25 @@
+# bettersqlite binaries
+### The native node bindings
+
+`better-sqlite3` has native Node bindings. With updates of `better-sqlite3`, but also of Electron and Node.js versions, these bindings need to be updated.
+
+Note that Electron and Node.js versions need different versions of these bindings, since Electron usually packs a different version of Node.js.
+
+During development, `pnpm install` tries to build or reuse prebuilt natives for the current Node.js version. This makes `npm run start-server` work out of the box. Trying to run `npm run start-electron` with these versions generally causes an error such as this:
+
+```
+Uncaught Exception:
+Error: The module '/Users/elian/Projects/Notes/node_modules/better-sqlite3/build/Release/better_sqlite3.node'
+was compiled against a different Node.js version using
+NODE_MODULE_VERSION 108. This version of Node.js requires
+NODE_MODULE_VERSION 116. Please try re-compiling or re-installing
+the module (for instance, using `npm rebuild` or `npm install`).
+```
+
+### How the natives are handled
+
+To avoid issues between the `server` and the `desktop`, the `desktop` build gets its own copy of the `bettersqlite3` dependency in its `node_module`. This copy is then rebuilt automatically to match the Electron version.
+
+This process of rebuilding is handled by `scripts/electron-rebuild.mts` which runs automatically after `pnpm install` (via `postinstall`).
+
+If needed, the script can be run manually again via `pnpm postinstall`.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Documentation.md b/docs/Developer Guide/Developer Guide/Documentation.md
new file mode 100644
index 0000000000..dac8a44b97
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Documentation.md
@@ -0,0 +1,85 @@
+# Documentation
+There are multiple types of documentation for Trilium:
+
+* The _User Guide_ represents the user-facing documentation. This documentation can be browsed by users directly from within Trilium, by pressing <kbd>F1</kbd>.
+* The _Developer's Guide_ represents a set of Markdown documents that present the internals of Trilium, for developers.
+* _Release Notes_, this contains the change log for each released or soon-to-be-released version. The release notes are used automatically by the CI when releasing a version.
+* The _Script API_, which is an automatically generated documentation for the front-end and back-end APIs for scripts.
+
+## Location of the documentation
+
+All documentation is stored in the [Trilium](https://github.com/TriliumNext/Trilium) repository:
+
+* `docs/Developer Guide` contains Markdown documentation that can be modified either externally (using a Markdown editor, or internally using Trilium).
+* `docs/Release Notes` is also stored in Markdown format and can be freely edited.
+* The _Script API_ is auto-generated and is **not** committed to the repository. It is built into the gitignored `site/` directory and published to [docs.triliumnotes.org](https://docs.triliumnotes.org/); see [Updating the Script API](#updating-the-script-api) below.
+* `docs/User Guide` contains Markdown documentation as well, together with a `!!!meta.json` file that describes the note tree (note IDs, share aliases, icons, attachments).
+ * From it, `apps/server/src/assets/doc_notes/en/User Guide` (the HTML rendered by the in-app help) and `apps/standalone/src/assets/help_meta.json` are generated. These generated files must never be edited by hand.
+ * The Markdown can be edited by hand, as long as the generated files are refreshed afterwards by running `pnpm edit-docs:sync-docs` (see below).
+
+The mappings between note trees and directories are listed in `edit-docs-config.yaml` at the root of the repository.
+
+## Editing the documentation
+
+There are two ways to modify documentation:
+
+* Using a special mode of Trilium.
+* By manually editing the files.
+
+### Using the `edit-docs` app
+
+To edit the documentation using Trilium, set up a working development environment via <a class="reference-link" href="Environment%20Setup.md">Environment Setup</a> and run the following command: `pnpm edit-docs:edit-docs`.
+
+How it works:
+
+* At startup, the documentation from `docs/` is imported from Markdown into a in-memory session (the initialization of the database is already handled by the application).
+* Each modification will trigger after 10s an export from the in-memory Trilium session back to Markdown, including the meta file, as well as the HTML and meta files used by the in-app help.
+
+### Manual editing
+
+Small modifications can be made directly using a Markdown editor or VS Code, for example. For the User Guide, run `pnpm edit-docs:sync-docs` afterwards: it performs the same import and export as the `edit-docs` app, without opening a window, so that the Markdown is normalized the same way and the in-app help is regenerated.
+
+When making manual modifications, keep in mind:
+
+* Images are handled as Trilium attachments which are stored in the meta file, so a picture cannot simply be dropped in the directory.
+* The file or directory structure is described by the meta file. A file that is not described in the meta file will cause the import to fail, and a file that is described but missing from the disk as well.
+* The `writing-documentation` skill in `.claude/skills` provides a `docs.mjs` script that handles these cases (creating a page, registering an image, renaming, moving or deleting a page) and audits the documentation for broken links, missing images and inconsistent metadata.
+
+### Reviewing & committing the changes
+
+Since the documentation is tracked with Git, after making the manual or automatic modifications (wait at least 10s after making the modification in the `edit-docs` app) the changes will reflect in Git.
+
+Make sure to analyze each modified file and report possible issues.
+
+Important aspects to consider:
+
+* The Trilium import/export mechanism is not perfect, so at the next import/export/import cycle some whitespace might get thrown in. It's generally safe to commit the changes as-is.
+* Since we are importing Markdown, editing HTML and then exporting the HTML back to Markdown there might be some edge cases where the formatting is not properly preserved. Try to identify such cases and report them in order to get them fixed (this will benefit also the users).
+
+## Automation
+
+The documentation is built via `apps/build-docs`:
+
+1. The output directory is cleared.
+2. The User Guide and the Developer Guide are built.
+ 1. The documentation from the repo is archived and imported into an in-memory instance.
+ 2. The documentation is exported using the shared theme.
+3. The API docs (internal and ETAPI) are statically rendered via Redocly.
+4. The script API is generated via `typedoc`
+
+The `deploy-docs` workflow triggers the documentation build and uploads it to CloudFlare Pages.
+
+## Updating the Script API
+
+As mentioned previously, the Script API is not manually editable since it is auto-generated using TypeDoc.
+
+The Script API is regenerated automatically as part of `pnpm docs:build` — its output goes into the gitignored `site/script-api/{backend,frontend,electron}` directory and is published by the `deploy-docs` workflow, so there is nothing to commit. To preview changes locally, run `pnpm docs:build` and inspect the output under `site/`.
+
+Note that in order to simulate the environment a script would have, some fake source files (in the sense that they are only used for documentation) are being used as entrypoints for the documentation. Look for `backend_script_entrypoint` and `frontend_script_entrypoint` in `apps/build-docs/src`.
+
+## Building locally
+
+In the Git root:
+
+* Run `pnpm docs:build`. The built documentation will be available in `site` at Git root.
+* To also run a webserver to test it, run `pnpm docs:preview` (this will not build the documentation) and navigate to `localhost:9000`.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Documentation/Documentation references in the application.md b/docs/Developer Guide/Developer Guide/Documentation/Documentation references in the application.md
new file mode 100644
index 0000000000..79c1bd80e9
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Documentation/Documentation references in the application.md
@@ -0,0 +1,33 @@
+# Documentation references in the application
+## Hard-coded links
+
+Hard-coded links are present throughout the application, either in dialogs or in the source code as comments.
+
+You can identify these links by searching for:
+
+```
+https://triliumnext.github.io/Docs/Wiki/
+```
+
+## Help buttons
+
+There is a pattern of “?” buttons throughout the application which make use of the `data-help-page` attribute. Whenever these buttons are pressed, the user is redirected to the corresponding wiki page by prepending the wiki root URL to the `data-help-page` attribute.
+
+### Deprecated `help-page` attribute
+
+Since the current wiki has a different structure than the original, for example to link to [https://github.com/TriliumNext/Docs/blob/main/Wiki/tree-concepts.md](https://github.com/TriliumNext/Docs/blob/main/Wiki/tree-concepts.md) the `data-help-page` attribute must be set to `tree-concepts.md`.
+
+For links to headings, simply add the heading after the `.md`: `tree-concepts.md#prefix`
+
+You can identify those by looking for:
+
+* `.attr("data-help-page"`
+* `data-help-page="`
+
+### More modern `data-in-app-help` attribute
+
+Instead of opening in a web browser, this opens the help directly in the application in a split view. This is handled via the `data-in-app-help` attribute, where the value is the note ID of the help page without the `_help_` prefix.
+
+### React
+
+Use the `HelpButton` component in the same fashion as the `data-in-app-help` attribute.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Environment Setup.md b/docs/Developer Guide/Developer Guide/Environment Setup.md
new file mode 100644
index 0000000000..a9b6ee127b
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Environment Setup.md
@@ -0,0 +1,54 @@
+# Environment Setup
+## Node.js
+
+Use the Node.js version pinned in `.nvmrc` at the root of the repository. With [nvm](https://github.com/nvm-sh/nvm), `nvm install` run inside the repository installs and activates it.
+
+## Setting up `pnpm`
+
+Trilium uses the `pnpm` package manager in order to better manage its mono-repo structure. Unlike `npm` which comes by default with Node.js, `pnpm` needs to be installed separately. The expected version is the `packageManager` field of the root `package.json`; a newer release of the same major works too, since `pmOnFail: ignore` in `pnpm-workspace.yaml` tolerates the difference.
+
+Install it with `npm`:
+
+```
+npm install -g pnpm
+```
+
+pnpm 12 is a native executable that its install script links into place, so the command needs lifecycle scripts allowed (npm's default). Under a version manager such as nvm, a global package belongs to one Node.js version, so run the command again after switching to another one. The [standalone installer](https://pnpm.io/installation) is an alternative that does not depend on the Node.js version.
+
+After that, run `pnpm` in a new terminal to see if it is working.
+
+> [!WARNING]
+> `corepack enable` is no longer the recommended way to obtain `pnpm`. Only Corepack 0.34.5 or newer (bundled from Node.js 24.12 on) can start the native pnpm 12, and Node.js 25 no longer ships Corepack at all. An older Corepack fails with `Cannot find module '…/corepack/v1/pnpm/12.x.y/bin/pnpm.cjs'`, and the `~/.cache/node/corepack/v1/pnpm/12.x.y` directory it wrote makes a newer Corepack fail the same way, so delete that directory too.
+
+As a quick heads-up of some differences when compared to `npm`:
+
+* Generally instead of `npm run` we have `pnpm run` instead.
+* Instead of `npx` we have `pnpm exec`.
+
+## Installing dependencies
+
+Run `pnpm i` at the top of the `Trilium` repository to install the dependencies.
+
+> [!NOTE]
+> Dependencies are kept up to date periodically in the project. Generally it's a good rule to do `pnpm i` after each `git pull` on the main branch.
+
+## IDE
+
+Our recommended IDE for working on Trilium is Visual Studio Code (or VSCodium if you are looking for a fully open-source alternative).
+
+By default we include a number of suggested extensions which should appear when opening the repository in VS Code. Most of the extensions are for integrating various technologies we are using such as Playwright and Vitest for testing or for <a class="reference-link" href="Concepts/Internationalisation%20%20Translations.md">Internationalisation / Translations</a>.
+
+## TypeScript
+
+The root `package.json` declares **both** `typescript` (6.x) and `@typescript/native` (an alias of `typescript@7`). This is deliberate — do not "deduplicate" them by bumping `typescript` to 7:
+
+* **`typescript` 6.x is the library.** TypeScript 7 is the native Go port and its package no longer exports the JS compiler API (`exports["."]` is just a version stub). Everything that does `require("typescript")` needs 6.x: TypeDoc, typescript-eslint, and — the one that also ships to users — `packages/codemirror`, which runs the real language service in the browser for script-note IntelliSense.
+* **`@typescript/native` is the compiler binary**, used only by `scripts/filter-tsc-output.mts` behind `pnpm typecheck`. It builds the whole project graph in roughly a seventh of the time 6.x takes.
+* pnpm gives `node_modules/.bin/tsc` to the alias, so a bare `tsc` on the command line is **7**, not the 6.x that tooling loads. That is also what keeps `.tsbuildinfo` in one format — the two majors cannot read each other's, and mixing them forces a full rebuild every time.
+
+**Do not switch to `@typescript/typescript6`.** Microsoft's documented side-by-side layout aliases `typescript` to that compatibility shim so the native compiler can own the `tsc` bin name. It does not fit here, for two reasons that only show up at build time:
+
+* The shim ships five files and **no `lib.*.d.ts`**, so the 96 `typescript/lib/lib.*.d.ts?raw` imports in `packages/codemirror/src/type_completion/ts_lib_files.ts` fail to resolve and the client build dies.
+* Working around that by keeping a real `typescript` under `packages/codemirror` splits resolution: `@typescript/vfs` and `@valtown/codemirror-ts` are hoisted to the root and follow the shim, while codemirror's own source follows its nested copy. Two physical paths means the 3.3 MB compiler is bundled **twice** into the lazy script-note chunk (measured: client `dist` 69 M → 72 M).
+
+The official layout assumes the only consumer of the `typescript` name is tooling. This repo also bundles it into a browser app, so the plain package has to stay.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Interoperability/Exported content with extended task states.md b/docs/Developer Guide/Developer Guide/Interoperability/Exported content with extended task states.md
new file mode 100644
index 0000000000..79c60312ea
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Interoperability/Exported content with extended task states.md
@@ -0,0 +1,45 @@
+# Exported content with extended task states
+If you're a developer working with HTML or Markdown content exported from Trilium, here are the details on how task states are stored.
+
+## HTML notes
+
+Trilium stores the task state identifier in the `data-trilium-task-state` attribute on the `<li>` element of the to-do list. The task state's title is also included to provide a fallback, human-readable tooltip (shown even when no custom checkbox is rendered).
+
+```html
+<ul class="todo-list">
+
+ <li data-trilium-task-state="urgent" title="Urgent priority">
+ <label class="todo-list__label">
+ <input type="checkbox" disabled="disabled">
+ <span class="todo-list__label__description">
+ Replace the timing belt
+ </span>
+ </label>
+ </li>
+
+</ul>
+```
+
+The checkbox glyph, color and other details are not present in the HTML markup. They are resolved at render time from the task state definition under "Task States" in Trilium's hidden subtree.
+
+The default task states use the following identifiers:
+
+| Title | Identifier | Counts as completed |
+| --- | --- | --- |
+| None | none | No |
+| Doing | doing | No |
+| Done | done | Yes |
+| Maybe | maybe | No |
+| Cancelled | cancelled | No |
+
+## Markdown notes
+
+Exported Markdown notes simply carry the Markdown symbol corresponding to the task state inside the checkbox body, just as it appears in the editor.
+
+```html
+- [ ] None
+- [/] Doing
+- [X] Done
+- [?] Maybe
+- [-] Cancelled
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Interoperability/Trilium Backup Container (.tnbackup) file format.md b/docs/Developer Guide/Developer Guide/Interoperability/Trilium Backup Container (.tnbackup) file format.md
new file mode 100644
index 0000000000..d741873938
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Interoperability/Trilium Backup Container (.tnbackup) file format.md
@@ -0,0 +1,366 @@
+# Trilium Backup Container (.tnbackup) file format
+A container wraps exactly one SQLite database file, with optional gzip compression and optional AES-256-GCM authenticated encryption. Containers are named `.tnbackup`.
+
+**Every container is written in a single forward pass.** Nothing in one is patched in afterwards, so a destination that cannot be written back to, a download already on its way to the user, holds the format as readily as a file does. That is what puts the payload digest at the end rather than in the header, and it is why even the plainest container, neither compressed nor encrypted, has a hash standing behind its contents.
+
+Whether a backup is a container at all is policy, not format: a writer may skip it and copy a plain `.db` when neither compression nor encryption is asked for.
+
+The **payload** is everything after the header: the wrapped database, in whichever of the four forms the flags select. All integers are little-endian unless stated otherwise. All offsets are absolute byte offsets from the start of the file.
+
+Normative references: gzip is RFC 1952, AES-256-GCM is NIST SP 800-38D, scrypt is RFC 7914, and the SQLite file header is section 1.3 of the SQLite file format specification.
+
+### Header layout
+
+Cells are bytes, 16 per row. The diagram shows an encrypted container. In an unencrypted one the fields from `KDF` through `Verifier tag` are absent, so the header is 40 bytes and the payload starts there.
+
+```mermaid
+---
+config:
+ packet:
+ bitsPerRow: 16
+---
+packet-beta
+0-19: "Magic: Trilium Notes Backup"
+20: "Ver"
+21-28: "Timestamp"
+29: "Flags"
+30-31: "Header length"
+32-39: "Plaintext size"
+40: "KDF"
+41-43: "KDF params"
+44-59: "Salt"
+60-67: "Nonce prefix"
+68-83: "Verifier tag"
+```
+
+The **verifier tag is always the last field of the header**. It is written once the key exists, so it is excluded from what it authenticates. Any field added by a later version goes before it and is therefore authenticated, as the timestamp is.
+
+### Fixed header
+
+Always present.
+
+| Offset | Size | Field | Value |
+| --- | --- | --- | --- |
+| 0 | 20 | Magic | ASCII `Trilium Notes Backup` |
+| 20 | 1 | Version | `1`. Version `0` is never valid |
+| 21 | 8 | Timestamp | When the backup was taken, in milliseconds since the Unix epoch. `0` when not recorded |
+| 29 | 1 | Flags | Bit 0: gzip-compressed. Bit 1: encrypted. Bits 2 to 7 reserved, must be 0 |
+| 30 | 2 | Header length | Total header size in bytes, i.e. the offset at which the payload starts |
+| 32 | 8 | Plaintext size | Size of the wrapped database in bytes, before compression. `0` when unknown. A hint; the trailer states it authoritatively |
+
+The flags byte, cells are bits:
+
+```mermaid
+---
+config:
+ packet:
+ bitsPerRow: 8
+---
+packet-beta
+0: "gzip"
+1: "enc"
+2-7: "reserved (must be 0)"
+```
+
+`Plaintext size` is a hint, never an instruction. It is unauthenticated in an unencrypted container and, in an encrypted one, is only confirmed once the verifier tag has been checked. Readers must not allocate from it, and must not let it widen any bound. When a container is encrypted but not compressed it equals the total payload plaintext length; when compressed, the payload is shorter by the compression ratio, which is therefore disclosed to anyone holding the file. That disclosure is an accepted trade-off for restore progress reporting and the final length check.
+
+### Trailer
+
+The last 40 bytes of every container, and the only part of it that could not be written until the payload was complete.
+
+| Offset from EOF | Size | Field | Value |
+| --- | --- | --- | --- |
+| \-40 | 32 | Payload digest | SHA-256 over the payload exactly as stored, i.e. bytes `[headerLength, EOF - 40)` |
+| \-8 | 8 | Plaintext size | The plaintext length as counted while writing |
+
+The **payload** therefore runs from `headerLength` to `EOF - 40`, not to end of file.
+
+Putting both at the end is what makes the format forward-writable, and forward-writability is what makes the digest unconditional. A digest in the header has to be patched in after the payload is known, which a download or a socket cannot do; at the end it is simply the next thing written. So every container carries one, including the uncompressed unencrypted container that has nothing else standing behind it.
+
+#### Payload digest
+
+It digests the payload **as stored**, not the plaintext. In an encrypted container that means it covers ciphertext, so it reveals nothing that holding the file does not already reveal, and it can be checked by anyone auditing a backup directory.
+
+It is a corruption check, not an authenticity check. It lies outside everything the header authenticates, so an attacker who can rewrite the file can rewrite the digest with it. Tampering is caught by GCM in an encrypted container; the digest exists to catch bit rot, truncated copies and mangled transfers.
+
+Its practical use on the failure path: when the verifier tag does not match, a reader that then finds the digest **intact** knows the file is undamaged and the passphrase is genuinely wrong.
+
+#### Plaintext size
+
+The authoritative one, counted as the payload went past rather than promised in advance. The header's own `Plaintext size` is a hint for what has to be known up front, a `Content-Length` or a progress bar; this is what the output is actually held to. A reader rejects output that does not measure exactly this, and rejects a header hint that is non-zero and disagrees with it.
+
+#### Finding the trailer
+
+Neither end of the format requires seeking.
+
+* **Encrypted.** Frames are self-delimiting and one carries the final flag, so the trailer is simply the 40 bytes that follow the last frame, and end of file must follow immediately.
+* **Unencrypted.** Nothing announces where the payload stops, so a reader holds the last 40 bytes back as they go past and whatever it is still holding when the input ends is the trailer.
+
+A file too short to contain a trailer is truncated, and says so.
+
+### Derived length
+
+A container that is **not compressed** has a length fixed by its header, because nothing in it varies with content:
+
+```
+unencrypted: 40 + plaintextSize + 40
+encrypted: 84 + plaintextSize + (floor(plaintextSize / 1048576) + 1) * 20 + 40
+```
+
+The encrypted form adds the 4-byte length field and 16-byte tag of every frame, including the empty final frame that a payload of an exact multiple of the frame size still carries. Both forms add the trailer.
+
+Two things follow. A writer knows the exact byte count before it writes anything, which is what lets a download state a `Content-Length` and a browser draw a progress bar. And a reader can compare that figure against the actual file size from the header alone, and reject a file that is short before spending a minute decrypting the part of it that did arrive.
+
+Compression breaks this: the payload is then shorter than the plaintext by a ratio the header does not state, so a compressed container has no predictable length and must not be measured this way.
+
+### Header length
+
+In version 1 the header length is fixed by the flags, and readers must require equality rather than a minimum:
+
+| Flags | Header length |
+| --- | --- |
+| Bit 1 clear | exactly 40 |
+| Bit 1 set | exactly 84 |
+
+A version that appends fields raises the version byte, so an older reader rejects the file on the version check before header length is ever in question. Across all versions two limits hold:
+
+* A header length beyond a reader's configured maximum, for which 4096 is a sane default, is rejected before anything is allocated or sought.
+* A header length extending past the end of the file is rejected. A reader must never seek past EOF on the strength of an unverified field.
+
+### Identifying a container
+
+What a container is, it states in the clear. The version, the timestamp, both flags and the plaintext size all sit in the first 40 bytes and none of them are encrypted, so a reader can tell a compressed backup from an encrypted one, and date it and size it, **without the passphrase and without touching the payload**. Listing a directory of backups costs 40 bytes a file, whatever the files weigh.
+
+A reader doing only this still applies the same checks as any other: the magic, the version, and the reserved flag bits. What it cannot make sense of it should report as an unidentified file rather than as a failure, so that one damaged container cannot derail a listing.
+
+### Encryption header
+
+Present only when flag bit 1 is set.
+
+| Offset | Size | Field | Value |
+| --- | --- | --- | --- |
+| 40 | 1 | KDF id | `1` = scrypt. `2` reserved for Argon2id. Other values reserved |
+| 41 | 3 | KDF params | Three bytes whose meaning is defined by `KDF id` |
+| 44 | 16 | Salt | Random, fresh per file |
+| 60 | 8 | Nonce prefix | Random, fresh per file |
+| 68 | 16 | Verifier tag | AES-256-GCM tag over an empty plaintext |
+
+#### KDF parameters
+
+The three parameter bytes are interpreted per algorithm, so a future KDF is not forced into scrypt's shape:
+
+| KDF id | Byte 41 | Byte 42 | Byte 43 |
+| --- | --- | --- | --- |
+| `1` scrypt | log2(N) | r | p |
+| `2` and above | Defined when the id is assigned | | |
+
+```
+key = scrypt(NFC(passphrase) as UTF-8, salt, 32 bytes, { N: 1 << log2N, r, p })
+```
+
+The passphrase is the user's backup passphrase, which is not the Trilium login password.
+
+**Passphrase encoding is part of the format**: the passphrase is normalised to Unicode NFC and encoded as UTF-8 before it reaches the KDF. Neither JavaScript nor Node normalises implicitly, so an implementation must call `String.prototype.normalize("NFC")` explicitly. Without this, the same passphrase typed with a composed `é` on one machine and a decomposed one on another derives a different key, and the user is told their passphrase is wrong.
+
+The salt is fresh per file, therefore the key is fresh per file, therefore a nonce can never repeat under a key.
+
+Recommended parameters for new files: log2(N) = 17, r = 8, p = 1. Readers must honour the parameters stored in the file rather than their own defaults, within the bounds below.
+
+#### Parameter bounds
+
+A container is untrusted input, and KDF parameters are a resource-exhaustion vector: `log2(N) = 30` asks a reader for more than 128 GiB before a single frame is read. Readers must reject, as an unsupported container:
+
+* scrypt outside `10 <= log2(N) <= 20`, `1 <= r <= 16`, `1 <= p <= 8`.
+* any parameter set whose derivation cost, `128 * N * r` bytes for scrypt, exceeds the reader's configured memory ceiling.
+
+The ceiling is what actually protects the reader, and it must be applied before the derivation is attempted, not caught afterwards.
+
+> A runtime may also impose a ceiling of its own, below these bounds. Node's `crypto.scrypt` defaults `maxmem` to 32 MiB, which is less than the recommended parameters need, so an implementation must raise it explicitly or every derivation fails. That limit belongs to the platform, not to the format: a container written with parameters one reader refuses is still a valid container.
+
+### Payload
+
+| Flags | Payload |
+| --- | --- |
+| Neither set | Raw database bytes, between the header and the trailer |
+| Compressed only | A single RFC 1952 gzip stream |
+| Encrypted | A sequence of frames |
+| Both | A sequence of frames whose plaintext is the RFC 1952 gzip stream |
+
+Compression is applied before encryption.
+
+Writers must emit the gzip stream with MTIME 0, no FNAME and no FEXTRA, and OS byte 255. The gzip header would otherwise carry a timestamp, possibly a source path, and the family of the operating system that wrote it, reintroducing in the payload the metadata this format deliberately keeps out of its own header.
+
+The OS byte usually needs setting after the fact. A zlib-based writer emits its build platform's code there — 3 on Unix, 10 on Windows — and typically offers no way to choose it, so the writer has to overwrite byte 9 of the gzip stream as it passes. That is safe: the byte is informational, and the gzip header lies outside the CRC32, which covers the uncompressed data alone. MTIME and the absent FNAME/FEXTRA usually need nothing, being zlib's defaults already.
+
+### Authenticated header
+
+One span, used by both the verifier tag and every frame:
+
+```
+authenticatedHeader = header bytes [0, verifierTagOffset) // [0, 68) in version 1
+```
+
+It stops before the verifier tag, because the tag is written once the key exists and cannot cover itself. Everything before it is covered, the timestamp included. The trailer is outside it too, being written after the payload, which costs nothing: its digest is a corruption check that GCM already supersedes for tampering.
+
+It matters that frames exclude the tag. Were a frame's AAD to cover the verifier tag, a single flipped bit in that tag would break every frame in the file, and the recovery below would be impossible.
+
+### Verifier tag
+
+```
+nonce = noncePrefix || uint32LE(0xFFFFFFFF)
+aad = authenticatedHeader
+plaintext = empty
+tag = 16 bytes, stored at verifierTagOffset
+```
+
+### Frames
+
+```
+frame := length (4 bytes, LE) || data (length bytes) || tag (16 bytes)
+```
+
+Cells are bytes. The data cell is drawn short: it is `length` bytes, normally 1 MiB.
+
+```mermaid
+---
+config:
+ packet:
+ bitsPerRow: 12
+---
+packet-beta
+0-3: "Length + final bit"
+4-19: "Frame data (length bytes)"
+20-35: "GCM tag"
+```
+
+The length field, cells are bits:
+
+```mermaid
+packet-beta
+0-30: "Frame data length"
+31: "Final"
+```
+
+| Field | Meaning |
+| --- | --- |
+| `length` bits 0 to 30 | Frame data length in bytes. GCM preserves length, so this is both the ciphertext and the plaintext length |
+| `length` bit 31 | Final frame flag |
+| `tag` | AES-256-GCM tag for this frame |
+
+Frames are numbered from 0 in file order. For frame `i`:
+
+```
+nonce_i = noncePrefix (8 bytes) || uint32LE(i)
+aad_i = authenticatedHeader || the 4-byte length field of this frame
+```
+
+Because the counter is in the nonce and the length field is in the AAD, every frame is authenticated to both its position and its length. Reordering, duplicating, resizing or splicing frames all fail verification.
+
+Counter `0xFFFFFFFF` is reserved for the verifier and must never be used by a frame.
+
+#### Framing is canonical
+
+One payload has exactly one valid framing:
+
+* Every frame before the final one carries exactly 1048576 bytes.
+* Exactly one frame has the final flag set, and it is the last frame in the file.
+* The final frame carries 1 to 1048576 bytes, except that it carries 0 bytes when the payload length is 0 or an exact multiple of 1048576.
+* End of file follows the final frame immediately. Trailing bytes make the container invalid.
+
+This constrains framing only. Two containers wrapping identical databases are not byte-identical: the salt and nonce prefix are random per file, and gzip output varies with encoder version and level.
+
+The empty final frame is what lets a writer stream in one pass: frames are sealed as they fill, and the flush seals whatever is left, so a writer never has to know whether more data is coming.
+
+A later version that wants a different frame size must signal it in the header, not vary it silently.
+
+#### Size limits
+
+Usable frame counters run from 0 to `0xFFFFFFFE`, which is 4294967295 frames. At 1 MiB per frame the largest representable payload is just under 4 PiB. Writers must reject a payload that would need more frames than this rather than wrapping the counter, which would repeat a nonce under the file's key.
+
+### Writer requirements
+
+* Fill salt and nonce prefix from a CSPRNG, independently for every file.
+* Normalise the passphrase to NFC and encode it as UTF-8 before deriving the key.
+* Set `Plaintext size` to the size of the source database, or `0` if it is not known.
+* Set reserved flag bits to 0.
+* Emit frames in counter order with no gaps, framed canonically as above, and stop at the frame counter limit rather than wrapping.
+* Emit exactly one final frame, as the last bytes of the file.
+* Compute the payload digest while streaming and write it, with the plaintext length counted as it went past, as the trailer. Never seek: everything is written once, in order.
+* Count the plaintext for the trailer at the input, before compression or framing, so it records the database's own length rather than what the payload became.
+
+The remaining two apply where the destination is a file. A writer streaming to something else, a download or a socket, has no rename to make atomic, and its output is not durable in any sense the writer controls.
+
+* Flush and `fsync` the file before renaming it, and `fsync` the containing directory after the rename on POSIX. Rename gives atomicity, not durability; without the flush a crash can leave a zero-length file under the final name, which is worse than no backup because it looks like one.
+* Write to a uniquely named temporary file in the destination directory and rename on success, so that a partial file never carries the final name and two writers cannot share a temporary. The final name is still a collision point, so writers must be serialised by the caller.
+
+### Reader requirements
+
+* Reject the file unless the first 20 bytes match the magic.
+* Reject version `0`, and reject a version above the reader's own.
+* Reject any reserved flag bit that is set.
+* Reject a header length that is not the exact value this version and these flags require, that exceeds the configured maximum, or that extends past the end of the file.
+* When encrypted, reject an unknown KDF id, reject out-of-bounds KDF parameters, then check the verifier tag before reading any frame.
+* Reject a frame whose claimed length exceeds 1048576, **before** reading its data. The length field can claim up to 2 GiB, and a reader that trusts it buffers that much before the tag check fails.
+* Reject a non-final frame whose length is not 1048576.
+* Verify each frame's tag before emitting any of its plaintext.
+* Reject any frame that follows the final frame, and any trailing bytes after it.
+* Reject end of file that is not preceded by a final frame.
+* Stop the payload at the trailer, not at end of file: after the final frame when encrypted, and by holding the last 40 bytes back when not.
+* Verify the payload digest over the bytes as read, and reject a mismatch. Every container has one.
+* Reject output whose length disagrees with the trailer's `Plaintext size`, and reject a header `Plaintext size` that is non-zero and disagrees with the trailer's.
+* Never allocate from `Plaintext size`. Stream the output and compare lengths at the end.
+* Reject a file with no room for a trailer, and any bytes following it.
+* Where a container is not compressed, its total length is derived from its header, so a file shorter than that is incomplete and may be rejected before any of it is read.
+* Apply a configured output ceiling to decompression **always**, and abort before the excess bytes reach the disk. A non-zero `Plaintext size` may only tighten that bound, never widen it: the field is unauthenticated in an unencrypted container, so a crafted value would otherwise disable the ceiling entirely.
+* Let the AEAD implementation verify tags. Where a tag is compared explicitly, the comparison must be constant-time.
+* Check the SQLite header of the output, as described below.
+
+#### SQLite header check
+
+Cheap, and it catches a container that wrapped something other than a database:
+
+* Bytes 0 to 15 are the magic `SQLite format 3\0`, hex `53514c69746520666f726d6174203300`.
+* Bytes 16 to 17 are the page size, a **big-endian** `uint16`. It must be a power of two between 512 and 32768, or the value `1`, which encodes a page size of 65536. A plain `<= 65536` bound wrongly rejects a 64 KiB-page database, since 65536 does not fit in the field.
+
+#### Rejection conditions
+
+| Condition | Reported as |
+| --- | --- |
+| Magic mismatch | Not a Trilium backup container |
+| Version `0` | Not a valid container |
+| Version above the reader's | Written by a newer Trilium |
+| Reserved flag bit set, unknown KDF id, or out-of-bounds KDF parameters | Unsupported container |
+| Header length wrong, too large, or past EOF | Not a valid container |
+| Verifier tag mismatch | Wrong backup passphrase, or the header is damaged |
+| Frame tag mismatch | Damaged at byte offset N |
+| Frame length out of range | Damaged at byte offset N |
+| Data after the trailer | Damaged |
+| End of file without a final frame | Incomplete or truncated |
+| Payload digest mismatch | Damaged |
+| File too short to hold a trailer | Incomplete or truncated |
+| File shorter than an uncompressed container's derived length | Incomplete or truncated |
+| Output length disagrees with the trailer's `Plaintext size` | Incomplete or truncated |
+| Header `Plaintext size` disagrees with the trailer's | Damaged |
+| Output fails the SQLite header check | Damaged |
+
+A verifier mismatch alone cannot distinguish a wrong passphrase from a bit flip in the salt, nonce prefix or tag. Two recoveries follow from the header layout:
+
+* Check the payload digest. Intact means the passphrase really is wrong.
+* Skip the verifier and attempt frame 0. This succeeds when the damage was confined to the verifier tag, because the tag lies outside the authenticated header.
+
+### Version history
+
+| Version | Change |
+| --- | --- |
+| 1 | Initial format |
+
+The format was reshaped before it shipped, and the version byte was deliberately left at 1: no container written by the old layout exists outside development, so there was nothing to stay compatible with. The two layouts are in any case distinguishable by header length, 64 or 108 against 40 or 84, should anything ever need to tell them apart.
+
+Extension rules:
+
+* Fields may only be appended, before the verifier tag and payload digest, and the version byte is raised when they are. `Header length` locates the payload without parsing the fields, and the authenticated header covers appended fields automatically.
+* Reserved flag bits may be assigned meanings without raising the version, because older readers already reject a bit they do not know. Prefer a flag over a version bump for anything that does not change the layout: it keeps every unaffected file readable by every existing reader.
+* A flag that changes what a reader must verify must say what stands in for the check it removes, and the substitute must be mandatory rather than advisory. Prefer not to have one: a check that every container carries is worth more than a flag that lets some of them skip it.
+* Fields that are only knowable once the payload is written belong in the trailer, never in the header, so that no writer ever has to seek and every destination can hold the format.
+* Version `0` is never valid, because it is what a zero-filled or truncated file produces.
+* The authenticated header is included in every frame's AAD verbatim, which is 68 bytes in version 1 and therefore free. A version that grows it to kilobytes should switch the frame AAD to a digest of it, so that per-frame authentication stays constant-cost.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Project Structure.md b/docs/Developer Guide/Developer Guide/Project Structure.md
new file mode 100644
index 0000000000..2e2a5438d4
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Project Structure.md
@@ -0,0 +1,30 @@
+# Project Structure
+As the application grew in complexity, we decided to switch to a monorepo based on `pnpm`. Our initial monorepo implementation used NX, but we've switched to pure `pnpm` workspaces and our own build scripts.
+
+## Project structure
+
+The mono-repo is mainly structured in:
+
+* `apps`, representing runnable entry-points such as the `desktop`, the `server` but also additional tooling.
+ * `client`, representing the front-end that is used both by the server and the desktop application.
+ * `server`, representing the Node.js / server version of the application.
+ * `desktop`, representing the Electron-based desktop application.
+ * `web-clipper`, representing the browser extension to easily clip web pages into Trilium, with support for both Firefox and Chrome (manifest V3).
+* `packages`, containing dependencies used by one or more `apps`.
+ * `commons`, containing shared code for all the apps.
+
+## Working with the project
+
+For example to run the server instance:
+
+```
+pnpm server:start
+```
+
+## Running and building
+
+Each application has a number of tasks. Here's a non-exhaustive list of the tasks that are useful during development. See <a class="reference-link" href="Building">Building</a>.
+
+## Managing dependencies across the mono-repo
+
+We are using [pnpm workspaces](https://pnpm.io/workspaces) to manage the project structure. The workspace configuration is in `pnpm-workspace.yaml` at project level but it generally should not be modified.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Testing.md b/docs/Developer Guide/Developer Guide/Testing.md
new file mode 100644
index 0000000000..77508ac347
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Testing.md
@@ -0,0 +1,97 @@
+# Testing
+### Test Organization
+
+**Parallel Tests** (can run simultaneously):
+
+* Client tests
+* Package tests
+* E2E tests (isolated databases)
+
+**Sequential Tests** (shared resources):
+
+* Server tests (shared database)
+* CKEditor plugin tests
+
+### Test Frameworks
+
+* **Vitest** - Unit and integration tests
+* **Playwright** - E2E tests
+* **Happy-DOM** - DOM testing environment
+
+## Test locations
+
+```
+apps/
+├── server/
+│ └── src/**/*.spec.ts # Server tests
+├── client/
+│ └── src/**/*.spec.ts # Client tests
+├── server/
+│ └── e2e/**/*.spec.ts # Server-specific E2E tests
+└── desktop/
+ └── e2e/**/*.spec.ts # Desktop E2E tests
+packages/
+└── trilium-e2e/
+ └── src/**/*.spec.ts # Shared E2E tests
+```
+
+## Running tests
+
+At project root:
+
+```
+pnpm test:all # All tests
+pnpm test:parallel # Fast parallel tests
+pnpm test:sequential # Sequential tests only
+```
+
+## Unit testing and integration testing
+
+Using `vitest`, there are some unit and integration tests done for both the client and the server.
+
+These tests can be found by looking for the corresponding `.spec.ts` in the same directory as the source file.
+
+<table>
+ <tbody>
+ <tr>
+ <td><p>To run the server-side tests:</p><pre><code class="language-text-x-trilium-auto">npm run server:test</code></pre><p>To view the code coverage for the server:</p><pre><code class="language-text-x-trilium-auto">npm run server:coverage</code></pre><p>Afterwards, a friendly HTML report can be found in <code>/coverage/index.html</code>.</p></td>
+ <td><p>To run the client-side tests:</p><pre><code class="language-text-x-trilium-auto">npm run client:test</code></pre><p>To view the code coverage for the client:</p><pre><code class="language-text-x-trilium-auto">npm run client:coverage</code></pre><p>Afterwards, a friendly HTML report can be found in <code>/src/public/app/coverage/index.html</code>.</p></td>
+ </tr>
+ </tbody>
+</table>
+
+To run both client and server-side tests:
+
+```
+npm run test
+```
+
+Note that some integration tests rely on an in-memory database in order to function. 
+
+### Browser-mode tests for the text editor
+
+`packages/ckeditor5` runs its tests in a real headless Chromium, through `@vitest/browser-playwright`, because the editor needs a real DOM and real selection handling. Playwright downloads the browser itself; install it once with `pnpm exec playwright install chromium` from the repository root.
+
+Where that downloaded browser cannot run — NixOS being the case in point, since it is dynamically linked against libraries no store path provides and dies on a missing `libxcb.so.1` — point the suite at a system browser instead:
+
+```
+CHROME_BIN=/path/to/chromium pnpm --filter @triliumnext/ckeditor5 test
+```
+
+`CHROME_BIN` is read by the package's `vitest.config.ts` and passed to the provider as `launchOptions.executablePath`, so Playwright launches that binary rather than its own download. There is no separate driver to supply — Playwright speaks CDP to the browser directly.
+
+The Nix dev shell (`nix develop`) sets it from `pkgs.chromium`, so inside it the tests run unchanged.
+
+### REST API testing for the server
+
+API tests are handled via `vitest` and `supertest` to initialize the Express server and run assertions without having to make actual requests to the server.
+
+An important aspect is that we have access to the Express `app` which allows for interesting assertions such as checking the state of the server, registering debug middleware and so on.
+
+One example is `src/share/routes.spec.ts`, or for the ETAPI in `apps/server/spec/etapi`.
+
+These integration tests are run alongside unit tests.
+
+## End-to-end testing
+
+See <a class="reference-link" href="Testing/End-to-end%20tests.md">End-to-end tests</a>.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Testing/End-to-end tests.md b/docs/Developer Guide/Developer Guide/Testing/End-to-end tests.md
new file mode 100644
index 0000000000..992f57743d
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Testing/End-to-end tests.md
@@ -0,0 +1,46 @@
+# End-to-end tests
+**Server E2E:**
+
+* Tests the entire ETAPI.
+* Tests WebSocket functionality
+
+**Desktop E2E:**
+
+* Playwright with Electron
+* Tests some basic functionality such as creating a new document.
+
+Shared E2E tests live in `packages/trilium-e2e/`. Server-specific tests are in `apps/server/e2e/`, desktop tests in `apps/desktop/e2e/`.
+
+Run E2E tests via:
+
+* `pnpm --filter server e2e` (server)
+* `pnpm --filter standalone e2e` (standalone)
+* `pnpm --filter desktop e2e` (desktop/Electron)
+
+## First-time run
+
+Before starting Playwright, it has to be installed locally via:
+
+```
+pnpm playwright install
+```
+
+## Starting the integration test server
+
+Simply run `pnpm e2e` in one of the e2e projects.
+
+The integration server doesn't have authentication enabled to avoid login issues.
+
+## Starting the interactive test runner
+
+After starting the integration test server, to run the Playwright UI, run in the terminal:
+
+```
+pnpm playwright test --ui
+```
+
+It is also possible to run the interactive code generator instead:
+
+```
+pnpm playwright codegen
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Testing/Integration testing.md b/docs/Developer Guide/Developer Guide/Testing/Integration testing.md
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/docs/Developer Guide/Developer Guide/Testing/Test database.md b/docs/Developer Guide/Developer Guide/Testing/Test database.md
new file mode 100644
index 0000000000..3bbf001777
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Testing/Test database.md
@@ -0,0 +1,32 @@
+# Test database
+The integration tests do not use the same database as `pnpm server:start`. Instead, the tracked fixture database lives at `packages/trilium-core/src/test/fixtures/document.db`.
+
+## In-memory database
+
+Even though we ship our own database, there is still the problem of one test affecting the content for the others or accidentally removing important test notes.
+
+To avoid this, the test setup (`apps/server/spec/setup.ts`) loads the fixture into memory and operates from there. That means any changes made while tests run are never persisted to disk. Another benefit of having the database in memory is that test files can run in parallel (each vitest fork gets its own copy) without interfering with each other.
+
+## How to make changes to the database
+
+The database can be edited manually to add content that is relevant to the tests. To do so, run a dedicated editing server:
+
+```
+pnpm --filter server run edit-integration-db
+```
+
+This opens a server on port **8086** that attaches **directly** to the tracked fixture (`packages/trilium-core/src/test/fixtures/document.db`) via `TRILIUM_DOCUMENT_PATH`, so your changes land in the committed file — no copy step is required. Ancillary runtime files (logs, tmp, `config.ini`) still live in the git-ignored `apps/server/spec/db/`.
+
+After finishing the desired changes, close the server (Ctrl-C) to prevent any interference with further test runs.
+
+## The database is tracked by Git
+
+This is intentional: any change to the database marks the file as changed in Git as well. Some tests require a specific note and it would be too wasteful to recreate it via Playwright each time. Instead the content is added manually and the tests operate directly on those notes.
+
+To keep the database easy to track, the editing server opens it in the rollback (`DELETE`) journal mode instead of WAL (see `apps/server/src/sql_provider.ts`). This means only the single `.db` file is produced and needs to be committed — no `-wal`/`-shm` sidecars. (Those sidecars are git-ignored under the fixtures directory regardless.)
+
+## Cleaning up the database
+
+It's recommended to clean up any deleted notes to avoid unnecessary changes being committed. To do so go to Recent Changes in the launcher and select "Erase deleted notes now".
+
+It's also a good idea to go to Options → Advanced → Vacuum database to clean it up.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Testing/Unit tests.md b/docs/Developer Guide/Developer Guide/Testing/Unit tests.md
new file mode 100644
index 0000000000..a009b8d92b
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Testing/Unit tests.md
@@ -0,0 +1,7 @@
+# Unit tests
+At project level:
+
+* `pnpm server:test`
+* `pnpm client:test`
+
+Unit tests are stored in the same directory as the source code being tested, with the `.spec.ts` suffix.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Troubleshooting/A note is listed in Recent Changes but missing from the tree.md b/docs/Developer Guide/Developer Guide/Troubleshooting/A note is listed in Recent Changes but missing from the tree.md
new file mode 100644
index 0000000000..9f182ef7e3
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Troubleshooting/A note is listed in Recent Changes but missing from the tree.md
@@ -0,0 +1,40 @@
+# A note is listed in Recent Changes but missing from the tree
+## Symptom
+
+A note that was definitely created does not appear in the tree. Recent Changes lists it, but shows it as **Deleted**, and hovering or trying to restore it fails with:
+
+```
+NotFoundError: Deleted note 'X' was not found.
+```
+
+The row is live in the database. Restarting the application makes the note appear normally.
+
+This looks like Becca or Froca corruption. It usually is not.
+
+## Cause: two processes on one data directory
+
+Entity-change propagation is **in-process only**. A note created by process A goes into A's Becca and into the shared SQLite file — but process B's Becca never hears about it, because the notification never leaves A.
+
+The two views then disagree, in a way that produces exactly the symptom above:
+
+* **Recent Changes reads the database directly.** `routes/api/recent_changes.ts` queries `notes` by raw SQL, so it sees the new row.
+* **The tree and `tree/load` read Becca**, which in process B has no such note. The client renders any entry it cannot resolve through Froca as a deleted-note link.
+* **Hovering that link calls `/api/deleted-notes/:noteId/metadata`**, which selects `... WHERE noteId = ? AND isDeleted = 1` and throws `NotFoundError` when it finds nothing — and it finds nothing precisely because the note is _alive_.
+
+Restarting the second instance reloads Becca from disk, which is why the note then appears.
+
+## Confirming it
+
+Check for more than one Trilium process bound to the same data directory. On Windows:
+
+```powershell
+Get-NetTCPConnection -LocalPort 37840,37841 -State Listen | Select-Object LocalPort, OwningProcess
+```
+
+then match the owning PIDs against the running executables. An installed build and a locally built desktop app both default to `%APPDATA%\trilium-data`, so the two share `document.db` without either warning about it. They also share the daily log file, and log lines carry no PID — so one process's output is indistinguishable from the other's, which is worth knowing before reading the log for clues.
+
+The same applies to any automation pointed at a running instance: a REST or MCP client talks to whichever process owns that port, and its writes land in that process's Becca — not in the window being watched.
+
+## Avoiding it
+
+Give each instance its own data directory (`TRILIUM_DATA_DIR`) whenever two are running at once. The development server already does this by default (`apps/server/data`); the installed application and a locally built desktop app do not.
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Troubleshooting/Error [TransformError] The package @esbuildlinux-x64 could not be found, and is needed by esbuild.md b/docs/Developer Guide/Developer Guide/Troubleshooting/Error [TransformError] The package @esbuildlinux-x64 could not be found, and is needed by esbuild.md
new file mode 100644
index 0000000000..82a5d93a8f
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Troubleshooting/Error [TransformError] The package @esbuildlinux-x64 could not be found, and is needed by esbuild.md
@@ -0,0 +1,40 @@
+# Error [TransformError]: The package "@esbuild/linux-x64" could not be found, and is needed by esbuild.
+Full log:
+
+```
+> [email protected] start-server
+> cross-env TRILIUM_DATA_DIR=./data TRILIUM_ENV=dev TRILIUM_SYNC_SERVER_HOST=http://tsyncserver:4000 nodemon src/main.ts
+
+[nodemon] 3.1.9
+[nodemon] to restart at any time, enter `rs`
+[nodemon] watching path(s): src/**/* translations/**/*
+[nodemon] watching extensions: ts,js,json
+[nodemon] starting `tsx src/main.ts`
+
+node:internal/process/promises:391
+ triggerUncaughtException(err, true /* fromPromise */);
+ ^
+Error [TransformError]: The package "@esbuild/linux-x64" could not be found, and is needed by esbuild.
+
+If you are installing esbuild with npm, make sure that you don't specify the
+"--no-optional" or "--omit=optional" flags. The "optionalDependencies" feature
+of "package.json" is used by esbuild to install the correct binary executable
+for your current platform.
+ at generateBinPath (/home/elian/Projects/TriliumNext/Notes/node_modules/esbuild/lib/main.js:1752:15)
+ at esbuildCommandAndArgs (/home/elian/Projects/TriliumNext/Notes/node_modules/esbuild/lib/main.js:1822:33)
+ at ensureServiceIsRunning (/home/elian/Projects/TriliumNext/Notes/node_modules/esbuild/lib/main.js:1979:25)
+ at transform (/home/elian/Projects/TriliumNext/Notes/node_modules/esbuild/lib/main.js:1880:37)
+ at file:///home/elian/Projects/TriliumNext/Notes/node_modules/tsx/dist/index-DlKgSVBb.mjs:16:2755
+ at applyTransformers (file:///home/elian/Projects/TriliumNext/Notes/node_modules/tsx/dist/index-DlKgSVBb.mjs:16:1266)
+ at transform (file:///home/elian/Projects/TriliumNext/Notes/node_modules/tsx/dist/index-DlKgSVBb.mjs:16:2702)
+ at load (file:///home/elian/Projects/TriliumNext/Notes/node_modules/tsx/dist/esm/index.mjs?1734213798404:2:2245)
+ at async nextLoad (node:internal/modules/esm/hooks:868:22)
+ at async Hooks.load (node:internal/modules/esm/hooks:451:20)
+```
+
+The solution is to remove `node_modules` and reinstall all dependencies:
+
+```
+rm -r node_modules
+pnpm install
+```
\ No newline at end of file
diff --git a/docs/Developer Guide/Developer Guide/Troubleshooting/better-sqlite3 was compiled against a different Node.js version.md b/docs/Developer Guide/Developer Guide/Troubleshooting/better-sqlite3 was compiled against a different Node.js version.md
new file mode 100644
index 0000000000..a048e3b4ea
--- /dev/null
+++ b/docs/Developer Guide/Developer Guide/Troubleshooting/better-sqlite3 was compiled against a different Node.js version.md
@@ -0,0 +1,6 @@
+# better-sqlite3 was compiled against a different Node.js version
+This generally can happen when running the development version of either the `desktop` or `server`, but it should not happen as often as it used to. The reason is that `better-sqlite3` is a native dependency and has different builds for either the system's Node.js (as used by the `server`), or Electron's one (as used by the `desktop`).
+
+To solve this, go to `apps/server` and run `pnpm rebuild`. For Electron (`desktop`) this step generally not necessary, however `pnpm postinstall` should solve it.
+
+If you can reproduce this issue consistently, please open a bug report.
\ No newline at end of file
diff --git a/docs/User Guide/User Guide/Collections/Kanban Board.md b/docs/User Guide/User Guide/Collections/Kanban Board.md
index 424a5ff8b1..30e5e5d294 100644
--- a/docs/User Guide/User Guide/Collections/Kanban Board.md
+++ b/docs/User Guide/User Guide/Collections/Kanban Board.md
@@ -290,7 +290,7 @@ You can remove one or more cards from the board and delete their associated note
#### Removing a card from the board without deleting the note
-To remove a card from the board's columns while keeping its note, open the card's context menu and select <span class="tn-icon bx bx-task-x"></span> **Remove from board**, or press <kbd>Delete</kbd>. On mobile, hold the card until the side toolbar appears, and then tap the <span class="tn-icon bx bx-task-x"></span> button.
+To remove a card from the board's columns while keeping its note, open the card's context menu and select <span class="tn-icon bx bx-task-x"></span> **Remove from column**, or press <kbd>Delete</kbd>. On mobile, hold the card until the side toolbar appears, and then tap the <span class="tn-icon bx bx-task-x"></span> button.
This command is not available when the inbox column is enabled. Instead, drag the card to the inbox column to achieve the same result.