The Core Principle: One Job Per Site
The “spread too thin” fear is valid — but the antidote isn’t fewer sites, it’s clarity of purpose. Each site should have exactly one audience and one job:
| Site | Audience | Job | Update Frequency |
|---|---|---|---|
| aaron.kr | General / peers | Personal hub, blog, thought leadership (ancient scripts, talks, opinions) | Weekly/monthly |
| aaronsnowberger.com | HR / search committees | Static contact + bio card | Yearly at most |
| keytokorean.com | Korean learners | Language teaching + digital products | Seasonal |
| aaronkr-courses → courses.aaron.kr | Your students | Course materials, Arduino, Capstone, conference prep | Per semester |
| pailab.io | Academia / tenure committee | Research lab: papers, datasets, curriculum, tutorials | Monthly/semesterly |
| blog.naver.com/aaron_kr | Korean-speaking audience | Mirror of aaron.kr posts in Korean | Same as aaron.kr |
The critical insight: aaronsnowberger.com and the courses site should be near-zero maintenance. Once set up well, they just sit there and do their job. Your active energy goes to aaron.kr and physicalailab.org only.