feat: add old website button in header#74
Merged
SimplyPancake merged 3 commits intomainfrom Apr 13, 2026
Merged
Conversation
SimplyPancake
approved these changes
Apr 13, 2026
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
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.
Please describe what your PR is fixing
Concretely, which issues does your PR solve? (Please reference them by typing
Fixes/References Inter-Actief/amelink#<issue_id>)Closes #63
This is going to cause merge conflicts with #73 because, well, yarn gettext:extract or smth 😅
Does your PR change how we process personal data, impact our privacy document, or modify (one of) our data export(s)?
no
Does your PR include any updates of packages?
no
Does your PR include the proper translations (did you add translations for new/modified strings)?
If so, did you also run
yarn gettext:extract?yes, I have included the translations
Does your PR change routing?
no
Did your PR include a modification of the environment variables (and did you include the correct types in .env.d.ts ?)
yes
Did you properly test your PR before submitting it?
yes