[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-search-in-admin-zh-CN":3,"blog-adjacent-search-in-admin-zh-CN":30,"blog-related-search-in-admin-zh-CN":64},{"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},69,"search-in-admin","后台搜索该怎么做","搜索框人人会放，真正难的是让搜索结果符合用户找数据的方式。","\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>","","slate","佳益方圆团队","2026-03-01T12:07: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":10,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},49,"log-writing-standards","日志规范：三个月后还能看懂","日志写给未来的同事看，也写给凌晨三点的自己看。结构化是底线。","2026-03-03T12:07:00+08:00",[38,39,40],"日志","规范","工程实践",{"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":26,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":57},29,"what-we-want-to-become","十年后想成为什么样的公司","不追求规模最大，希望成为本地最值得托付的技术团队。","2026-02-21T12:07:00+08:00",[54,55,56],"创业","战略","长期",{"id":58,"parentId":21,"slug":59,"name":60,"description":61,"icon":62,"cover":9,"tone":26,"kind":27,"sortOrder":63,"count":21},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,[65,76,85],{"id":28,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":69,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":75},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","indigo","2026-10-15T09:00:00+08:00",[72,73,74],"需求","产品方法","风险管理",{"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":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":69,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":20,"featured":14,"tags":82,"category":84},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[83,18],"行业产品",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":86,"slug":87,"title":88,"excerpt":89,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":90,"updatedAt":90,"readingMinutes":13,"featured":14,"tags":91,"category":93},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[92,73,72],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]