Bay Area K Group
K-Night 2026
Designing and shipping the K-Night 2026 event website
Designing and shipping the K-Night 2026 event website
Role
Product Designer, Volunteer
Timeline
Jun - Sep 2026
Industry
Events & Community
Team
Media Team
Bay Area K Group
K-Night 2026
Designing and shipping the K-Night 2026 event website
Role
Product Designer, Volunteer
Timeline
Jun - Sep 2026
Industry
Events & Community
Team
Media Team
For K-Night 2026, I redesigned and launched the event website for a Bay Area Korean technology community gathering at the Computer History Museum. As speakers, schedules, sponsors, and ticket information continued to change leading up to the event, I focused on creating a responsive structure that kept essential information clear and easy to access across desktop and mobile.
For K-Night 2026, I redesigned and launched the event website for a Bay Area Korean technology community gathering at the Computer History Museum. As speakers, schedules, sponsors, and ticket information continued to change leading up to the event, I focused on creating a responsive structure that kept essential information clear and easy to access across desktop and mobile.
I designed the experience in Figma, supported implementation with Codex, and managed the live site through GitHub, allowing the website to evolve alongside the event. The final site became the primary digital touchpoint for 380 attendees, helping people navigate the event before and during the day while giving the organizing team a flexible system for ongoing updates.
I designed the experience in Figma, supported implementation with Codex, and managed the live site through GitHub, allowing the website to evolve alongside the event. The final site became the primary digital touchpoint for 380 attendees, helping people navigate the event before and during the day while giving the organizing team a flexible system for ongoing updates.
Reflection
01
Design for changing information
Event content changed until the last minute, so I learned to design structure first—not just individual screens. A clear content system made updates faster without breaking the experience.
02
Design through launch
Working across Figma, Codex, and GitHub made me more aware of how design decisions behave in a live product. I started thinking about responsiveness and maintainability earlier, not only after handoff.
03
Prioritize what people need in the moment
Designing for a live event taught me to consider not only what information people need, but when they need it. The experience had to surface what mattered quickly, especially when users were moving and making decisions in the moment.
01
Design for changing information
Event content changed until the last minute, so I learned to design structure first—not just individual screens. A clear content system made updates faster without breaking the experience.
02
Design through launch
Working across Figma, Codex, and GitHub made me more aware of how design decisions behave in a live product. I started thinking about responsiveness and maintainability earlier, not only after handoff.
03
Prioritize what people need in the moment
Designing for a live event taught me to consider not only what information people need, but when they need it. The experience had to surface what mattered quickly, especially when users were moving and making decisions in the moment.
