Skip to content

feat(site): name every tool in the features page's start line, and Google Calendar on the landing - #471

Merged
leemour merged 1 commit into
mainfrom
feat/landing-tool-names
Oct 31, 2026
Merged

leemour merged 1 commit into
mainfrom
feat/landing-tool-names

Conversation

@leemour

@leemour leemour commented Oct 31, 2026

Copy link
Copy Markdown
Collaborator

Task

The features page still said "Start with Telegram or MAX", and the landing's Google Calendar row was labelled "Calendar".

What

  • Features page (EN/RU/ES): "Start with any WireCat tool, such as Telegram, WhatsApp, MAX, Google Drive or Google Calendar, and add more context at your own pace."
  • Landing tool row: "Calendar" / "Календарь" → Google Calendar in every language, as in tools.json and the page's own intro. The now unused RU Calendar string is removed.
  • pnpm landing:export regenerated lib/editorial/*.json; the CSS it reformatted is left unchanged.

Testing

  • Rendered /, /ru, /es and /{en,ru,es}/features from next dev: the gcal link carries the calendar icon and the name Google Calendar; Google Drive keeps its icon; the old sentence is gone in all three languages.
  • pnpm lint passes. pnpm test: 366 passed; 3 in scripts/command-groups.test.ts fail locally only because they read synced upstream sources (content/upstream/*) that a local checkout does not have.

🤖 Generated with Claude Code

…ogle Calendar on the landing

The features page said "Start with Telegram or MAX", from before WhatsApp,
Google Drive and Google Calendar were published. It now names them all
(EN/RU/ES). The landing's gcal row said "Calendar" ("Календарь" in RU);
tools.json and the rest of the page call it Google Calendar, untranslated.
The unused RU "Calendar" string is dropped. lib/editorial regenerated with
pnpm landing:export; its CSS output is left as it was.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 5841ba5 into main Oct 31, 2026
2 checks passed
@leemour
leemour deleted the feat/landing-tool-names branch October 31, 2026 23:22
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