[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-permissions-are-product-design-zh-CN":3,"blog-adjacent-permissions-are-product-design-zh-CN":30,"blog-related-permissions-are-product-design-zh-CN":59},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":29},54,"permissions-are-product-design","权限设计其实是产品设计","权限不是技术附录，它决定了组织里每个人能看到什么、能做什么。","\u003Cp>项目里讨论权限时，通常只关注角色名称：管理员、主管、员工。但真正影响使用的是边界细节：主管能不能看到下属的薪资？员工离职后历史审批由谁处理？这些都不是技术问题。\u003C\u002Fp>\n\u003Ch2>三个必须由业务回答的问题\u003C\u002Fh2>\n\u003Cp>谁对数据负责？责任人变更时，历史数据的归属是否跟着变？\u003C\u002Fp>\n\u003Cp>越权访问如何被发现？系统需要留痕，而不是只在事后追责。\u003C\u002Fp>\n\u003Cp>权限申请流程是什么？临时授权到期后是否自动收回？\u003C\u002Fp>\n\u003Ch2>落地建议\u003C\u002Fh2>\n\u003Cp>权限点按业务动作命名，而不是按页面命名，这样组织调整时不必重做界面。\u003C\u002Fp>\n\u003Cp>默认最小权限，需要更多权限时走申请流程，比默认开放再收紧更安全。\u003C\u002Fp>\n\u003Cp>把权限配置做成可视化界面，让业务管理员自己维护，减少开发介入。\u003C\u002Fp>\n\u003Cp>权限设计的本质是把组织规则翻译成可执行的控制。翻译得准确，系统才真正贴合业务。\u003C\u002Fp>","","slate","佳益方圆团队","2026-08-28T13:52:00+08:00",1,false,[16,17,18],"权限","产品设计","组织",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},2,0,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","blue","article",50,{},{"previous":31,"next":47},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},34,"nuxt-ssr-cache-strategy","Nuxt SSR 的缓存与首屏速度","服务端渲染不等于快。首屏速度取决于数据请求的组织方式，而不是渲染模式本身。","2026-08-30T13:52:00+08:00",[38,39,40],"Nuxt","SSR","性能",{"id":13,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":26,"kind":27,"sortOrder":46,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":53,"updatedAt":54,"readingMinutes":13,"featured":14,"tags":55,"category":58},6,"design-handoff-contract","从设计稿到设计系统：和研发协作的三个约定","间距不一致、状态没覆盖、组件重复实现，往往不是态度问题，而是没有写下共同约定。","indigo","2026-08-28T10:00:00+08:00","2026-10-18T15:58:14.717+08:00",[56,57],"设计系统","团队协作",{"id":13,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":26,"kind":27,"sortOrder":46,"count":21},[60,70,79],{"id":28,"slug":61,"title":62,"excerpt":63,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":64,"updatedAt":64,"readingMinutes":13,"featured":14,"tags":65,"category":69},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","2026-10-15T09:00:00+08:00",[66,67,68],"需求","产品方法","风险管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":20,"slug":71,"title":72,"excerpt":73,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":74,"updatedAt":75,"readingMinutes":20,"featured":14,"tags":76,"category":78},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[77,17],"行业产品",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":80,"slug":81,"title":82,"excerpt":83,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":84,"updatedAt":84,"readingMinutes":13,"featured":14,"tags":85,"category":87},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[86,67,66],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]