Add four themed road trip journal SEO landing pages

[drumpat01]

Adds four public SEO landing pages on the same wiring as #268, #270, #273, and #276 (9057b86):

• /route-66-road-trip-journal
• /pacific-coast-highway-road-trip-journal
• /national-parks-road-trip-journal
• /texas-hill-country-road-trip-journal

Each page has a public path, sitemap entry, server tests, verify-live expectations and feature map row, canonical, meta and OG tags, FAQ JSON-LD, Umami, and the plain App Store CTA so campaign.js can add pt / ct / mt on campaign visits.

Copy follows the attached draft, with unconfirmed personal lines removed, then these design-review fixes. Visible FAQ answers and JSON-LD FAQ text stay identical.

• Route 66: "Route 66 turned 100 in 2026." Offline FAQ: "No. Core recording works offline, which matters out in the Mojave." Guide FAQ: "No. It won't tell you where the next neon sign is. Use your guide for that."
• PCH intro: "A private iPhone journal for Highway 1. Route, miles and photos, saved on your phone. Works offline, even where the signal doesn't." FAQ answers updated in order.
• National parks auto-track FAQ: "No. Nothing runs in the background. You start it. You stop it." Signal FAQ: "No. Lots of parks have little or no signal, and core recording works offline on your iPhone."
• Hill Country How to keep the drive: "Start a journey when you back out of the driveway and forget about it until you're eating brisket." Guide FAQ: "No. It won't plan your stops or find the best peach stand. It just keeps the drive." Closing question links to /support.

No em or en dashes. Journeys start only when the user taps Start Journey. Nothing records automatically.

Cross-links:

• /road-trip-journal-app "Journals for specific roads"
• /private-driving-journal themed-trip paragraph
• /apple-music-soundtrack footer
• Sibling links on each new page

Screenshots

Updated after the design-review copy pass.

/route-66-road-trip-journal

390

1280

Full page at 390

Full page at 1280

/pacific-coast-highway-road-trip-journal

390

1280

Full page at 390

Full page at 1280

/national-parks-road-trip-journal

390

1280

Full page at 390

Full page at 1280

/texas-hill-country-road-trip-journal

390

1280

Full page at 390

Full page at 1280

What reviewers should check

• Design-review FAQ and intro copy is applied
• Visible FAQ answers match JSON-LD
• No em or en dashes
• Start Journey is manual
• Hill Country closer links to /support

Verification

• node --test --import tsx server/tests/api.test.ts server/tests/campaign.test.ts server/tests/verify-live.test.ts (34 passed locally)
• JourneyDeck CI / validate
• Playwright screenshots at 390x844 and 1280x800 after the copy pass

Do not merge or deploy from this PR.

  

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-12T21:44:56.785047Z	df6288c	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: df6288c0ca

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Apply the public accessibility layer to the new pages

All four new landing pages omit /public-a11y.css?v=2, the #main target, and the skip link required by the established public-page accessibility pattern in server/tests/public-a11y.test.ts. As a result, keyboard users must traverse the sticky header on every visit, and these pages also miss the shared tap-target and 390px header fixes. Add the stylesheet and skip-link/main-target markup to each new page, and include the routes in that accessibility test.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Describe manual start without denying background recording

When a user starts a journey and then locks the phone or switches apps, JourneyDeck explicitly continues recording with background location, as documented in web/privacy.html and implemented by the recorder. Publishing “Nothing runs in the background” in both the visible FAQ and FAQ JSON-LD therefore contradicts the app's permission disclosure and can mislead users about location behavior; state that recording does not start automatically instead.

Useful? React with 👍 / 👎.