Skip to content

feat(blog): call flows post in nine languages#131

Open
wavekat-eason wants to merge 3 commits into
mainfrom
feat/blog-call-flows
Open

feat(blog): call flows post in nine languages#131
wavekat-eason wants to merge 3 commits into
mainfrom
feat/blog-call-flows

Conversation

@wavekat-eason

@wavekat-eason wavekat-eason commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Covers the 2026-07-25 releases — wavekat-voice 0.0.43 and wavekat-platform 0.0.24 — as one story rather than two: a call flow answers incoming calls, is authored on the platform, and runs on the desktop app.

What's in here

  • New postanswer-calls-with-a-call-flow.md, "Call Flows — Your Phone Answers, You Watch, You Take Over". Sections: what a call flow is (step table) → build on the web / run on your computer → watch it answer live → take over mid-message → what lands in history → Free vs Pro → 8 FAQs → Try it.
  • All nine localesde, es, fr, it, ja, ko, zh-Hans, zh-Hant alongside English, each with /<slug>/-prefixed in-body links.
  • Five screenshots per locale, one per section — so the Japanese post shows a Japanese app.
  • Click-to-call post published. It was written ahead of its release and held at draft: true; 0.0.43 is now out, so the flag is removed across all nine locales and the date moves to the release day so it surfaces with the release it shipped in.

Translations quote the app, not a fresh translation

Every UI string the post names is taken from wavekat-voice's own locale files, so a German reader sees „Empfang nimmt an" and Annehmen — the words on their screen — rather than a plausible-sounding invention. The same pass corrected the Chinese post, which had paraphrased four strings (活动 line, the Flows section name, the line badge, and the history label).

The post's base path also joins fullSite in src/lib/i18n.ts, which is what earns it hreflang alternates (14 entries, including the zh-Hant-TW/HK/MO fan-out) and sitemap entries in every locale.

Screenshots

Shot Section From
flow-detail What a call flow is wavekat/wavekat-voice#292
flow-editor Build it on the web wavekat/wavekat-platform#173
flow-answering Watch it answer, live wavekat/wavekat-voice#292
flow-takeover Take over mid-message wavekat/wavekat-voice#292
call-details-flow After the call wavekat/wavekat-voice#292

Both product PRs should land before this one, since the scenes are the source of the committed WebPs.

The sync also refreshed the nine existing app scenes. They were captured from an older build, so re-running the pipeline re-rendered them against current main — the visible change is the app's own drift (the Flows item now in the sidebar, the account row's Pro badge). Worth a look, but it keeps every shot on the site depicting the app a reader downloads today rather than mixing two eras of chrome.

Claims checked against shipped code, not the design notes

A few design docs were ahead of what actually shipped, so each factual claim was verified at the released tag:

  • Template gallery and blank starter both shipped in wavekat-platform-v0.0.24; the quick-pick offers templates in the reader's own language, which the post says.
  • Prompt audio is generated only — there's no upload path in the flow editor — so the post describes the bulk "voice every step at once" pass instead of a recording upload.
  • Pro gating is the platform's publish-time check, not a client gate: Free answers the phone (greeting, ring, message, hangup; 1 published flow), Pro routes the call (+ hours, menu, transfer; 10 flows).
  • Take-over is offered only during a message, never mid-greeting or mid-menu.
  • The free-upgrade link points at platform.wavekat.com/profile, where the one-click grant lives.
  • The "is this an AI receptionist?" FAQ answers not yet, since the assistant node is still a later milestone.

Building the screenshots corrected two more: a call's flow steps are pinned along its recording, not listed on their own (the standalone list only renders when there's no recording to pin them to), and the walk-through now follows the open-hours path the demo call actually takes.

Verification

make build + npm run check:links + npm run check:screenshots — 213 pages, no broken or leaking internal links, all 162 screenshots present.

Per-locale checks on the built HTML: each of the nine pages carries 5 images that resolve on disk and use its own locale code, 8 questions extracted into FAQPage schema (Chinese and Japanese included), and the same structure as English — 2 tables, 11 rows, 8 h2, 8 h3.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KiSyWdGUrQLc9tRqsJDiF5

Covers the 2026-07-25 releases — wavekat-voice 0.0.43 and
wavekat-platform 0.0.24 — as one story: a call flow answers incoming
calls (greeting, hours, menu, ring, message, transfer), authored on the
platform and run by the desktop app, with the live step view and
take-over mid-message.

Claims were checked against the shipped code rather than the design
notes: the template gallery and blank starter both shipped, prompt audio
is generated (no upload path in the editor), and Pro gating is the
platform's publish-time check — Free answers the phone, Pro routes the
call.

Also publishes the click-to-call post, which was held as a draft until
its feature shipped: 0.0.43 is out, so `draft: true` is removed across
all nine locales and the date moves to the release day.

Translations for de, es, fr, it, ja, ko and zh-hant are still to come.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KiSyWdGUrQLc9tRqsJDiF5
@github-actions

Copy link
Copy Markdown
Contributor

wavekat-eason and others added 2 commits July 26, 2026 04:20
Five shots, one per section: the flow's map in the app, the web editor
with a step open, the flow answering a call live, the take-over moment
with the caller's message arriving as text, and the finished call.

Four come from wavekat-voice's new demo scenes and one from
wavekat-platform's new flow-editor scene; all nine locales are synced, so
the Chinese post shows a Chinese app.

Building the shots corrected two claims in the post. A call's steps are
pinned along its recording rather than listed on their own — the
standalone list only appears when there's no recording to pin them to —
and the demo call takes the open-hours path, so the walk-through now
matches what the picture shows.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KiSyWdGUrQLc9tRqsJDiF5
Adds de, es, fr, it, ja, ko and zh-Hant alongside the English and
Simplified Chinese posts, so the capability lands in every language the
app itself speaks.

Each translation quotes the app's own wording in that language — pulled
from wavekat-voice's locale files rather than translated afresh — so a
German reader sees "Empfang nimmt an" and "Annehmen", the words their
screen actually shows. The same pass corrected the Chinese post, which
had paraphrased four strings.

The post's base path joins `fullSite` in i18n.ts, which is what gives it
hreflang alternates and sitemap entries across the nine locales.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KiSyWdGUrQLc9tRqsJDiF5
@wavekat-eason
wavekat-eason marked this pull request as ready for review July 25, 2026 16:39
@wavekat-eason wavekat-eason changed the title feat(blog): call flows post (en + zh) feat(blog): call flows post in nine languages Jul 25, 2026
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