mirror of
https://github.com/zadam/trilium.git
synced 2025-06-06 18:08:33 +02:00
Updated Document (markdown)
parent
f96add393f
commit
a7a6c655a8
@ -17,3 +17,9 @@ When you run Trilium for the first time, it will generate a demo document for yo
|
|||||||
### Restoring demo document
|
### Restoring demo document
|
||||||
|
|
||||||
In some cases you might want to take a look at the demo document after you deleted it. Or you might want to see if there was something added (sometimes we add a new feature demonstration into demo document). In such case you can just [download .tar archive](https://github.com/zadam/trilium/raw/stable/db/demo.zip) of the latest document and import it somewhere into the tree (right click on a note where you want to import the demo document and choose "Import").
|
In some cases you might want to take a look at the demo document after you deleted it. Or you might want to see if there was something added (sometimes we add a new feature demonstration into demo document). In such case you can just [download .tar archive](https://github.com/zadam/trilium/raw/stable/db/demo.zip) of the latest document and import it somewhere into the tree (right click on a note where you want to import the demo document and choose "Import").
|
||||||
|
|
||||||
|
## Manually modifying the document
|
||||||
|
|
||||||
|
Trilium provides a lot of flexibility, but with that you can also potentially shoot yourself in the foot (e.g. with startup script which blanks the app view).
|
||||||
|
|
||||||
|
In such cases you can manually fix notes on the database layer - you can use e.g. [https://sqlitebrowser.org/](https://sqlitebrowser.org/) to open `document.db` file, find problematic notes and manually fix them. Don't forget to commit / write changes after you're done.
|
Loading…
x
Reference in New Issue
Block a user