fix(core): update all `[...locale]` pages

chartgerink commented

2025-10-16 20:29:45 +00:00

Owner

The pages are being worked on continuously prior to (re)launch, and it is key to ensure everything is consistent. This issue tracks that work. All pages with .astro have to be updated.

The pages are being worked on continuously prior to (re)launch, and it is key to ensure everything is consistent. This issue tracks that work. All pages with `.astro` have to be updated.

chartgerink added this to the ResearchEquals 2.0 milestone

2026-01-05 07:33:48 +00:00

chartgerink added the

Future

label

2026-01-28 20:53:20 +00:00

chartgerink added the

PATCH

label

2026-04-21 07:05:56 +00:00

chartgerink referenced this issue

2026-04-22 06:35:27 +00:00

Explore whether we can refactor the [...local] pages into one set of pages #7

chartgerink commented

2026-04-22 07:46:52 +00:00

Author

Owner

So the option is to refactor the pages into components, which get passed the locale. Ideally, the duplication would not be necessary to begin with, and that would require all pages to redir to some locale (MDN does this too, for example). This would require testing middleware properly to always redir to the default if none is present, and that is a bit more of an undertaking.

To be continued...

So the option is to refactor the pages into components, which get passed the locale. Ideally, the duplication would not be necessary to begin with, and that would require all pages to redir to some locale (MDN does this too, for example). This would require testing middleware properly to always redir to the default if none is present, and that is a bit more of an undertaking. To be continued...

chartgerink commented

2026-04-22 10:33:53 +00:00

Author

Owner

Some items for me to keep track of:

Incorrect paths correctly route to a localized 404 page STATIC
Incorrect paths correctly route to a localized 404 page DYNAMIC (eg @username)
generally 404 response is handled elegantly (as is right now)
~~ensure links throughout the application are localized (OrganizationCard, Usercard for example)~~ -> #81
non-localized paths default to the default locale correclty
non-existing pages lead to 404 (e.g., /en/fdfasdfdsa does not lead to homepage)
click through test of all pages and actions

Some items for me to keep track of: - [x] Incorrect paths correctly route to a localized 404 page STATIC - [x] Incorrect paths correctly route to a localized 404 page DYNAMIC (eg @username) - [x] generally 404 response is handled elegantly (as is right now) - [ ] ~~ensure links throughout the application are localized (OrganizationCard, Usercard for example)~~ -> #81 - [x] non-localized paths default to the default locale correclty - [x] non-existing pages lead to 404 (e.g., `/en/fdfasdfdsa` does not lead to homepage) - [x] click through test of all pages and actions

chartgerink commented

2026-04-22 14:03:47 +00:00

Author

Owner