chore(docs): update with deterministic order

This commit is contained in:
Elian Doran
2025-03-11 18:05:42 +02:00
parent a2795f3440
commit 0af357ece8
103 changed files with 250 additions and 236 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 136 KiB

After

Width:  |  Height:  |  Size: 100 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 188 KiB

After

Width:  |  Height:  |  Size: 212 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 212 KiB

After

Width:  |  Height:  |  Size: 583 KiB

View File

@@ -20,7 +20,7 @@ If that doesn't work, then:
Once you have Dev Tools open, click on "Console" tab:
![](1_Error%20logs_image.png)
![](Error%20logs_image.png)
Copy-paste (or screenshot) the logs. It's better to provide not just errors, but the whole log, which might provide context while analyzing the bug.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 100 KiB

After

Width:  |  Height:  |  Size: 136 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 583 KiB

After

Width:  |  Height:  |  Size: 188 KiB

View File

@@ -1,5 +1,5 @@
# "TriliumNext Notes" Not Opened
![](2_TriliumNext%20Notes%20Not%20Open.png)
# "TriliumNext Notes" Not Opened
![](1_TriliumNext%20Notes%20Not%20Open.png)
When running TriliumNext for the first time or updating to a newer version, macOS will prevent its execution.
@@ -13,4 +13,4 @@ To bypass this issue, follow these steps:
| | |
| --- | --- |
| ![](TriliumNext%20Notes%20Not%20Open.png) <br> <br>The privacy settings in “System Settings”, showing the alert that TriliumNext was blocked. | ![](2_TriliumNext%20Notes%20Not%20Open.png) <br> <br>The confirmation screen to bypass the run restrictions. |
| ![](2_TriliumNext%20Notes%20Not%20Open.png) <br> <br>The privacy settings in “System Settings”, showing the alert that TriliumNext was blocked. | ![](1_TriliumNext%20Notes%20Not%20Open.png) <br> <br>The confirmation screen to bypass the run restrictions. |