chore(monorepo): put back docs

docs/User Guide/User Guide/Advanced Usage/Advanced Showcases/Day Notes.md

@@ -0,0 +1,103 @@
+# Day Notes
+A common pattern in note-taking is that a lot of notes will be centered around a certain date - e.g. you have some tasks which needs to be done on a certain date, you have meeting minutes from a certain date, you have your thoughts etc. and it all revolves around a date on which they occurred. For this reason, it makes sense to create a certain "day workspace" which will centralize all those notes relevant for a certain date.
+
+For this, Trilium provides a concept of "day note". Trilium semi-automatically generates a single note for each day. Under this note you can save all those relevant notes.
+
+Select an existing day note, and the menubar contains a calendar widget. Select any day to create a note for that day. 
+
+![](1_Day%20Notes_image.png)
+
+This pattern works well also because of [Cloning Notes](../../Basic%20Concepts%20and%20Features/Notes/Cloning%20Notes.md) functionality - note can appear in multiple places in the note tree, so besides appearing under day note, it can also be categorized into other notes.
+
+## Demo
+
+![](Day%20Notes_image.png)
+
+You can see the structure of day notes appearing under "Journal" note - there's a note for the whole year 2025, under it, you have "03 - March" which then contains "09 - Monday". This is our "day note" which contains some text in its content and also has some child notes (some of them are from [Task manager](Task%20Manager.md)).
+
+You can also notice how this day note has [promoted attribute](../Attributes/Promoted%20Attributes.md) "weight" where you can track your daily weight. This data is then used in [Weight tracker](Weight%20Tracker.md).
+
+## Week Note and Quarter Note
+
+Week and quarter notes are disabled by default, since it might be too much for some people. To enable them, you need to set `#enableWeekNotes` and `#enableQuarterNotes` attributes on the root calendar note, which is identified by `#calendarRoot` label. Week note is affected by the first week of year option. Be careful when you already have some week notes created, it will not automatically change the existing week notes and might lead to some duplicates.
+
+## Templates
+
+Trilium provides [template](../Templates.md) functionality, and it could be used together with day notes.
+
+You can define one of the following relations on the root of the journal (identified by `#calendarRoot` label):
+
+*   yearTemplate
+*   quarterTemplate (if `#enableQuarterNotes` is set)
+*   monthTemplate
+*   weekTemplate (if `#enableWeekNotes` is set)
+*   dateTemplate
+
+All of these are relations. When Trilium creates a new note for year or month or date, it will take a look at the root and attach a corresponding `~template` relation to the newly created role. Using this, you can e.g. create your daily template with e.g. checkboxes for daily routine etc.
+
+## Naming pattern
+
+You can customize the title of generated journal notes by defining a `#datePattern`, `#weekPattern`, `#monthPattern`, `#quarterPattern` and `#yearPattern` attribute on a root calendar note (identified by `#calendarRoot` label). The naming pattern replacements follow a level-up compatibility - each level can use replacements from itself and all levels above it. For example, `#monthPattern` can use month, quarter and year replacements, while `#weekPattern` can use week, month, quarter and year replacements. But it is not possible to use week replacements in `#monthPattern`.
+
+### Date pattern
+
+It's possible to customize the title of generated date notes by defining a `#datePattern` attribute on a root calendar note (identified by `#calendarRoot` label). Following are possible values:
+
+*   `{isoDate}` results in an ISO 8061 formatted date (e.g. "2025-03-09" for March 9, 2025)
+*   `{dateNumber}` results in a number like `9` for the 9th day of the month, `11` for the 11th day of the month
+*   `{dateNumberPadded}` results in a number like `09` for the 9th day of the month, `11` for the 11th day of the month
+*   `{ordinal}` is replaced with the ordinal date (e.g. 1st, 2nd, 3rd) etc.
+*   `{weekDay}` results in the full day name (e.g. `Monday`)
+*   `{weekDay3}` is replaced with the first 3 letters of the day, e.g. Mon, Tue, etc.
+*   `{weekDay2}` is replaced with the first 2 letters of the day, e.g. Mo, Tu, etc.
+
+The default is `{dateNumberPadded} - {weekDay}`
+
+### Week pattern
+
+It is also possible to customize the title of generated week notes through the `#weekPattern` attribute on the root calendar note. The options are:
+
+*   `{weekNumber}` results in a number like `9` for the 9th week of the year, `11` for the 11th week of the year
+*   `{weekNumberPadded}` results in a number like `09` for the 9th week of the year, `11` for the 11th week of the year
+*   `{shortWeek}` results in a short week string like `W9` for the 9th week of the year, `W11` for the 11th week of the year
+*   `{shortWeek3}` results in a short week string like `W09` for the 9th week of the year, `W11` for the 11th week of the year
+
+The default is `Week {weekNumber}`
+
+### Month pattern
+
+It is also possible to customize the title of generated month notes through the `#monthPattern` attribute on the root calendar note. The options are:
+
+*   `{isoMonth}` results in an ISO 8061 formatted month (e.g. "2025-03" for March 2025)
+*   `{monthNumber}` results in a number like `9` for September, and `11` for November
+*   `{monthNumberPadded}` results in a number like `09` for September, and `11` for November
+*   `{month}` results in the full month name (e.g. `September` or `October`)
+*   `{shortMonth3}` is replaced with the first 3 letters of the month, e.g. Jan, Feb, etc.
+*   `{shortMonth4}` is replaced with the first 4 letters of the month, e.g. Sept, Octo, etc.
+
+The default is `{monthNumberPadded} - {month}`
+
+### Quarter pattern
+
+It is also possible to customize the title of generated quarter notes through the `#quarterPattern` attribute on the root calendar note. The options are:
+
+*   `{quarterNumber}` results in a number like `1` for the 1st quarter of the year
+*   `{shortQuarter}` results in a short quarter string like `Q1` for the 1st quarter of the year
+
+The default is `Quarter {quarterNumber}`
+
+### Year pattern
+
+It is also possible to customize the title of generated year notes through the `#yearPattern` attribute on the root calendar note. The options are:
+
+*   `{year}` results in the full year (e.g. `2025`)
+
+The default is `{year}`
+
+## Implementation
+
+Trilium has some special support for day notes in the form of [backend Script API](https://triliumnext.github.io/Notes/backend_api/BackendScriptApi.html) - see e.g. getDayNote() function.
+
+Day (and year, month) notes are created with a label - e.g. `#dateNote="2025-03-09"` this can then be used by other scripts to add new notes to day note etc.
+
+Journal also has relation `child:child:child:template=Day template` (see \[\[attribute inheritance\]\]) which effectively adds \[\[template\]\] to day notes (grand-grand-grand children of Journal). Please note that, when you enable week notes or quarter notes, it will not automatically change the relation for the child level.

docs/User Guide/User Guide/Advanced Usage/Advanced Showcases/Task Manager.md

@@ -0,0 +1,63 @@
+# Task Manager
+Task Manager is a [promoted attributes](../Attributes/Promoted%20Attributes.md) and [scripts](../../Scripting.md)showcase present in the [demo notes](../Database.md).
+
+## Demo
+
+![](Task%20Manager_task-manager.png)
+
+Task Manager manages outstanding (TODO) tasks and finished tasks (non-empty doneDate attribute). Outstanding tasks are further categorized by location and arbitrary tags - whenever you change tag attribute in the task note, this task is then automatically moved to appropriate location.
+
+Task Manager also integrates with [day notes](Day%20Notes.md) - notes are [cloned](../../Basic%20Concepts%20and%20Features/Notes/Cloning%20Notes.md) into day note to both todoDate note and doneDate note (with [prefix](../../Basic%20Concepts%20and%20Features/Navigation/Tree%20Concepts.md) of either "TODO" or "DONE").
+
+## Implementation
+
+New tasks are created in the TODO note which has `~child:template` [relation](../Attributes.md)(see [attribute inheritance](../Attributes/Attribute%20Inheritance.md)) pointing to the task template.
+
+### Attributes
+
+Task template defines several [promoted attributes](../Attributes/Promoted%20Attributes.md) - todoDate, doneDate, tags, location. Importantly it also defines `~runOnAttributeChange` relation - [event](../../Scripting/Events.md) handler which is run on attribute change. This [script](../../Scripting.md) handles when e.g. we fill out the doneDate attribute - meaning the task is done and should be moved to "Done" note and removed from TODO, locations and tags.
+
+### New task button
+
+There's also "button" note which contains simple script which adds a button to create new note (task) in the TODO note.
+
+```
+api.addButtonToToolbar({
+    title: 'New task',
+    icon: 'check',
+    shortcut: 'alt+n',
+    action: async () => {
+        // creating notes is backend (server) responsibility so we need to pass
+        // the control there
+        const taskNoteId = await api.runOnBackend(async () => {
+            const todoRootNote = await api.getNoteWithLabel('taskTodoRoot');
+            const {note} = await api.createNote(todoRootNote.noteId, 'new task', '');
+
+            return note.noteId;
+        });
+
+        // we got an ID of newly created note and we want to immediatelly display it
+        await api.activateNewNote(taskNoteId);
+    }
+});
+```
+
+### CSS
+
+In the demo screenshot above you may notice that TODO tasks are in red color and DONE tasks are green.
+
+This is done by having this CSS [code note](../../Note%20Types/Code.md) which defines extra CSS classes:
+
+```
+span.fancytree-node.todo .fancytree-title {
+    color: red !important;
+}
+
+span.fancytree-node.done .fancytree-title {
+    color: green !important;
+}
+```
+
+This [code note](../../Note%20Types/Code.md) has `#appCss` [label](../Attributes.md)which is recognized by Trilium on startup and loaded as CSS into the application.
+
+Second part of this functionality is based in event handler described above which assigns `#cssClass` label to the task to either "done" or "todo" based on the task status.

docs/User Guide/User Guide/Advanced Usage/Advanced Showcases/Weight Tracker.md

@@ -0,0 +1,70 @@
+# Weight Tracker
+![](Weight%20Tracker_image.png)
+
+The `Weight Tracker` is a [Script API](../../Scripting/Script%20API.md) showcase present in the [demo notes](../Database.md).
+
+By adding `weight` as a [promoted attribute](../Attributes/Promoted%20Attributes.md) in the [template](../Templates.md) from which [day notes](Day%20Notes.md) are created, you can aggregate the data and plot weight change over time.
+
+## Implementation
+
+The `Weight Tracker` note in the screenshot above is of the type `Render Note`. That type of note doesn't have any useful content itself. Instead it is a placeholder where a [script](../../Scripting.md) can render its output.
+
+Scripts for `Render Notes` are defined in a [relation](../Attributes.md) called `~renderNote`. In this example, it's the `Weight Tracker`'s child `Implementation`. The Implementation consists of two [code notes](../../Note%20Types/Code.md) that contain some HTML and JavaScript respectively, which load all the notes with a `weight` attribute and display their values in a chart.
+
+To actually render the chart, we're using a third party library called [chart.js](https://www.chartjs.org/)which is imported as an attachment, since it's not built into Trilium.
+
+### Code
+
+Here's the content of the script which is placed in a [code note](../../Note%20Types/Code.md) of type `JS Frontend`:
+
+```
+async function getChartData() {
+    const days = await api.runOnBackend(async () => {
+        const notes = api.getNotesWithLabel('weight');
+        const days = [];
+
+        for (const note of notes) {
+            const date = note.getLabelValue('dateNote');
+            const weight = parseFloat(note.getLabelValue('weight'));
+
+            if (date && weight) {
+                days.push({ date, weight });
+            }
+        }
+
+        days.sort((a, b) => a.date > b.date ? 1 : -1);
+
+        return days;
+    });
+
+    const datasets = [
+        {
+            label: "Weight (kg)",
+            backgroundColor: 'red',
+            borderColor: 'red',
+            data: days.map(day => day.weight),
+            fill: false,
+            spanGaps: true,
+            datalabels: {
+                display: false
+            }
+        }
+    ];
+
+    return {
+        datasets: datasets,
+        labels: days.map(day => day.date)
+    };
+}
+
+const ctx = $("#canvas")[0].getContext("2d");
+
+new chartjs.Chart(ctx, {
+    type: 'line',
+    data: await getChartData()
+});
+```
+
+## How to remove the Weight Tracker button from the top bar
+
+In the link map of the `Weight Tracker`, there is a note called `Button`. Open it and delete or comment out its contents. The `Weight Tracker` button will disappear after you restart Trilium.