Unify how the docs link to Discord, and move contact details to .com - #17
Open
atsetilam wants to merge 3 commits into
Open
Unify how the docs link to Discord, and move contact details to .com#17atsetilam wants to merge 3 commits into
atsetilam wants to merge 3 commits into
Conversation
Every page now links to the "Join our Discord" contact page rather than to a raw invite, and that page holds the single tracked Discord URL. This keeps the invite link in one place and ensures visits are attributed. Previously three different invite URLs were pasted across the docs (discord.gg/..., discord.com/invite/..., and internal page links), none of which carried tracking.
The footer social icon linked to the untracked invite; point it at the same tracked URL the docs now use. Also update hello@spectralcompute.co.uk to hello@spectralcompute.com. The legal@spectralcompute.co.uk addresses in notices.md and use_of_trademarks.md are left alone: different mailbox, not asked for.
Updates legal@spectralcompute.co.uk in notices.md and use_of_trademarks.md, and the footer copyright link. The copyright link uses the bare https://spectralcompute.com: both the www. host and the old .co.uk domain redirect there, so this avoids a redirect hop.
atsetilam
force-pushed
the
docs/unify-discord-links
branch
from
July 15, 2026 10:48
a7f37eb to
a9e8567
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Gives the docs a single source of truth for the Discord invite, and moves the remaining contact details off the
.co.ukdomain.https://scale-lang.com/s/discord?utm_source=docs&utm_medium=internal.hello@spectralcompute.co.uk→hello@spectralcompute.com, andlegal@spectralcompute.co.uk→.com.https://spectralcompute.com.Why
The docs contained three different Discord URLs (
discord.gg/...,discord.com/invite/..., and internal page links), none of the raw ones carrying tracking — so Discord clicks from the docs went unattributed.Notes
spectralcompute.comis used for the copyright link: bothwww.and the old.co.ukredirect there, so this avoids a redirect hop, and it matches the privacy-policy link already in the footer.legal@line innotices.mdis Spectral's own sentence, immediately above where the NVIDIA license text begins. No third-party license body was touched.Verification
mkdocs build --strict: clean.docs/; the tracked URL exists in exactly one file.discord.com/invite/KNpgGbTc38— the same server as before.legal@spectralcompute.comis a live mailbox. The domain redirects fine on the web, but mail routing is separate, and a bouncing legal/trademark contact would be a bad failure.