写作Writing
当部署、数据和界面都足够好理解时，这套小产品栈才真正好用。A small product stack works best when deployment, data, and UI stay easy to reason about.
很多小产品不是败给野心，而是败给摩擦。所以我更喜欢一套能把关键运动部件都摊平给人看的技术栈。
| Layer | Choice | Why |
|---|---|---|
| UI | Next.js | 路由和服务端渲染默认值都很顺手 |
| Hosting | Vercel | 部署和预览都很干净 |
| Data | Supabase | 有足够结构，但不会一开始就堆太重 |
| Styling | Tailwind CSS | 迭代快，仪式感低 |
重点从来不是“选了哪套栈”，而是把发布路径做得足够无聊：
npm run lint npm run build npm run dev
对于大多数小产品，这已经够用了。任何额外复杂度，都应该先证明自己真的有必要。
Small products usually fail from friction, not ambition. So I like a stack that keeps the moving parts obvious.
| Layer | Choice | Why |
|---|---|---|
| UI | Next.js | Good routing and server rendering defaults |
| Hosting | Vercel | Clean deploys and previews |
| Data | Supabase | Enough structure without overbuilding |
| Styling | Tailwind CSS | Fast iteration, low ceremony |
The key is not the stack itself. It is keeping the release path boring:
pnpm lint pnpm build pnpm dev
That is enough for most small products. Anything more should earn its place.
和这篇笔记关联的项目与案例研究。Projects and case studies connected to this note.
项目Projects
一个兼顾图片叙事与可维护结构的作品集系统。A refined portfolio system that balances image-led presentation with maintainable structure.
为小型社区活动提供从策划、邀请到跟进的一条轻量工作流。A small-community event flow for planning sessions, invites, and follow-up without heavy admin overhead.
案例研究Case studies
一个以图片叙事为主、同时保持易维护的平静型作品集结构。A calm, image-led portfolio structure that still stays easy to maintain.
一个覆盖活动收集、提醒与跟进的轻量协调层。A small coordination layer for event intake, reminders, and follow-up.
和这个主题相邻的更多笔记。More notes close to this topic.
一个实用的 AI 工作环境：能起草、测试和发布，又不会把流程缠在一起。A practical setup for drafting, testing, and shipping AI work without letting the workflow get tangled.
怎样组织案例研究，才能证明判断力，而不只是展示结果。How to structure a case study so it proves judgment, not just output.
公共索引真正有用，往往不是因为页面多复杂，而是因为内容模型足够小、足够清楚、足够容易改。A public index gets more useful when the content model is small, explicit, and easy to revise.