diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation.html index 7b999c53b..73b4c3ef3 100644 --- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation.html +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation.html @@ -1,16 +1,26 @@

One of the Trilium's goals is to provide fast and comfortable navigation between notes.

Backwards and forward

-

You can use alt-left and alt-right to move back and forward in history - of viewed pages.

-

This works identically to browser backwards / forwards, it's actually - using built-in browser support for this.

-

- -

+

To move back and forward in history of viewed pages:

+

Jump to note

-

This is useful to quickly find and view arbitrary notes - click on Jump to button - on the top or press Ctrl + J . Then type part of the - note name and autocomplete will help you pick the desired note.

-

See Jump to Note for +

This is useful to quickly find and view arbitrary notes - click on + Jump tobutton on the top or press Ctrl + J . + Then type part of the note name and autocomplete will help you pick the + desired note.

+

See Jump to... for more information.

\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation_image.png b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation_image.png deleted file mode 100644 index 2ea269012..000000000 Binary files a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Note Navigation_image.png and /dev/null differ diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Tabs.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Tabs.html index 8d9b0ad58..e4c690f92 100644 --- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Tabs.html +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Tabs.html @@ -6,37 +6,48 @@

Layout

Depending on the Vertical and horizontal layout:

Interaction

Keyboard interaction

Since tabs are a commonly used feature, there are multiple keyboard shortcuts that can be used:

\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Render Note.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Render Note.html index c65b789d0..f0f720b87 100644 --- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Render Note.html +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Render Note.html @@ -7,13 +7,10 @@ via an attribute.

Creating a render note

    -
  1. Create a Code note - with the HTML language, with what needs to be displayed (for example - <p>Hello world.</p>).
    2. -
  2. Create a Render Note.
    3. -
  3. Assign the renderNote relation to +
  4. Create a Code note + with the HTML language, with what needs to be displayed (for example <p>Hello world.</p>).
    5. +
  5. Create a Render Note.
    6. +
  6. Assign the renderNote relation to point at the previously created code note.

Legacy scripting using jQuery

@@ -29,7 +26,7 @@ The current date & time is <span class="date"></span>
const $dateEl = api.$container.find(".date");
 $dateEl.text(new Date());
-

Now create a render note at any place and set its ~renderNote relation +

Now create a render note at any place and set its ~renderNote relation to point to the HTML note. When the render note is accessed it will display:

Current date & time @@ -42,33 +39,37 @@ $dateEl.text(new Date()); need to provide a HTML anymore.

Here are the steps to creating a simple render note:

    -
  1. Create a note of type Render Note.
    2. -
  2. -

    Create a child Code note +

  3. +

    Create a note of type Render Note.

    +
    4. +
  4. +

    Create a child Code note with JSX as the language. -
    As an example, use the following content:

    export default function() {
+      
    As an example, use the following content:
    export default function() {
     return (
         <>
             <p>Hello world.</p>
         </>
     );
 }
    
-
    5. -
  5. In the parent render note, define a ~renderNote relation - pointing to the newly created child.
    6. -
  6. Refresh the render note and it should display a “Hello world” message.
    7. + +
  7. +

    In the parent render note, define a ~renderNote relation pointing + to the newly created child.

    +
    8. +
  8. +

    Refresh the render note and it should display a “Hello world” message.

    +

Refreshing the note

It's possible to refresh the note via:

Examples

\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Common concepts/Script bundles.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Common concepts/Script bundles.html index 2abeaa288..f9d7fab75 100644 --- a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Common concepts/Script bundles.html +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Scripting/Common concepts/Script bundles.html @@ -1,22 +1,22 @@ -

For both Render Note and +

For both Render Note and more complicated scripts, it's generally useful to split the code into - multiple Code notes.

+ multiple Code notes.

When a script is run, the sub-children of the script being run (or the  Render Note) are checked for children. If the children are Code notes + class="reference-link" href="#root/_help_HcABDtFCkbFN">Render Note) are checked for children. If the children are Code notes of the corresponding type (front-end or backend) as the code being run, they will be evaluated as well.

The collection of a script and its child notes is called a bundle. A child note inside a bundle is called a module.

As a basic example of dependencies, consider the following note structure: