Nota — a free DAW for macOS, Windows and Linux. No subscription, no account — just open it and make music.
C# audioaudio-unitavaloniacpp20cross-platformdawdigital-audio-workstationdspjucelinux-audiomcp-servermidimusicmusic-productionpiano-rollplugin-hostsequencersynthesizervstvst3
(feat) Docs
Egor Khindikaynencfb3b5de3d6f
diff --git a/.claude/launch.json b/.claude/launch.jsonnew file mode 100644index 00000000..4905b6cd--- /dev/null+++ b/.claude/launch.json@@ -0,0 +1,11 @@+{+ "version": "0.0.1",+ "configurations": [+ {+ "name": "nota-docs",+ "runtimeExecutable": "/opt/homebrew/Cellar/node/26.10.0_1/bin/node",+ "runtimeArgs": ["../nota-docs/node_modules/astro/bin/astro.mjs", "dev", "--root", "../nota-docs", "--port", "4321"],+ "port": 4321+ }+ ]+}diff --git a/.claude/skills/nota-docs/SKILL.md b/.claude/skills/nota-docs/SKILL.mdnew file mode 100644index 00000000..b648ce49--- /dev/null+++ b/.claude/skills/nota-docs/SKILL.md@@ -0,0 +1,134 @@+---+name: nota-docs+description: Keep the user documentation (sibling repo ../nota-docs, Astro Starlight, EN + RU) in sync with the app. Run this WHENEVER you add, change or remove a user-visible feature — a new device or parameter, a new view/panel/window, a changed workflow, a moved menu item, a new or re-mapped shortcut, a new Preferences option — i.e. whenever you write a CHANGELOG [Unreleased] entry. Also run it from /release to catch anything that slipped. Handles: finding the affected pages, editing the EN page and its RU twin, re-shooting screenshots (nota-design mockups or the headless app), regenerating the shortcuts page, and building/checking the site.+user-invocable: true+---++# Keeping Nota Docs honest++The user manual lives in **`../nota-docs`** (relative to this repo; GitHub `nota-daw/nota-docs`),+built with Astro Starlight in **English (root) and Russian (`/ru/`)**. It is written by hand,+so every user-visible change in this repo must be mirrored there or the manual lies. The+overall structure and conventions are in `../nota-docs/PLAN.md` — read it once if you have+not.++**Trigger:** you wrote (or are about to write) a `CHANGELOG.md` entry under `[Unreleased]`.+`Added` / `Changed` / `Removed` almost always need a docs edit; `Fixed` only when the fix+changes what the docs describe. Pure refactors, perf and internal changes need nothing.++**Argument** (`/nota-docs <arg>`, optional): a feature name, a changelog line, or `audit`+(reconcile *all* `[Unreleased]` entries — used by `/release`). No argument → the change you+just made in this session.++If the page that should cover the change is still a stub (`status: todo`) and you are not+writing it now, append `{page, change, version}` to the `pending:` list at the bottom+of `../nota-docs/coverage.yml` so the stage that writes that page picks it up, tell the user,+and stop.++## 1. Work out what changed for the user++From the diff and the CHANGELOG entry, list concretely: new/renamed UI labels, new+parameters with ranges and defaults, new menu items and where they sit, new shortcuts,+changed behaviour, removed things. Take names and numbers **from the code** (the device's+DSP class and card under `src/managed/Nota.App/DeviceCards/…`, menus in `MainWindow.axaml`,+`PreferencesWindow.cs`), never from memory or the mockup — the changelog itself can be+contradicted by a later entry.++## 2. Find the pages++1. `../nota-docs/coverage.yml` maps features and source paths → page slugs. Look up every+ file you touched and every feature you named.+2. Grep page frontmatter `sources:` in `../nota-docs/src/content/docs/**/*.mdx` for the+ touched paths, and grep page bodies for the old UI label / old shortcut.+3. Nothing found → it is a new feature. Decide its place in the sidebar (see `PLAN.md`),+ copy `templates/page.mdx` (or `templates/device.mdx`) into both+ `src/content/docs/<slug>.mdx` and `src/content/docs/ru/<slug>.mdx`, and add it to+ `coverage.yml`. The sidebar autogenerates per directory (order via `sidebar.order`); only a+ brand-new top-level section needs an entry in `astro.config.mjs`.++Typical fan-out — check all that apply:+- the feature's own page (device, view, panel, preference pane);+- the overview that lists it (Devices index, Views index, "Main window tour");+- `reference/shortcuts` — regenerated, see step 4;+- the glossary, if you introduced a term;+- tutorials that walk through the changed flow (the old steps may no longer work);+- a new built-in device or a renamed device page → the slug maps in+ `src/managed/Nota.App/NotaDocs.cs` (`Instruments` / `AudioEffects` / `MidiEffects`, indexed by+ engine kind) so the device header's Documentation item opens the right page.++## 3. Edit EN, then RU++- English page under `src/content/docs/<slug>.mdx`, Russian twin at+ `src/content/docs/ru/<slug>.mdx` — **same path, same structure, same screenshots**. Never+ leave one language behind; `scripts/check.mjs` fails on a missing or stale twin.+- A stub page (`status: todo`) you fill in becomes `status: draft` (or `done` once its+ screenshots are in); drop the "Being written" aside.+- Bump `updated:` in both frontmatters to the version in `VERSION` (plus `since:` on new+ pages); add any new source paths to `sources:`.+- Style: short, second person, like the CHANGELOG. UI names exactly as on screen in+ **bold**, keys via `<Kbd>`. In Russian, UI names stay in English (the app is English); the+ explanation is native Russian, not a word-for-word translation.+- Removed feature → delete the text and its screenshots; removed page → delete both+ languages, the sidebar entry and the `coverage.yml` entry, and fix links into it.++## 4. Screenshots and generated pages++`../nota-docs/shots/manifest.yml` lists every image (its header documents the scenes and+args). `npm run shots -- <id-prefix> …` retakes them into `src/assets/shots/{dark,light}/`.++- **app** shots render the real UI headlessly (`shots/app`, both themes, 2×, user/device names+ scrubbed). They build against this repo's `src/managed/Nota.App`, so build the app first if+ you changed it. **design** shots come from `../nota-design` (dark only).+- UI that changed visibly → retake its ids (e.g. `npm run shots -- devices/audio-effects/shutter`).+- New device → add `devices/<group>/<slug>/card` (`scene: device` with its kind id) plus one+ shot per tab you document (`args: {tab: "<tab text>"}`, a chain like `"L>Env"` when a size+ switch comes first, `preset` for an interesting state). Write the page from+ `templates/device.mdx`; facts come from the engine header's top comment and `paramName`,+ the card file's header comment and labels, and `FactoryPresetCatalog` — give a range only+ when the code states it.+- New window / view / Settings page → a new scene in `shots/app/Scenes.cs` if none fits; keep+ it deterministic (demo song, no real user data).+- Mockup no longer matches the code → switch that id to `source: app`; never document the mockup.+- A scene breaks after an app refactor (renamed private method, control name) → fix the+ harness; it reflects into `MainWindow` / `PreferencesWindow` privates on purpose.+- Shortcut changed → `npm run shortcuts` regenerates `reference/shortcuts` (EN + RU) from+ `PreferencesWindow.ShortcutGroups`; run the `nota-shortcuts` skill first so that list is+ right.++## 5. Verify and commit++```bash+cd ../nota-docs+npm run build+npm run check+```++Node may not be on PATH (Homebrew's node isn't linked on this Mac) — use+`/opt/homebrew/Cellar/node/*/bin`. The dev server is the `nota-docs` entry in this repo's+`.claude/launch.json` (preview_start).++Both must pass (broken links, missing RU twin, image id not in manifest, `updated:` older+than a touched source). Look at the changed pages in `npm run preview` via the built-in+browser when screenshots or layout changed.++Commit in **`../nota-docs`**, separately from the app repo: `(docs) <what changed>`, no+Claude attribution trailer. Don't push unless the user asked.++## 6. Report++List the pages changed (EN + RU), screenshots re-shot, anything you could not document+(e.g. a scene the harness can't render) and the gaps you left in `coverage.yml`.++## /release audit mode++Go through every `Added` / `Changed` / `Removed` entry of `[Unreleased]`, check each against+the docs as above, fix what's missing, then `npm run build && npm run check`. Report+the coverage to the user before the tag is created; missing docs do not block a release, but+say so plainly.++## Don't+- Don't document plans, mockup-only features or anything not in the code.+- Don't update only one language.+- Don't hand-edit the generated shortcuts page.+- Don't copy CHANGELOG prose verbatim — the changelog says what changed, the docs say how+ to use it now.diff --git a/.claude/skills/nota-features/SKILL.md b/.claude/skills/nota-features/SKILL.mdnew file mode 100644index 00000000..7fe279a8--- /dev/null+++ b/.claude/skills/nota-features/SKILL.md@@ -0,0 +1,104 @@+---+name: nota-features+description: Keep FEATURES.md (the consolidated "what Nota can do" list in the repo root) in sync with the app. Run this WHENEVER you add, change or remove a user-visible capability — a new device or parameter, a new view/panel/window, a new workflow or editing command, a new MCP tool, a new export option, a new platform/build/CI capability — i.e. whenever you write a CHANGELOG [Unreleased] Added/Changed/Removed entry. Also run it from /release in `audit` mode to catch anything that slipped and bump the "as of version" line.+user-invocable: true+---++# Keeping FEATURES.md honest++`FEATURES.md` is the single page that answers "what can Nota do *right now*". It is written+by hand and is not generated from the changelog, so it drifts unless every feature change is+folded into it. It describes **what is implemented in the code**, not plans, and it is a+**current-state** document: no history, no "now", no "previously", no version numbers per+item — that is the CHANGELOG's job.++**Trigger:** you wrote (or are about to write) a `CHANGELOG.md` entry under `[Unreleased]`.+- `Added` → almost always a new bullet or an extension of an existing one.+- `Changed` → rewrite the bullet that describes the old behaviour so it describes the new.+- `Removed` → delete the mention (search the whole file — features get cross-referenced).+- `Fixed` → only if the fix changes what the list claims (a limit lifted, a platform now+ supported). Pure bug fixes, refactors, perf and internals need nothing.++**Argument** (`/nota-features <arg>`, optional): a feature name, a changelog line, or+`audit` (reconcile everything since the version in the file's header — used by `/release`).+No argument → the change you just made in this session.++## 1. Find where it belongs++Read the Contents list at the top of `FEATURES.md` and pick the section by what the user+sees, not by which code you touched:++| Change | Section |+|---|---|+| OS support, installers, auto-update, audio/MIDI backends | Platforms and distribution |+| Projects, saving, version history, transport, tempo, loop, metronome | Project and transport |+| Arrangement / Session / Modular / clip editors / piano roll behaviour | Views |+| Track types, routing, sends, groups, mixer window | Tracks and mixer |+| Note editing, MIDI input, MIDI Learn, controllers | MIDI and virtual instruments |+| Recording, audio clips, warp, stretch, stems | Audio: recording, clips, warp |+| Automation lanes, envelopes, modulation | Automation |+| A built-in instrument / audio effect / MIDI effect / rack | Built-in devices → the matching `###` subsection |+| VST3/AU hosting, plugin scanning, plugin windows | Plugin hosting |+| Browser tabs, sample library, presets, smart samples | Browser and assets |+| Render / bounce / stems export | Export |+| Windows, themes, menus, dialogs, Nota Remote UI | Windows and interface |+| A new Preferences option | Preferences |+| A new or changed MCP tool | MCP / AI control (also mention it on the feature's own bullet if it has one, as existing device bullets do: "MCP `read_sampler` / `set_sampler`") |+| Build scripts, CI, tests, licensing | Other |++Before writing, `grep -n` the file for the feature's name and its key words — the feature+may already be partly described (often it is an extension of an existing bullet, e.g. a new+parameter on a device). **Extend the existing bullet rather than adding a duplicate.** If a+genuinely new top-level area appears, add a `##` section *and* its Contents link (anchor =+GitHub slug of the heading).++## 2. Write it in the file's voice++Match the surrounding bullets — read the neighbours first.+- One bullet per feature; **bold** the feature's name at the start, then a dash or colon and+ what it does. Nested bullets only for sub-features of one thing (see Transport).+- English, present tense, plain language a musician understands. State capabilities and+ user-facing names (menu items, tab names, button labels exactly as in the UI), shortcuts+ in the app's glyphs (⌘ ⇧ ⌥, "Cmd/Ctrl" where the file already does).+- Concrete over vague: parameter names, modes, counts ("25 factory presets", "Poly 16 /+ Mono / Legato") — but verify each number in the code/presets, don't copy it blindly from+ the changelog.+- Condense. The changelog entry explains the change; FEATURES states the result in roughly+ half the words. No rationale, no "fixes", no internal class names (file paths only in+ Other / Platforms, as already done there).+- Built-in devices: follow the existing device bullet shape — what it is · its main controls+ and modes · tabs/sizes of the card · preset count · MCP tools if any.+- Hard-wrap at ~90 columns like the rest of the file.++## 3. Verify against the code++The changelog can be ahead of, or behind, reality. For each claim you add, confirm it in the+source (device kind registration, the view/menu code, the MCP tool list in the MCP server,+the preset folder). If something in the changelog was later reverted or is behind a flag+that is off by default, leave it out (or say "experimental, off by default" if the user can+turn it on).++## 4. `audit` mode (from /release)++1. Read the version in the header line ("as of version **X.Y.Z**").+2. Collect every `CHANGELOG.md` entry newer than that version: all `## [A.B.C]` sections+ above `## [X.Y.Z]`, plus `[Unreleased]` / the section being released right now.+3. For each `Added` / `Changed` / `Removed` entry (and relevant `Fixed`), check whether+ `FEATURES.md` reflects it; fix what is missing or stale per sections 1–3.+4. Update the header: set the version to the one being released (or the latest released+ version when run outside a release), keep "(plus changes in development on `main`)".+5. Report the list of entries you added/changed in FEATURES.md and anything you+ deliberately skipped (and why).++## 5. Finish++- Re-read the edited section as a whole: no duplicates, no contradictions with other+ sections, Contents still matches the `##` headings.+- The SPDX header on line 1 stays.+- Commit FEATURES.md together with the feature (or the release commit in audit mode);+ don't make a separate commit unless the user asks.++## Don't+- Don't paste changelog entries verbatim, and don't add dates or version tags to items.+- Don't describe planned, unmerged or disabled-by-default work as available.+- Don't reorganize or restyle sections you weren't asked to touch.diff --git a/.claude/skills/release/SKILL.md b/.claude/skills/release/SKILL.mdindex fc9a0a30..c0d9bb13 100644--- a/.claude/skills/release/SKILL.md+++ b/.claude/skills/release/SKILL.md@@ -124,10 +124,22 @@ not a word-for-word translation.Commit the posts together with the release. Show both to the user in the report.+## 3d. Docs check++Run the `nota-docs` skill in `audit` mode over the `[Unreleased]` entries you just promoted.+Docs changes are committed in `../nota-docs`, not in the release commit. Missing docs don't+block the release — list them in the report.++## 3e. Feature list++Run the `nota-features` skill in `audit` mode: fold every changelog entry since the version in+`FEATURES.md`'s header into the list and set the header to `X.Y.Z`. `FEATURES.md` goes into+the release commit.+## 4. Commit, tag, push```bash-git add VERSION CHANGELOG.md src/native/nota.engine/VERSION docs/news/+git add VERSION CHANGELOG.md FEATURES.md src/native/nota.engine/VERSION docs/news/git commit -m "(chore) Release vX.Y.Z"git tag -a "vX.Y.Z" -m "Nota vX.Y.Z"git push origin maindiff --git a/CHANGELOG.md b/CHANGELOG.mdindex e3d0cb20..435468e8 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -18,6 +18,12 @@ Entry categories: `Added`, `Changed`, `Fixed`, `Removed`.## [Unreleased]+### Added+- **A user manual, in English and Russian** — at https://nota-daw.github.io/nota-docs/, from the+ first track to every knob of every built-in device. **Help ▸ Documentation** opens it (in Russian+ when your system is), the start window links to the first-track tutorial, and every device's+ header menu has a **Documentation** item that opens that device's page.+### Fixed- **The Mixer shows your track names:** a track renamed to "Drums" used to read "Inst 2" inits mixer strip. Strips now carry the same name as the Arrangement — or the instrument'sdiff --git a/README.md b/README.mdindex d51f4b35..90e03d53 100644--- a/README.md+++ b/README.md@@ -21,6 +21,7 @@<a href="https://github.com/nota-daw/nota/releases"><img src="https://img.shields.io/github/downloads/nota-daw/nota/total?color=D9A13F" alt="Downloads"></a><a href="LICENSES/"><img src="https://img.shields.io/badge/license-AGPL--3.0-D9A13F" alt="License: AGPL-3.0"></a><img src="https://img.shields.io/badge/platform-macOS%20%7C%20Windows%20%7C%20Linux-D9A13F" alt="Platforms: macOS, Windows, Linux">+ <a href="https://nota-daw.github.io/nota-docs/"><img src="https://img.shields.io/badge/docs-user%20manual-D9A13F" alt="Documentation"></a><a href="https://t.me/notadaw"><img src="https://img.shields.io/badge/Telegram-2CA5E0?logo=telegram&logoColor=white" alt="Telegram"></a><a href="https://discord.gg/apf4Q2JKWk"><img src="https://img.shields.io/badge/Discord-5865F2?logo=discord&logoColor=white" alt="Discord"></a></p>@@ -155,6 +156,9 @@ Nota checks for updates itself and shows what's new after each update.## Status+New to Nota? The [user manual](https://nota-daw.github.io/nota-docs/) (English and Russian)+walks through every view and device.+Nota is young and moving fast — new releases come out every week or so (see the[changelog](CHANGELOG.md)). It's already used to make real music, but expect rough edges.Found a bug or missing something? [Open an issue](https://github.com/nota-daw/nota/issues/new/choose) —diff --git a/src/managed/Nota.App/DeviceChainView.Shell.cs b/src/managed/Nota.App/DeviceChainView.Shell.csindex cd619fc8..6e2e274f 100644--- a/src/managed/Nota.App/DeviceChainView.Shell.cs+++ b/src/managed/Nota.App/DeviceChainView.Shell.cs@@ -256,6 +256,19 @@ public sealed partial class DeviceChainViewvar rightMi = new MenuItem { Header = "Move right", IsEnabled = di < s.Count - 1, Icon = MenuKit.Icon(GlyphKind.StepRight) }; rightMi.Click += (_, _) => Move(di + 1);flyout.Items.Add(left); flyout.Items.Add(rightMi);}+ // This device's page in the user manual (a plug-in gets the plug-ins page).+ var docs = new MenuItem { Header = "Documentation" };+ docs.Click += (_, _) =>+ {+ int kind = s.Kind switch+ {+ ChainKind.Instrument => _engine.TrackInstrumentKind(_trackId),+ ChainKind.Midi => _engine.MidiEffectKind(_trackId, di),+ _ => _engine.TrackDeviceBuiltinKind(_trackId, di),+ };+ NotaDocs.Open(headerBar, NotaDocs.DevicePage(s.Kind, kind));+ };+ flyout.Items.Add(docs);flyout.Items.Add(new Separator());}diff --git a/src/managed/Nota.App/MainWindow.Menu.cs b/src/managed/Nota.App/MainWindow.Menu.csindex 7d23da49..ff96ed5c 100644--- a/src/managed/Nota.App/MainWindow.Menu.cs+++ b/src/managed/Nota.App/MainWindow.Menu.cs@@ -27,6 +27,9 @@ public partial class MainWindowprivate void OnWhatsNew(object? sender, EventArgs e) => ShowWhatsNew();+ // Help ▸ Documentation: the user manual in the browser.+ private void OnDocumentation(object? sender, EventArgs e) => NotaDocs.Open(this);+private void OnPreferences(object? sender, EventArgs e) => ShowPreferences();public void ShowPreferences(){diff --git a/src/managed/Nota.App/MainWindow.axaml b/src/managed/Nota.App/MainWindow.axamlindex d74aa65f..5d842524 100644--- a/src/managed/Nota.App/MainWindow.axaml+++ b/src/managed/Nota.App/MainWindow.axaml@@ -90,6 +90,7 @@<NativeMenuItem Header="Help"><NativeMenuItem.Menu><NativeMenu>+ <NativeMenuItem Header="Documentation" Click="OnDocumentation"/><NativeMenuItem Header="What's New" Click="OnWhatsNew"/><NativeMenuItemSeparator/><NativeMenuItem Header="About Nota" Click="OnAbout"/>diff --git a/src/managed/Nota.App/NotaDocs.cs b/src/managed/Nota.App/NotaDocs.csnew file mode 100644index 00000000..d2c19797--- /dev/null+++ b/src/managed/Nota.App/NotaDocs.cs@@ -0,0 +1,63 @@+// SPDX-License-Identifier: AGPL-3.0-only+// Copyright (c) 2026 Egor Khindikaynen (Nota). See LICENSES/ for license terms.+//+// Links into the user manual (nota-daw/nota-docs, published on GitHub Pages): Help ▸+// Documentation and each device card's "Documentation" item. The manual is English with a+// Russian translation under /ru/; a Russian UI culture opens that one. The page slugs mirror+// the manual's src/content/docs tree — keep them in step when a device is added there.++using System;+using System.Globalization;+using Avalonia.Controls;++namespace Nota.App;++internal static class NotaDocs+{+ private const string BaseUrl = "https://nota-daw.github.io/nota-docs/";++ // Engine kind ids → page slug (devices/<group>/<slug>/).+ private static readonly string[] Instruments =+ {+ "instruments/synth", "instruments/sampler", "instruments/physical", "racks/instrument-rack",+ "racks/drum-rack", "instruments/aurora", "instruments/volt", "instruments/bass",+ "instruments/pendulum", "instruments/operator", "instruments/grain", "instruments/flux",+ "instruments/rhythm", "instruments/monolith", "instruments/pentad", "instruments/consort",+ };+ private static readonly string[] AudioEffects =+ {+ "eq-8", "compressor", "reverb", "delay", "utility", "", "valve", "auto-filter", "vintage",+ "orbit", "auto-shift", "beat-repeat", "crush", "dynamic-eq", "ceiling", "strata", "eq-3",+ "forge", "level", "shutter", "chamber", "prism", "lens", "flanger", "phaser", "chorus",+ };+ private static readonly string[] MidiEffects = { "arp", "chord", "scale", "length", "velocity", "random" };++ /// <summary>The manual's address for a page ("" = the home page), in the UI's language.</summary>+ public static string Url(string page = "")+ {+ bool ru = CultureInfo.CurrentUICulture.TwoLetterISOLanguageName == "ru";+ return BaseUrl + (ru ? "ru/" : "") + (page.Length > 0 ? page.TrimEnd('/') + "/" : "");+ }++ /// <summary>The page for a built-in device, or the plug-ins page for anything else.</summary>+ public static string DevicePage(DeviceChainView.ChainKind kind, int engineKind)+ {+ string slug = kind switch+ {+ DeviceChainView.ChainKind.Instrument => Pick(Instruments, engineKind),+ DeviceChainView.ChainKind.Midi => Pick(MidiEffects, engineKind) is { Length: > 0 } m ? "midi-effects/" + m : "",+ _ => engineKind == 5 ? "racks/audio-effect-rack"+ : Pick(AudioEffects, engineKind) is { Length: > 0 } a ? "audio-effects/" + a : "",+ };+ return slug.Length > 0 ? "devices/" + slug : "plugins";+ }++ private static string Pick(string[] map, int i) => i >= 0 && i < map.Length ? map[i] : "";++ /// <summary>Open a manual page in the default browser.</summary>+ public static void Open(Control anchor, string page = "")+ {+ var launcher = TopLevel.GetTopLevel(anchor)?.Launcher;+ if (launcher != null) _ = launcher.LaunchUriAsync(new Uri(Url(page)));+ }+}diff --git a/src/managed/Nota.App/WelcomeWindow.cs b/src/managed/Nota.App/WelcomeWindow.csindex de435f6e..d1d9a916 100644--- a/src/managed/Nota.App/WelcomeWindow.cs+++ b/src/managed/Nota.App/WelcomeWindow.cs@@ -172,11 +172,11 @@ public sealed class WelcomeWindow : NotaWindowGrid.SetRow(recentPanel, 2);root.Children.Add(recentPanel);- // --- Footer: show-on-startup + Settings / What's New --------------+ // --- Footer: show-on-startup + Documentation / Settings / What's New --------------var footer = new Grid{Margin = new Thickness(0, 20, 0, 0),- ColumnDefinitions = new ColumnDefinitions("Auto,*,Auto,Auto"),+ ColumnDefinitions = new ColumnDefinitions("Auto,*,Auto,Auto,Auto"),};var startupTrack = new SwitchTrack { IsOn = showOnStartup };@@ -212,15 +212,22 @@ public sealed class WelcomeWindow : NotaWindowGrid.SetColumn(startup, 0);footer.Children.Add(startup);+ // The user manual, for a first launch that wants a guided start.+ var docsBtn = FooterLink("Documentation");+ docsBtn.Click += (_, _) => NotaDocs.Open(this, "start-here/first-track");+ Grid.SetColumn(docsBtn, 2);+ footer.Children.Add(docsBtn);+var settingsBtn = FooterLink("Settings");+ settingsBtn.Margin = new Thickness(8, 0, 0, 0);settingsBtn.Click += (_, _) => onSettings();- Grid.SetColumn(settingsBtn, 2);+ Grid.SetColumn(settingsBtn, 3);footer.Children.Add(settingsBtn);var whatsNewBtn = FooterLink("What's New");whatsNewBtn.Margin = new Thickness(8, 0, 0, 0);whatsNewBtn.Click += (_, _) => onWhatsNew();- Grid.SetColumn(whatsNewBtn, 3);+ Grid.SetColumn(whatsNewBtn, 4);footer.Children.Add(whatsNewBtn);Grid.SetRow(footer, 3);