You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Non-Italian users are a very low percentage so there is no point in taking the language at every request and then rendering it. The performance is still very good but it is not a best practice considering that the site is in fact in Italian by default and can change client-side language if needed.
My proposal is to restore static generation on all pages except for the degree course page that requires ssr.
Pros:
Extremely high performance;
Improved SEO.
Cons:
international users searching for "network studentiunimi" on search engines would get the result in Italian.
To-do
Remove global SSR and use italian localization by default;
Dialog on client-side (first website visit) to suggest language change.
The text was updated successfully, but these errors were encountered:
Feature request: at runtime (client-side), read the Accept-Language header. If 'italian' is not accepted, show a banner in English to guide the user to change the site language.
Also, enable SSR on degree pages would be crazy too 🚀. Maybe with periodic (server-side) refreshing to address db updates.
Non-Italian users are a very low percentage so there is no point in taking the language at every request and then rendering it. The performance is still very good but it is not a best practice considering that the site is in fact in Italian by default and can change client-side language if needed.
My proposal is to restore static generation on all pages except for the degree course page that requires ssr.
Pros:
Cons:
To-do
The text was updated successfully, but these errors were encountered: