Merge remote-tracking branch 'origin/master'

Backup.md

@@ -21,6 +21,7 @@ Let's assume you want to restore the weekly backup, here's how to do it:
 * at this point stop/kill Trilium
 * delete `~/trilium-data/document.db`, `~/trilium-data/document.db-wal` and `~/trilium-data/document.db-shm` (latter two files are auto generated)
 * copy and rename this `~/trilium-data/backup/backup-weekly.db` to `~/trilium-data/document.db`
+* make sure that the file is writable, e.g. with `chmod 600 document.db`
 * start Trilium again
 
 If you have configured sync then you need to do it across all members of the sync cluster, otherwise older version (restored backup) of the document will be detected and synced to the newer version.

Patterns-of-personal-knowledge-base.md

@@ -140,7 +140,7 @@ This where I store hard "knowledge" - summarized topics and findings from differ
 
 ### Work knowledge base
 
-I usually keep top level note for the company I currently work at (past jobs are moved elsewhere). I track basic organization of the company (divisions, business units), who is who ([relation maps](https://github.com/zadam/trilium/wiki/Relation-maps)) are again useful for visualization), projects I work at etc.
+I usually keep top level note for the company I currently work at (past jobs are moved elsewhere). I track basic organization of the company (divisions, business units), who is who ([relation maps](https://github.com/zadam/trilium/wiki/Relation-map)) are again useful for visualization), projects I work at etc.
 
 There's a number of credentials to various company services I need to use. Companies usually have a bunch of complex processes and tools. I record meeting minutes, link to the company wiki (which is usually difficult to find relevant info). In general there's a lot of company specific information I need to know or need have them at hand in a nice structure I can understand. Often it's just copy pasting and reshuffling of existing information into something more understandable for me.
 

Release-notes-v0.48.md

@@ -25,7 +25,7 @@ Now supports also hierarchical view of the notes:
 Mermaid diagrams
 ----------------
 
-Thanks to @abitofeverything for this contribution!
+Thanks to [@abitofevrything](https://github.com/abitofevrything) for this contribution!
 
 ![](relnotes48/mermaid.png)
 
@@ -85,7 +85,9 @@ all the `await` (and `async`) should disappear from the backend code, but should
 
 ### Migrate custom themes
 
-With the redesign you might need to adjust your custom themes - especially if you don't use only the CSS variables but also trilium's classes.
+With the redesign you might need to adjust your custom themes - check the modified list of available CSS variables in the [default theme](https://github.com/zadam/trilium/blob/master/src/public/stylesheets/theme-light.css). If your theme also uses CSS selectors then that will probably have to be rewritten as well.
+
+Themes are annotated with `#appTheme` label, previously this label could but did not have to contain value - with this release the value is required so define the label as e.g. `#appTheme=my-theme-name`.
 
 Additionally, CSS themes are now loaded differently than before - previously all themes were loaded at the startup and which one was active was decided by the active CSS class. Themes were then prefixed like this:
 
@@ -104,7 +106,7 @@ Additionally, CSS themes are now loaded differently than before - previously all
 
 This prefixing is not needed anymore (and also doesn't work anymore). Remove the prefixes like this:
 
-    root {
+    :root {
         --main-font-family: 'Raleway';
         --main-font-size: normal;
         

Themes.md

@@ -6,7 +6,7 @@ This is what it looks like:
 
 ## Custom CSS themes
 
-Trilium provides a concept of custom user theme. You can make yourself one by creating a CSS [[code note|code notes]] and annotating it with `appTheme` [[label|attributes]].
+Trilium provides a concept of custom user theme. You can make yourself one by creating a CSS [[code note|code notes]] and annotating it with `#appTheme=my-theme-name` [[label|attributes]].
 
 You can see an example of what you can put there below:
 
@@ -68,8 +68,6 @@ body.theme-steel-blue .CodeMirror {
 
 We define a custom font (provided by [[custom request handler]]) and then just define a bunch of CSS variables. These variables are then used in Trilium's CSS stylesheets. You can also use standard CSS selectors for further customization (open dev tools using `CTRL-SHIFT-I` to help with that), but keep in mind that HTML structure can change in future releases which might break your selectors. For that reason it is better to restrict yourself to use CSS variables as much as possible.
 
-All selectors should be prefixed with `body.theme-my-theme` so that the stylesheet is applied only when your theme is selected. This class name is automatically created from note's name - e.g. "My theme" will transform into `theme-my-theme` (`theme-` is a common prefix). If you want to manually specify the class name you set it as a value for `appTheme` (`theme-` prefix is prepended to final class as well).
-
 To activate your custom theme, go to Options -> Appearance. In the select box you should see all notes (themes) labeled with `appTheme`.
 
 If you make a change to your theme, you should reload the frontend by pressing `CTRL-R` so the changes will take effect.