Practical knowledge shared by store owners.
조회 128 · 좋아요 12 · 댓글 4Team Product · Monorepo · 2026
Jeomjuro
Keeping the consumer experience at the center while sharing admin and UI foundations
Built the store-owner consumer community as the primary product surface, with admin operations and a shared design system maintained in the same pnpm and Turborepo monorepo.
- 3 apps
- consumer · admin · storybook
- 4 packages
- api · config · design-system · test-utils
- Turborepo
- Build, test, and typecheck flow
Consumer and admin work needed one operating structure
Community, brand, profile, notification, and moderation features were growing inside one repository without clear boundaries between applications, shared UI, API clients, tests, Storybook, and delivery rules.
Rebuild the repository as a product monorepo
I moved the existing app into apps/consumer, added apps/admin and apps/storybook, and separated API, configuration, design-system, and test utilities into packages. pnpm workspace and Turborepo now coordinate builds, tests, and type checks.
Consumer tokens and flows were refined alongside admin authentication, moderation tables, search, filters, delete and restore actions, optimistic notification reads, Storybook, and CI.
One repository for the product and its operations
Consumer and operator experiences now evolve inside explicit app and package boundaries, with shared interface rules and repeatable verification from development through deployment.
Trace
Role
pnpm and Turborepo migration, consumer, admin and Storybook apps, shared API, design-system and test packages, notifications, and CI
Focus
Monorepo · Admin tools · Optimistic UI · Delivery
Stack
Next.js · React · TypeScript · TanStack Query · pnpm workspace · Turborepo · Storybook · Biome · Vitest · GitHub Actions · Vercel · Cloudflare OpenNext