Localization and interaction extend beyond the main content
I contributed to the renewal and maintenance of Bigtablet’s Korean and English company website, including company information, history, and recruitment content.
Error screens could retain Korean copy or display mismatched history content. Rapid year changes could also leave an earlier GSAP animation running against the new screen.
Align rendering, language, and interaction lifetimes
Keep static composition on the server
I removed the unnecessary client declaration from the main page’s static widget composition. The about page reads localized messages in a server component and validates the history structure with Zod instead of relying on a type assertion.
Translate failure and return paths
The next-intl messages cover errors, retries, and back-to-list actions across recruitment, blog, about, root error, and 404 pages. I also corrected multiline message rendering and news-image alternative text.
Clean up the animations an effect creates
History animations run inside a gsap.context scoped to the content element and revert on cleanup. This cleans up the created tweens as well as the animation frame when the year changes or the screen unmounts.
A reduced-motion hook is applied to scroll effects and the banner so interaction respects the user’s system preference.
Maintain the public delivery surface
I maintained metadata, sitemap and robots output, asset paths, localized links, and responsive behavior alongside build checks and deployment-branch changes.
Concrete changes to rendering, language, and motion
Static page composition moved to server rendering while interactive areas retained client behavior. Localization now includes error, retry, and return actions.
History animations clean up on transitions and support reduced-motion preferences. Public commits show the authored changes to these rendering and interaction boundaries.