Fursys website and admin

Context

I redesigned Fursys’s official site and its operations admin at the same time, in one monorepo. The site had to keep scrolling smooth despite dense interactions, and the admin had to let the operations team edit every area themselves, from product registration to documents and terms. Twenty-four backend APIs were not built yet, so I also designed a way to implement them ahead of the backend and switch over instantly, keeping them from blocking the site’s schedule. I took on the whole scope alone, within two months.

Decisions and implementation

• I made the site’s Parallax interactions animate only the sections in view and rely mainly on GPU-accelerated transforms, which spread the scroll load. For the store finder, I requested location permission only after the user tapped a call-to-action button, and built virtual scrolling, Kakao Maps clusters, and filters that could be shared by URL.
• In the admin, I built flows for the operations team to register and manage the product catalog and internal documents themselves. I limited the product detail builder to choosing and rearranging five templates (T1 to T5) instead of free assembly, which kept the catalog design consistent, and placed a preview beside the editing screen with undo and redo.
• I built the terms editor on Plate with version snapshots and rollback, and gave the news editor URL unfurling and an S3 proxy for og:image, so the operations team could edit on its own. I also set up a shared design system in the monorepo so the site and the admin used the same tokens and components.
• I implemented the 24 missing APIs ahead of time with MSW, so one environment variable switched between mocks and the real server, and wrote some of the needed APIs directly in the Java backend. AI agents drafted the repetitive implementation while I owned the design, contracts, and review, and that split kept the schedule.