Skip to content

a contact page, and the mailto stops being invisible - #2755

Merged
Flotapponnier merged 1 commit into
devfrom
feat/contact-page
Oct 1, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
feat/contact-page

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

The page

There was none. The address lived in the footer and on /about, /team and /partners, and those pages drew about 1 % of the traffic (17, 15, 14, 13 and 11 visitors over the 11 days PostHog has been recording, against 1,215 in a week).

/contact routes a request to the channel that answers it rather than collecting everything in one inbox:

Request Goes to Why
A number looks wrong data-quality.yml the form asks for the bench slug and the value, which is what makes it checkable
A provider correcting their own entry provider-correction.yml asks who they are, so the change can be attributed in the changelog
A benchmark that does not exist new-benchmark.yml metric, providers and methodology get reviewed before anyone writes a harness
Our independence looks compromised private security advisory the one case where filing in public first makes it worse
Everything else the email address unconditional, and last

No form: it would put a database between the reader and us for no gain. A closing section says what we cannot do (move a provider up, remove an unflattering result, support someone else's product), because those three arrive anyway and silence invites them.

The half that mattered more

posthog-provider.tsx returns early on any protocol that is not http(s). That is correct for the cursor:// and vscode: deeplinks on /mcp, and it silently dropped every mailto. The only contact channel the site had was the only surface it never measured, so "nobody wrote to us" and "we never looked" were the same number.

A mailto now fires contact_click with the page it was clicked from. No address is sent: there is one and it is already public.

Caught in passing

The sitemap gained a duplicate /contact while this was being written, because a grep for "/contact" does not match a template literal spelled `${SITE.url}/contact`. That is the same defect that put /chains/cosmos-hub in the production sitemap twice yesterday. The static route list now has a test that fails on any repeat.

The footer comment counted its own links and named which ones the sitemap lacks; adding one made both halves wrong, so both are corrected.

Verified

tsc --noEmit clean, 395 tests pass (5 new), pnpm validate 241 specs, VERCEL_ENV=production next build emits /contact as static.

Goes to dev first, then this commit alone is cherry-picked to main.

There was no contact page. The address lived in the footer and on three
other pages, so every kind of request arrived in one inbox with no
context, and the pages carrying it drew about 1 % of the traffic.

The page routes a request to the channel that answers it. A wrong number
goes to the data-quality template, which asks for the bench slug and the
value and is therefore checkable. A provider correcting their own entry
goes to the provider template, which asks who they are so the change can
be attributed. A benchmark proposal goes through an issue before anyone
writes a harness. An integrity problem goes to a private advisory rather
than a public issue, which is the one case where filing in the open
makes things worse.

Email stays last and unconditional. A contact page that only offers forms
turns people away, and the ones most worth hearing from are often the
ones who will not open a GitHub account to tell us we are wrong. No form
on the page either: it would put a database between the reader and us for
no gain.

A section says what we cannot do, because those three requests arrive
anyway and a page that stays silent about them invites them.

The second half is why this was worth doing at all. The outbound-click
listener returns early on any protocol that is not http(s), which is
correct for the cursor:// and vscode: deeplinks on /mcp and silently
dropped every mailto. The one contact channel the site had was the one
surface it never measured, so "nobody wrote to us" and "we never looked"
were the same number: zero. A mailto now fires contact_click with the
page it was clicked from, and no address, since there is one and it is
already public.

Also: the sitemap gained a duplicate /contact while this was being
written, because a grep for "/contact" does not match a template literal
spelled ${SITE.url}/contact. That is the same defect that put
/chains/cosmos-hub in the production sitemap twice yesterday, so the
static route list now has a test that fails on any repeat.

The footer comment counted its own links and named which ones the sitemap
lacks. Adding one made both halves wrong, so both are corrected.
@Flotapponnier
Flotapponnier merged commit ac59dff into dev Oct 1, 2026
2 checks passed
@Flotapponnier
Flotapponnier deleted the feat/contact-page branch October 1, 2026 14:37
Flotapponnier added a commit that referenced this pull request Oct 1, 2026
There was no contact page. The address lived in the footer and on three
other pages, so every kind of request arrived in one inbox with no
context, and the pages carrying it drew about 1 % of the traffic.

The page routes a request to the channel that answers it. A wrong number
goes to the data-quality template, which asks for the bench slug and the
value and is therefore checkable. A provider correcting their own entry
goes to the provider template, which asks who they are so the change can
be attributed. A benchmark proposal goes through an issue before anyone
writes a harness. An integrity problem goes to a private advisory rather
than a public issue, which is the one case where filing in the open
makes things worse.

Email stays last and unconditional. A contact page that only offers forms
turns people away, and the ones most worth hearing from are often the
ones who will not open a GitHub account to tell us we are wrong. No form
on the page either: it would put a database between the reader and us for
no gain.

A section says what we cannot do, because those three requests arrive
anyway and a page that stays silent about them invites them.

The second half is why this was worth doing at all. The outbound-click
listener returns early on any protocol that is not http(s), which is
correct for the cursor:// and vscode: deeplinks on /mcp and silently
dropped every mailto. The one contact channel the site had was the one
surface it never measured, so "nobody wrote to us" and "we never looked"
were the same number: zero. A mailto now fires contact_click with the
page it was clicked from, and no address, since there is one and it is
already public.

Also: the sitemap gained a duplicate /contact while this was being
written, because a grep for "/contact" does not match a template literal
spelled ${SITE.url}/contact. That is the same defect that put
/chains/cosmos-hub in the production sitemap twice yesterday, so the
static route list now has a test that fails on any repeat.

The footer comment counted its own links and named which ones the sitemap
lacks. Adding one made both halves wrong, so both are corrected.
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