docs: update the a/b variations of three SEM landingpages - #8975
Merged
Conversation
Retire the variations that lost their a/b test on gaidxdb1, gadxie2 and galocal1, and give each page a new challenger variation so it keeps testing more than one copy. - gaidxdb1: retire variation 'b', add variation 'd'. - gadxie2: retire variations 'a' and 'c', add variation 'd'. - galocal1: retire variations 'a' and 'c', add variation 'd'. Retired variations are commented out instead of deleted, so their letters stay reserved and are never re-assigned to different copy. New variations take the next unused letter, which is 'd' on all three pages. Two follow-ups that come with retiring variation 'a': - The server render can no longer default to a hardcoded 'a', because that variation is retired on gadxie2 and galocal1. The pages now take the first live key from Object.keys(variations), which is what getSemVariation() already uses as its own fallback. - The metaTitle of gaidxdb1 and gadxie2 was taken from a variation that is now retired, so both were rewritten to match the copy the page still shows. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013hkkM8BihS5Z2zKX1mjGuX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains:
Improved docs (SEM landingpage copy), plus a small correctness fix to how those pages pick which variation to render.
Describe the problem you have without this PR
Three SEM landingpages (
gaidxdb1,gadxie2,galocal1) were each running an a/b test over three copy variations. Some of those variations have finished their run and are being retired, and each page needs a fresh challenger so it keeps testing more than one copy instead of collapsing to a single variation.Retiring variation
aalso exposes two problems in the existing pages:'a'.Page()useduseState('a')and?? variations.a. On a page where variationais retired, that resolves toundefinedand the page renders nothing on the server and on the first client render. Fixed by taking the first live key fromObject.keys(variations), which is exactly whatgetSemVariation()already uses as its own fallback, so the two now agree.metaTitlewas copied from one variation's title. Ongaidxdb1andgadxie2that variation is now retired, so the browser tab and the search-result title advertised copy the page no longer shows. Both were rewritten to match the copy that is still live.What changed per page
gaidxdb1badgadxie2a,cbdgalocal1a,cbdRetired variations are commented out, not deleted, per the rules documented in
getSemVariation(): a letter is never reused for different copy, so tracking events stay comparable over time. New variations take the next unused letter, which isdon all three pages sincecis retired everywhere.Todos
Verification
node_moduleswas not installed in this environment, sonpm run check-typesandnpm run lintwere not run. Note that the roottsconfig.jsonlistsdocs-srcin bothincludeandexclude, andexcludewins, sonpm run check-typesdoes not cover these files either way. Instead the three changed files were type-checked with a standalonetsc 5.7.2under--strict, filtering the module-resolution errors caused by the missing dependencies. The same check was run against the unmodified originals as a control, and the changed files are clean at the same level as the originals.🤖 Generated with Claude Code
https://claude.ai/code/session_013hkkM8BihS5Z2zKX1mjGuX
Generated by Claude Code