Skip to content

Build your personal knowledge base with Trilium Notes

docs(user): sync table churn

Elian Doran4ecc8dd324a5
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes.html
index 3ca86d0e77..b5a3a5815e 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes.html
@@ -21,158 +21,160 @@
select <em>Advanced</em> → <em>Show Hidden Subtree</em>.</p>
<h2>Contents of the hidden note tree</h2>
<p>Here is a brief summary of all the notes within the hidden tree:</p>
-<table
-class="ck-table-resized">
- <colgroup>
- <col style="width:19.93%;">
- <col style="width:80.07%;">
- </colgroup>
- <thead>
- <tr>
- <th>Note</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_globalNoteMap">Note Map</a>
- </td>
- <td>
- <p>This note is actually opened when the&nbsp;<a class="reference-link" href="#root/_help_bdUJEHsAPYQR">Note Map</a>&nbsp;feature
- that is accessed from the&nbsp;<a class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>.</p>
- <p>It is possible to create any child notes in it without any additional
- meaning. For example, it can be used to store a list of note maps which
- can be linked to from other notes or <a href="#root/_help_u3YFHC9tQlpm">bookmarked</a>.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_sqlConsole">SQL Console History</a>
- </td>
- <td>
- <p>When SQL queries or commands are executed in the&nbsp;<a class="reference-link"
- href="#root/_help_YKWqdJhzi2VY">SQL Console</a>, they are stored here, grouped
- by month. Only the query is stored and not the results.</p>
- <p>This section can be accessed without going to the hidden tree by simply
- going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
- selecting Advanced → Open SQL Console History.</p>
- <p>Notes can be added as children of this tree, but it's generally not recommended
- to do so to not interfere with the normal history process.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_search">Search History</a>
- </td>
- <td>
- <p>Whenever a search is executed from the full&nbsp;<a class="reference-link"
- href="#root/_help_eIg8jdvaoNNd">Search</a>, the query will be stored here, grouped
- by month. Only the search parameters are stored and not the results themselves.</p>
- <p>This section can be accessed without going to the hidden tree by simply
- going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
- selecting Advanced → Open Search History.</p>
- <p>Notes can be added as children of this tree, but it's generally not recommended
- to do so to not interfere with the normal history process.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_bulkAction">Bulk Action</a>
- </td>
- <td>
- <p>This section is used for&nbsp;<a class="reference-link" href="#root/_help_ivYnonVFBxbQ">Bulk Actions</a>.
- The last configuration for bulk actions will be stored as part of this
- note, each action in its own <code>action</code> label.</p>
- <p>Notes can be added as children of this tree, but there won't be any benefit
- in doing so.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_backendLog">Backend Log</a>
- </td>
- <td>
- <p>This note corresponds to the backend log feature (see&nbsp;<a class="reference-link"
- href="#root/_help_qzNzp9LYQyPT">Error logs</a>).</p>
- <p>This item can be accessed without going to the hidden try by going to
- the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
- selecting Advanced → Show backend log.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_userHidden">User Hidden</a>
- </td>
- <td>This section can be used by <a href="#root/_help_CdNpE2pqjmI6">scripts</a> to
- create their own notes that should not be directly visible to the user.
- The note can be identified by scripts by its unique ID: <code>_userHidden</code>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_lbTplRoot">Launch Bar Templates</a>
- </td>
- <td>
- <p>This section contains the templates for the creation of launchers in the&nbsp;
- <a
- class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>. It is not possible to create child notes here.</p>
- <p>Theoretically some of the notes here can be customized, but there's not
- much benefit to be had in doing so.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_share">Shared Notes</a>
- </td>
- <td>
- <p>This tree lists all of the notes that are <a href="#root/_help_R9pX4DGra2Vt">shared</a> publicly.
- It can be useful to track down which notes are shared regardless of their
- position in the note tree.</p>
- <p>This section can be accessed without going to the hidden tree simply by
- going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
- selecting <em>Show Shared Notes Subtree</em>.</p>
- <p>Sub-notes cannot be created here.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_lbRoot">Launch Bar</a>
- </td>
- <td>
- <p>The tree contains both available and displayed items of the&nbsp;<a class="reference-link"
- href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>.</p>
- <p>This section can be accessed without going to the hidden tree by:</p>
- <ul>
- <li>Going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
- selecting <em>Configure Launchbar</em>.</li>
- <li>Right-clicking an empty space on the&nbsp;<a class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>&nbsp;and
- selecting <em>Configure Launchbar</em>.</li>
- </ul>
- <p>Sub-notes cannot be created here.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_options">Options</a>
- </td>
- <td>
- <p>This section stores the list of&nbsp;<a class="reference-link" href="#root/_help_4TIF1oA4VQRO">Options</a>.</p>
- <p>This section can be accessed without going to the hidden tree by:</p>
- <ul>
- <li>Going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
- selecting <em>Options</em>.</li>
- <li>Pressing the dedicated Options icon in the&nbsp;<a class="reference-link"
- href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_lbMobileRoot">Mobile Launch Bar</a>
- </td>
- <td>
- <p>This is very similar to the <em>Launch Bar</em>, but is dedicated for the
- mobile UI only.</p>
- <p>Accessing it outside the <em>Launch Bar</em> is the same as the Launch Bar,
- but needs to be done so from the mobile interface.</p>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_hidden/_help">User Guide</a>
- </td>
- <td>This is where the note structure for the User Guide is actually stored.
- Only the metadata is stored, as the help itself is present as actual files
- in the application directory.</td>
- </tr>
- </tbody>
- </table>
\ No newline at end of file
+<figure
+class="table">
+ <table class="ck-table-resized">
+ <colgroup>
+ <col style="width:19.93%;">
+ <col style="width:80.07%;">
+ </colgroup>
+ <thead>
+ <tr>
+ <th>Note</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_globalNoteMap">Note Map</a>
+ </td>
+ <td>
+ <p>This note is actually opened when the&nbsp;<a class="reference-link" href="#root/_help_bdUJEHsAPYQR">Note Map</a>&nbsp;feature
+ that is accessed from the&nbsp;<a class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>.</p>
+ <p>It is possible to create any child notes in it without any additional
+ meaning. For example, it can be used to store a list of note maps which
+ can be linked to from other notes or <a href="#root/_help_u3YFHC9tQlpm">bookmarked</a>.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_sqlConsole">SQL Console History</a>
+ </td>
+ <td>
+ <p>When SQL queries or commands are executed in the&nbsp;<a class="reference-link"
+ href="#root/_help_YKWqdJhzi2VY">SQL Console</a>, they are stored here, grouped
+ by month. Only the query is stored and not the results.</p>
+ <p>This section can be accessed without going to the hidden tree by simply
+ going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
+ selecting Advanced → Open SQL Console History.</p>
+ <p>Notes can be added as children of this tree, but it's generally not recommended
+ to do so to not interfere with the normal history process.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_search">Search History</a>
+ </td>
+ <td>
+ <p>Whenever a search is executed from the full&nbsp;<a class="reference-link"
+ href="#root/_help_eIg8jdvaoNNd">Search</a>, the query will be stored here, grouped
+ by month. Only the search parameters are stored and not the results themselves.</p>
+ <p>This section can be accessed without going to the hidden tree by simply
+ going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
+ selecting Advanced → Open Search History.</p>
+ <p>Notes can be added as children of this tree, but it's generally not recommended
+ to do so to not interfere with the normal history process.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_bulkAction">Bulk Action</a>
+ </td>
+ <td>
+ <p>This section is used for&nbsp;<a class="reference-link" href="#root/_help_ivYnonVFBxbQ">Bulk Actions</a>.
+ The last configuration for bulk actions will be stored as part of this
+ note, each action in its own <code>action</code> label.</p>
+ <p>Notes can be added as children of this tree, but there won't be any benefit
+ in doing so.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_backendLog">Backend Log</a>
+ </td>
+ <td>
+ <p>This note corresponds to the backend log feature (see&nbsp;<a class="reference-link"
+ href="#root/_help_qzNzp9LYQyPT">Error logs</a>).</p>
+ <p>This item can be accessed without going to the hidden try by going to
+ the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
+ selecting Advanced → Show backend log.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_userHidden">User Hidden</a>
+ </td>
+ <td>This section can be used by <a href="#root/_help_CdNpE2pqjmI6">scripts</a> to
+ create their own notes that should not be directly visible to the user.
+ The note can be identified by scripts by its unique ID: <code>_userHidden</code>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_lbTplRoot">Launch Bar Templates</a>
+ </td>
+ <td>
+ <p>This section contains the templates for the creation of launchers in the&nbsp;
+ <a
+ class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>. It is not possible to create child notes here.</p>
+ <p>Theoretically some of the notes here can be customized, but there's not
+ much benefit to be had in doing so.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_share">Shared Notes</a>
+ </td>
+ <td>
+ <p>This tree lists all of the notes that are <a href="#root/_help_R9pX4DGra2Vt">shared</a> publicly.
+ It can be useful to track down which notes are shared regardless of their
+ position in the note tree.</p>
+ <p>This section can be accessed without going to the hidden tree simply by
+ going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
+ selecting <em>Show Shared Notes Subtree</em>.</p>
+ <p>Sub-notes cannot be created here.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_lbRoot">Launch Bar</a>
+ </td>
+ <td>
+ <p>The tree contains both available and displayed items of the&nbsp;<a class="reference-link"
+ href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>.</p>
+ <p>This section can be accessed without going to the hidden tree by:</p>
+ <ul>
+ <li>Going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
+ selecting <em>Configure Launchbar</em>.</li>
+ <li>Right-clicking an empty space on the&nbsp;<a class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>&nbsp;and
+ selecting <em>Configure Launchbar</em>.</li>
+ </ul>
+ <p>Sub-notes cannot be created here.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_options">Options</a>
+ </td>
+ <td>
+ <p>This section stores the list of&nbsp;<a class="reference-link" href="#root/_help_4TIF1oA4VQRO">Options</a>.</p>
+ <p>This section can be accessed without going to the hidden tree by:</p>
+ <ul>
+ <li>Going to the&nbsp;<a class="reference-link" href="#root/_help_x3i7MxGccDuM">Global menu</a>&nbsp;and
+ selecting <em>Options</em>.</li>
+ <li>Pressing the dedicated Options icon in the&nbsp;<a class="reference-link"
+ href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_lbMobileRoot">Mobile Launch Bar</a>
+ </td>
+ <td>
+ <p>This is very similar to the <em>Launch Bar</em>, but is dedicated for the
+ mobile UI only.</p>
+ <p>Accessing it outside the <em>Launch Bar</em> is the same as the Launch Bar,
+ but needs to be done so from the mobile interface.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_hidden/_help">User Guide</a>
+ </td>
+ <td>This is where the note structure for the User Guide is actually stored.
+ Only the metadata is stored, as the help itself is present as actual files
+ in the application directory.</td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
\ No newline at end of file
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Sharing.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Sharing.html
index 44d71bedb5..a581460179 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Sharing.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Advanced Usage/Sharing.html
@@ -18,153 +18,155 @@ class="image">
<li>Displaying the date of the last update of the note.</li>
</ul>
<h3>By note type</h3>
- <table class="ck-table-resized">
- <colgroup>
- <col style="width:19.92%;">
- <col style="width:41.66%;">
- <col style="width:38.42%;">
- </colgroup>
- <thead>
- <tr>
- <th>&nbsp;</th>
- <th>Supported features</th>
- <th>Limitations</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <th><a class="reference-link" href="#root/_help_iPIMuisry3hd">Text</a>
- </th>
- <td>
- <ul>
- <li>Table of contents.</li>
- <li>Syntax highlight of code blocks, provided a language is selected (does
- not work if “Auto-detected” is enabled).</li>
- <li>Rendering for math equations.</li>
- <li><a href="#root/_help_nBAXQFj20hS1">Including notes</a> (only if the included
- notes are also shared).</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Inline Mermaid diagrams are not rendered.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_6f9hih2hXXZk">Code</a>
- </th>
- <td>
- <ul>
- <li>Basic support (displaying the contents of the note in a monospace font).</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>No syntax highlight.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_m523cpzocqaD">Saved Search</a>
- </th>
- <td>Not supported.</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_iRwzGnHPzonm">Relation Map</a>
- </th>
- <td>Not supported.</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_bdUJEHsAPYQR">Note Map</a>
- </th>
- <td>Not supported.</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_HcABDtFCkbFN">Render Note</a>
- </th>
- <td>Not supported.</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_GTwFsgaA0lCt">Collections</a>
- </th>
- <td>
- <ul>
- <li>The child notes are displayed in a fixed format.&nbsp;</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>More advanced view types such as the calendar view are not supported.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_s1aBHPd79XYj">Mermaid Diagrams</a>
- </th>
- <td>
- <ul>
- <li>The diagram is displayed as a vector image.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>No further interaction supported.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_grjYqerjn243">Canvas</a>
- </th>
- <td>
- <ul>
- <li>The diagram is displayed as a vector image.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>No further interaction supported.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_1vHRoWCEjj0L">Web View</a>
- </th>
- <td>Not supported.</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_gBbsAeiuUxI5">Mind Map</a>
- </th>
- <td>The diagram is displayed as a vector image.</td>
- <td>
- <ul>
- <li>No further interaction supported.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_81SGnPGMk7Xc">Geo Map</a>
- </th>
- <td>Not supported.</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <th><a class="reference-link" href="#root/_help_W8vYD3Q1zjCR">File</a>
- </th>
- <td>Basic interaction (downloading the file).</td>
- <td>
- <ul>
- <li>No further interaction supported.</li>
- </ul>
- </td>
- </tr>
- </tbody>
- </table>
+ <figure class="table">
+ <table class="ck-table-resized">
+ <colgroup>
+ <col style="width:19.92%;">
+ <col style="width:41.66%;">
+ <col style="width:38.42%;">
+ </colgroup>
+ <thead>
+ <tr>
+ <th>&nbsp;</th>
+ <th>Supported features</th>
+ <th>Limitations</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_iPIMuisry3hd">Text</a>
+ </th>
+ <td>
+ <ul>
+ <li>Table of contents.</li>
+ <li>Syntax highlight of code blocks, provided a language is selected (does
+ not work if “Auto-detected” is enabled).</li>
+ <li>Rendering for math equations.</li>
+ <li><a href="#root/_help_nBAXQFj20hS1">Including notes</a> (only if the included
+ notes are also shared).</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>Inline Mermaid diagrams are not rendered.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_6f9hih2hXXZk">Code</a>
+ </th>
+ <td>
+ <ul>
+ <li>Basic support (displaying the contents of the note in a monospace font).</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>No syntax highlight.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_m523cpzocqaD">Saved Search</a>
+ </th>
+ <td>Not supported.</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_iRwzGnHPzonm">Relation Map</a>
+ </th>
+ <td>Not supported.</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_bdUJEHsAPYQR">Note Map</a>
+ </th>
+ <td>Not supported.</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_HcABDtFCkbFN">Render Note</a>
+ </th>
+ <td>Not supported.</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_GTwFsgaA0lCt">Collections</a>
+ </th>
+ <td>
+ <ul>
+ <li>The child notes are displayed in a fixed format.&nbsp;</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>More advanced view types such as the calendar view are not supported.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_s1aBHPd79XYj">Mermaid Diagrams</a>
+ </th>
+ <td>
+ <ul>
+ <li>The diagram is displayed as a vector image.</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>No further interaction supported.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_grjYqerjn243">Canvas</a>
+ </th>
+ <td>
+ <ul>
+ <li>The diagram is displayed as a vector image.</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>No further interaction supported.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_1vHRoWCEjj0L">Web View</a>
+ </th>
+ <td>Not supported.</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_gBbsAeiuUxI5">Mind Map</a>
+ </th>
+ <td>The diagram is displayed as a vector image.</td>
+ <td>
+ <ul>
+ <li>No further interaction supported.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_81SGnPGMk7Xc">Geo Map</a>
+ </th>
+ <td>Not supported.</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <th><a class="reference-link" href="#root/_help_W8vYD3Q1zjCR">File</a>
+ </th>
+ <td>Basic interaction (downloading the file).</td>
+ <td>
+ <ul>
+ <li>No further interaction supported.</li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
<p>While the sharing feature is powerful, it has some limitations:</p>
<ul>
<li><strong>Code Notes</strong>: No syntax highlighting.</li>
@@ -353,100 +355,102 @@ for (const attr of parentNote.attributes) {
by its direct URL — the label only changes how links to it behave.</p>
</aside>
<h2>Attribute reference</h2>
- <table class="ck-table-resized">
- <colgroup>
- <col style="width:18.38%;">
- <col style="width:81.62%;">
- </colgroup>
- <thead>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><code spellcheck="false">#shareHiddenFromTree</code>
- </td>
- <td>this note is hidden from left navigation tree, but still accessible with
- its URL</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareExternalLink</code>
- </td>
- <td>when a link points to this note (from the share index, a subpage list,
- or an inline link in another shared note), it redirects to the given external
- URL in a new tab instead of the note's shared page. Value is the absolute
- URL, e.g. <code spellcheck="false">https://example.com</code>.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareAlias</code>
- </td>
- <td>define an alias using which the note will be available under <code spellcheck="false">https://your_trilium_host/share/[your_alias]</code>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareOmitDefaultCss</code>
- </td>
- <td>default share page CSS will be omitted. Use when you make extensive styling
- changes.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareRoot</code>
- </td>
- <td>marks note which is served on /share root.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareDescription</code>
- </td>
- <td>define text to be added to the HTML meta tag for description</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareRaw</code>
- </td>
- <td>Note will be served in its raw format, without HTML wrapper. See also&nbsp;
- <a
- class="reference-link" href="#root/_help_Qjt68inQ2bRj">Serving directly the content of a note</a>&nbsp;for an alternative method
- without setting an attribute.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareDisallowRobotIndexing</code>
- </td>
- <td>
- <p>Indicates to web crawlers that the page should not be indexed of this
- note by:</p>
- <ul>
- <li>Setting the <code spellcheck="false">X-Robots-Tag: noindex</code> HTTP header.</li>
- <li>Setting the <code spellcheck="false">noindex, follow</code> meta tag.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareCredentials</code>
- </td>
- <td>require credentials to access this shared note. Value is expected to be
- in format <code spellcheck="false">username:password</code>. Don't forget
- to make this inheritable to apply to child-notes/images.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareIndex</code>
- </td>
- <td>Note with this label will list all roots of shared notes.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#shareHtmlLocation</code>
- </td>
- <td>defines where custom HTML injected via <code spellcheck="false">~shareHtml</code> relation
- should be placed. Applied to the HTML snippet note itself. Format:
- <code
- spellcheck="false">location:position</code>where location is <code spellcheck="false">head</code>,
+ <figure class="table">
+ <table class="ck-table-resized">
+ <colgroup>
+ <col style="width:18.38%;">
+ <col style="width:81.62%;">
+ </colgroup>
+ <thead>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code spellcheck="false">#shareHiddenFromTree</code>
+ </td>
+ <td>this note is hidden from left navigation tree, but still accessible with
+ its URL</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareExternalLink</code>
+ </td>
+ <td>when a link points to this note (from the share index, a subpage list,
+ or an inline link in another shared note), it redirects to the given external
+ URL in a new tab instead of the note's shared page. Value is the absolute
+ URL, e.g. <code spellcheck="false">https://example.com</code>.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareAlias</code>
+ </td>
+ <td>define an alias using which the note will be available under <code spellcheck="false">https://your_trilium_host/share/[your_alias]</code>
+ </td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareOmitDefaultCss</code>
+ </td>
+ <td>default share page CSS will be omitted. Use when you make extensive styling
+ changes.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareRoot</code>
+ </td>
+ <td>marks note which is served on /share root.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareDescription</code>
+ </td>
+ <td>define text to be added to the HTML meta tag for description</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareRaw</code>
+ </td>
+ <td>Note will be served in its raw format, without HTML wrapper. See also&nbsp;
+ <a
+ class="reference-link" href="#root/_help_Qjt68inQ2bRj">Serving directly the content of a note</a>&nbsp;for an alternative method
+ without setting an attribute.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareDisallowRobotIndexing</code>
+ </td>
+ <td>
+ <p>Indicates to web crawlers that the page should not be indexed of this
+ note by:</p>
+ <ul>
+ <li>Setting the <code spellcheck="false">X-Robots-Tag: noindex</code> HTTP header.</li>
+ <li>Setting the <code spellcheck="false">noindex, follow</code> meta tag.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareCredentials</code>
+ </td>
+ <td>require credentials to access this shared note. Value is expected to be
+ in format <code spellcheck="false">username:password</code>. Don't forget
+ to make this inheritable to apply to child-notes/images.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareIndex</code>
+ </td>
+ <td>Note with this label will list all roots of shared notes.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#shareHtmlLocation</code>
+ </td>
+ <td>defines where custom HTML injected via <code spellcheck="false">~shareHtml</code> relation
+ should be placed. Applied to the HTML snippet note itself. Format:
<code
- spellcheck="false">body</code>, or <code spellcheck="false">content</code> and position is
+ spellcheck="false">location:position</code>where location is <code spellcheck="false">head</code>,
<code
- spellcheck="false">start</code>or <code spellcheck="false">end</code>. Defaults to <code spellcheck="false">content:end</code>.</td>
- </tr>
- </tbody>
- </table>
+ spellcheck="false">body</code>, or <code spellcheck="false">content</code> and position is
+ <code
+ spellcheck="false">start</code>or <code spellcheck="false">end</code>. Defaults to <code spellcheck="false">content:end</code>.</td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
<h3>Customizing logo</h3>
<p>It's possible to adjust the logo which is displayed on the top-left of
the left pane.</p>
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export.html
index 0472f62fe9..c794051ccc 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export.html
@@ -63,42 +63,44 @@
<p>You can easily move the notes onto the root using the tree's&nbsp;<a class="reference-link"
href="#root/_help_yTjUdsOi4CIE">Multiple selection</a>&nbsp;and delete the redundant
root note.</p>
-<table>
- <thead>
- <tr>
- <th scope="col">Before</th>
- <th scope="col">After</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- <ul>
- <li>root
- <ul>
- <li>one</li>
- <li>two</li>
- </ul>
- </li>
- </ul>
- </td>
- <td>
- <ul>
- <li>root (existing)
- <ul>
- <li>root (from import)
- <ul>
- <li>one</li>
- <li>two</li>
- </ul>
- </li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- </tbody>
-</table>
+<figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th scope="col">Before</th>
+ <th scope="col">After</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ <ul>
+ <li>root
+ <ul>
+ <li>one</li>
+ <li>two</li>
+ </ul>
+ </li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>root (existing)
+ <ul>
+ <li>root (from import)
+ <ul>
+ <li>one</li>
+ <li>two</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
<aside class="admonition tip">
<p>Instead of exporting full ZIPs (including the root note), consider using
<a
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Anytype.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Anytype.html
index 601670b0c0..5fa50fa647 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Anytype.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Anytype.html
@@ -107,54 +107,56 @@
as fallback for unsupported collection layouts.</li>
</ul>
<p>The following types are supported:</p>
-<table>
- <thead>
- <tr>
- <th scope="col">Anytype property type</th>
- <th scope="col">Trilium</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>Text / Select</td>
- <td>Single-valued <code spellcheck="false">text</code> label</td>
- </tr>
- <tr>
- <td>Number</td>
- <td>Single-valued <code spellcheck="false">number</code> label</td>
- </tr>
- <tr>
- <td>Multi-select</td>
- <td>One <code spellcheck="false">text</code> label per option (multi)</td>
- </tr>
- <tr>
- <td>Date / Date with time</td>
- <td>
- <ul>
- <li><code spellcheck="false">datetime</code> if the time is included.</li>
- <li><code spellcheck="false">date</code> if only dates.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>File</td>
- <td>The files are preserved as attachments, and a link to them is prepended
- to the content of the note for visibility.</td>
- </tr>
- <tr>
- <td>Checkbox</td>
- <td><code spellcheck="false">boolean</code> label (<code spellcheck="false">true</code>/
- <code
- spellcheck="false">false</code>).</td>
- </tr>
- <tr>
- <td>URL / Email / Phone</td>
- <td><code spellcheck="false">url</code> label (<code spellcheck="false">mailto:</code>,
- <code
- spellcheck="false">tel:</code>prefix)</td>
- </tr>
- </tbody>
-</table>
+<figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th scope="col">Anytype property type</th>
+ <th scope="col">Trilium</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Text / Select</td>
+ <td>Single-valued <code spellcheck="false">text</code> label</td>
+ </tr>
+ <tr>
+ <td>Number</td>
+ <td>Single-valued <code spellcheck="false">number</code> label</td>
+ </tr>
+ <tr>
+ <td>Multi-select</td>
+ <td>One <code spellcheck="false">text</code> label per option (multi)</td>
+ </tr>
+ <tr>
+ <td>Date / Date with time</td>
+ <td>
+ <ul>
+ <li><code spellcheck="false">datetime</code> if the time is included.</li>
+ <li><code spellcheck="false">date</code> if only dates.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td>File</td>
+ <td>The files are preserved as attachments, and a link to them is prepended
+ to the content of the note for visibility.</td>
+ </tr>
+ <tr>
+ <td>Checkbox</td>
+ <td><code spellcheck="false">boolean</code> label (<code spellcheck="false">true</code>/
+ <code
+ spellcheck="false">false</code>).</td>
+ </tr>
+ <tr>
+ <td>URL / Email / Phone</td>
+ <td><code spellcheck="false">url</code> label (<code spellcheck="false">mailto:</code>,
+ <code
+ spellcheck="false">tel:</code>prefix)</td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
<h2>Reporting issues</h2>
<p>When importing your Anytype notes, you might find issues in how a note
is imported; in that case consider <a href="#root/_help_wy8So3yZZlH9">reporting</a> it.</p>
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Notion.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Notion.html
index 43c0470e28..c2dfef2ba7 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Notion.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Import & Export/Importing data from other applications/Notion.html
@@ -101,96 +101,98 @@
of the original view the database was exported in. That's because the active
view is not saved in the export and the table collection is the most compatible
with Notion.</p>
-<table>
- <thead>
- <tr>
- <th scope="col">Notion type</th>
- <th scope="col">Trilium</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>Text / Select / Status / Place</td>
- <td>Single-valued <code spellcheck="false">text</code> label</td>
- </tr>
- <tr>
- <td>Number</td>
- <td>Single-valued <code spellcheck="false">number</code> label for plain numbers.
- Formatted values (currency, percent, thousands separators) are normalized
- to a bare number, e.g. <code spellcheck="false">$1,200.50</code> → <code spellcheck="false">1200.50</code>.</td>
- </tr>
- <tr>
- <td>ID</td>
- <td>Single-valued <code spellcheck="false">number</code> or <code spellcheck="false">text</code> label
- (depending on whether a prefix is configured)</td>
- </tr>
- <tr>
- <td>Multi-select</td>
- <td>One text label per option (multi)</td>
- </tr>
- <tr>
- <td>URL / Email / Phone</td>
- <td><code spellcheck="false">url</code> label (<code spellcheck="false">mailto:</code>,
- <code
- spellcheck="false">tel:</code>prefix)</td>
- </tr>
- <tr>
- <td>Date</td>
- <td>
- <ul>
- <li><code spellcheck="false">datetime</code> if at least one has time.</li>
- <li><code spellcheck="false">date</code> if only dates.</li>
- <li>Two attributes if any of the dates have an end date.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Checkbox</td>
- <td><code spellcheck="false">boolean</code> label (<code spellcheck="false">true</code>/
- <code
- spellcheck="false">false</code>).</td>
- </tr>
- <tr>
- <td>Person</td>
- <td>One text label per user (multi)</td>
- </tr>
- <tr>
- <td>Created by / Edited by</td>
- <td>Single-valued <code spellcheck="false">text</code> label</td>
- </tr>
- <tr>
- <td>Created time / Last edited time</td>
- <td>Assigned to the note's creation and modification date.</td>
- </tr>
- <tr>
- <td>Relation</td>
- <td>Mapped to <a href="#root/_help_Cq5X6iKQop6R">relations</a>, each link resolved
- to its target note via the existing cross-page map; targets outside the
- import are dropped.</td>
- </tr>
- <tr>
- <td>Files &amp; Media</td>
- <td>The files are preserved as attachments, and a link to them is prepended
- to the content of the note for visibility.</td>
- </tr>
- <tr>
- <td>Formulas / Rollup</td>
- <td>
- <p>A <code spellcheck="false">text</code>, <code spellcheck="false">number</code> or
+<figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th scope="col">Notion type</th>
+ <th scope="col">Trilium</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Text / Select / Status / Place</td>
+ <td>Single-valued <code spellcheck="false">text</code> label</td>
+ </tr>
+ <tr>
+ <td>Number</td>
+ <td>Single-valued <code spellcheck="false">number</code> label for plain numbers.
+ Formatted values (currency, percent, thousands separators) are normalized
+ to a bare number, e.g. <code spellcheck="false">$1,200.50</code> → <code spellcheck="false">1200.50</code>.</td>
+ </tr>
+ <tr>
+ <td>ID</td>
+ <td>Single-valued <code spellcheck="false">number</code> or <code spellcheck="false">text</code> label
+ (depending on whether a prefix is configured)</td>
+ </tr>
+ <tr>
+ <td>Multi-select</td>
+ <td>One text label per option (multi)</td>
+ </tr>
+ <tr>
+ <td>URL / Email / Phone</td>
+ <td><code spellcheck="false">url</code> label (<code spellcheck="false">mailto:</code>,
+ <code
+ spellcheck="false">tel:</code>prefix)</td>
+ </tr>
+ <tr>
+ <td>Date</td>
+ <td>
+ <ul>
+ <li><code spellcheck="false">datetime</code> if at least one has time.</li>
+ <li><code spellcheck="false">date</code> if only dates.</li>
+ <li>Two attributes if any of the dates have an end date.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td>Checkbox</td>
+ <td><code spellcheck="false">boolean</code> label (<code spellcheck="false">true</code>/
<code
- spellcheck="false">boolean</code>label depending on the value. Dates are rendered as
+ spellcheck="false">false</code>).</td>
+ </tr>
+ <tr>
+ <td>Person</td>
+ <td>One text label per user (multi)</td>
+ </tr>
+ <tr>
+ <td>Created by / Edited by</td>
+ <td>Single-valued <code spellcheck="false">text</code> label</td>
+ </tr>
+ <tr>
+ <td>Created time / Last edited time</td>
+ <td>Assigned to the note's creation and modification date.</td>
+ </tr>
+ <tr>
+ <td>Relation</td>
+ <td>Mapped to <a href="#root/_help_Cq5X6iKQop6R">relations</a>, each link resolved
+ to its target note via the existing cross-page map; targets outside the
+ import are dropped.</td>
+ </tr>
+ <tr>
+ <td>Files &amp; Media</td>
+ <td>The files are preserved as attachments, and a link to them is prepended
+ to the content of the note for visibility.</td>
+ </tr>
+ <tr>
+ <td>Formulas / Rollup</td>
+ <td>
+ <p>A <code spellcheck="false">text</code>, <code spellcheck="false">number</code> or
<code
- spellcheck="false">text</code>because the export doesn't offer any type information.</p>
- <p>The Notion export does not preserve the formula/rollup configuration itself,
- instead it just exports the value.</p>
- </td>
- </tr>
- <tr>
- <td>Button / Verification / any other type</td>
- <td>Unsupported, they will be dropped from the import.</td>
- </tr>
- </tbody>
-</table>
+ spellcheck="false">boolean</code>label depending on the value. Dates are rendered as
+ <code
+ spellcheck="false">text</code>because the export doesn't offer any type information.</p>
+ <p>The Notion export does not preserve the formula/rollup configuration itself,
+ instead it just exports the value.</p>
+ </td>
+ </tr>
+ <tr>
+ <td>Button / Verification / any other type</td>
+ <td>Unsupported, they will be dropped from the import.</td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
<aside class="admonition note">
<p><strong>Technical information</strong>
</p>
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Sorting Notes.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Sorting Notes.html
index c68d8b1eb9..3d0dedb1a4 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Sorting Notes.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Sorting Notes.html
@@ -13,68 +13,70 @@
<h2>Automatic/Permanent Sorting</h2>
<p>Child notes can be automatically sorted by attaching specific <a href="#root/_help_zEY4DaJG4YT5">labels</a> to
the parent note:</p>
-<table>
- <thead>
- <tr>
- <th>Label</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><code spellcheck="false">#sorted</code>
- </td>
- <td>
- <p>Keeps child notes sorted by title alphabetically.</p>
- <p>When given a value, it will sort by the value of another label instead.
- If one of the child notes doesn't have the specified label, the title will
- be used for them instead.</p>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">#sortDirection</code>
- </td>
- <td>
- <p>If <code spellcheck="false">sorted</code> is applied, specifies the direction
- of the sort:</p>
- <ul>
- <li><code spellcheck="false">ASC</code>, ascending (default)</li>
- <li><code spellcheck="false">DESC</code>, descending</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">#sortFoldersFirst</code>
- </td>
- <td>If <code spellcheck="false">sorted</code> is applied, folders (notes with
- children) will be sorted as a group at the top, and the rest will be sorted.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#sortNatural</code>
- </td>
- <td>Sort numbers naturally instead of alphabetically, so 2 comes before 10.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#sortLocale</code>
- </td>
- <td>The language code driving the natural sort (e.g. <code spellcheck="false">zh-CN</code>,
- <code
- spellcheck="false">de</code>). Only meaningful together with <code spellcheck="false">#sortNatural</code>.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#top</code>
- </td>
- <td>If <code spellcheck="false">sorted</code> is applied to the parent note,
- keeps given note on top in its parent.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#bottom</code>
- </td>
- <td>If <code spellcheck="false">sorted</code> is applied to the parent note,
- keeps given note on bottom in its parent.</td>
- </tr>
- </tbody>
-</table>
+<figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th>Label</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code spellcheck="false">#sorted</code>
+ </td>
+ <td>
+ <p>Keeps child notes sorted by title alphabetically.</p>
+ <p>When given a value, it will sort by the value of another label instead.
+ If one of the child notes doesn't have the specified label, the title will
+ be used for them instead.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#sortDirection</code>
+ </td>
+ <td>
+ <p>If <code spellcheck="false">sorted</code> is applied, specifies the direction
+ of the sort:</p>
+ <ul>
+ <li><code spellcheck="false">ASC</code>, ascending (default)</li>
+ <li><code spellcheck="false">DESC</code>, descending</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#sortFoldersFirst</code>
+ </td>
+ <td>If <code spellcheck="false">sorted</code> is applied, folders (notes with
+ children) will be sorted as a group at the top, and the rest will be sorted.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#sortNatural</code>
+ </td>
+ <td>Sort numbers naturally instead of alphabetically, so 2 comes before 10.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#sortLocale</code>
+ </td>
+ <td>The language code driving the natural sort (e.g. <code spellcheck="false">zh-CN</code>,
+ <code
+ spellcheck="false">de</code>). Only meaningful together with <code spellcheck="false">#sortNatural</code>.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#top</code>
+ </td>
+ <td>If <code spellcheck="false">sorted</code> is applied to the parent note,
+ keeps given note on top in its parent.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#bottom</code>
+ </td>
+ <td>If <code spellcheck="false">sorted</code> is applied to the parent note,
+ keeps given note on bottom in its parent.</td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
<p>Sorting is done by comparing note properties or specific labels on child
notes. There are four sorting levels, with the first having the highest
priority. Lower priority levels are applied only if higher priority comparisons
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Calendar.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Calendar.html
index 027db52b37..6eff04bc43 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Calendar.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Collections/Calendar.html
@@ -132,77 +132,6 @@
</ul>
<h2>Configuring the calendar using attributes</h2>
<p>The following attributes can be added to the Collection type:</p>
-<table>
- <thead>
- <tr>
- <th>Name</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><code spellcheck="false">#calendar:hideWeekends</code>
- </td>
- <td>When present (regardless of value), it will hide Saturday and Sundays
- from the calendar.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:weekNumbers</code>
- </td>
- <td>When present (regardless of value), it will show the number of the week
- on the calendar.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:initialDate</code>
- </td>
- <td>Change the date the calendar opens on. When not present, the calendar
- opens on the current date.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:view</code>
- </td>
- <td>
- <p>Which view to display in the calendar:</p>
- <ul>
- <li><code spellcheck="false">timeGridDay</code> for the <em>day</em> view;</li>
- <li><code spellcheck="false">timeGridWeek</code> for the <em>week</em> view;</li>
- <li><code spellcheck="false">dayGridMonth</code> for the <em>month</em> view;</li>
- <li><code spellcheck="false">multiMonthYear</code> for the <em>year</em> view;</li>
- <li><code spellcheck="false">listMonth</code> for the <em>list</em> view.</li>
- </ul>
- <p>Any other value will be dismissed and the default view (month) will be
- used instead.</p>
- <p>The value of this label is automatically updated when changing the view
- using the UI buttons.</p>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:slotDuration</code>
- </td>
- <td>Sets how long each timeslot is on the calendar. Defaults to <code spellcheck="false">00:15:00</code> (15
- minutes). Must have the format "HH:MM:SS". For example, to create timeslots
- for every 10 minutes, you would set <code spellcheck="false">#calendar:slotDuration="00:10:00"</code>.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:slotLabelInterval</code>
- </td>
- <td>Sets how often the timeslots on the calendar should be labeled. Defaults
- to <code spellcheck="false">01:00:00</code> (1 hour). Must have the format
- "HH:MM:SS". For example, to label timeslots every 30 minutes, you would
- set <code spellcheck="false">#calendar:slotLabelInterval="00:30:00"</code>.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">~child:template</code>
- </td>
- <td>Defines the template for newly created notes in the calendar (via dragging
- or clicking).</td>
- </tr>
- </tbody>
-</table>
-<p>In addition, the first day of the week can be either Sunday or Monday
- and can be adjusted from the application settings.</p>
-<h2>Configuring the calendar events using attributes</h2>
-<p>For each note of the calendar, the following attributes can be used:</p>
<figure
class="table">
<table>
@@ -214,359 +143,433 @@ class="table">
</thead>
<tbody>
<tr>
- <td><code spellcheck="false">#startDate</code>
+ <td><code spellcheck="false">#calendar:hideWeekends</code>
</td>
- <td>The date the event starts, which will display it in the calendar. The
- format is <code spellcheck="false">YYYY-MM-DD</code> (year, month and day
- separated by a minus sign).</td>
+ <td>When present (regardless of value), it will hide Saturday and Sundays
+ from the calendar.</td>
</tr>
<tr>
- <td><code spellcheck="false">#endDate</code>
+ <td><code spellcheck="false">#calendar:weekNumbers</code>
</td>
- <td>Similar to <code spellcheck="false">startDate</code>, mentions the end
- date if the event spans across multiple days. The date is inclusive, so
- the end day is also considered. The attribute can be missing for single-day
- events.</td>
+ <td>When present (regardless of value), it will show the number of the week
+ on the calendar.</td>
</tr>
<tr>
- <td><code spellcheck="false">#startTime</code>
+ <td><code spellcheck="false">#calendar:initialDate</code>
</td>
- <td>The time the event starts at. If this value is missing, then the event
- is considered a full-day event. The format is <code spellcheck="false">HH:MM</code> (hours
- in 24-hour format and minutes).</td>
+ <td>Change the date the calendar opens on. When not present, the calendar
+ opens on the current date.</td>
</tr>
<tr>
- <td><code spellcheck="false">#endTime</code>
+ <td><code spellcheck="false">#calendar:view</code>
</td>
- <td>Similar to <code spellcheck="false">startTime</code>, it mentions the time
- at which the event ends (in relation with <code spellcheck="false">endDate</code> if
- present, or <code spellcheck="false">startDate</code>).</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#recurrence</code>
- </td>
- <td>This is an optional CalDAV <code spellcheck="false">RRULE</code> string
- that if present, determines whether a task should repeat or not. Note that
- it does not include the <code spellcheck="false">DTSTART</code> attribute,
- which is derived from the <code spellcheck="false">#startDate</code> and
- <code
- spellcheck="false">#startTime</code>directly. For examples of valid <code spellcheck="false">RRULE</code> strings
- see <a href="https://icalendar.org/rrule-tool.html">https://icalendar.org/rrule-tool.html</a>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">#color</code>
- </td>
- <td>Displays the event with a specified color (named such as <code spellcheck="false">red</code>,
- <code
- spellcheck="false">gray</code>or hex such as <code spellcheck="false">#FF0000</code>). This
- will also change the color of the note in other places such as the note
- tree.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:color</code>
+ <td>
+ <p>Which view to display in the calendar:</p>
+ <ul>
+ <li><code spellcheck="false">timeGridDay</code> for the <em>day</em> view;</li>
+ <li><code spellcheck="false">timeGridWeek</code> for the <em>week</em> view;</li>
+ <li><code spellcheck="false">dayGridMonth</code> for the <em>month</em> view;</li>
+ <li><code spellcheck="false">multiMonthYear</code> for the <em>year</em> view;</li>
+ <li><code spellcheck="false">listMonth</code> for the <em>list</em> view.</li>
+ </ul>
+ <p>Any other value will be dismissed and the default view (month) will be
+ used instead.</p>
+ <p>The value of this label is automatically updated when changing the view
+ using the UI buttons.</p>
</td>
- <td><strong>❌️ Removed since v0.100.0. Use</strong> <code spellcheck="false">#color</code> <strong>instead.</strong>&nbsp;&nbsp;&nbsp;&nbsp;
- <br>
- <br>Similar to <code spellcheck="false">#color</code>, but applies the color
- only for the event in the calendar and not for other places such as the
- note tree.</td>
</tr>
<tr>
- <td><code spellcheck="false">#iconClass</code>
+ <td><code spellcheck="false">#calendar:slotDuration</code>
</td>
- <td>If present, the icon of the note will be displayed to the left of the
- event title.</td>
+ <td>Sets how long each timeslot is on the calendar. Defaults to <code spellcheck="false">00:15:00</code> (15
+ minutes). Must have the format "HH:MM:SS". For example, to create timeslots
+ for every 10 minutes, you would set <code spellcheck="false">#calendar:slotDuration="00:10:00"</code>.</td>
</tr>
<tr>
- <td><code spellcheck="false">#calendar:title</code>
+ <td><code spellcheck="false">#calendar:slotLabelInterval</code>
</td>
- <td>Changes the title of an event to point to an attribute of the note other
- than the title, can either a label or a relation (without the <code spellcheck="false">#</code> or
- <code
- spellcheck="false">~</code>symbol). See <em>Use-cases</em> for more information.</td>
+ <td>Sets how often the timeslots on the calendar should be labeled. Defaults
+ to <code spellcheck="false">01:00:00</code> (1 hour). Must have the format
+ "HH:MM:SS". For example, to label timeslots every 30 minutes, you would
+ set <code spellcheck="false">#calendar:slotLabelInterval="00:30:00"</code>.</td>
</tr>
<tr>
- <td><code spellcheck="false">#calendar:displayedAttributes</code>
- </td>
- <td>Allows displaying the value of one or more attributes in the calendar
- like this:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- <br>
- <br>
- <img src="6_Calendar_image.png">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- <br>
- <br><code spellcheck="false">#weight="70" #Mood="Good" #calendar:displayedAttributes="weight,Mood"</code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- <br>
- <br>It can also be used with relations, case in which it will display the
- title of the target note:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
- <br>
- <br><code spellcheck="false">~assignee=@My assignee #calendar:displayedAttributes="assignee"</code>
+ <td><code spellcheck="false">~child:template</code>
</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:startDate</code>
- </td>
- <td>Allows using a different label to represent the start date, other than
- <code
- spellcheck="false">startDate</code>(e.g. <code spellcheck="false">expiryDate</code>). The
- label name <strong>must not be</strong> prefixed with <code spellcheck="false">#</code>.
- If the label is not defined for a note, the default will be used instead.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:endDate</code>
- </td>
- <td>Similar to <code spellcheck="false">#calendar:startDate</code>, allows
- changing the attribute which is being used to read the end date.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:startTime</code>
- </td>
- <td>Similar to <code spellcheck="false">#calendar:startDate</code>, allows
- changing the attribute which is being used to read the start time.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">#calendar:endTime</code>
- </td>
- <td>Similar to <code spellcheck="false">#calendar:startDate</code>, allows
- changing the attribute which is being used to read the end time.</td>
+ <td>Defines the template for newly created notes in the calendar (via dragging
+ or clicking).</td>
</tr>
</tbody>
</table>
</figure>
- <h2>How the calendar works</h2>
- <p>
- <img src="8_Calendar_image.png">
- </p>
- <p>The calendar displays all the child notes of the Collection that have
- a <code spellcheck="false">#startDate</code>. An <code spellcheck="false">#endDate</code> can
- optionally be added.</p>
- <p>The start date &amp; end date can easily be edited from the calendar collection
- itself by clicking on the event. To edit the date while in the event note
- itself, the following attributes can be added to the Collection note:</p><pre><code class="language-text-x-trilium-auto">#viewType=calendar #label:startDate(inheritable)="promoted,alias=Start Date,single,date"
-#label:endDate(inheritable)="promoted,alias=End Date,single,date"
-#hidePromotedAttributes </code></pre>
- <p>This will result in:</p>
- <p>
- <img src="7_Calendar_image.png">
- </p>
- <p>When not used in a Journal, the calendar is recursive. That is, it will
- look for events not just in its child notes but also in the children of
- these child notes.</p>
- <h2>Recurrence</h2>
- <p>The built in calendar view also supports repeating tasks (e.g. every week,
- every month as well as more complex recurrency rules).</p>
- <p>Starting with v0.105.0, recurrence can be directly edited from the calendar
- by clicking on an event and then selecting the <em>Repeats</em> option.</p>
- <h3>Custom recurrence using a subset of RRULE</h3>
- <p>If the existing recurrence editor from the event popup is not sufficient,
- more complex rules can be manually set via the <code spellcheck="false">#recurrence</code> label.</p>
- <p>For example, to make a note repeat on the calendar:</p>
- <ul>
- <li>Every Day - <code spellcheck="false">#recurrence="FREQ=DAILY;INTERVAL=1"</code>
- </li>
- <li>Every 3 days - <code spellcheck="false">#recurrence="FREQ=DAILY;INTERVAL=3"</code>
- </li>
- <li>Every week - <code spellcheck="false">#recurrence="FREQ=WEEKLY;INTERVAL=1"</code>
- </li>
- <li>Every 2 weeks on Monday, Wednesday and Friday - <code spellcheck="false">#recurrence="FREQ=WEEKLY;INTERVAL=2;BYDAY=MO,WE,FR"</code>
- </li>
- <li>Every 3 months - <code spellcheck="false">#recurrence="FREQ=MONTHLY;INTERVAL=3"</code>
- </li>
- <li>Every 2 months on the First Sunday - <code spellcheck="false">#recurrence="FREQ=MONTHLY;INTERVAL=2;BYDAY=1SU"</code>
- </li>
- <li>Every month on the Last Friday - <code spellcheck="false">#recurrence="FREQ=MONTHLY;INTERVAL=1;BYDAY=-1FR"</code>
- </li>
- </ul>
- <p>For other examples of valid <code spellcheck="false">RRULE</code> strings
- see <a href="https://icalendar.org/rrule-tool.html">https://icalendar.org/rrule-tool.html</a>
- </p>
- <p>Note that the recurrence string does not include the <code spellcheck="false">DTSTART</code> attribute
- as defined in the iCAL specifications. This is derived directly from the
- <code
- spellcheck="false">startDate</code>and <code spellcheck="false">startTime</code> attributes</p>
- <p>If you want to override the label the calendar uses to fetch the recurrence
- string, you can use the <code spellcheck="false">#calendar:recurrence</code> attribute.
- For example, you can set <code spellcheck="false">#calendar:recurrence=taskRepeats</code>.
- Then you can set your recurrence string like <code spellcheck="false">#taskRepeats="FREQ=DAILY;INTERVAL=1"</code>
- </p>
- <p>Also note that the recurrence label can be made promoted as with the start
- and end dates.&nbsp;</p>
- <aside class="admonition warning">
- <p>If the recurrence string is not valid, a toast will be shown with the
- note ID and title of the note with the erroneous recurrence message. This
- note will not be added to the calendar</p>
- </aside>
- <h2>Slot Duration &amp; Slot Label Interval</h2>
- <p>Trilium's calendar view is powered by FullCalendar, which gives you fine-grained
- control over how the time grid looks and behaves for day and week views.
- Two labels you can use to configure these views are <code spellcheck="false">#calendar:slotDuration</code> and
- <code
- spellcheck="false">#calendar:slotLabelInterval</code>. Understanding what each one does —
- and how they interact — lets you tailor the calendar to match your workflow,
- whether you're scheduling in 15-minute increments or planning out your
- day in broad hourly blocks.</p>
- <p>These settings can also be adjusted from the <em>Collections</em> tab in
- the&nbsp;<a class="reference-link" href="#root/_help_BlN9DFI679QC">Ribbon</a>.</p>
- <h3>Slot duration</h3>
- <p>Controls how tall each time slot is on the calendar — essentially the
- smallest unit of time the grid is divided into. A shorter duration means
- more rows and finer granularity; a longer one means fewer, chunkier rows.
- The default is one row every 15 minutes.</p>
- <p><strong>Examples:</strong>
- </p>
- <figure class="table">
+ <p>In addition, the first day of the week can be either Sunday or Monday
+ and can be adjusted from the application settings.</p>
+ <h2>Configuring the calendar events using attributes</h2>
+ <p>For each note of the calendar, the following attributes can be used:</p>
+ <figure
+ class="table">
<table>
<thead>
<tr>
- <th>Value</th>
- <th>Result</th>
+ <th>Name</th>
+ <th>Description</th>
</tr>
</thead>
<tbody>
<tr>
- <td><code spellcheck="false">#calendar:slotDuration="00:15:00"</code>
+ <td><code spellcheck="false">#startDate</code>
</td>
- <td>One row every 15 minutes</td>
+ <td>The date the event starts, which will display it in the calendar. The
+ format is <code spellcheck="false">YYYY-MM-DD</code> (year, month and day
+ separated by a minus sign).</td>
</tr>
<tr>
- <td><code spellcheck="false">#calendar:slotDuration="00:30:00"</code>
+ <td><code spellcheck="false">#endDate</code>
</td>
- <td>One row every 30 minutes</td>
+ <td>Similar to <code spellcheck="false">startDate</code>, mentions the end
+ date if the event spans across multiple days. The date is inclusive, so
+ the end day is also considered. The attribute can be missing for single-day
+ events.</td>
</tr>
<tr>
- <td><code spellcheck="false">#calendar:slotDuration="01:00:00"</code>
+ <td><code spellcheck="false">#startTime</code>
</td>
- <td>One row every hour</td>
+ <td>The time the event starts at. If this value is missing, then the event
+ is considered a full-day event. The format is <code spellcheck="false">HH:MM</code> (hours
+ in 24-hour format and minutes).</td>
</tr>
- </tbody>
- </table>
- </figure>
- <h3>Label interval</h3>
- <p>Controls how often a time label appears on the left-hand axis. This is
- independent of the slot size — you can have very small slots but only label
- every hour to keep the axis readable. The default is a time label shown
- every hour.</p>
- <p><strong>Examples:</strong>
- </p>
- <figure class="table">
- <table>
- <thead>
<tr>
- <th>Value</th>
- <th>Result</th>
+ <td><code spellcheck="false">#endTime</code>
+ </td>
+ <td>Similar to <code spellcheck="false">startTime</code>, it mentions the time
+ at which the event ends (in relation with <code spellcheck="false">endDate</code> if
+ present, or <code spellcheck="false">startDate</code>).</td>
</tr>
- </thead>
- <tbody>
<tr>
- <td><code spellcheck="false">#calendar:slotLabelInterval="00:30:00"</code>
+ <td><code spellcheck="false">#recurrence</code>
+ </td>
+ <td>This is an optional CalDAV <code spellcheck="false">RRULE</code> string
+ that if present, determines whether a task should repeat or not. Note that
+ it does not include the <code spellcheck="false">DTSTART</code> attribute,
+ which is derived from the <code spellcheck="false">#startDate</code> and
+ <code
+ spellcheck="false">#startTime</code>directly. For examples of valid <code spellcheck="false">RRULE</code> strings
+ see <a href="https://icalendar.org/rrule-tool.html">https://icalendar.org/rrule-tool.html</a>
</td>
- <td>Show a time label every 30 minutes</td>
</tr>
<tr>
- <td><code spellcheck="false">#calendar:slotLabelInterval="01:00:00"</code>
+ <td><code spellcheck="false">#color</code>
</td>
- <td>Show a time label every hour</td>
+ <td>Displays the event with a specified color (named such as <code spellcheck="false">red</code>,
+ <code
+ spellcheck="false">gray</code>or hex such as <code spellcheck="false">#FF0000</code>). This
+ will also change the color of the note in other places such as the note
+ tree.</td>
</tr>
- </tbody>
- </table>
- </figure>
- <h3>Useful combinations</h3>
- <figure class="table">
- <table>
- <thead>
<tr>
- <th><code spellcheck="false">#calendar:slotDuration</code>
- </th>
- <th><code spellcheck="false">#calendar:slotLabelInterval</code>
- </th>
- <th>Result</th>
+ <td><code spellcheck="false">#calendar:color</code>
+ </td>
+ <td><strong>❌️ Removed since v0.100.0. Use</strong> <code spellcheck="false">#color</code> <strong>instead.</strong>&nbsp;&nbsp;&nbsp;&nbsp;
+ <br>
+ <br>Similar to <code spellcheck="false">#color</code>, but applies the color
+ only for the event in the calendar and not for other places such as the
+ note tree.</td>
</tr>
- </thead>
- <tbody>
<tr>
- <td><code spellcheck="false">00:15:00</code>
+ <td><code spellcheck="false">#iconClass</code>
</td>
- <td><code spellcheck="false">01:00:00</code>
+ <td>If present, the icon of the note will be displayed to the left of the
+ event title.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#calendar:title</code>
</td>
- <td>Fine grid, clean axis — good for busy schedules</td>
+ <td>Changes the title of an event to point to an attribute of the note other
+ than the title, can either a label or a relation (without the <code spellcheck="false">#</code> or
+ <code
+ spellcheck="false">~</code>symbol). See <em>Use-cases</em> for more information.</td>
</tr>
<tr>
- <td><code spellcheck="false">00:30:00</code>
+ <td><code spellcheck="false">#calendar:displayedAttributes</code>
</td>
- <td><code spellcheck="false">01:00:00</code>
+ <td>Allows displaying the value of one or more attributes in the calendar
+ like this:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <br>
+ <br>
+ <img src="6_Calendar_image.png">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <br>
+ <br><code spellcheck="false">#weight="70" #Mood="Good" #calendar:displayedAttributes="weight,Mood"</code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <br>
+ <br>It can also be used with relations, case in which it will display the
+ title of the target note:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <br>
+ <br><code spellcheck="false">~assignee=@My assignee #calendar:displayedAttributes="assignee"</code>
</td>
- <td>Standard calendar feel</td>
</tr>
<tr>
- <td><code spellcheck="false">01:00:00</code>
+ <td><code spellcheck="false">#calendar:startDate</code>
</td>
- <td><code spellcheck="false">01:00:00</code>
+ <td>Allows using a different label to represent the start date, other than
+ <code
+ spellcheck="false">startDate</code>(e.g. <code spellcheck="false">expiryDate</code>). The
+ label name <strong>must not be</strong> prefixed with <code spellcheck="false">#</code>.
+ If the label is not defined for a note, the default will be used instead.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#calendar:endDate</code>
</td>
- <td>Simple hourly grid — good for day planning</td>
+ <td>Similar to <code spellcheck="false">#calendar:startDate</code>, allows
+ changing the attribute which is being used to read the end date.</td>
</tr>
<tr>
- <td><code spellcheck="false">00:15:00</code>
+ <td><code spellcheck="false">#calendar:startTime</code>
</td>
- <td><code spellcheck="false">00:30:00</code>
+ <td>Similar to <code spellcheck="false">#calendar:startDate</code>, allows
+ changing the attribute which is being used to read the start time.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#calendar:endTime</code>
</td>
- <td>Fine grid, labels every 30 min — balanced detail</td>
+ <td>Similar to <code spellcheck="false">#calendar:startDate</code>, allows
+ changing the attribute which is being used to read the end time.</td>
</tr>
</tbody>
</table>
- </figure>
- <h3>Format</h3>
- <p>Both values use <code spellcheck="false">HH:mm:ss</code> format. Hours can
- go up to <code spellcheck="false">24</code> (<code spellcheck="false">24:00:00</code>),
- while minutes and seconds must be between <code spellcheck="false">00</code> and
- <code
- spellcheck="false">59</code>. The minimum meaningful duration is 1 minute (<code spellcheck="false">00:01:00</code>).</p>
- <h2>Use-cases</h2>
- <h3>Using with the Journal / calendar</h3>
- <p>It is possible to integrate the calendar view into the Journal with day
- notes. In order to do so change the note type of the Journal note (calendar
- root) to Collection and then select the Calendar View.</p>
- <p>While in journal mode, the popup editor will not show dates, recurrence,
- colors or removal, since day notes aren't editable events.</p>
- <p>Based on the <code spellcheck="false">#calendarRoot</code> (or <code spellcheck="false">#workspaceCalendarRoot</code>)
- attribute, the calendar will know that it's in a calendar and apply the
- following:</p>
- <ul>
- <li>The calendar events are now rendered based on their <code spellcheck="false">dateNote</code> attribute
- rather than <code spellcheck="false">startDate</code>.</li>
- <li>Interactive editing such as dragging over an empty era or resizing an
- event is no longer possible.</li>
- <li>Clicking on the empty space on a date will automatically open that day's
- note or create it if it does not exist.</li>
- <li>Direct children of a day note will be displayed on the calendar despite
- not having a <code spellcheck="false">dateNote</code> attribute. Children
- of the child notes will not be displayed.</li>
- </ul>
- <img src="5_Calendar_image.png" width="1217" height="724">
- <h3>Using a different attribute as event title</h3>
- <p>
- <img class="image-style-align-right" src="2_Calendar_image.png"
- width="445" height="124">By default, events are displayed on the calendar by their note title.
- However, it is possible to configure a different attribute to be displayed
- instead.</p>
- <p>To do so, assign <code spellcheck="false">#calendar:title</code> to the
- child note (not the calendar/Collection note), with the value being
- <code
- spellcheck="false">name</code>where <code spellcheck="false">name</code> can be any label (make
- not to add the <code spellcheck="false">#</code> prefix). The attribute can
- also come through inheritance such as a template attribute. If the note
- does not have the requested label, the title of the note will be used instead.</p><pre><code class="language-text-x-trilium-auto">#startDate=2025-02-11 #endDate=2025-02-13 #name="My vacation" #calendar:title="name"</code></pre>
- <h3>Using a relation attribute as event title</h3>
- <p>
- <img class="image-style-align-right image_resized" style="aspect-ratio:294/151;width:21.22%;"
- src="3_Calendar_image.png" width="294" height="151">Similarly to using an attribute, use <code spellcheck="false">#calendar:title</code> and
- set it to <code spellcheck="false">name</code> where <code spellcheck="false">name</code> is
- the name of the relation to use.</p>
- <p>Moreover, if there are more relations of the same name, they will be displayed
- as multiple events coming from the same note.</p><pre><code class="language-text-x-trilium-auto">#startDate=2025-02-14 #endDate=2025-02-15 ~for=@John Smith ~for=@Jane Doe #calendar:title="for"</code></pre>
- <p>
- <img class="image-style-align-left" src="Calendar_image.png"
- width="296" height="150">Note that it's even possible to have a <code spellcheck="false">#calendar:title</code> on
- the target note (e.g. “John Smith”) which will try to render an attribute
- of it. Note that it's not possible to use a relation here as well for safety
- reasons (an accidental recursion &nbsp;of attributes could cause the application
- to loop infinitely).</p><pre><code class="language-text-x-trilium-auto">#calendar:title="shortName" #shortName="John S."</code></pre>
\ No newline at end of file
+ </figure>
+ <h2>How the calendar works</h2>
+ <p>
+ <img src="8_Calendar_image.png">
+ </p>
+ <p>The calendar displays all the child notes of the Collection that have
+ a <code spellcheck="false">#startDate</code>. An <code spellcheck="false">#endDate</code> can
+ optionally be added.</p>
+ <p>The start date &amp; end date can easily be edited from the calendar collection
+ itself by clicking on the event. To edit the date while in the event note
+ itself, the following attributes can be added to the Collection note:</p><pre><code class="language-text-x-trilium-auto">#viewType=calendar #label:startDate(inheritable)="promoted,alias=Start Date,single,date"
+#label:endDate(inheritable)="promoted,alias=End Date,single,date"
+#hidePromotedAttributes </code></pre>
+ <p>This will result in:</p>
+ <p>
+ <img src="7_Calendar_image.png">
+ </p>
+ <p>When not used in a Journal, the calendar is recursive. That is, it will
+ look for events not just in its child notes but also in the children of
+ these child notes.</p>
+ <h2>Recurrence</h2>
+ <p>The built in calendar view also supports repeating tasks (e.g. every week,
+ every month as well as more complex recurrency rules).</p>
+ <p>Starting with v0.105.0, recurrence can be directly edited from the calendar
+ by clicking on an event and then selecting the <em>Repeats</em> option.</p>
+ <h3>Custom recurrence using a subset of RRULE</h3>
+ <p>If the existing recurrence editor from the event popup is not sufficient,
+ more complex rules can be manually set via the <code spellcheck="false">#recurrence</code> label.</p>
+ <p>For example, to make a note repeat on the calendar:</p>
+ <ul>
+ <li>Every Day - <code spellcheck="false">#recurrence="FREQ=DAILY;INTERVAL=1"</code>
+ </li>
+ <li>Every 3 days - <code spellcheck="false">#recurrence="FREQ=DAILY;INTERVAL=3"</code>
+ </li>
+ <li>Every week - <code spellcheck="false">#recurrence="FREQ=WEEKLY;INTERVAL=1"</code>
+ </li>
+ <li>Every 2 weeks on Monday, Wednesday and Friday - <code spellcheck="false">#recurrence="FREQ=WEEKLY;INTERVAL=2;BYDAY=MO,WE,FR"</code>
+ </li>
+ <li>Every 3 months - <code spellcheck="false">#recurrence="FREQ=MONTHLY;INTERVAL=3"</code>
+ </li>
+ <li>Every 2 months on the First Sunday - <code spellcheck="false">#recurrence="FREQ=MONTHLY;INTERVAL=2;BYDAY=1SU"</code>
+ </li>
+ <li>Every month on the Last Friday - <code spellcheck="false">#recurrence="FREQ=MONTHLY;INTERVAL=1;BYDAY=-1FR"</code>
+ </li>
+ </ul>
+ <p>For other examples of valid <code spellcheck="false">RRULE</code> strings
+ see <a href="https://icalendar.org/rrule-tool.html">https://icalendar.org/rrule-tool.html</a>
+ </p>
+ <p>Note that the recurrence string does not include the <code spellcheck="false">DTSTART</code> attribute
+ as defined in the iCAL specifications. This is derived directly from the
+ <code
+ spellcheck="false">startDate</code>and <code spellcheck="false">startTime</code> attributes</p>
+ <p>If you want to override the label the calendar uses to fetch the recurrence
+ string, you can use the <code spellcheck="false">#calendar:recurrence</code> attribute.
+ For example, you can set <code spellcheck="false">#calendar:recurrence=taskRepeats</code>.
+ Then you can set your recurrence string like <code spellcheck="false">#taskRepeats="FREQ=DAILY;INTERVAL=1"</code>
+ </p>
+ <p>Also note that the recurrence label can be made promoted as with the start
+ and end dates.&nbsp;</p>
+ <aside class="admonition warning">
+ <p>If the recurrence string is not valid, a toast will be shown with the
+ note ID and title of the note with the erroneous recurrence message. This
+ note will not be added to the calendar</p>
+ </aside>
+ <h2>Slot Duration &amp; Slot Label Interval</h2>
+ <p>Trilium's calendar view is powered by FullCalendar, which gives you fine-grained
+ control over how the time grid looks and behaves for day and week views.
+ Two labels you can use to configure these views are <code spellcheck="false">#calendar:slotDuration</code> and
+ <code
+ spellcheck="false">#calendar:slotLabelInterval</code>. Understanding what each one does —
+ and how they interact — lets you tailor the calendar to match your workflow,
+ whether you're scheduling in 15-minute increments or planning out your
+ day in broad hourly blocks.</p>
+ <p>These settings can also be adjusted from the <em>Collections</em> tab in
+ the&nbsp;<a class="reference-link" href="#root/_help_BlN9DFI679QC">Ribbon</a>.</p>
+ <h3>Slot duration</h3>
+ <p>Controls how tall each time slot is on the calendar — essentially the
+ smallest unit of time the grid is divided into. A shorter duration means
+ more rows and finer granularity; a longer one means fewer, chunkier rows.
+ The default is one row every 15 minutes.</p>
+ <p><strong>Examples:</strong>
+ </p>
+ <figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th>Value</th>
+ <th>Result</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code spellcheck="false">#calendar:slotDuration="00:15:00"</code>
+ </td>
+ <td>One row every 15 minutes</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#calendar:slotDuration="00:30:00"</code>
+ </td>
+ <td>One row every 30 minutes</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#calendar:slotDuration="01:00:00"</code>
+ </td>
+ <td>One row every hour</td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
+ <h3>Label interval</h3>
+ <p>Controls how often a time label appears on the left-hand axis. This is
+ independent of the slot size — you can have very small slots but only label
+ every hour to keep the axis readable. The default is a time label shown
+ every hour.</p>
+ <p><strong>Examples:</strong>
+ </p>
+ <figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th>Value</th>
+ <th>Result</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code spellcheck="false">#calendar:slotLabelInterval="00:30:00"</code>
+ </td>
+ <td>Show a time label every 30 minutes</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">#calendar:slotLabelInterval="01:00:00"</code>
+ </td>
+ <td>Show a time label every hour</td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
+ <h3>Useful combinations</h3>
+ <figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th><code spellcheck="false">#calendar:slotDuration</code>
+ </th>
+ <th><code spellcheck="false">#calendar:slotLabelInterval</code>
+ </th>
+ <th>Result</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code spellcheck="false">00:15:00</code>
+ </td>
+ <td><code spellcheck="false">01:00:00</code>
+ </td>
+ <td>Fine grid, clean axis — good for busy schedules</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">00:30:00</code>
+ </td>
+ <td><code spellcheck="false">01:00:00</code>
+ </td>
+ <td>Standard calendar feel</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">01:00:00</code>
+ </td>
+ <td><code spellcheck="false">01:00:00</code>
+ </td>
+ <td>Simple hourly grid — good for day planning</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">00:15:00</code>
+ </td>
+ <td><code spellcheck="false">00:30:00</code>
+ </td>
+ <td>Fine grid, labels every 30 min — balanced detail</td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
+ <h3>Format</h3>
+ <p>Both values use <code spellcheck="false">HH:mm:ss</code> format. Hours can
+ go up to <code spellcheck="false">24</code> (<code spellcheck="false">24:00:00</code>),
+ while minutes and seconds must be between <code spellcheck="false">00</code> and
+ <code
+ spellcheck="false">59</code>. The minimum meaningful duration is 1 minute (<code spellcheck="false">00:01:00</code>).</p>
+ <h2>Use-cases</h2>
+ <h3>Using with the Journal / calendar</h3>
+ <p>It is possible to integrate the calendar view into the Journal with day
+ notes. In order to do so change the note type of the Journal note (calendar
+ root) to Collection and then select the Calendar View.</p>
+ <p>While in journal mode, the popup editor will not show dates, recurrence,
+ colors or removal, since day notes aren't editable events.</p>
+ <p>Based on the <code spellcheck="false">#calendarRoot</code> (or <code spellcheck="false">#workspaceCalendarRoot</code>)
+ attribute, the calendar will know that it's in a calendar and apply the
+ following:</p>
+ <ul>
+ <li>The calendar events are now rendered based on their <code spellcheck="false">dateNote</code> attribute
+ rather than <code spellcheck="false">startDate</code>.</li>
+ <li>Interactive editing such as dragging over an empty era or resizing an
+ event is no longer possible.</li>
+ <li>Clicking on the empty space on a date will automatically open that day's
+ note or create it if it does not exist.</li>
+ <li>Direct children of a day note will be displayed on the calendar despite
+ not having a <code spellcheck="false">dateNote</code> attribute. Children
+ of the child notes will not be displayed.</li>
+ </ul>
+ <img src="5_Calendar_image.png" width="1217" height="724">
+ <h3>Using a different attribute as event title</h3>
+ <p>
+ <img class="image-style-align-right" src="2_Calendar_image.png"
+ width="445" height="124">By default, events are displayed on the calendar by their note title.
+ However, it is possible to configure a different attribute to be displayed
+ instead.</p>
+ <p>To do so, assign <code spellcheck="false">#calendar:title</code> to the
+ child note (not the calendar/Collection note), with the value being
+ <code
+ spellcheck="false">name</code>where <code spellcheck="false">name</code> can be any label (make
+ not to add the <code spellcheck="false">#</code> prefix). The attribute can
+ also come through inheritance such as a template attribute. If the note
+ does not have the requested label, the title of the note will be used instead.</p><pre><code class="language-text-x-trilium-auto">#startDate=2025-02-11 #endDate=2025-02-13 #name="My vacation" #calendar:title="name"</code></pre>
+ <h3>Using a relation attribute as event title</h3>
+ <p>
+ <img class="image-style-align-right image_resized" style="aspect-ratio:294/151;width:21.22%;"
+ src="3_Calendar_image.png" width="294" height="151">Similarly to using an attribute, use <code spellcheck="false">#calendar:title</code> and
+ set it to <code spellcheck="false">name</code> where <code spellcheck="false">name</code> is
+ the name of the relation to use.</p>
+ <p>Moreover, if there are more relations of the same name, they will be displayed
+ as multiple events coming from the same note.</p><pre><code class="language-text-x-trilium-auto">#startDate=2025-02-14 #endDate=2025-02-15 ~for=@John Smith ~for=@Jane Doe #calendar:title="for"</code></pre>
+ <p>
+ <img class="image-style-align-left" src="Calendar_image.png"
+ width="296" height="150">Note that it's even possible to have a <code spellcheck="false">#calendar:title</code> on
+ the target note (e.g. “John Smith”) which will try to render an attribute
+ of it. Note that it's not possible to use a relation here as well for safety
+ reasons (an accidental recursion &nbsp;of attributes could cause the application
+ to loop infinitely).</p><pre><code class="language-text-x-trilium-auto">#calendar:title="shortName" #shortName="John S."</code></pre>
\ No newline at end of file
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text.html
index b3f0374561..c3d5ad15d3 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text.html
@@ -18,175 +18,178 @@
<p>Fore more information see&nbsp;<a class="reference-link" href="#root/_help_nRhnJkTT8cPs">Formatting toolbar</a>.</p>
<h2>Features and formatting</h2>
<p>Here's a list of various features supported by text notes:</p>
-<table>
- <thead>
- <tr>
- <th>Dedicated article</th>
- <th>Feature</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><a class="reference-link" href="#root/_help_Gr6xFaF6ioJ5">General formatting</a>
- </td>
- <td>
- <ul>
- <li>Headings (section titles, paragraph)</li>
- <li>Font size</li>
- <li>Bold, italic, underline, strike-through</li>
- <li>Superscript, subscript</li>
- <li>Font color &amp; background color</li>
- <li>Remove formatting</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_S6Xx8QIWTV66">Lists</a>
- </td>
- <td>
- <ul>
- <li>Bulleted lists</li>
- <li>Numbered lists</li>
- <li>To-do lists</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_NwBbFdNZ9h7O">Block quotes &amp; admonitions</a>
- </td>
- <td>
- <ul>
- <li>Block quotes</li>
- <li>Admonitions</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_NdowYOC1GFKS">Tables</a>
- </td>
- <td>
- <ul>
- <li>Basic tables</li>
- <li>Merging cells</li>
- <li>Styling tables and cells.</li>
- <li>Table captions</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_UYuUB1ZekNQU">Developer-specific formatting</a>
- </td>
- <td>
- <ul>
- <li>Inline code</li>
- <li>Code blocks</li>
- <li>Keyboard shortcuts</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_AgjCISero73a">Footnotes</a>
- </td>
- <td>
- <ul>
- <li>Footnotes</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_mT0HEkOsz6i1">Images</a>
- </td>
- <td>
- <ul>
- <li>Images</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_QEAPj01N5f7w">Links</a>
- </td>
- <td>
- <ul>
- <li>External links</li>
- <li>Internal Trilium links</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_nBAXQFj20hS1">Include Note</a>
- </td>
- <td>
- <ul>
- <li>Include note</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_CohkqWQC1iBv">Insert buttons</a>
- </td>
- <td>
- <ul>
- <li>Symbols</li>
- <li><a class="reference-link" href="#root/_help_YfYAtQBcfo5V">[missing note]</a>
- </li>
- <li>Mermaid diagrams</li>
- <li>Horizontal ruler</li>
- <li>Page break</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_dEHYtoWWi8ct">[missing note]</a>
- </td>
- <td>
- <ul>
- <li>Indentation
- <ul>
- <li>Markdown import</li>
- </ul>
- </li>
- <li><a class="reference-link" href="#root/_help_2x0ZAX9ePtzV">Cut to subnote</a>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><a class="reference-link" href="#root/_help_gLt3vA97tMcp">[missing note]</a>
- </td>
- <td>
- <ul>
- <li><a class="reference-link" href="#root/_help_ZlN4nump6EbW">Slash Commands</a>
- </li>
- <li><a class="reference-link" href="#root/_help_KC1HB96bqqHX">Templates</a>
- </li>
- <li><a class="reference-link" href="#root/_help_5wZallV2Qo1t">Format Painter</a>
- </li>
- </ul>
- </td>
- </tr>
- </tbody>
-</table>
-<h2>Read-Only vs. Editing Mode</h2>
-<p>Text notes are usually opened in edit mode. However, they may open in
- read-only mode if the note is too big or the note is explicitly marked
- as read-only. For more information, see&nbsp;<a class="reference-link"
- href="#root/_help_CoFPLs3dRlXc">[missing note]</a>.</p>
-<h2>Keyboard shortcuts</h2>
-<p>There are numerous keyboard shortcuts to format the text without having
- to use the mouse. For a reference of all the key combinations, see&nbsp;
- <a
- class="reference-link" href="#root/_help_A9Oc6YKKc65v">Keyboard Shortcuts</a>. In addition, see&nbsp;<a class="reference-link"
- href="#root/_help_QrtTYPmdd1qq">Markdown-like formatting</a>&nbsp;as an alternative
- to the keyboard shortcuts.</p>
-<h2>Content width</h2>
-<p>For readability purposes on wider screens, the width of text notes is
- limited via a configurable option. See&nbsp;<a class="reference-link" href="#root/_help_t596jLvPrqkS">[missing note]</a>&nbsp;for
- more information.</p>
-<h2>Converting to a Markdown note</h2>
-<p>Text notes can be converted to&nbsp;<a class="reference-link" href="#root/_help_6RM1Q7ppFVoj">Markdown</a>&nbsp;notes.
- See&nbsp;<a class="reference-link" href="#root/_help_jludwdW7N4hg">Converting between note types</a>.</p>
-<h2>Technical details</h2>
-<p>For the text editing functionality, Trilium uses a commercial product
- (with an open-source base) called&nbsp;<a class="reference-link" href="#root/_help_MI26XDLSAlCD">[missing note]</a>.
- This brings the benefit of having a powerful WYSIWYG (What You See Is What
- You Get) editor.</p>
\ No newline at end of file
+<figure
+class="table">
+ <table>
+ <thead>
+ <tr>
+ <th>Dedicated article</th>
+ <th>Feature</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_Gr6xFaF6ioJ5">General formatting</a>
+ </td>
+ <td>
+ <ul>
+ <li>Headings (section titles, paragraph)</li>
+ <li>Font size</li>
+ <li>Bold, italic, underline, strike-through</li>
+ <li>Superscript, subscript</li>
+ <li>Font color &amp; background color</li>
+ <li>Remove formatting</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_S6Xx8QIWTV66">Lists</a>
+ </td>
+ <td>
+ <ul>
+ <li>Bulleted lists</li>
+ <li>Numbered lists</li>
+ <li>To-do lists</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_NwBbFdNZ9h7O">Block quotes &amp; admonitions</a>
+ </td>
+ <td>
+ <ul>
+ <li>Block quotes</li>
+ <li>Admonitions</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_NdowYOC1GFKS">Tables</a>
+ </td>
+ <td>
+ <ul>
+ <li>Basic tables</li>
+ <li>Merging cells</li>
+ <li>Styling tables and cells.</li>
+ <li>Table captions</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_UYuUB1ZekNQU">Developer-specific formatting</a>
+ </td>
+ <td>
+ <ul>
+ <li>Inline code</li>
+ <li>Code blocks</li>
+ <li>Keyboard shortcuts</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_AgjCISero73a">Footnotes</a>
+ </td>
+ <td>
+ <ul>
+ <li>Footnotes</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_mT0HEkOsz6i1">Images</a>
+ </td>
+ <td>
+ <ul>
+ <li>Images</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_QEAPj01N5f7w">Links</a>
+ </td>
+ <td>
+ <ul>
+ <li>External links</li>
+ <li>Internal Trilium links</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_nBAXQFj20hS1">Include Note</a>
+ </td>
+ <td>
+ <ul>
+ <li>Include note</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_CohkqWQC1iBv">Insert buttons</a>
+ </td>
+ <td>
+ <ul>
+ <li>Symbols</li>
+ <li><a class="reference-link" href="#root/_help_YfYAtQBcfo5V">[missing note]</a>
+ </li>
+ <li>Mermaid diagrams</li>
+ <li>Horizontal ruler</li>
+ <li>Page break</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_dEHYtoWWi8ct">[missing note]</a>
+ </td>
+ <td>
+ <ul>
+ <li>Indentation
+ <ul>
+ <li>Markdown import</li>
+ </ul>
+ </li>
+ <li><a class="reference-link" href="#root/_help_2x0ZAX9ePtzV">Cut to subnote</a>
+ </li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><a class="reference-link" href="#root/_help_gLt3vA97tMcp">[missing note]</a>
+ </td>
+ <td>
+ <ul>
+ <li><a class="reference-link" href="#root/_help_ZlN4nump6EbW">Slash Commands</a>
+ </li>
+ <li><a class="reference-link" href="#root/_help_KC1HB96bqqHX">Templates</a>
+ </li>
+ <li><a class="reference-link" href="#root/_help_5wZallV2Qo1t">Format Painter</a>
+ </li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </figure>
+ <h2>Read-Only vs. Editing Mode</h2>
+ <p>Text notes are usually opened in edit mode. However, they may open in
+ read-only mode if the note is too big or the note is explicitly marked
+ as read-only. For more information, see&nbsp;<a class="reference-link"
+ href="#root/_help_CoFPLs3dRlXc">[missing note]</a>.</p>
+ <h2>Keyboard shortcuts</h2>
+ <p>There are numerous keyboard shortcuts to format the text without having
+ to use the mouse. For a reference of all the key combinations, see&nbsp;
+ <a
+ class="reference-link" href="#root/_help_A9Oc6YKKc65v">Keyboard Shortcuts</a>. In addition, see&nbsp;<a class="reference-link"
+ href="#root/_help_QrtTYPmdd1qq">Markdown-like formatting</a>&nbsp;as an alternative
+ to the keyboard shortcuts.</p>
+ <h2>Content width</h2>
+ <p>For readability purposes on wider screens, the width of text notes is
+ limited via a configurable option. See&nbsp;<a class="reference-link" href="#root/_help_t596jLvPrqkS">[missing note]</a>&nbsp;for
+ more information.</p>
+ <h2>Converting to a Markdown note</h2>
+ <p>Text notes can be converted to&nbsp;<a class="reference-link" href="#root/_help_6RM1Q7ppFVoj">Markdown</a>&nbsp;notes.
+ See&nbsp;<a class="reference-link" href="#root/_help_jludwdW7N4hg">Converting between note types</a>.</p>
+ <h2>Technical details</h2>
+ <p>For the text editing functionality, Trilium uses a commercial product
+ (with an open-source base) called&nbsp;<a class="reference-link" href="#root/_help_MI26XDLSAlCD">[missing note]</a>.
+ This brings the benefit of having a powerful WYSIWYG (What You See Is What
+ You Get) editor.</p>
\ No newline at end of file
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text/Link Previews.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text/Link Previews.html
index 772ce10bbf..7e9c856831 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text/Link Previews.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Text/Link Previews.html
@@ -17,38 +17,40 @@
</ul>
</li>
</ul>
-<table class="ck-table-resized">
- <colgroup>
- <col style="width:21.85%;">
- <col style="width:38.84%;">
- <col style="width:39.31%;">
- </colgroup>
- <tbody>
- <tr>
- <td>
- <figure class="image image_resized" style="width:100%;">
- <img style="aspect-ratio:251/42;" src="Link Previews_image.png"
- width="251" height="42">
- <figcaption><em>Inline</em> link preview</figcaption>
- </figure>
- </td>
- <td>
- <figure class="image image_resized" style="width:100%;">
- <img style="aspect-ratio:1217/196;" src="2_Link Previews_image.png"
- width="1217" height="196">
- <figcaption><em>Card</em> link preview</figcaption>
- </figure>
- </td>
- <td>
- <figure class="image image_resized" style="width:100%;">
- <img style="aspect-ratio:994/563;" src="1_Link Previews_image.png"
- width="994" height="563">
- <figcaption><em>Embed</em> link preview</figcaption>
- </figure>
- </td>
- </tr>
- </tbody>
-</table>
+<figure class="table">
+ <table class="ck-table-resized">
+ <colgroup>
+ <col style="width:21.85%;">
+ <col style="width:38.84%;">
+ <col style="width:39.31%;">
+ </colgroup>
+ <tbody>
+ <tr>
+ <td>
+ <figure class="image image_resized" style="width:100%;">
+ <img style="aspect-ratio:251/42;" src="Link Previews_image.png"
+ width="251" height="42">
+ <figcaption><em>Inline</em> link preview</figcaption>
+ </figure>
+ </td>
+ <td>
+ <figure class="image image_resized" style="width:100%;">
+ <img style="aspect-ratio:1217/196;" src="2_Link Previews_image.png"
+ width="1217" height="196">
+ <figcaption><em>Card</em> link preview</figcaption>
+ </figure>
+ </td>
+ <td>
+ <figure class="image image_resized" style="width:100%;">
+ <img style="aspect-ratio:994/563;" src="1_Link Previews_image.png"
+ width="994" height="563">
+ <figcaption><em>Embed</em> link preview</figcaption>
+ </figure>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
<h2>Inserting a link preview</h2>
<p>There are two ways to create one:</p>
<h3>1. By pasting a URL</h3>
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Backend scripts/Backend Events.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Backend scripts/Backend Events.html
index cd039c8c2a..8571f190d8 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Backend scripts/Backend Events.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Backend scripts/Backend Events.html
@@ -5,43 +5,45 @@
<p>Global events are attached to the script note via label. Simply create
a <code spellcheck="false">run</code> label with some of these values and
script note will be executed once the event occurs.</p>
-<table>
- <thead>
- <tr>
- <th>Label</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><code spellcheck="false">run</code>
- </td>
- <td>
- <p>Defines on which events script should run. Possible values are:</p>
- <ul>
- <li><code spellcheck="false">backendStartup</code> - when Trilium backend starts
- up</li>
- <li><code spellcheck="false">hourly</code> - run once an hour. You can use
- additional label <code spellcheck="false">runAtHour</code> to specify at
- which hour, on the back-end.</li>
- <li><code spellcheck="false">daily</code> - run once a day, on the back-end</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><code spellcheck="false">runOnInstance</code>
- </td>
- <td>Specifies that the script should only run on a particular&nbsp;<a class="reference-link"
- href="#root/_help_c5xB8m4g2IY6">Trilium instance</a>.</td>
- </tr>
- <tr>
- <td><code spellcheck="false">runAtHour</code>
- </td>
- <td>On which hour should this run. Should be used together with <code spellcheck="false">#run=hourly</code>.
- Can be defined multiple times for more runs during the day.</td>
- </tr>
- </tbody>
-</table>
+<figure class="table">
+ <table>
+ <thead>
+ <tr>
+ <th>Label</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code spellcheck="false">run</code>
+ </td>
+ <td>
+ <p>Defines on which events script should run. Possible values are:</p>
+ <ul>
+ <li><code spellcheck="false">backendStartup</code> - when Trilium backend starts
+ up</li>
+ <li><code spellcheck="false">hourly</code> - run once an hour. You can use
+ additional label <code spellcheck="false">runAtHour</code> to specify at
+ which hour, on the back-end.</li>
+ <li><code spellcheck="false">daily</code> - run once a day, on the back-end</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">runOnInstance</code>
+ </td>
+ <td>Specifies that the script should only run on a particular&nbsp;<a class="reference-link"
+ href="#root/_help_c5xB8m4g2IY6">Trilium instance</a>.</td>
+ </tr>
+ <tr>
+ <td><code spellcheck="false">runAtHour</code>
+ </td>
+ <td>On which hour should this run. Should be used together with <code spellcheck="false">#run=hourly</code>.
+ Can be defined multiple times for more runs during the day.</td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
<p>Frontend scripts also have similar&nbsp;<a class="reference-link" href="#root/_help_irkwjdNtjcxR">Events</a>,
such as when the application starts.</p>
<aside class="admonition note">
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Custom Widgets.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Custom Widgets.html
index 6c8add8746..ea9350bde2 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Custom Widgets.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Custom Widgets.html
@@ -61,78 +61,80 @@ export default defineWidget({
should appear underneath the content area.</p>
<h2>Widget location (parent widget)</h2>
<p>A widget can be placed in one of the following sections of the applications:</p>
-<table
-class="ck-table-resized">
- <colgroup>
- <col style="width:15.59%;">
- <col style="width:30.42%;">
- <col style="width:16.68%;">
- <col style="width:37.31%;">
- </colgroup>
- <thead>
- <tr>
- <th>Value for <code spellcheck="false">parentWidget</code>
- </th>
- <th>Description</th>
- <th>Sample widget</th>
- <th>Special requirements</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <th><code spellcheck="false">left-pane</code>
- </th>
- <td>Appears within the same pane that holds the&nbsp;<a class="reference-link"
- href="#root/_help_oPVyFC7WL2Lp">Note Tree</a>.</td>
- <td>Same as above, with only a different <code spellcheck="false">parentWidget</code>.</td>
- <td>None.</td>
- </tr>
- <tr>
- <th><code spellcheck="false">center-pane</code>
- </th>
- <td>In the content area. If a split is open, the widget will span all of the
- splits.</td>
- <td>See example above.</td>
- <td>None.</td>
- </tr>
- <tr>
- <th><code spellcheck="false">note-detail-pane</code>
- </th>
- <td>
- <p>In the content area, inside the note detail area. If a split is open,
- the widget will be contained inside the split.</p>
- <p>This is ideal if the widget is note-specific.</p>
- </td>
- <td><a class="reference-link" href="#root/_help_GhurYZjh8e1V">Note context aware widget</a>
- </td>
- <td>
- <ul>
- <li>The widget must export a <code spellcheck="false">class</code> and not an
- instance of the class (e.g. <code spellcheck="false">no new</code>) because
- it needs to be multiplied for each note, so that splits work correctly.</li>
- <li>Since the <code spellcheck="false">class</code> is exported instead of an
- instance, the <code spellcheck="false">parentWidget</code> getter must be
- <code
- spellcheck="false">static</code>, otherwise the widget is ignored.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <th><code spellcheck="false">right-pane</code>
- </th>
- <td>In the&nbsp;<a class="reference-link" href="#root/_help_RnaPdbciOfeq">Right Sidebar</a>,
- as a dedicated section.</td>
- <td><a class="reference-link" href="#root/_help_M8IppdwVHSjG">Right pane widget</a>
- </td>
- <td>
- <ul>
- <li>Although not mandatory, it's best to use a <code spellcheck="false">RightPanelWidget</code> instead
- of a <code spellcheck="false">BasicWidget</code> or a <code spellcheck="false">NoteContextAwareWidget</code>.</li>
- </ul>
- </td>
- </tr>
- </tbody>
+<figure
+class="table">
+ <table class="ck-table-resized">
+ <colgroup>
+ <col style="width:15.59%;">
+ <col style="width:30.42%;">
+ <col style="width:16.68%;">
+ <col style="width:37.31%;">
+ </colgroup>
+ <thead>
+ <tr>
+ <th>Value for <code spellcheck="false">parentWidget</code>
+ </th>
+ <th>Description</th>
+ <th>Sample widget</th>
+ <th>Special requirements</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <th><code spellcheck="false">left-pane</code>
+ </th>
+ <td>Appears within the same pane that holds the&nbsp;<a class="reference-link"
+ href="#root/_help_oPVyFC7WL2Lp">Note Tree</a>.</td>
+ <td>Same as above, with only a different <code spellcheck="false">parentWidget</code>.</td>
+ <td>None.</td>
+ </tr>
+ <tr>
+ <th><code spellcheck="false">center-pane</code>
+ </th>
+ <td>In the content area. If a split is open, the widget will span all of the
+ splits.</td>
+ <td>See example above.</td>
+ <td>None.</td>
+ </tr>
+ <tr>
+ <th><code spellcheck="false">note-detail-pane</code>
+ </th>
+ <td>
+ <p>In the content area, inside the note detail area. If a split is open,
+ the widget will be contained inside the split.</p>
+ <p>This is ideal if the widget is note-specific.</p>
+ </td>
+ <td><a class="reference-link" href="#root/_help_GhurYZjh8e1V">Note context aware widget</a>
+ </td>
+ <td>
+ <ul>
+ <li>The widget must export a <code spellcheck="false">class</code> and not an
+ instance of the class (e.g. <code spellcheck="false">no new</code>) because
+ it needs to be multiplied for each note, so that splits work correctly.</li>
+ <li>Since the <code spellcheck="false">class</code> is exported instead of an
+ instance, the <code spellcheck="false">parentWidget</code> getter must be
+ <code
+ spellcheck="false">static</code>, otherwise the widget is ignored.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <th><code spellcheck="false">right-pane</code>
+ </th>
+ <td>In the&nbsp;<a class="reference-link" href="#root/_help_RnaPdbciOfeq">Right Sidebar</a>,
+ as a dedicated section.</td>
+ <td><a class="reference-link" href="#root/_help_M8IppdwVHSjG">Right pane widget</a>
+ </td>
+ <td>
+ <ul>
+ <li>Although not mandatory, it's best to use a <code spellcheck="false">RightPanelWidget</code> instead
+ of a <code spellcheck="false">BasicWidget</code> or a <code spellcheck="false">NoteContextAwareWidget</code>.</li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
</table>
+ </figure>
<p>To position the widget somewhere else, just change the value passed to
<code
spellcheck="false">get parentWidget()</code>for legacy widgets or the <code spellcheck="false">parent</code> field
diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Examples/New Task launcher button.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Examples/New Task launcher button.html
index b7e3c724f7..7f387c90a3 100644
--- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Examples/New Task launcher button.html
+++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Frontend Basics/Examples/New Task launcher button.html
@@ -39,14 +39,15 @@
<a
href="#root/_help_s8alTXmpFR61">refresh the application</a>.</p>
<h2>Understanding how the script works</h2>
-<table class="ck-table-resized">
- <colgroup>
- <col style="width:50%;">
+<figure class="table">
+ <table class="ck-table-resized">
+ <colgroup>
<col style="width:50%;">
- </colgroup>
- <tbody>
- <tr>
- <td><pre><code class="language-text-x-trilium-auto">api.addButtonToToolbar({
+ <col style="width:50%;">
+ </colgroup>
+ <tbody>
+ <tr>
+ <td><pre><code class="language-text-x-trilium-auto">api.addButtonToToolbar({
title: "New task",
icon: "task",
shortcut: "alt+n",
@@ -54,83 +55,84 @@
// [...]
}
});</code></pre>
- </td>
- <td>
- <p>This uses the <a href="#root/_help_yIhgI5H7A2Sm">Front-end API</a> to create a
- icon in the&nbsp;<a class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>,
- by specifying:</p>
- <ul>
- <li>A title</li>
- <li>A corresponding boxicons icon (without the <code spellcheck="false">bx-</code> prefix).</li>
- <li>Optionally, a keyboard shortcut to assign to it.</li>
- <li>The action, which will be executed when the button is pressed.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><pre><code class="language-text-x-trilium-auto">const taskNoteId = await api.runOnBackend(() =&gt; {
+ </td>
+ <td>
+ <p>This uses the <a href="#root/_help_yIhgI5H7A2Sm">Front-end API</a> to create a
+ icon in the&nbsp;<a class="reference-link" href="#root/_help_xYmIYSP6wE3F">Launch Bar</a>,
+ by specifying:</p>
+ <ul>
+ <li>A title</li>
+ <li>A corresponding boxicons icon (without the <code spellcheck="false">bx-</code> prefix).</li>
+ <li>Optionally, a keyboard shortcut to assign to it.</li>
+ <li>The action, which will be executed when the button is pressed.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><pre><code class="language-text-x-trilium-auto">const taskNoteId = await api.runOnBackend(() =&gt; {
// Shown below.
return resp.note.noteId;
});</code></pre>
- </td>
- <td>
- <ul>
- <li>This portion of code is actually executed on the server (backend) and
- not on the client (i.e. browser).
- <ul>
- <li>The reason is that the creating notes is the responsibility of the server.</li>
- </ul>
- </li>
- <li>Here we can also see that it is possible to return results from the server
- execution and read them in the client (<code spellcheck="false">taskNoteId</code>).</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><pre><code class="language-text-x-trilium-auto">const todoRootNote = api.getNoteWithLabel("taskTodoRoot");</code></pre>
- </td>
- <td>
- <ul>
- <li>Here we identify a note with the <a href="#root/_help_zEY4DaJG4YT5">label</a>
- <code
- spellcheck="false">#taskTodoRoot</code>. This is how the&nbsp;<a class="reference-link" href="#root/_help_xYjQUYhpbUEW">Task Manager</a>&nbsp;showcase
- knows where to place all the different tasks.</li>
- <li>Normally this might return a <code spellcheck="false">null</code> value
- if no such note could be identified, but error handling is outside the
- scope of this example.&nbsp;</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><pre><code class="language-text-x-trilium-auto">const resp = api.createTextNote(todoRootNote.noteId, "New task", "")</code></pre>
- </td>
- <td>
- <ul>
- <li>We create a new child note within the to-do root note (first argument)
- with the title “New task" (second argument) and no content by default (third
- argument).</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><pre><code class="language-text-x-trilium-auto">await api.waitUntilSynced();</code></pre>
- </td>
- <td>
- <ul>
- <li>Back on the client, since we created a new note on the server, we now
- need to wait for the change to be reflected in the client.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><pre><code class="language-text-x-trilium-auto">await api.activateNewNote(taskNoteId);</code></pre>
- </td>
- <td>
- <ul>
- <li>Since we know the <a href="#root/_help_m1lbrzyKDaRB">ID</a> of the newly created
- note, all we have to do now is to show this note to the user.</li>
- </ul>
- </td>
- </tr>
- </tbody>
-</table>
\ No newline at end of file
+ </td>
+ <td>
+ <ul>
+ <li>This portion of code is actually executed on the server (backend) and
+ not on the client (i.e. browser).
+ <ul>
+ <li>The reason is that the creating notes is the responsibility of the server.</li>
+ </ul>
+ </li>
+ <li>Here we can also see that it is possible to return results from the server
+ execution and read them in the client (<code spellcheck="false">taskNoteId</code>).</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><pre><code class="language-text-x-trilium-auto">const todoRootNote = api.getNoteWithLabel("taskTodoRoot");</code></pre>
+ </td>
+ <td>
+ <ul>
+ <li>Here we identify a note with the <a href="#root/_help_zEY4DaJG4YT5">label</a>
+ <code
+ spellcheck="false">#taskTodoRoot</code>. This is how the&nbsp;<a class="reference-link" href="#root/_help_xYjQUYhpbUEW">Task Manager</a>&nbsp;showcase
+ knows where to place all the different tasks.</li>
+ <li>Normally this might return a <code spellcheck="false">null</code> value
+ if no such note could be identified, but error handling is outside the
+ scope of this example.&nbsp;</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><pre><code class="language-text-x-trilium-auto">const resp = api.createTextNote(todoRootNote.noteId, "New task", "")</code></pre>
+ </td>
+ <td>
+ <ul>
+ <li>We create a new child note within the to-do root note (first argument)
+ with the title “New task" (second argument) and no content by default (third
+ argument).</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><pre><code class="language-text-x-trilium-auto">await api.waitUntilSynced();</code></pre>
+ </td>
+ <td>
+ <ul>
+ <li>Back on the client, since we created a new note on the server, we now
+ need to wait for the change to be reflected in the client.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><pre><code class="language-text-x-trilium-auto">await api.activateNewNote(taskNoteId);</code></pre>
+ </td>
+ <td>
+ <ul>
+ <li>Since we know the <a href="#root/_help_m1lbrzyKDaRB">ID</a> of the newly created
+ note, all we have to do now is to show this note to the user.</li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</figure>
\ No newline at end of file