Skip to content

fix(organizations): drop noreferrer from sponsor logo links - #513

Merged
ilteoood merged 1 commit into
mainfrom
feature/organizations-remove-noreferrer
Oct 8, 2026
Merged

ilteoood merged 1 commit into
mainfrom
feature/organizations-remove-noreferrer

Conversation

@ilteoood

@ilteoood ilteoood commented Oct 8, 2026

Copy link
Copy Markdown
Member

Description

Drops noreferrer from the sponsor logo links rendered by
OrganizationLogo.astro, leaving noopener in place. This
restores the fastify.dev URL as the HTTP Referer sent to
sponsor destinations when users click through from either the
home page hero ticker or the organizations page tier showcase.

The noreferrer token also implied the noopener behaviour,
so removing it does not regress tabnabbing protection.

Why

Sponsors requested to see traffic sourced from fastify.dev in
their analytics.

Changes

  • src/components/OrganizationLogo.astro: rel="noopener noreferrer" → rel="noopener" (1 line)

Test plan

  • npx @biomejs/biome check src/components/OrganizationLogo.astro → clean
  • Visual: click a sponsor logo on the home page hero and on the organizations page tier sections; DevTools network panel should show Referer: https://fastify.dev/....

Sponsors want to see fastify.dev as the referrer when visitors
click through from the home marquee or tier showcase, so we keep
noopener for tabnabbing protection but no longer strip referrer.

@mcollina mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ilteoood
ilteoood merged commit 2c8b2e7 into main Oct 8, 2026
5 checks passed
@ilteoood
ilteoood deleted the feature/organizations-remove-noreferrer branch October 8, 2026 16:34

This branch was successfully deployed

2 active deployments
staging — 5c5d3ca7 Deployed Oct 8, 2026 by ilteoood via deploy-to-staging #198
sandbox — 5c5d3ca7 Deployed Oct 8, 2026 by ilteoood via build-and-upload #198
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.

2 participants