Skip to content

docs: Documents & files section (Markdown, Notion, Yandex Disk, Google Drive) - #669

Closed
leemour wants to merge 3 commits into
mainfrom
docs/documents-files-section
Closed

leemour wants to merge 3 commits into
mainfrom
docs/documents-files-section

Conversation

@leemour

@leemour leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member

Task

A new sidebar section, Documents & files, with Markdown, Notion, Yandex Disk and Google Drive. Each start page opens with what the reader gets, then an "On this page" list, then "How it works" (the ideas a newcomer needs), then setup and details.

What

  • Sidebar: a documentsFiles entry in toolGroups (lib/docs-sidebar-tree.tsx), built like Meetings & Calls. It is an open folder in "Connect a source" with no URL changes. Labels are in lib/words.ts (EN/RU/ES). In meta*.json, Google Calendar still follows Drive, so in the sidebar it now comes right after the group.
  • Markdown (content/docs/markdown.{mdx,ru,es}, new): Markdown folders and Obsidian vaults through memo's folders add. Facts come from cli-memo v0.135.0 docs/notes.md, and the page links memo's reference for details. There is no separate Markdown tool.
  • Yandex Disk (content/docs/ydisk.{mdx,ru,es}, new): written from WireCatLabs/ydisk at c13b765 (code, docs, DESIGN.md, skill), not from the README. @wirecat/yandex-disk-cli has no npm release and no tag yet, so it cannot be a tools.json tool. This is a single site page for now. Token steps were checked against Yandex ID's debug-token guide.
  • Google Drive (translations/overviews/drive.*, new): a start page owned by this site. The released index opened with "WireCat Drive is a command-line tool" and had no contents list. The old section anchors are kept.
  • Notion (translations/overviews/notion.*): adds a "How it works" section.
  • Rows in the start page's "Which tool do I need" table, README index rows, cspell words, and a navigation test.

Before merging

  • Deploy runs on each merge to main. The ydisk page says npm install -g @wirecat/yandex-disk-cli, which returns 404 until the package is published.
  • After ydisk's first release, add it to tools.json and move content/docs/ydisk.*.mdx into translations/overviews/ydisk.*.md, so the URL stays /docs/ydisk.

Notes for ydisk

  • The generated example for folders add says FOLDER_ID, but the argument is a Disk path such as /Documents.

Testing

Run locally:

  • lint, docs:lint, docs:versions, docs:opening (9 changed pages), check:links --source, standards:check, ci:quick (510 tests), typecheck.
  • pnpm sync, docs:contracts, docs:quality --strict (0 reference gaps, 0 invalid examples).
  • docs:spell on the new pages.
  • The six new .mdx files compile with @mdx-js/mdx.

Not run:

  • next build: the kernel killed it while compiling (swap full, other processes on the machine), even with 2 workers. It runs in the deploy.
  • Playwright: runs in the deploy.

🤖 Generated with Claude Code

leemour and others added 3 commits November 17, 2026 11:33
…k and Google Drive

The sidebar's "Connect a source" gets an open "Documents & files" group, built
the same way as Meetings & Calls (a toolGroups entry, so no URL changes):
Markdown, Notion, Yandex Disk, Google Drive. Google Calendar still follows
Drive in meta.json, so it now sits right after the group.

Every start page in the group follows one order: what the reader gets, an
"On this page" list, "How it works" with the ideas a newcomer needs, then
setup, tasks and details.

- markdown.{mdx,ru,es}: new site page. Markdown folders and Obsidian vaults
  through memo's `folders add` (facts from cli-memo v0.135.0 notes.md), with
  links to memo's reference instead of copying it.
- ydisk.{mdx,ru,es}: new site page for @wirecat/yandex-disk-cli, written from
  the ydisk repo's code and docs at c13b765. The package has no npm release
  or tag yet, so it cannot be a tools.json tool; once released, this page
  moves into translations/overviews/ydisk.* at the same URL.
- translations/overviews/drive.*: a site-owned Drive start page. The released
  index opened with "WireCat Drive is a command-line tool" and had no
  contents list. Anchors of the old sections are kept.
- translations/overviews/notion.*: a "How it works" section.
- Rows in the docs start page's "Which tool do I need" table, README index
  rows, cspell words, a navigation test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nc limit, Drive says when to use your own Google app

