Skip to content

Change footer support email to contact@elixir.no - #359

Closed
yasinmiran wants to merge 1 commit into
mainfrom
bever/yasinmiran/ccb69066e0bf
Closed

yasinmiran wants to merge 1 commit into
mainfrom
bever/yasinmiran/ccb69066e0bf

Conversation

@yasinmiran

Copy link
Copy Markdown
Collaborator

What changed

Updated contact.supportEmail in src/data/site.json from support@elixir.no to contact@elixir.no.

The footer's Contact column renders site.contact.supportEmail (as both the visible text and the mailto: link), so this single key change updates the footer email as requested.

Verification

  • astro check passes: 0 errors (remaining hints are pre-existing in untouched files).
  • Diff contains exactly one changed line in src/data/site.json.

Assumptions and side effects

  • The request asked for the footer's support email to become contact@elixir.no. The footer renders the shared contact.supportEmail key from site.json, and components cannot be modified, so the key itself was updated.
  • Side effect: the same key is also used on the Research Support page (src/pages/research-support.astro), where it appears as the hero contact button and in the pricing section's contact buttons. Those will now also show contact@elixir.no. If the Research Support page should keep the old address, that would require a separate key or component change, which is outside what the tools allow here.
  • After this change, contact.supportEmail and contact.generalEmail hold the same value (contact@elixir.no). The two mailboxes were not swapped; only the support email was changed, as requested.
  • No other content was modified.

Copilot AI balanced review requested due to automatic review settings October 22, 2026 21:45

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

@yasinmiran yasinmiran closed this Oct 22, 2026
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