Point the Signals docs at the Signals site trial, and cross-link the two - #1948
jborlase-snowplow wants to merge 2 commits into
Conversation
Every page under /docs/signals now carries one trial tip, from a single reusable partial, pointing at signals.snowplow.io/start rather than the company-wide trial. The nine Signals tutorials point there too. The navbar CTA is deliberately unchanged: it stays on the Snowplow trial for every section of the site. Seven pages also link to the part of the Signals site that answers the question the docs do not: what to compare Signals with, what it costs, and what an application does with what it retrieves. The Sandbox is retired, so the release note announcing it now says so and its links go to the trial. Two links in that note pointed at http://signals-interventions/start, which was never a real URL. Frontmatter and three tutorial intros described Signals as "a real-time personalization engine for customer intelligence". Both phrases are ruled out by the current messaging: personalization engines are what Signals feeds, not what it is. Replaced with the plain description the body copy already used. "real-time personalization" stays in the keywords, where it describes a use case rather than the category. No parameters on the outbound links. Both sites share the _sp_biz1_ cookie on .snowplow.io, so refr_urlpath already identifies the referring page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Missing SEO metadataThe following markdown files are missing required metadata fields:
Required fieldsThe file metadata is important for SEO and marketing. All markdown files, except for those with filenames starting with
Please add the missing metadata. |
Docs style reviewOverall this is a clean, consistent change: the reusable A few things to fix: 1. Wrong admonition type for the Sandbox retirement
CLAUDE.md reserves Warning for "important cautions about data loss or security risks"; Note is for "general information, context, or clarifications". A product being retired is a clarification. Fix: 2. The release note body now contradicts its own warning
The note above says the Sandbox is no longer available, but the next sentence says it "is available today", and the link text still says "Signals Sandbox" while pointing at the trial signup. The same swap happens twice more ("The Signals Sandbox provides a ready-to-use environment...", "1. Try the Signals Sandbox"), which mislabels the destination — the style guide asks you to describe links clearly and use the target page name where possible. Fix: leave the historical body as unlinked text ( 3. Filler word and orphaned bare domain
Two issues on a line this PR touched: the style guide says remove filler words including "simply", and de-linking left a bare domain sitting in prose that no longer points anywhere. Fix: 4. "E-Commerce" hyphenation
Style guide: "No hyphen in 'ecommerce'. Capitalize only for product names." Applies to both occurrences of this link text on touched lines. Fix: 5. "For why…" / "For how…" sentence openers read awkwardly
Same pattern in Fix: 6. Inconsistent trial link textThree different labels for the same destination across the PR: "free 14-day Signals trial" (the reusable partial), "free 14-day trial" ( Minor
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
documentation | 34dda3e | Commit Preview URL Branch Preview URL |
Sep 20 2026, 09:39 AM |
The release note said the Sandbox was retired and then, two lines later, that it "is available today", with three links labelled "Signals Sandbox" pointing at the trial. The historical body now keeps its own words without links, and the note at the top carries the only live link. Warning became note: a retirement is a clarification, not a caution about data loss. Also in that file: "simply" is a filler word, de-linking had left a bare domain in prose, and ecommerce takes no hyphen or capital outside a product name. "For why" and "For how" openers on two pages became "To understand why/how". One label for one destination: 13 links now all read "free 14-day Signals trial", where three variants had crept in. Dropped "with no credit card" from the partial, which read as signup-page copy; the linked page states the terms. Removed a comma before a compound predicate in the two descriptions and three tutorial intros this branch wrote. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
All six points and both minors are fixed in 34dda3e. The release note was the worst of it and the review is right about why: I put a retirement notice on top of a body that still said the Sandbox "is available today", with three links labelled "Signals Sandbox" pointing at trial signup. The historical body now keeps its own words with no links, and the notice carries the only live link. Also took Settled on one label: all 13 links now read "free 14-day Signals trial". Dropped "with no credit card" from the partial. Not fixing: the metadata bot wants Left alone deliberately: the release note body still says the Sandbox let developers "experiment with real-time customer intelligence". That phrase is ruled out for current copy, and this PR removes it everywhere it appears in |
2 participants
Half of a pair. The other half is snowplow/signals-website#42, which links the product and use case pages back to these docs.
Today there are zero links from the documentation to signals.snowplow.io, and thirteen links sending Signals readers to the company-wide trial instead of the Signals one.
Trial links
Every page under
/docs/signals, all 19 routes, now carries one trial tip pointing atsignals.snowplow.io/start. It comes from a single reusable partial atdocs/reusable/signals-trial/_index.md, following the existingdocs/reusable/convention, so the wording changes in one place:The four pages that already had an inline trial sentence had it replaced in place rather than gaining a second one. The nine Signals tutorials point at
/starttoo.The navbar CTA is deliberately unchanged. It stays on the Snowplow trial, for every section of the site.
Links to the Signals site
Seven pages link to the part of the Signals site that answers a question the docs deliberately do not: what to compare Signals with, what it costs, and what an application does with what it retrieves.
introductionsetupconceptsagentic-contextsinterventionsml-training-datasetsattributes/warehouse-configOne outbound link per page, at a section boundary, phrased as a factual pointer rather than a pitch.
The Sandbox is retired
All four
try-signals.snowplow.iolinks now go to/start, and the release note announcing the Sandbox carries a warning at the top so the body reads as a historical record rather than live instructions. One plain-text mention of the domain survives inside the sentence describing what the Sandbox was.While in that file: two links pointed at
http://signals-interventions/start, which was never a real URL. They now point at the tutorial.Product description
Seven places described Signals as "a real-time personalization engine for customer intelligence": frontmatter on three pages, body copy in three tutorial intros, and one tutorial description.
Both phrases are ruled out by the current messaging. Personalization engines are a destination Signals feeds, not what Signals is. The replacement is the plain description that
introduction/index.mdalready used in its own body:real-time personalizationstays in the keywords, where it names a use case rather than the category. Addedreal-time customer contextandreal-time feature store.Notes
No query parameters on the outbound links. Both sites set the
_sp_biz1_cookie on.snowplow.ioand land in the same table, sorefr_urlpathalready identifies the referring page and a parameter would only add noise to 30 links.Checks
yarn buildpasses. Coverage and every link target were verified against the built HTML: all 19 Signals routes carry the trial link, and all seven microsite targets plus every docs and tutorial target resolve.🤖 Generated with Claude Code