Skip to content

docs: correct the user manual, and name the two menus for users - #650

Merged
TheSevenPens merged 2 commits into
masterfrom
docs/manual-accuracy
Sep 2, 2026
Merged

docs: correct the user manual, and name the two menus for users#650
TheSevenPens merged 2 commits into
masterfrom
docs/manual-accuracy

Conversation

@TheSevenPens

@TheSevenPens TheSevenPens commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Started from one wrong sentence, checked the rest of the manual, then renamed the two menus for users and filled a documentation gap.

Terminology (second commit)

The mental model is that the app is made of pages, and a page may be divided into tabs. So the two menus are named after what they select:

was now
top row "top navigation bar" page menu
row beneath "pivot row" tab menu

Pages with nothing to divide (Home, Scribble) simply have no tab menu — the manual now says that outright rather than leaving it to inference.

Internal names are untouched. WordmarkNav / PivotTab in the code, and "wordmark bar" / "pivots" in the redesign spec, still mean what they always did. This is what we call them to users, not a rename of the implementation.

Corrections (first commit)

  • "the active page is underlined in the accent colour" — it never was. Both menus mark the current item with accent colour + weight and no underline; that was an explicit call in the redesign.
  • The tablet switcher was described as "at the top-right … shown when more than one is connected". The position was stale (it moved into the page menu in feat: move the tablet switcher into the shell top bar #646), and the count gate never existedShowTabletSwitcher is simply "are we on Tablet or Pen".
  • Home tablets were described as having a Settings button. That was replaced by double-click; Forget is a trash icon. HOME.md already said this correctly, so the two pages contradicted each other.
  • TABLET.md / PEN.md both described a per-page header holding the switcher + Refresh. There is no page header any more.
  • The theme list named four skins. There are six — Dark Sakura and Custom were missing.

Documentation gap filled

Highlight colour and Card colour existed but had never been written up — only Card opacity had. The new Colours & opacity section covers all four controls, how the picker works (swatch + hex, opening a wheel / palette / hex box), that everything is stored per skin, and what Reset to defaults actually resets.

Verifying that section against the source turned up one more error: "Falling petals (Sakura only)" is wrong — ShowPetalsToggle is Sakura or Dark Sakura or Custom.

Checked and left alone

  • HOME.md'"'"'s double-click + trash description — already correct.
  • ADVANCED.md'"'"'s claim that the Diagnostics Show picker hides with a single tablet — verified, ShowTabletPicker really is Count > 1.

Docs only, no code. Every claim was checked against the source rather than against memory of what we built.

TheSevenPens and others added 2 commits September 2, 2026 05:14
Started from one wrong sentence and checked the rest. Five corrections,
four of them things this session's UI work invalidated.

USERMANUAL
  "the active page is underlined in the accent colour" -- it never was.
  Both nav levels mark the active item with accent colour + weight and
  no underline; that was an explicit call in the Zune redesign, and the
  pivots use the same cue deliberately.

  The tablet switcher was described as "at the top-right ... shown when
  more than one is connected". It now sits in the top navigation bar
  (it moved there this session), and it is NOT gated on tablet count --
  ShowTabletSwitcher is just "are we on Tablet or Pen". Checked for a
  count gate before rewriting; there is none anywhere.

  Home tablets were described as having "a Settings button and a Forget
  button". The per-row Settings button was replaced by double-click, and
  Forget is a trash icon. HOME.md already said this correctly, so the
  two pages disagreed.

TABLET / PEN
  Both described a per-page header holding the switcher + Refresh. There
  is no page header any more; both live in the top navigation bar.

SETTINGS
  The theme list named four skins. There are six -- Dark Sakura and
  Custom were missing. Pre-existing, not from this session.

Also verified as still ACCURATE and left alone: HOME's double-click and
trash description, and ADVANCED's claim that the Diagnostics "Show"
picker is hidden with a single tablet (ShowTabletPicker really is
Count > 1).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… & opacity

Terminology, in the user-facing docs only. The mental model is that the
app is made of PAGES, and a page may be divided into TABS -- so the two
menus are named after what they select:

  page menu   the top row (was "top navigation bar")
  tab menu    the row beneath it (was "pivot row")

Pages with nothing to divide (Home, Scribble) simply have no tab menu,
which the manual now says outright rather than leaving to inference.
The internal names are untouched: WordmarkNav / PivotTab in the code and
"wordmark bar" / "pivots" in the redesign spec still mean what they
always did. This is what we call them TO USERS, not a rename of the
implementation.

Also fills the documentation gap under Appearance. Highlight colour and
Card colour existed but had never been written up -- only Card opacity
had. The new "Colours & opacity" section covers all four controls, how
the picker works (swatch + hex, opening a wheel / palette / hex box),
that everything is stored PER SKIN, and what Reset to defaults actually
resets.

And one more inaccuracy found while verifying that section against the
source: "Falling petals (Sakura only)" is wrong -- ShowPetalsToggle is
Sakura OR Dark Sakura OR Custom.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@TheSevenPens TheSevenPens changed the title docs: correct the user manual where it described the old UI docs: correct the user manual, and name the two menus for users Sep 2, 2026
@TheSevenPens
TheSevenPens merged commit c6e7b0b into master Sep 2, 2026
3 checks passed
@TheSevenPens
TheSevenPens deleted the docs/manual-accuracy branch September 2, 2026 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant