[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-permissions-are-product-design-en":3,"blog-related-permissions-are-product-design-en":30,"blog-adjacent-permissions-are-product-design-en":60},{"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","Permission Design Is Product Design","Permissions are not a technical appendix. They decide what each person in the organisation can see and do.","\u003Cp>Permission discussions usually focus on role names: admin, supervisor, employee. What actually matters is the boundary detail: can a supervisor see a subordinate's salary, and who handles the approvals of an employee who left? None of that is a technical question.\u003C\u002Fp>\n\u003Ch2>Three questions only the business can answer\u003C\u002Fh2>\n\u003Cp>Who owns the data, and does historical ownership move when the responsible person changes?\u003C\u002Fp>\n\u003Cp>How is unauthorised access detected? The system must record it, not just assign blame later.\u003C\u002Fp>\n\u003Cp>What is the access request process, and does temporary access expire automatically?\u003C\u002Fp>\n\u003Ch2>Implementation advice\u003C\u002Fh2>\n\u003Cp>Name permission points after business actions rather than pages, so reorganisations do not require rebuilding screens.\u003C\u002Fp>\n\u003Cp>Default to least privilege with a request path for more, which is safer than opening everything and tightening later.\u003C\u002Fp>\n\u003Cp>Provide a visual permission editor so business administrators can maintain it without developers.\u003C\u002Fp>\n\u003Cp>Permission design translates organisational rules into enforceable control. Translate accurately and the system fits the business.\u003C\u002Fp>","","slate","佳益方圆团队","2026-08-28T13:52:00+08:00",1,false,[16,17,18],"Permissions","Product Design","Organisation",{"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","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb","blue","article",50,{},[31,42,51],{"id":28,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},"grading-requirement-confidence","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","indigo","2026-10-15T09:00:00+08:00",[38,39,40],"Requirements","Product","Risk",{"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":43,"title":44,"excerpt":45,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":46,"updatedAt":47,"readingMinutes":13,"featured":14,"tags":48,"category":50},"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[49,17],"Industry Products",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":52,"slug":53,"title":54,"excerpt":55,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":56,"updatedAt":56,"readingMinutes":13,"featured":14,"tags":57,"category":59},51,"mvp-boundary","Drawing the Boundary of an MVP","Minimum viable is not the fewest features; it is one complete business loop running end to end.","2026-10-03T10:13:00+08:00",[58,39,38],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":61,"next":77},{"id":62,"slug":63,"title":64,"excerpt":65,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":66,"updatedAt":66,"readingMinutes":13,"featured":14,"tags":67,"category":71},34,"nuxt-ssr-cache-strategy","Caching and First Paint in Nuxt SSR","Server rendering is not automatically fast. First paint depends on how requests are organised, not on the rendering mode.","2026-08-30T13:52:00+08:00",[68,69,70],"Nuxt","SSR","Performance",{"id":13,"parentId":21,"slug":72,"name":73,"description":74,"icon":75,"cover":9,"tone":26,"kind":27,"sortOrder":76,"count":21},"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60,{"id":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":82,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":87},6,"design-handoff-contract","From Design File to Design System: Three Agreements with Engineering","Inconsistent spacing, missing states and duplicated components are rarely attitude problems. They usually mean the team never wrote down shared agreements before handoff.","2026-08-28T10:00:00+08:00","2026-10-18T15:58:14.717+08:00",[85,86],"Design Systems","Team Collaboration",{"id":13,"parentId":21,"slug":72,"name":73,"description":74,"icon":75,"cover":9,"tone":26,"kind":27,"sortOrder":76,"count":21}]