From the review of #669. The old Drive start page translations go to CLEANUP.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 17, 2026
…U/ES (#671)

## Task
Move three tools' docs on wirecat.dev to the versions on npm: Notion
0.2.0 → 0.5.0, Bitrix24 (b24) 0.15.0 → 0.24.0, Asterisk (pbx) 0.7.1 →
0.7.2. Done the way #665 moved gcal.

## What
- `tools.json`: `docsRef` for notion, b24 and pbx.
- RU/ES translations of every page the sync marked stale. Each was
translated from the released source diff (old tag against new tag), read
in full against the English and accepted with `docs:translation accept`.
- Notion: changelog (0.3.0 to 0.5.0), commands, configuration,
installation (new Sign in section), troubleshooting, security (source
change was punctuation only).
- b24: changelog (0.16.0 to 0.24.0), commands, configuration, index,
installation, mcp, permissions, roadmap, security, troubleshooting,
usage.
- b24 **Calls**, a new page in 0.24.0:
`translations/b24/calls.{ru,es}.md`, a sidebar icon (`PhoneCall`) and
SEO descriptions in `lib/b24-descriptions.ts`.
  - pbx: changelog 0.7.2 and the one changed sentence in usage.
- Commands RU/ES: the localized intro and headings re-applied onto the
new generated reference, the rest stays in the help's language, as
before.
- Site-owned pages:
- Notion roadmap EN/RU/ES: page writes (`documents
create|update|delete|restore`, 0.3.0) and comments and file upload
(`comments`, `files upload`, 0.4.0) shipped, so they move from the plan
to "What works today".
- Notion compare EN/RU/ES: "Create a page or change its text from
Markdown" is now ✅, with the note rewritten.
- b24 compare EN/RU/ES: `api call` reads leads too for an administrator
only (0.24.0).
- `scripts/docs-corrections.json`: the pbx changelog link correction
follows the v0.7.2 tag.
- `docs/release-notes-review.json`: reviews for b24 v0.24.0 (roadmap
changed: activities on deals and leads shipped) and pbx v0.7.2 (roadmap
unchanged). Notion has no upstream roadmap, so it needs no record.

## Terms
- timeline: RU «таймлайн», ES «línea de tiempo»
- activities / to-dos: RU «дела», ES «actividades» / «pendientes»
- other phone systems: RU «другие телефонные системы», ES «otras
centralitas» (as the pbx pages)
- Bitrix24's call list in RU: «Телефония → Детализация звонков», the
name in [Bitrix24's Russian
help](https://helpdesk.bitrix24.ru/open/18641558/). ES keeps the English
UI labels, as the other ES b24 pages do.
- ES "Changed — may break callers" headings use «Cambios — pueden romper
scripts», as the older entries do.

## Source issues for bitrix24-cli
- `docs/usage.md` says `disk` is "for the files feature that comes
next": a promise in a pinned guide.
- `docs/calls.md` writes "such as pbx" as plain text, not as `pbx` or a
link.
- `docs/calls.md` opens with "Read this page if…" and a "Words this page
uses" block, which the site's opening rules
([AUTHORING.md](docs/AUTHORING.md)) avoid. The translations mirror the
release, so the fix belongs in the tool repository.

## Not in this PR
- b24 compare has no rows for calls yet: a row needs evidence for each
of the four other tools.
- The b24 `summary` in `tools.json` still names deals, leads, contacts
and companies only.
- The Notion overview (`translations/overviews/notion.*`) is untouched:
the upstream index did not change, and #669 rewrites it.

## Testing
- `pnpm sync` (all tools), `pnpm docs:contracts`, `pnpm docs:check` (0
reference gaps, 0 invalid examples), `pnpm docs:release-notes`, `pnpm
lint`, `pnpm typecheck`, `pnpm exec vitest run` (49 files, 515 tests),
`pnpm search:check`, `pnpm check:links --source`.
- `docs:translation check` on every changed translation: structure ok,
fingerprint current.
- `docs:spell` on the new and site-owned files: only product names and
Russian inflections of «вебхук».
- `next dev`: `/en|ru|es/docs/b24/calls` answer 200 with their anchors,
the RU b24 sidebar lists Calls, and the changed Notion, pbx and b24
pages answer 200.
- `pnpm build` was not run to the end: the export was killed for lack of
memory on this machine (exit 137). The deploy runs it.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 17, 2026
…es (EN/RU/ES)

Brings in the Yandex Disk page and the Notion start page's "How it works" section from
PR #669, so the Documents & files section ships as one PR.

- ydisk.mdx (EN/RU/ES): a site page for Yandex Disk, before ydisk's first release. The owner
  decided that unreleased tools may be documented. A "Coming soon" lead-in, as agents.mdx
  uses for planned work, says the npm package is not out yet; the install command stays as
  it will work after the release. Commands and options checked against ydisk-cli main
  (552e53d, docs/commands.md and src/commands/files.ts).
- Yandex Disk joins the sidebar group (between Notion and Markdown), meta.json in every
  language, the start page's "Which tool do I need" table and the docs index.
- Notion's start page gets "How it works" right after its contents list: the copy, the
  token, the profile, the sync and the agent.
- cspell words from #669, and the navigation test covers the new page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour

leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member Author

Merged into #668 (its Yandex Disk page and the Notion 'How it works' section), so the section ships as one PR.

@leemour leemour closed this Nov 17, 2026
leemour added a commit that referenced this pull request Nov 17, 2026
… mail in EN/RU/ES (#672)

Readers of the tg, max, wa, zm and mail overviews could not see what the
tool gives them: the pages opened with setup and a guide table. Each
overview is now a benefit-first page in EN, RU and ES, following the
overview template from the docs-marketing plan (cli-private
`plans/2026-11-17-docs-marketing/overview-template.md`).

## What changed per tool

Every page now has: an opening that names the reader's gain, a numbered
"On this page", **What you get** (gains with a fact each), **Things a
newcomer would not guess**, a You/Agent example, **Why <tool>** with
facts from the comparison page plus a link to it and one "fits better"
line, what it can do by task, **How it works**, a start, **Limits** and
a task-to-guide table.

- **tg:** gains (replies you owe, offline search with word forms and
meaning, promises, voice without Premium, group rules, auto-replies, 185
Bot API methods). Proof: no WireCat server, official API with your own
app, the three search rows no other tool on the comparison documents,
keyring. Limits: meaning search needs a 219 MB model, call history,
privacy settings and stickers not yet in tg.
- **max:** Russian page written first. Gains include moderation by rules
(marks by default) and the Bot API. Proof: the compare rows only max has
(unread in all chats, owe/owed, meaning and offline search, local voice,
morning digest, agent limits). Limits state the internal API and the MAX
user agreement risk once, plainly, with a link to security (answers the
search-intent question "is automating a personal account allowed").
- **wa:** was 16 lines of links. Now a full page. Proof: the "hold every
send when WhatsApp says slow down" row only wa has. Keeps the `wa/bot`
and `wa/permissions` links the browser test needs. `server install` +
`server start` named correctly (install alone starts nothing, macOS and
Linux only).
- **zm:** sidebar label loses its long dash ("Zoom: start here").
Example ends with a previewed `remote-meetings update` the user
approves. Quick start no longer has the `<public-client-id>` placeholder
(WC-DOC-12): it installs, then links First run.
- **mail:** gain moves to the first sentence, the page-about-the-page
opening goes, providers table moves under "What it can do", "Why mail"
adds the two rows only mail has (one store with chats, undo). "Every
change can be undone" narrowed to moves and deletions, with a Limits
line on deleted drafts and Gmail's 30-day Trash. `session start` runs
without `--address` (it asks at a terminal).
- **Docs start page:** the mail row no longer says "(read only)" in EN,
RU, ES.
- **`tests/zoom-docs.spec.ts`:** follows the new Zoom H1.

## Titles (`lib/seo-copy.json` → `toolTitles`, the HTML H1 and
`<title>`)

| Tool | Lang | Before | After |
|---|---|---|---|
| tg | en | Telegram CLI client for AI agents | Telegram MCP server and
CLI for your own account |
| tg | ru | CLI-клиент Telegram для ИИ-агентов | Telegram MCP-сервер и
CLI для личного аккаунта |
| tg | es | Cliente CLI de Telegram para agentes de IA | Servidor MCP y
CLI de Telegram para tu cuenta |
| max | en | MAX CLI for AI agents and bots | MAX messenger MCP server,
CLI and Bot API |
| max | ru | MAX CLI для ИИ-агентов и ботов | MCP-сервер и CLI для
мессенджера MAX |
| max | es | CLI de MAX para agentes de IA y bots | Servidor MCP y CLI
de MAX Messenger |
| wa | en | WhatsApp CLI for your AI agent and business bots | WhatsApp
MCP server and CLI for your personal account |
| wa | ru | WhatsApp CLI для ИИ-агентов и бизнес-ботов | WhatsApp
MCP-сервер и CLI для личного аккаунта |
| wa | es | CLI de WhatsApp para tu agente de IA y bots de empresa |
Servidor MCP y CLI de WhatsApp para tu cuenta |
| zm | en | Connect Zoom transcripts and recordings to your AI agent |
Zoom transcripts MCP server and CLI |
| zm | ru | Подключите расшифровки и записи Zoom к ИИ-агенту |
MCP-сервер и CLI для расшифровок Zoom |
| zm | es | Conecta las transcripciones y grabaciones de Zoom a tu
agente de IA | Servidor MCP y CLI para transcripciones de Zoom |
| mail | en | Connect your mail to your AI agent over IMAP | IMAP mail
MCP server and CLI with offline search |
| mail | ru | Подключите почту к ИИ-агенту по IMAP | MCP-сервер почты по
IMAP с поиском без интернета |
| mail | es | Conecta tu correo a tu agente de IA por IMAP | Servidor
MCP de correo IMAP con búsqueda sin conexión |

Titles are the SEO set from cli-private `seo-keywords.md`. Meta
descriptions (frontmatter) are new: a gain plus a fact, different from
the opening.

## Reviewer checklist (template's 11 points), per page

Checked on each page in EN, RU and ES.

| # | Check | tg | max | wa | zm | mail |
|---|---|---|---|---|---|---|
| 1 | A newcomer can say what they get from the first screen | ✅ | ✅ | ✅
| ✅ | ✅ |
| 2 | First sentence names a gain, reader or agent as subject | ✅ | ✅ |
✅ | ✅ | ✅ |
| 3 | "What you get", 5 to 7 gains, no command in bold | ✅ 7 | ✅ 6 | ✅ 6
| ✅ 6 | ✅ 6 |
| 4 | You/Agent example with a source and an approved write | ✅ | ✅ | ✅
| ✅ | 🟡 the draft is asked for and saved, nothing is sent, no separate
yes |
| 5 | Fact against a named rival, comparison link, fits-better line | ✅
| ✅ | ✅ | ✅ | ✅ |
| 6 | Nothing technical before "What you get" | ✅ | ✅ | ✅ | ✅ | ✅ |
| 7 | Title, description and opening are three different sentences | ✅ |
✅ | ✅ | ✅ | ✅ |
| 8 | Claims true at the `docsRef` pin | ✅ | ✅ | ✅ | ✅ | 🟡 two facts
from main (below) |
| 9 | Ends with a next step (guide table) | ✅ | ✅ | ✅ | ✅ | ✅ |
| 10 | VOICE: no `;`, long dashes, `ё`, guillemets, hype words | ✅ | ✅ |
✅ | ✅ | ✅ |
| 11 | `docs:opening` passes (run on the files by name, since it only
scans `content/docs`) | ✅ | ✅ | ✅ | ✅ | ✅ |

**Claims dropped or narrowed as unverifiable at the pin:** "search
forgives typos" (max), "every change can be undone" (mail), "speakers
stay unknown" and "needs ffmpeg" (zm), "some of it is not checked
against real WhatsApp" (wa, also editorial history per AUTHORING), "only
to the people you choose" for tg auto-replies (narrowed: replies go to
everyone a rule matches unless you limit the audience). **From mail-cli
main, not the pin (4 commits apart):** the first sync reads 30 days by
default (`src/commands/sync.ts`), Gmail empties Trash after 30 days.

## Checks run locally

`pnpm lint`, `pnpm search:check`, `pnpm docs:release-notes`, `pnpm
docs:contracts`, `pnpm docs:check`, `pnpm check:links --source`, `pnpm
test` (515 passed), `pnpm typecheck`, `docs:opening` on the 15 overview
files by name. `pnpm docs:spell` fails on main already (55 issues in
other files, none in changed files) and is not in CI. `next build` was
not run locally (memory cap on this machine); the Full validation
workflow is dispatched on this branch for the build, links, SEO and
browser tests.

Not touched: drive, notion and Documents & files (#668, #669), and b24,
gcal, memo, pbx.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 17, 2026
…es (EN/RU/ES)

Brings in the Yandex Disk page and the Notion start page's "How it works" section from
PR #669, so the Documents & files section ships as one PR.

- ydisk.mdx (EN/RU/ES): a site page for Yandex Disk, before ydisk's first release. The owner
  decided that unreleased tools may be documented. A "Coming soon" lead-in, as agents.mdx
  uses for planned work, says the npm package is not out yet; the install command stays as
  it will work after the release. Commands and options checked against ydisk-cli main
  (552e53d, docs/commands.md and src/commands/files.ts).
- Yandex Disk joins the sidebar group (between Notion and Markdown), meta.json in every
  language, the start page's "Which tool do I need" table and the docs index.
- Notion's start page gets "How it works" right after its contents list: the copy, the
  token, the profile, the sync and the agent.
- cspell words from #669, and the navigation test covers the new page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 17, 2026
…es (EN/RU/ES)

Brings in the Yandex Disk page and the Notion start page's "How it works" section from
PR #669, so the Documents & files section ships as one PR.

- ydisk.mdx (EN/RU/ES): a site page for Yandex Disk, before ydisk's first release. The owner
  decided that unreleased tools may be documented. A "Coming soon" lead-in, as agents.mdx
  uses for planned work, says the npm package is not out yet; the install command stays as
  it will work after the release. Commands and options checked against ydisk-cli main
  (552e53d, docs/commands.md and src/commands/files.ts).
- Yandex Disk joins the sidebar group (between Notion and Markdown), meta.json in every
  language, the start page's "Which tool do I need" table and the docs index.
- Notion's start page gets "How it works" right after its contents list: the copy, the
  token, the profile, the sync and the agent.
- cspell words from #669, and the navigation test covers the new page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 17, 2026
…k and Markdown (EN/RU/ES) (#668)

## What

A new sidebar group, **Documents & files**, under "Connect a source", in
EN/RU/ES. It holds:

- **Google Drive**, with a new portal start page
(`translations/overviews/drive.*.md`), as Notion already has.
- **Notion**, unchanged (its portal start page already follows the same
order).
- **Markdown and Obsidian** (`content/docs/markdown*.mdx`), a new
site-owned page. There is no Markdown tool: `memo`
reads folders of notes, so the page works like the Google Meet page does
for `gcal`.

The group is built like Meetings & Calls and CRM (`toolGroups` in
`lib/docs-sidebar-tree.tsx`, labels in
`lib/words.ts`). URLs do not change.

## Page order

Each new page opens with what the reader gets, then what the agent can
do for them, then "On this page", then the
ideas a newcomer needs (Markdown folder or Obsidian vault; profile and
local copy), then the rest.

## Sources

- Markdown: cli-memo v0.135.0 (pinned in `tools.json`), `docs/notes.md`,
`docs/commands.md`, `docs/installation.md`.
- Google Drive: drive-cli v0.65.0, `docs/index.md`,
`docs/installation.md`, `docs/usage.md`, `docs/commands.md`.
- No placeholders in runnable commands: the example folder `~/Notes` and
the example Drive folder link are labelled.

## Merged from #669

- **Yandex Disk** (`content/docs/ydisk*.mdx`): a site page before
ydisk's first release (the owner allows unreleased
tools). A "Coming soon" lead-in says the npm package is not out yet.
Commands checked against ydisk-cli main.
- **Notion**: a "How it works" section after the contents list.

## Checks run locally

`pnpm lint`, `search:check`, `sync`, `docs:release-notes`, `test` (525
passed), `docs:contracts`, `docs:check`,
`typecheck`, cspell on the new pages. `next build` cannot run on this
machine: it hits an 11 GB cap on `main` too.

## Why CI adds swap before `next build`

`next build` hung at random in CI: 4 of 9 builds on this branch, and it
can hit `main` too. I ran it in a systemd
cgroup that reports its memory peak, on the same `ubuntu-latest` runner
(4 CPUs, 16 GB RAM):

| Run | Result |
| --- | --- |
| `main`, swap allowed | passed, 14.3 to 14.4 GB RAM plus 2.1 to 2.9 GB
swap |
| this branch, swap allowed | passed once at 14.2 GB plus 1.4 GB swap;
killed once on a runner with no swap (14.6 GB) |
| `main` and this branch, no swap, 13 GB cap | 8 of 8 killed at 13 GB
during compile |
| `turbopackPluginRuntimeStrategy: "workerThreads"`, no swap | 2 of 2
killed at 14.8 GB |
| 8 GB swap file | 2 of 2 passed in about 3.7 minutes |

So the build needs about 17 GB, more than the runner has. Some runners
have 3 GB of swap and some have none. With
none, the machine stalls instead of failing, which is the hang. This
branch's few extra pages do not change the peak
in a way the runs can tell apart from `main`. The `check`,
`search-playground` and Deploy build jobs now add an 8 GB
swap file before `next build`.

Notion's start page also lists writing to Notion now. 0.3.0 to 0.5.0
added it, and the old list still said it had no write
commands.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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