[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-multilingual-product-costs-en":3,"blog-related-multilingual-product-costs-en":30,"blog-adjacent-multilingual-product-costs-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},64,"multilingual-product-costs","The Hidden Cost of a Multilingual Product","Translating the interface into English is only the beginning. The real cost sits in content, formats and business flows.","\u003Cp>When clients ask for an English version, they assume a language switcher is enough. Once work starts, interface copy turns out to be about thirty percent of the effort; the rest lives in content maintenance, formatting and process differences.\u003C\u002Fp>\n\u003Ch2>Three underestimated costs\u003C\u002Fh2>\n\u003Cp>Content translation: articles, product descriptions and help pages must be maintained in two sets and updated in sync.\u003C\u002Fp>\n\u003Cp>Format differences: dates, numbers, currency and address order all change by language. Hard-coded formats produce wrong output.\u003C\u002Fp>\n\u003Cp>Process differences: some regions require consent, invoice formats or tax fields that translation cannot solve.\u003C\u002Fp>\n\u003Ch2>How we handle it\u003C\u002Fh2>\n\u003Cp>All copy lives in language files rather than inside components, and missing translations fall back to the default language instead of showing blanks.\u003C\u002Fp>\n\u003Cp>Content supports field-level fallback: empty translations show the original, so editors can publish Chinese first and add English later.\u003C\u002Fp>\n\u003Cp>Language-related logic is centralised in one utility layer instead of conditionals scattered everywhere.\u003C\u002Fp>\n\u003Cp>Multilingual is a product capability, not a translation task. Design the structure early and adding a language later does not mean rebuilding.\u003C\u002Fp>","","slate","佳益方圆团队","2026-04-30T15:02:00+08:00",1,false,[16,17,18],"Multilingual","Product","i18n",{"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,41,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":40},"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,17,39],"Requirements","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":42,"title":43,"excerpt":44,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":45,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"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",[48,49],"Industry Products","Product Design",{"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,17,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":78},{"id":62,"slug":63,"title":64,"excerpt":65,"content":9,"cover":9,"tone":66,"author":11,"publishedAt":67,"updatedAt":67,"readingMinutes":13,"featured":14,"tags":68,"category":72},44,"file-storage-evolution","File Storage: From Local Disk to Object Storage","Attachment features start simple, until clients upload multi-gigabyte videos and ask for per-file permissions.","cyan","2026-05-02T15:02:00+08:00",[69,70,71],"Storage","Architecture","Files",{"id":13,"parentId":21,"slug":73,"name":74,"description":75,"icon":76,"cover":9,"tone":26,"kind":27,"sortOrder":77,"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":79,"slug":80,"title":81,"excerpt":82,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":88},84,"outsourcing-visibility","Retrospective: Visibility Beats Promises in Outsourcing","The vendor said nearly done every week, until a week before delivery revealed half the work was missing.","2026-04-28T15:02:00+08:00",[85,86,87],"Retrospective","Outsourcing","Delivery",{"id":89,"parentId":21,"slug":90,"name":91,"description":92,"icon":93,"cover":9,"tone":26,"kind":27,"sortOrder":94,"count":21},3,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",40]