Skip to content

feat: voice landing pages and unified chrome#36

Merged
wavekat-eason merged 2 commits intomainfrom
feat/voice-landing
Apr 29, 2026
Merged

feat: voice landing pages and unified chrome#36
wavekat-eason merged 2 commits intomainfrom
feat/voice-landing

Conversation

@wavekat-eason
Copy link
Copy Markdown
Contributor

Summary

  • Adds /voice/, /voice/use-cases/, /voice/talk/ landing pages for the Google Ads campaign. Primary CTA is the Google Calendar booking link; email signup and direct mailto are secondary.
  • Extracts shared Header and Footer components used across home, blog, and voice sections — voice/blog pills are neutral by default, brand-active on the current section.
  • Consolidates contact UI into a single configurable TalkCTA component (replaces Subscribe + a short-lived EmailForm) so the homepage newsletter and voice booking share one implementation.
  • Establishes a clearer card system: clickable cards keep the filled-bg + hover + arrow style; non-clickable items drop the card chrome.
  • De-emphasises the wavekat-voice name in marketing copy (kept where it's a real product reference — the Solutions listing on the homepage and mailto subject lines).

Test plan

  • make build succeeds and emits /voice/, /voice/use-cases/, /voice/talk/
  • Visit /voice/ — booking button opens the Google Calendar appointment page in a new tab
  • Visit /voice/talk/ — booking, email signup (Buttondown tagged voice-interest), and mailto links all work
  • Visit /blog/, /blog/<post>/, /, and /voice/* — header and footer are consistent across all four
  • Confirm active state: voice pill shows orange on /voice/*, blog pill shows darker neutral on /blog/*
  • Toggle dark/light mode on each page — theme persists, no FOUC
  • Mobile viewport — header pills wrap cleanly, forms stack

Add /voice/, /voice/use-cases/, /voice/talk/ as ad-campaign landing
pages with a shared Voice layout. Primary CTA is a Google Calendar
booking link; email signup (Buttondown, tagged voice-interest) and
mailto are secondary paths.

Extract Header and Footer components used across home, blog, and
voice sections so navigation and chrome stay consistent. Active
section is highlighted in the header (voice = brand orange, blog =
neutral).

Consolidate the contact pattern into a single TalkCTA component
(replaces Subscribe + EmailForm) with optional booking button so
the homepage newsletter and the voice booking section share one
implementation.

Distinguish clickable vs non-clickable cards: clickable keep the
filled-bg/border/hover/arrow style, non-clickable drop the card
chrome and present as inline content.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 29, 2026

- Wrap TalkCTA and the wavekat-voice solution in non-clickable cards
  (bg, no border, no hover) — distinct from clickable cards which
  keep border and hover state.
- Simplify TalkCTA: drop optional props, render the same content on
  every page.
- Use-case items rendered as non-clickable cards with the same bg.
- Replace bordered "in development" pill with a dot + label status
  indicator; align it to the right of the Solutions card on the
  homepage.
- Sub-nav on /voice/* pages now uses the same pill style as the main
  header voice/blog tabs, with an added "overview" tab for /voice/.
- Blog tags drop the bordered pill in favor of the plain "#tag" style
  used in PostCard, with more spacing between tags.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@wavekat-eason wavekat-eason merged commit 3a42154 into main Apr 29, 2026
2 checks passed
@wavekat-eason wavekat-eason deleted the feat/voice-landing branch April 29, 2026 23:53
wavekat-eason pushed a commit that referenced this pull request Apr 29, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.0.15](wavekat-com-v0.0.14...wavekat-com-v0.0.15)
(2026-04-29)


### Features

* voice landing pages and unified chrome
([#36](#36))
([3a42154](3a42154))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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