Skip to content

feat(support): link Discord for support and feedback (BLD-217) - #22

Merged
dani-polani merged 1 commit into
mainfrom
feat/bld-217-discord-support-link
Sep 30, 2026
Merged

dani-polani merged 1 commit into
mainfrom
feat/bld-217-discord-support-link

Conversation

@dani-polani

Copy link
Copy Markdown
Member

What

Support and feedback now go to the #word-aligner-support channel on Discord.

  • Header: the Tally "Feedback" button is now a Discord link (logo + "Discord"; logo only on mobile, with the name kept for screen readers).
  • Footers: SiteFooter shows "Support and feedback on Discord"; the home page footer shows "Discord" where "Send feedback" was.
  • About → Contact: Discord first, then the Tally feedback form and email as alternatives.
  • Privacy / Terms: references to the in-app "Send feedback" form now point to the form on the About page.

The invite (https://discord.gg/T6jHGWT5Vz) never expires and has no use limit, checked through the Discord API. It lives in one constant, DISCORD_INVITE_URL in brand.ts.

Notes

  • The Tally embed script still loads site-wide through defer-third-party.ts, since the About page uses it. Privacy text about Tally stays accurate, so its "Last updated" date is unchanged.

Checks

svelte-check, prettier, eslint, and vitest (205) are clean. Checked on a local dev server with headless Chromium: header at desktop and 375px, both footers, the About contact block, and that the About feedback button still opens the Tally popup.

🤖 Generated with Claude Code

The header and both footers now link to the #word-aligner-support
channel on Discord instead of opening the Tally form. The About page's
Contact block leads with Discord and keeps the Tally form and email as
alternatives; Privacy and Terms point to the form's new home there.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@dani-polani
dani-polani merged commit c279973 into main Sep 30, 2026
2 checks passed
@dani-polani
dani-polani deleted the feat/bld-217-discord-support-link branch September 30, 2026 00:15
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