Skip to content

Build your personal knowledge base with Trilium Notes

feat(collections/list): move expand/collapse to toolbar

Elian Doran56eda8d45307
diff --git a/apps/client/src/widgets/collections/legacy/ListExpandControls.css b/apps/client/src/widgets/collections/legacy/ListExpandControls.css
new file mode 100644
index 0000000000..dc9d156bfe
--- /dev/null
+++ b/apps/client/src/widgets/collections/legacy/ListExpandControls.css
@@ -0,0 +1,20 @@
+.list-expand-controls {
+ display: inline-flex;
+ align-items: center;
+ gap: 0.5em;
+
+ .list-expand-split {
+ display: inline-flex;
+ align-items: center;
+
+ > .icon-action {
+ border-start-end-radius: 0;
+ border-end-end-radius: 0;
+ }
+
+ > .dropdown .icon-action {
+ border-start-start-radius: 0;
+ border-end-start-radius: 0;
+ }
+ }
+}
diff --git a/apps/client/src/widgets/collections/legacy/ListExpandControls.spec.tsx b/apps/client/src/widgets/collections/legacy/ListExpandControls.spec.tsx
new file mode 100644
index 0000000000..12d50cbc5d
--- /dev/null
+++ b/apps/client/src/widgets/collections/legacy/ListExpandControls.spec.tsx
@@ -0,0 +1,80 @@
+import { act } from "preact/test-utils";
+import { beforeEach, describe, expect, it, vi } from "vitest";
+
+const writes = vi.hoisted(() => ({
+ setLabel: vi.fn(),
+ removeAttributeById: vi.fn()
+}));
+
+vi.mock("../../../services/attributes", async (importOriginal) => {
+ const actual = await importOriginal<typeof import("../../../services/attributes")>();
+ return {
+ ...actual,
+ default: {
+ ...actual.default,
+ setLabel: (...args: unknown[]) => writes.setLabel(...args),
+ removeAttributeById: (...args: unknown[]) => writes.removeAttributeById(...args)
+ }
+ };
+});
+
+import froca from "../../../services/froca";
+import { buildNote } from "../../../test/easy-froca";
+import { renderInto } from "../../../test/render";
+import ListExpandControls from "./ListExpandControls";
+
+async function click(button: HTMLElement | null | undefined) {
+ await act(async () => {
+ button?.click();
+ await Promise.resolve();
+ });
+}
+
+describe("ListExpandControls", () => {
+ beforeEach(() => vi.clearAllMocks());
+
+ it("collapses the collection's own expanded label, leaving an inherited one alone", async () => {
+ const parent = buildNote({
+ title: "Parent",
+ "#expanded(inheritable)": "3",
+ children: [ { id: "collection", title: "Collection", "#expanded": "2" } ]
+ });
+ const collection = froca.getNoteFromCache("collection");
+ const inherited = parent.getOwnedLabels("expanded")[0];
+ const owned = collection?.getOwnedLabels("expanded")[0];
+ if (!collection || !owned) throw new Error("collection fixture missing");
+
+ const container = renderInto(<ListExpandControls note={collection} />);
+ await click(container.querySelector<HTMLElement>(".list-expand-controls > .icon-action"));
+
+ expect(writes.removeAttributeById).toHaveBeenCalledTimes(1);
+ expect(writes.removeAttributeById).toHaveBeenCalledWith("collection", owned.attributeId);
+ expect(writes.removeAttributeById).not.toHaveBeenCalledWith("collection", inherited.attributeId);
+ });
+
+ it("expands the direct children from the main button", async () => {
+ const collection = buildNote({ title: "Collection" });
+
+ const container = renderInto(<ListExpandControls note={collection} />);
+ await click(container.querySelector<HTMLElement>(".list-expand-split > .icon-action"));
+
+ expect(writes.setLabel).toHaveBeenCalledWith(collection.noteId, "expanded", "");
+ });
+
+ it("offers every depth from the split's menu, and sets the one picked", async () => {
+ const collection = buildNote({ title: "Collection" });
+
+ const container = renderInto(<ListExpandControls note={collection} />);
+ await click(container.querySelector<HTMLElement>(".list-expand-split .dropdown button"));
+
+ const items = await vi.waitFor(() => {
+ const found = [ ...document.querySelectorAll<HTMLElement>(".tn-popup li.dropdown-item") ];
+ expect(found).toHaveLength(6);
+ return found;
+ });
+
+ await click(items.at(-1));
+
+ expect(writes.setLabel).toHaveBeenCalledWith(collection.noteId, "expanded", "all");
+ });
+});
diff --git a/apps/client/src/widgets/collections/legacy/ListExpandControls.tsx b/apps/client/src/widgets/collections/legacy/ListExpandControls.tsx
new file mode 100644
index 0000000000..30b82217eb
--- /dev/null
+++ b/apps/client/src/widgets/collections/legacy/ListExpandControls.tsx
@@ -0,0 +1,77 @@
+import "./ListExpandControls.css";
+
+import FNote from "../../../entities/fnote";
+import attributes from "../../../services/attributes";
+import { t } from "../../../services/i18n";
+import ActionButton from "../../react/ActionButton";
+import Dropdown from "../../react/Dropdown";
+import { FormDropdownDivider, FormListItem } from "../../react/FormList";
+import { useNoteLabel } from "../../react/hooks";
+
+const MAX_DEPTH = 5;
+
+export default function ListExpandControls({ note }: { note: FNote }) {
+ const [ expanded ] = useNoteLabel(note, "expanded");
+
+ async function collapseAll() {
+ // Removing only owned labels keeps an `expanded` inherited from a parent in force.
+ for (const attribute of note.getOwnedLabels("expanded")) {
+ await attributes.removeAttributeById(note.noteId, attribute.attributeId);
+ }
+ }
+
+ async function expandTo(depth: number | "all") {
+ // Depth 1 is the label's empty value; an absent label and 0 both mean fully collapsed.
+ const value = depth === 1 ? "" : String(depth);
+ if (value === note.getLabelValue("expanded")) return;
+ await attributes.setLabel(note.noteId, "expanded", value);
+ }
+
+ return (
+ <div className="list-expand-controls">
+ <ActionButton
+ icon="bx bx-layer-minus"
+ text={t("book_properties.collapse_all_notes")}
+ onClick={() => void collapseAll()}
+ />
+ <div className="list-expand-split">
+ <ActionButton
+ icon="bx bx-move-vertical"
+ text={t("book_properties.expand_tooltip")}
+ onClick={() => void expandTo(1)}
+ />
+ <Dropdown
+ buttonClassName="bx bx-chevron-down"
+ buttonProps={{ "aria-label": t("split_button.more_actions") }}
+ iconAction
+ hideToggleArrow
+ noSelectButtonStyle
+ title={t("split_button.more_actions")}
+ placement="bottom-end"
+ mobileBottomSheet
+ >
+ <FormListItem
+ onClick={() => void expandTo(1)}
+ checked={expanded === ""}
+ checkable
+ >{t("book_properties.expand_first_level")}</FormListItem>
+ <FormDropdownDivider />
+ {Array.from({ length: MAX_DEPTH - 1 }, (_, index) => index + 2).map((depth) => (
+ <FormListItem
+ key={depth}
+ onClick={() => void expandTo(depth)}
+ checked={expanded === String(depth)}
+ checkable
+ >{t("book_properties.expand_nth_level", { depth })}</FormListItem>
+ ))}
+ <FormDropdownDivider />
+ <FormListItem
+ onClick={() => void expandTo("all")}
+ checked={expanded === "all"}
+ checkable
+ >{t("book_properties.expand_all_levels")}</FormListItem>
+ </Dropdown>
+ </div>
+ </div>
+ );
+}
diff --git a/apps/client/src/widgets/collections/legacy/ListOrGridView.tsx b/apps/client/src/widgets/collections/legacy/ListOrGridView.tsx
index b2355ef959..7bc2d665ee 100644
--- a/apps/client/src/widgets/collections/legacy/ListOrGridView.tsx
+++ b/apps/client/src/widgets/collections/legacy/ListOrGridView.tsx
@@ -9,6 +9,7 @@ import attribute_renderer from "../../../services/attribute_renderer";
import content_renderer from "../../../services/content_renderer";
import { t } from "../../../services/i18n";
import link from "../../../services/link";
+import { isShare } from "../../../services/utils";
import CollectionProperties from "../../note_bars/CollectionProperties";
import { useImperativeSearchHighlighlighting, useNoteLabel, useNoteLabelBoolean, useNoteProperty } from "../../react/hooks";
import Icon from "../../react/Icon";
@@ -16,6 +17,7 @@ import NoteLink from "../../react/NoteLink";
import { ParentComponent } from "../../react/react_utils";
import { ViewModeProps } from "../interface";
import { Pager, usePagination, PaginationContext } from "../Pagination";
+import ListExpandControls from "./ListExpandControls";
import { filterChildNotes, useFilteredNoteIds } from "./utils";
import { JSX } from "preact/jsx-runtime";
import { clsx } from "clsx";
@@ -78,7 +80,8 @@ export function ListView({ note, noteIds: unfilteredNoteIds, highlightedTokens,
const searchResultsLayout = (noteType === "search") || !!listOptions?.searchResultsLayout;
const expandDepth = listOptions?.expandDepth ?? labelExpandDepth;
- return <NoteList note={note} viewMode="list-view" noteIds={noteIds} pagination={pagination}>
+ return <NoteList note={note} viewMode="list-view" noteIds={noteIds} pagination={pagination}
+ rightChildren={!isShare ? <ListExpandControls note={note} /> : undefined}>
<Card heading={listOptions?.title} className={clsx("nested-note-list", {"search-results": searchResultsLayout})}>
{pageNotes?.map(childNote => (
<ListNoteCard
@@ -124,6 +127,7 @@ interface NoteListProps {
viewMode: "list-view" | "grid-view",
noteIds: string[],
pagination: PaginationContext,
+ rightChildren?: ComponentChildren;
children: ComponentChildren
}
@@ -135,6 +139,7 @@ function NoteList(props: NoteListProps) {
<CollectionProperties
note={props.note}
centerChildren={<Pager className="note-list-top-pager" {...props.pagination} />}
+ rightChildren={props.rightChildren}
/>
{props.noteIds.length > 0 && <div className="note-list-wrapper">
diff --git a/apps/client/src/widgets/note_bars/collection-properties-config.tsx b/apps/client/src/widgets/note_bars/collection-properties-config.tsx
index ac0d10e78d..14f54b38c8 100644
--- a/apps/client/src/widgets/note_bars/collection-properties-config.tsx
+++ b/apps/client/src/widgets/note_bars/collection-properties-config.tsx
@@ -1,15 +1,11 @@
import { t } from "i18next";
-import Component from "../../components/component";
import FNote from "../../entities/fnote";
-import attributes from "../../services/attributes";
import { ROUTINE_OCCURRENCES_PER_WEEK } from "../collections/calendar/recurrence";
import { DEFAULT_MAP_LAYER_NAME, isTileUrl, MAP_LAYERS, type MapLayer } from "../collections/geomap/map_layer";
import { ViewTypeOptions } from "../collections/interface";
import { DEFAULT_THEME, getPresentationThemes } from "../collections/presentation/themes";
-import { FormDropdownDivider, FormListItem } from "../react/FormList";
-import { useNoteLabel } from "../react/hooks";
-import { BookProperty, ClickContext, ComboBoxItem } from "../react/NotePropertyMenu";
+import { BookProperty, ComboBoxItem } from "../react/NotePropertyMenu";
/** How long a row of the calendar's day and week views lasts, until `#calendar:slotDuration` says. */
export const DEFAULT_SLOT_DURATION = "00:15:00";
@@ -28,32 +24,7 @@ export const bookPropertiesConfig: Record<ViewTypeOptions, BookConfig> = {
properties: []
},
list: {
- properties: [
- {
- label: t("book_properties.collapse"),
- title: t("book_properties.collapse_all_notes"),
- type: "button",
- icon: "bx bx-layer-minus",
- async onClick({ note, triggerCommand }) {
- const { noteId } = note;
-
- // owned is important - we shouldn't remove inherited expanded labels
- for (const expandedAttr of note.getOwnedLabels("expanded")) {
- await attributes.removeAttributeById(noteId, expandedAttr.attributeId);
- }
-
- triggerCommand("refreshNoteList", { noteId });
- },
- },
- {
- label: t("book_properties.expand"),
- title: t("book_properties.expand_tooltip"),
- type: "split-button",
- icon: "bx bx-move-vertical",
- onClick: buildExpandListHandler(1),
- items: ListExpandDepth
- }
- ]
+ properties: []
},
calendar: {
properties: [
@@ -224,44 +195,3 @@ function isTimeGridCalendarView(note: FNote) {
const view = note.getLabelValue("calendar:view");
return view === "timeGridDay" || view === "timeGridWeek";
}
-
-function ListExpandDepth(context: { note: FNote, parentComponent: Component }) {
- const [ currentDepth ] = useNoteLabel(context.note, "expanded");
-
- return (
- <>
- <ListExpandDepthButton label={t("book_properties.expand_first_level")} depth={1} {...context} checked={currentDepth === ""} />
- <FormDropdownDivider />
- {Array.from({ length: 4 }, (_, i) => i + 2).map(depth => [
- <ListExpandDepthButton label={t("book_properties.expand_nth_level", { depth })} depth={depth} {...context} checked={!!currentDepth && parseInt(currentDepth, 10) === depth} />
- ])}
- <FormDropdownDivider />
- <ListExpandDepthButton label={t("book_properties.expand_all_levels")} depth="all" checked={currentDepth === "all"} {...context} />
- </>
- );
-}
-
-function ListExpandDepthButton({ label, depth, note, parentComponent, checked }: { label: string, depth: number | "all", note: FNote, parentComponent: Component, checked?: boolean }) {
- const handler = buildExpandListHandler(depth);
-
- return (
- <FormListItem
- onClick={() => handler({ note, triggerCommand: parentComponent.triggerCommand.bind(parentComponent) })}
- checked={checked}
- >{label}</FormListItem>
- );
-}
-
-function buildExpandListHandler(depth: number | "all") {
- return async ({ note, triggerCommand }: ClickContext) => {
- const { noteId } = note;
-
- const existingValue = note.getLabelValue("expanded");
- let newValue: string | undefined = typeof depth === "number" ? depth.toString() : depth;
- if (depth === 1) newValue = undefined; // maintain existing behaviour
- if (newValue === existingValue) return;
-
- await attributes.setLabel(noteId, "expanded", newValue);
- triggerCommand("refreshNoteList", { noteId });
- };
-}
diff --git a/apps/server/src/assets/help/help_content.json b/apps/server/src/assets/help/help_content.json
index 2a0e97fd00..d9e897a3e4 100644
--- a/apps/server/src/assets/help/help_content.json
+++ b/apps/server/src/assets/help/help_content.json
@@ -181,8 +181,8 @@
"_help_ZRDXGc0nAIh4": "<p>An image map is a geo map drawn over an image of your own instead of a world map, such as a floor plan, a fantasy map for a tabletop game, or a diagram to annotate. Markers and shapes work as they do on a geo map, but their positions are measured on the image instead of in latitude and longitude: in the image's own pixels, or in a coordinate system of your choosing, such as the one a video game uses.</p><h2>Creating an image map</h2><ol><li>Upload the image as a note of its own, for example by dragging the file into the note tree. PNG, JPEG, WebP and GIF images are supported; SVG images are not.</li><li>Create a geo map, or open an existing one.</li><li>Open the <span class=\"tn-icon bx bx-cog\"></span><em>Geo map properties</em> dialog from the&nbsp;<a class=\"reference-link\" href=\"#root/_help_8YBEPzcpUgxw\">Note menu</a> or from the settings menu of the&nbsp;<a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a>.</li><li>Under <em>Background</em>, set <em>Type</em> to <em>Custom image</em>, then choose the image note in <em>Image note</em>. The list only offers image notes in a format the map can draw (PNG, JPEG, WebP or GIF), and shows all of them before anything is typed.</li></ol><p>The map then shows the image instead of the world map and opens with the whole image in view. To go back to a world map, set <em>Type</em> back to <em>Vector &amp; Raster</em>. The image is switched off rather than removed: its relation is renamed to <code>~disabled:map:image</code>, so setting <em>Type</em> to <em>Custom image</em> again brings back the same image, with its coordinates. An image that the geo map inherits from a parent note or a template can only be switched off on the note that holds it.</p><p>The image note is stored in a <code>~map:image</code> <a href=\"#root/_help_Cq5X6iKQop6R\">relation</a> of the geo map, which can also be added by hand.</p><h2>Image size</h2><p>Images are resized when they are uploaded, so by default the image of a map is at most 2000 pixels on its longer side, which can be too coarse for a detailed map. To keep an image at a higher resolution, do one of the following before uploading it:</p><ul><li>In <a class=\"reference-link\" href=\"#root/_help_4TIF1oA4VQRO\">Options</a> → <em>Media</em>, raise <em>Max image dimensions</em> or turn off <em>Automatically compress images</em>.</li><li>Upload it through the <em>Import</em> dialog with <em>Compress images</em> unchecked.</li></ul><p>An image that was already uploaded keeps its size; upload it again after changing the settings.</p><p>The image is drawn as a single picture by the graphics card, which limits how large it can be. Images up to 4096 pixels on their longer side are safe on practically every device, and most computers handle up to 16384 pixels. On a device whose graphics card cannot hold the image, the markers and shapes still appear but the image itself does not. The <em>Geo map properties</em> dialog warns about an image larger than 4096 pixels, and about one that can't be used at all, such as an SVG image.</p><h2>Interaction</h2><p>Adding, moving and removing markers, drawing shapes, the popup view and the contextual menu work as described for the&nbsp;<a class=\"reference-link\" href=\"#root/_help_81SGnPGMk7Xc\">Geo Map</a>. The camera stays over the image and can zoom in up to four times past the image's own resolution.</p><p>The features that only make sense on a real map are not available on an image map:</p><ul><li>Searching the map and searching for places online.</li><li>Going to your location.</li><li>Adding GPS tracks.</li><li>Clicking the places the base map shows.</li><li>The 3D buildings.</li><li>Opening a location in an external map application.</li></ul><p>The look of the marker titles follows the image: if the image is dark, turn on <em>Dark image</em> under <em>Background</em> in the <em>Geo map properties</em> dialog, so that the titles are drawn in a light color. This sets the <code>#map:darkStyle</code> label.</p><p>The <em>Map style</em> setting doesn't apply to an image map, so it's hidden from the settings menu of the collection while the map has an image.</p><h2>Choosing the coordinate system</h2><p>By default, positions are measured in pixels of the image at its original size, from its top-left corner, with <code>x</code> growing to the right and <code>y</code> growing downwards.</p><p>To use coordinates of your own instead, open the <em>Geo map properties</em> dialog, set <em>Coordinates</em> under <em>Background</em> to <em>Custom</em>, and enter the coordinates of the image's <em>Top-left corner</em> and <em>Bottom-right corner</em>. Switching to <em>Custom</em> starts from the image's size in pixels, so the markers stay where they are until the corners are changed; for that reason, <em>Custom</em> can only be chosen once the image has loaded. All positions are then read and written in those coordinates, including the ones shown in the contextual menu and in the popup view. To go back to pixels, set <em>Coordinates</em> to <em>Image pixels</em>. Corners that the geo map inherits from a parent note or a template can only be removed on the note that holds them; entering other corners on this map overrides them.</p><p>The corners are stored in the <code>#map:imageBounds</code> label of the geo map as <code>x,y x,y</code>, with a space between the two corners, which can also be set by hand. For example:</p><ul><li>A screenshot of a game map that covers <code>x</code> from -512 to 512 and <code>y</code> from -512 to 512, with <code>y</code> growing downwards: <code>#map:imageBounds=-512,-512 512,512</code>. Coordinates copied from the game can then be pasted directly into <code>#mapPosition</code>.</li><li>A world whose <code>y</code> grows upwards, with the origin in the middle of the image: <code>#map:imageBounds=-2000,1000 2000,-1000</code>. A top-left <code>y</code> larger than the bottom-right one is what flips the axis.</li><li>A floor plan measured in meters: <code>#map:imageBounds=0,0 24,12</code>.</li></ul><p>The two axes don't have to use the same scale. A circle is always measured in the map's own units, so it appears as an ellipse when the units are stretched differently along the two axes.</p><p>Corners that share an <code>x</code> or a <code>y</code> don't span an area: the dialog doesn't save them, and a label holding them, or a value that cannot be read, is ignored and the pixels of the image are used instead.</p><h2>Coordinate rulers</h2><p>Enabling <em>Show scale</em> in the collection properties draws rulers along the edges of the image instead of a distance scale. Round values of the map's coordinates are marked with ticks along all four edges, labeled along the top and left ones, with faint grid lines across the image. The spacing follows the zoom level, and the values follow <code>#map:imageBounds</code> when it is set.</p><p>The rulers are drawn on the image itself, so they move out of view along with its edges when zooming in. The grid lines remain visible across the image.</p><h2>How the positions are stored</h2><p>Because positions are stored in different labels from the ones of a geo map, the same note can be placed both on a geo map and on an image map.</p><figure class=\"table\"><table><thead><tr><th>Label</th><th>Content</th></tr></thead><tbody><tr><td><code>#mapPosition</code></td><td>The position of a marker, as <code>x,y</code>, for example <code>#mapPosition=320,145</code>.</td></tr><tr><td><code>#mapShape</code></td><td>A shape, in the same format as <code>#geoShape</code> (see&nbsp;<a class=\"reference-link\" href=\"#root/_help_C2H9HK4BzwG7\">Drawing shapes</a>) but with <code>x,y</code> pairs, and a circle's radius in the map's units, for example <code>#mapShape=circle:400,300 50</code>.</td></tr></tbody></table></figure><p>The positions belong to the coordinate system, not to the image. When replacing the image with a different one, for example a higher-resolution copy, keep <code>#map:imageBounds</code> describing the area the new image covers and every marker stays in place. With <em>Image pixels</em>, the positions are pixels, so an image of a different size moves the markers relative to what the image shows; to avoid that, switch <em>Coordinates</em> to <em>Custom</em> before replacing the image, which keeps the size of the old one (<code>0,0 &lt;width&gt;,&lt;height&gt;</code>) as the corners.</p><aside class=\"admonition tip\"><p>To draw freely over an image instead of placing notes on it, consider a&nbsp;<a class=\"reference-link\" href=\"#root/_help_grjYqerjn243\">Canvas</a>.</p></aside>",
"_help_zP3PMqaG71Ct": "<figure class=\"image\"><img style=\"aspect-ratio:1120/763;\" src=\"{{helpAssets}}/User%20Guide/Collections/Presentation_image.png\" width=\"1120\" height=\"763\"></figure><p>The Presentation view allows the creation of slideshows directly from within Trilium.</p><h3>Creating a new presentation</h3><p>Right click on an existing note in the&nbsp;<a class=\"reference-link\" href=\"#root/_help_oPVyFC7WL2Lp\">Note Tree</a>&nbsp;and select <em>Insert child note</em> → <em>Collection</em> → <em>Presentation</em>.</p><h2>How it works</h2><ul><li>Each slide is a child note of the collection.</li><li>The order of the child notes determines the order of the slides.</li><li>Unlike traditional presentation software, slides can be laid out both horizontally and vertically (see below for more information).</li><li>Direct children will be laid out horizontally and the children of those will be laid out vertically. Children deeper than two levels of nesting are ignored.</li></ul><h2>Interaction and navigation</h2><p>In the floating toolbar (top-right):</p><ul><li><span class=\"tn-icon bx bx-edit\"></span> <em>Edit this slide</em> button to go to the corresponding note of the current slide. A <a href=\"#root/_help_CoFPLs3dRlXc\">read-only</a> presentation doesn't show it.</li><li>Press the <span class=\"tn-icon bx bx-grid-horizontal\"></span> Overview button (or the <kbd>O</kbd> key) to show a birds-eye view of the slides. Press the button again to disable it.</li><li>Press the <span class=\"tn-icon bx bx-fullscreen\"></span> “Start presentation” button to show the presentation in full-screen.</li></ul><p>The following keyboard shortcuts are supported:</p><ul><li>Press <kbd>←</kbd> and <kbd>→</kbd> (or <kbd>H</kbd> and <kbd>L</kbd>) to go to the slide on the left or on the right (horizontal).</li><li>Press <kbd>↑</kbd> and <kbd>↓</kbd> &nbsp;(or <kbd>K</kbd> and <kbd>J</kbd>) to go to the upward or downward slide (vertical).</li><li>Press <kbd>Space</kbd> and <kbd>Shift</kbd> + <kbd>Space</kbd> or &nbsp;to go to the next/previous slide in order.</li><li>And a few more, press <kbd>?</kbd> to display a popup with all the supported keyboard combinations.</li></ul><h2>Vertical slides and nesting</h2><p>Unlike traditional presentation software such as Microsoft PowerPoint, the slides in Trilium can be laid out horizontally or vertically in order to create depth or better organize the slides by topic.</p><p>This horizontal/vertical organization affects transitions (especially on the “slide” transition), however it is most noticeable in navigation.</p><ul><li>Pressing <kbd>←</kbd> and <kbd>→</kbd> will navigate through slides horizontally, thus skipping vertical notes under the current slide. This is useful to skip entire chapters/related slides.</li><li>Pressing <kbd>↑</kbd> and <kbd>↓</kbd> will navigate through the vertical slides at the current level.</li><li>Pressing <kbd>Space</kbd> and <kbd>Shift</kbd> + <kbd>Space</kbd> will go to the next/previous slide in order, regardless of the direction. This is generally the key combination to use when presenting.</li><li>The arrows on the bottom-right of the slide will also reflect this navigation scheme.</li></ul><figure class=\"image image-style-align-right image_resized\" style=\"width:55.57%;\"><img style=\"aspect-ratio:890/569;\" src=\"{{helpAssets}}/User%20Guide/Collections/1_Presentation_image.png\" width=\"890\" height=\"569\"></figure><p>All direct children of the collection will be laid out horizontally. If a direct child also has children, those children will be placed as vertical slides.</p><p>In the following example, the note structure is as follows:</p><ul><li>Presentation collection<ul><li>Trilium Notes (demo page)</li><li>“Introduction” slide<ul><li>“The challenge of personal knowledge management”</li><li>“Note-taking structures”</li></ul></li><li>“Demo &amp; Feature highlights” slide<ul><li>“Really fast installation process”</li><li>Video slide</li></ul></li></ul></li></ul><h2>Customization</h2><p>At collection level, it's possible to adjust:</p><ul><li>The theme of the entire presentation to one of the predefined themes by going to the&nbsp;<a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a>&nbsp;and looking for the <em>Theme</em> option.</li><li>It's currently not possible to create custom themes, although it is planned.</li><li>Note that it is note possible to alter the CSS via&nbsp;<a class=\"reference-link\" href=\"#root/_help_AlhDUqhENtH7\">Custom app-wide CSS</a>&nbsp;because the slides are rendered isolated (in a shadow DOM).</li></ul><p>At slide level:</p><ul><li>It's possible to adjust the background color of a slide by using the <a href=\"#root/_help_OFXdgB2nNk1F\">predefined promoted attribute</a> for the color or manually setting <code>#slide:background</code> to a hex color.</li><li>More complex backgrounds can be achieved via gradients. There's no UI for it; it has to be set via <code>#slide:background</code> to a CSS gradient definition such as: <code>linear-gradient(to bottom, #283b95, #17b2c3)</code>.</li></ul><h2>Tips and tricks</h2><ul><li>Text notes generally respect the formatting (bold, italic, foreground and background colors) and font size. Code blocks and tables also work.</li><li>Try using more than just text notes, the presentation uses the same mechanism as <a href=\"#root/_help_R9pX4DGra2Vt\">shared notes</a> and&nbsp;<a class=\"reference-link\" href=\"#root/_help_0ESUbbAxVnoK\">Note List</a>&nbsp;so it should be able to display&nbsp;<a class=\"reference-link\" href=\"#root/_help_s1aBHPd79XYj\">Mermaid Diagrams</a>,&nbsp;<a class=\"reference-link\" href=\"#root/_help_grjYqerjn243\">Canvas</a>&nbsp;and&nbsp;<a class=\"reference-link\" href=\"#root/_help_gBbsAeiuUxI5\">Mind Map</a>&nbsp;in full-screen (without the interactivity).<ul><li><p>Consider using a transparent background for&nbsp;<a class=\"reference-link\" href=\"#root/_help_grjYqerjn243\">Canvas</a>, if the slides have a custom background (go to the hamburger menu in the Canvas, press the button select a custom color and write <code>transparent</code>).</p></li><li><p>For&nbsp;<a class=\"reference-link\" href=\"#root/_help_s1aBHPd79XYj\">Mermaid Diagrams</a>, some of them have a predefined background which can be changed via the frontmatter. For example, for XY-charts:</p><pre><code class=\"language-text-x-trilium-auto\">---\nconfig:\n themeVariables:\n xyChart:\n backgroundColor: transparent\n---</code></pre></li></ul></li></ul><h2>Under the hood</h2><p>The Presentation view uses <a href=\"https://revealjs.com/\">Reveal.js</a> to handle the navigation and layout of the slides.</p>",
"_help_8QqnMzx393bx": "<figure class=\"image\"><img style=\"aspect-ratio:990/590;\" src=\"{{helpAssets}}/User%20Guide/Collections/Grid%20View_image.png\" width=\"990\" height=\"590\"></figure><p>This view presents the child notes in a grid format, allowing for a more visual navigation experience.</p><p>Each tile contains:</p><ul><li>The title of a note.</li><li>A snippet of the content.</li><li>For empty notes, the sub-children are also displayed, allowing for quick navigation.</li></ul><p>Depending on the type of note:</p><ul><li>For&nbsp;<a class=\"reference-link\" href=\"#root/_help_iPIMuisry3hd\">Text</a>&nbsp;notes, the text can be slightly scrollable via the mouse wheel to reveal more context.</li><li>For&nbsp;<a class=\"reference-link\" href=\"#root/_help_6f9hih2hXXZk\">Code</a>&nbsp;notes, syntax highlighting is applied, with line numbers.</li><li>For&nbsp;<a class=\"reference-link\" href=\"#root/_help_W8vYD3Q1zjCR\">File</a>&nbsp;notes, a preview is made available for audio, video and PDF notes.</li><li>If the note does not have a content, a list of its child notes will be displayed instead.</li></ul><p>The grid view is also used by default in the&nbsp;<a class=\"reference-link\" href=\"#root/_help_0ESUbbAxVnoK\">Note List</a>&nbsp;of every note, making it easy to navigate to children notes.</p><h3>Creating a new table</h3><p>Right click on an existing note in the&nbsp;<a class=\"reference-link\" href=\"#root/_help_oPVyFC7WL2Lp\">Note Tree</a>&nbsp;and select <em>Insert child note</em> → <em>Collection</em> → <em>Grid View</em>.</p><h2>Configuration</h2><p>Unlike most other view types, the grid view is not actually configurable.</p>",
- "_help_mULW0Q3VojwY": "<figure class=\"image\"><img style=\"aspect-ratio:1387/758;\" src=\"{{helpAssets}}/User%20Guide/Collections/List%20View_image.png\" width=\"1387\" height=\"758\"></figure><p>List view is similar to&nbsp;<a class=\"reference-link\" href=\"#root/_help_8QqnMzx393bx\">Grid View</a>, but in the list view mode, each note is displayed in a single row with only the title and the icon of the note being visible by the default. By pressing the <span class=\"tn-icon bx bx-chevron-right\"></span> expand button it's possible to view the content of the note, as well as the children of the note (recursively).</p><p>In the example above, the \"Node.js\" note on the left panel contains several child notes. The right panel displays the content of these child notes as a single continuous document.</p><h3>Creating a new table</h3><p>Right click on an existing note in the&nbsp;<a class=\"reference-link\" href=\"#root/_help_oPVyFC7WL2Lp\">Note Tree</a>&nbsp;and select <em>Insert child note</em> → <em>Collection</em> → <em>List View</em>.</p><h2>Interaction</h2><ul><li>Each note can be expanded or collapsed by clicking on the <span class=\"tn-icon bx bx-chevron-right\"></span> arrow to the left of the title.</li><li>In the&nbsp;<a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a>, there are buttons to expand (<span class=\"tn-icon bx bx-move-vertical\"></span>) and to collapse (<span class=\"tn-icon bx bx-layer-minus\"></span>) all notes easily.</li></ul><h2>Printing and exporting to PDF</h2><p>Since v0.100.0, list collections can be <a href=\"#root/_help_NRnIZmSMc5sj\">printed or exported to PDF</a>.</p><p>A printed list collection will print all the notes in the collection, in the right order and preserving the full hierarchy.</p><p>If exported to PDF within the desktop application, there is additional functionality:</p><ul><li>The table of contents of the PDF will reflect the structure of the notes.</li><li>Reference and inline links to other notes within the same hierarchy will be functional (will jump to the corresponding page). If a link refers to a note that is not in the printed hierarchy, it will be unlinked.</li></ul><h2>Expanding and collapsing multiple notes at once</h2><p>Apart from individually expanding or collapsing notes, it's also possible to expand or collapse them all at once. To do so, go to the&nbsp;<a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a>&nbsp;and look for the corresponding button.</p><p>By default, the <em>Expand</em> (<span class=\"tn-icon bx bx-move-vertical\"></span>) button will only expand the direct children (first level) of the collection. Starting with v0.100.0, it's possible to expand multiple levels of notes using the arrow button next to the button.</p><p>Manually expanded notes will reset if the application/tab is closed and then the collection is visited again. However notes automatically expanded/collapsed via the buttons in&nbsp;<a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a>&nbsp;will persist.</p><aside class=\"admonition tip\"><p>By design, the UI provides only a handful of levels of depth for expanding notes (direct children, 2-5, all levels). It's also possible to specify any desired depth by manually setting the <a href=\"#root/_help_HI6GBBIduIgv\">corresponding label</a>. For example: <code>#expanded=100</code> to expand up to 100 levels of depth.</p></aside><aside class=\"admonition note\"><p>From a performance standpoint, the List collection is efficient since it does not load child notes unless the notes are actually expanded. Expanding the list for a significantly large hierarchy can cause slow-downs.</p></aside>",
- "_help_CssoWBu8I7jF": "<figure class=\"image\"><img style=\"aspect-ratio:1177/98;\" src=\"{{helpAssets}}/User%20Guide/Collections/Collection%20Properties_image.png\" width=\"1177\" height=\"98\"></figure><p>The <em>Collection Properties</em> is a toolbar that is displayed at the top of every <a href=\"#root/_help_GTwFsgaA0lCt\">collection note</a>.</p><p>The collection properties has:</p><ul><li>A quick selector for the view type (e.g. grid, calendar, board).</li><li>A settings button with:<ul><li>Settings for the current view, for example hiding the weekends in a calendar.</li><li>Generic settings for the collection, such as <a href=\"#root/_help_wyaGBBQrl4i3\">hiding the child notes</a> or showing <a href=\"#root/_help_MKmLg5x6xkor\">archived notes</a>.</li></ul></li><li>Specific interactions for the current view, for example month selector and view switcher for the calendar.</li></ul>",
+ "_help_mULW0Q3VojwY": "<figure class=\"image\"><img style=\"aspect-ratio:1387/758;\" src=\"{{helpAssets}}/User%20Guide/Collections/List%20View_image.png\" width=\"1387\" height=\"758\"></figure><p>List view is similar to&nbsp;<a class=\"reference-link\" href=\"#root/_help_8QqnMzx393bx\">Grid View</a>, but in the list view mode, each note is displayed in a single row with only the title and the icon of the note being visible by the default. By pressing the <span class=\"tn-icon bx bx-chevron-right\"></span> expand button it's possible to view the content of the note, as well as the children of the note (recursively).</p><p>In the example above, the \"Node.js\" note on the left panel contains several child notes. The right panel displays the content of these child notes as a single continuous document.</p><h3>Creating a new table</h3><p>Right click on an existing note in the&nbsp;<a class=\"reference-link\" href=\"#root/_help_oPVyFC7WL2Lp\">Note Tree</a>&nbsp;and select <em>Insert child note</em> → <em>Collection</em> → <em>List View</em>.</p><h2>Interaction</h2><ul><li>Each note can be expanded or collapsed by clicking on the <span class=\"tn-icon bx bx-chevron-right\"></span> arrow to the left of the title.</li><li>In the <a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a> toolbar, the buttons at the right end expand (<span class=\"tn-icon bx bx-move-vertical\"></span>) and collapse (<span class=\"tn-icon bx bx-layer-minus\"></span>) all notes easily.</li></ul><h2>Printing and exporting to PDF</h2><p>Since v0.100.0, list collections can be <a href=\"#root/_help_NRnIZmSMc5sj\">printed or exported to PDF</a>.</p><p>A printed list collection will print all the notes in the collection, in the right order and preserving the full hierarchy.</p><p>If exported to PDF within the desktop application, there is additional functionality:</p><ul><li>The table of contents of the PDF will reflect the structure of the notes.</li><li>Reference and inline links to other notes within the same hierarchy will be functional (will jump to the corresponding page). If a link refers to a note that is not in the printed hierarchy, it will be unlinked.</li></ul><h2>Expanding and collapsing multiple notes at once</h2><p>Apart from individually expanding or collapsing notes, it's also possible to expand or collapse them all at once. To do so, go to the <a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a> toolbar and look for the buttons at its right end.</p><p>By default, the <span class=\"tn-icon bx bx-move-vertical\"></span> button expands only the direct children (first level) of the collection. Starting with v0.100.0, it's possible to expand multiple levels of notes using the <span class=\"tn-icon bx bx-chevron-down\"></span> button next to it.</p><p>Manually expanded notes will reset if the application/tab is closed and then the collection is visited again. However notes automatically expanded/collapsed via the buttons in&nbsp;<a class=\"reference-link\" href=\"#root/_help_CssoWBu8I7jF\">Collection Properties</a>&nbsp;will persist.</p><aside class=\"admonition tip\"><p>By design, the UI provides only a handful of levels of depth for expanding notes (direct children, 2-5, all levels). It's also possible to specify any desired depth by manually setting the <a href=\"#root/_help_HI6GBBIduIgv\">corresponding label</a>. For example: <code>#expanded=100</code> to expand up to 100 levels of depth.</p></aside><aside class=\"admonition note\"><p>From a performance standpoint, the List collection is efficient since it does not load child notes unless the notes are actually expanded. Expanding the list for a significantly large hierarchy can cause slow-downs.</p></aside>",
+ "_help_CssoWBu8I7jF": "<figure class=\"image\"><img style=\"aspect-ratio:1177/98;\" src=\"{{helpAssets}}/User%20Guide/Collections/Collection%20Properties_image.png\" width=\"1177\" height=\"98\"></figure><p>The <em>Collection Properties</em> is a toolbar that is displayed at the top of every <a href=\"#root/_help_GTwFsgaA0lCt\">collection note</a>.</p><p>The collection properties has:</p><ul><li>A quick selector for the view type (e.g. grid, calendar, board).</li><li>A settings button with:<ul><li>Settings for the current view, for example hiding the weekends in a calendar.</li><li>Generic settings for the collection, such as <a href=\"#root/_help_wyaGBBQrl4i3\">hiding the child notes</a> or showing <a href=\"#root/_help_MKmLg5x6xkor\">archived notes</a>.</li></ul></li><li>Specific interactions for the current view, for example the expand and collapse buttons in the list view, or the month selector and view switcher for the calendar.</li></ul>",
"_help_IF7Q6I9x7zuw": "<figure class=\"image\"><img style=\"aspect-ratio:1406/1030;\" src=\"{{helpAssets}}/User%20Guide/Collections/Dashboard_image.png\" width=\"1406\" height=\"1030\"></figure><aside class=\"admonition note\"><p>The dashboard is currently considered beta. This means that it might face some changes in behavior until it is stabilized.</p></aside><p>The dashboard is a collection introduced in Trilium v0.104.0. It is similar to the&nbsp;<a class=\"reference-link\" href=\"#root/_help_8QqnMzx393bx\">Grid View</a>&nbsp;collection, but with some key differences:</p><ul><li>The grid layout is not fixed, allowing for tiles of varying widths and heights. The grid has 12 columns and an unlimited number of rows.</li><li>Each widget represents a child note of the collection and can be reordered or resized.</li><li>The grid will distribute the columns evenly to fill the entire screen.<ul><li>If the available space is too low (e.g. in a split or in mobile), the columns are collapsed so that all widgets are displayed one under the other.</li><li>While the columns are collapsed, the widgets cannot be reordered or resized.</li></ul></li><li>Unlike the&nbsp;<a class=\"reference-link\" href=\"#root/_help_8QqnMzx393bx\">Grid View</a>, the widgets are not clickable which allows them to be interactive.</li></ul><h2>Types of widgets</h2><p>The dashboard uses the same rendering mechanism as the&nbsp;<a class=\"reference-link\" href=\"#root/_help_8QqnMzx393bx\">Grid View</a>&nbsp;or the&nbsp;<a class=\"reference-link\" href=\"#root/_help_0ESUbbAxVnoK\">Note List</a>, which means every note can be rendered, such as:</p><ul><li>Static content, via&nbsp;<a class=\"reference-link\" href=\"#root/_help_iPIMuisry3hd\">Text</a>&nbsp;or&nbsp;<a class=\"reference-link\" href=\"#root/_help_6f9hih2hXXZk\">Code</a>.</li><li>Images via&nbsp;<a class=\"reference-link\" href=\"#root/_help_W8vYD3Q1zjCR\">File</a>,&nbsp;<a class=\"reference-link\" href=\"#root/_help_s1aBHPd79XYj\">Mermaid Diagrams</a>,&nbsp;<a class=\"reference-link\" href=\"#root/_help_gBbsAeiuUxI5\">Mind Map</a>.</li><li>Interactive widgets via&nbsp;<a class=\"reference-link\" href=\"#root/_help_HcABDtFCkbFN\">Render Note</a>.</li><li>Web pages can be displayed via&nbsp;<a class=\"reference-link\" href=\"#root/_help_1vHRoWCEjj0L\">Web View</a>&nbsp;and refreshed via the context menu.</li><li><a class=\"reference-link\" href=\"#root/_help_GTwFsgaA0lCt\">Collections</a>&nbsp;render interactively inside the dashboard</li></ul><aside class=\"admonition tip\"><p>Interactive widgets through the use of&nbsp;<a class=\"reference-link\" href=\"#root/_help_HcABDtFCkbFN\">Render Note</a>&nbsp;is the highlighted use case of the dashboard. Using the&nbsp;<a class=\"reference-link\" href=\"#root/_help_GBBMSlVSOIGP\">AI</a>&nbsp;chat, these widgets can be easily created as the AI is instructed in how to write them.</p></aside><h2>Adding new widgets</h2><p>There are two ways to add widgets to a dashboard:</p><ul><li>Create a child note of any type, the dashboard will automatically pick it up and add it onto the grid.</li><li>From the&nbsp;<a class=\"reference-link\" href=\"#root/_help_oPVyFC7WL2Lp\">Note Tree</a>, drag an existing note onto the dashboard and it will be placed there. This will <a href=\"#root/_help_IakOLONlIfGI\">clone</a> the note into the collection.</li></ul><h2>Read-only dashboards</h2><p>On a <a href=\"#root/_help_CoFPLs3dRlXc\">read-only</a> dashboard, the widgets can't be moved or resized, notes dragged from the <a class=\"reference-link\" href=\"#root/_help_oPVyFC7WL2Lp\">Note Tree</a> aren't added, and the menu of a widget no longer offers to remove it.</p>",
"_help_BgmBlOIl72jZ": "<p>While Trilium is actively maintained and stable, encountering bugs is possible.</p><h2>General Quick Fix</h2><p>The first step in troubleshooting is often a restart.</p><p>If you experience an UI issue, the frontend may have entered an inconsistent state. Reload the application by pressing <kbd>Ctrl</kbd> + <kbd>R</kbd>. This will reload the frontend.</p><p>If the issue persists or appears to be a backend problem, restart the entire application. For the desktop (Electron) build, simply close and reopen the window. If you're using a Docker build, restart the container.</p><h2>Reporting Bugs</h2><p>Reporting bugs is highly valuable. Here are some tips:</p><ul><li>Use GitHub issues for reporting: <a href=\"https://github.com/TriliumNext/Trilium/issues\">https://github.com/TriliumNext/Trilium/issues</a></li><li>Refer to the <a href=\"#root/_help_qzNzp9LYQyPT\">error logs</a> page for information on providing necessary details.</li></ul><details class=\"trilium-collapsible\" open=\"\"><summary>Broken Note Crashes Trilium</summary><p>Certain problems, such as rendering a note with a faulty script, can cause Trilium to crash. If Trilium attempts to reload the problematic note upon restart, it will continue to crash.</p><p>To resolve this, use the <code>TRILIUM_START_NOTE_ID</code> environment variable to reset the open tabs to a single specified note ID (e.g., <code>root</code>). In Linux, you can set it as follows:</p><pre><code class=\"language-text-x-trilium-auto\">TRILIUM_START_NOTE_ID=root ./trilium</code></pre></details><details class=\"trilium-collapsible\" open=\"\"><summary>Broken Script Prevents Application Startup</summary><p>If a custom script causes Trilium to crash, and it is set as a startup script or in an active <a href=\"#root/_help_MgibgPcfeuGz\">custom widget</a>, start Triliumin \"safe mode\" to prevent any custom scripts from executing:</p><pre><code class=\"language-text-x-trilium-auto\">TRILIUM_SAFE_MODE=true ./trilium</code></pre><p>Depending on your Trilium distribution, you may have pre-made scripts available: <code>trilium-safe-mode.bat</code> and <code>trilium-safe-mode.sh</code>.</p><p>Once Trilium starts, locate and fix or delete the problematic note.</p></details><details class=\"trilium-collapsible\" open=\"\"><summary>Sync and Consistency Checks</summary><p>Trilium periodically verifies the logical consistency of the database (e.g., ensuring every note has a parent). If inconsistencies are detected, you will be notified via the UI.</p><p>In such cases, file a bug report and attach an <a href=\"#root/_help_x59R8J8KV5Bp\">anonymized database</a> if necessary.</p></details><details class=\"trilium-collapsible\" open=\"\"><summary>Restoring Backup</summary><p>Trilium makes regular automatic backups. If issues become severe, you can <a href=\"#root/_help_ODY7qQn5m2FT\">restore from a backup</a>.</p></details><details class=\"trilium-collapsible\" open=\"\"><summary>Forgotten Password</summary><p>See&nbsp;<a class=\"reference-link\" href=\"#root/_help_lwAX5SvbrK2g\">Resetting your password</a>.</p></details>",
"_help_wy8So3yZZlH9": "<p>Go to <a href=\"https://github.com/TriliumNext/Trilium/issues\">Issues · TriliumNext/Trilium</a> and press “New issue”.</p><p>If you are reporting a bug, select “Bug Report” and fill in the details.</p>",
diff --git a/docs/User Guide/User Guide/Collections/Collection Properties.md b/docs/User Guide/User Guide/Collections/Collection Properties.md
index 4a1d687d67..7a204d1b15 100644
--- a/docs/User Guide/User Guide/Collections/Collection Properties.md
+++ b/docs/User Guide/User Guide/Collections/Collection Properties.md
@@ -9,4 +9,4 @@ The collection properties has:
* A settings button with:
* Settings for the current view, for example hiding the weekends in a calendar.
* Generic settings for the collection, such as [hiding the child notes](../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tree/Hiding%20the%20subtree.md) or showing [archived notes](../Basic%20Concepts%20and%20Features/Notes/Archived%20Notes.md).
-* Specific interactions for the current view, for example month selector and view switcher for the calendar.
\ No newline at end of file
+* Specific interactions for the current view, for example the expand and collapse buttons in the list view, or the month selector and view switcher for the calendar.
\ No newline at end of file
diff --git a/docs/User Guide/User Guide/Collections/List View.md b/docs/User Guide/User Guide/Collections/List View.md
index 6a68c44d8b..bf09c16fda 100644
--- a/docs/User Guide/User Guide/Collections/List View.md
+++ b/docs/User Guide/User Guide/Collections/List View.md
@@ -12,7 +12,7 @@ Right click on an existing note in the <a class="reference-link" href="../Basic
## Interaction
* Each note can be expanded or collapsed by clicking on the <span class="tn-icon bx bx-chevron-right"></span> arrow to the left of the title.
-* In the <a class="reference-link" href="Collection%20Properties.md">Collection Properties</a>, there are buttons to expand (<span class="tn-icon bx bx-move-vertical"></span>) and to collapse (<span class="tn-icon bx bx-layer-minus"></span>) all notes easily.
+* In the <a class="reference-link" href="Collection%20Properties.md">Collection Properties</a> toolbar, the buttons at the right end expand (<span class="tn-icon bx bx-move-vertical"></span>) and collapse (<span class="tn-icon bx bx-layer-minus"></span>) all notes easily.
## Printing and exporting to PDF
@@ -27,9 +27,9 @@ If exported to PDF within the desktop application, there is additional functiona
## Expanding and collapsing multiple notes at once
-Apart from individually expanding or collapsing notes, it's also possible to expand or collapse them all at once. To do so, go to the <a class="reference-link" href="Collection%20Properties.md">Collection Properties</a> and look for the corresponding button.
+Apart from individually expanding or collapsing notes, it's also possible to expand or collapse them all at once. To do so, go to the <a class="reference-link" href="Collection%20Properties.md">Collection Properties</a> toolbar and look for the buttons at its right end.
-By default, the _Expand_ (<span class="tn-icon bx bx-move-vertical"></span>) button will only expand the direct children (first level) of the collection. Starting with v0.100.0, it's possible to expand multiple levels of notes using the arrow button next to the button.
+By default, the <span class="tn-icon bx bx-move-vertical"></span> button expands only the direct children (first level) of the collection. Starting with v0.100.0, it's possible to expand multiple levels of notes using the <span class="tn-icon bx bx-chevron-down"></span> button next to it.
Manually expanded notes will reset if the application/tab is closed and then the collection is visited again. However notes automatically expanded/collapsed via the buttons in <a class="reference-link" href="Collection%20Properties.md">Collection Properties</a> will persist.