[{"data":1,"prerenderedAt":288},["ShallowReactive",2],{"docs-nav-en":3,"landing-footer-friend-links":59,"docs-nav-zh":62,"docs-page-en-support-and-refund":98,"docs-page-zh-support-and-refund":203},[4,10,16,22,27,32,37,42,48,53],{"path":5,"title":6,"label":7,"description":8,"order":9},"/docs/introduction","web-nuxt template overview","Introduction","What the Nuxt template already ships today, and where to customize it.","1",{"path":11,"title":12,"label":13,"description":14,"order":15},"/docs/quick-start","Quick start for web-nuxt","Quick start","Go from first visit to live demo, dashboard activation, and launch-ready trust surfaces.","2",{"path":17,"title":18,"label":19,"description":20,"order":21},"/docs/billing-and-credits","Billing and credits","Billing","How pricing, credits, subscriptions, and order history fit together in the Nuxt template.","3",{"path":23,"title":24,"label":25,"description":26,"order":21},"/docs/skills-and-vibe-coding","Skills and vibe coding for web-nuxt","Skills & vibe coding","Use repo skills to customize apps/web-nuxt with prompt-driven edits instead of starting from a blank spec.",{"path":28,"title":29,"label":29,"description":30,"order":31},"/docs/auth-and-guest-mode","Auth and guest mode","Understand login, guest access, account conversion, and where each path should lead users.","4",{"path":33,"title":34,"label":34,"description":35,"order":36},"/docs/ai-playground","AI workspace","The user-facing Chat, Image Agent, Studio, and Usage surfaces in web-nuxt.","5",{"path":38,"title":39,"label":39,"description":40,"order":41},"/docs/support-and-refund","Support and refund","Where users should go for help, how refunds are handled, and what to expose on the public site.","6",{"path":43,"title":44,"label":45,"description":46,"order":47},"/docs/analytics","Analytics providers in web-nuxt","Analytics","Optional analytics support for GA4, Plausible, and Microsoft Clarity.","7",{"path":49,"title":50,"label":50,"description":51,"order":52},"/docs/footer-configuration","Footer configuration","Configure footer brand copy, contact email, social links, navigation columns, legal text, and copyright from zship.app.json.","8",{"path":54,"title":55,"label":56,"description":57,"order":58},"/docs/docs-system","How the built-in docs work","Docs system","The Nuxt Content docs setup inside web-nuxt and how to extend it.","9",{"code":60,"data":61},200,[],[63,67,71,74,78,81,84,87,91,94],{"path":5,"title":64,"label":65,"description":66,"order":9},"web-nuxt 模板概览","模板概览","说明 web-nuxt 当前已经具备什么，以及主要改动入口在哪里。",{"path":11,"title":68,"label":69,"description":70,"order":15},"web-nuxt 快速开始","快速开始","从首次访问到真实演示、仪表盘激活路径与对外发布前检查清单。",{"path":17,"title":72,"label":72,"description":73,"order":21},"计费与积分","说明定价、积分、订阅与订单历史在 Nuxt 模板中的关系。",{"path":23,"title":75,"label":76,"description":77,"order":21},"web-nuxt 的 Skills 与 vibe coding","Skills 与 vibe coding","通过 repo 里的 skills，用自然语言驱动方式修改和自定义 apps/web-nuxt。",{"path":28,"title":79,"label":79,"description":80,"order":31},"登录与访客模式","说明登录、访客访问、账户升级以及这些路径应该把用户带到哪里。",{"path":33,"title":82,"label":82,"description":83,"order":36},"AI 工作区","说明 web-nuxt 面向用户的 Chat、Image Agent、Studio 与 Usage 产品面。",{"path":38,"title":85,"label":85,"description":86,"order":41},"支持与退款","说明用户应该去哪里求助、退款如何处理，以及公开站点应暴露哪些信任入口。",{"path":43,"title":88,"label":89,"description":90,"order":47},"web-nuxt 的 Analytics 支持","数据分析","说明 web-nuxt 目前如何接入 GA4、Plausible 和 Clarity。",{"path":49,"title":92,"label":92,"description":93,"order":52},"Footer 配置","通过 zship.app.json 配置 Footer 的品牌文案、联系邮箱、社交链接、导航栏目、法律声明与版权信息。",{"path":54,"title":95,"label":96,"description":97,"order":58},"内置 Docs 系统说明","Docs 系统","说明 web-nuxt 当前基于 Nuxt Content 的站内文档能力，以及如何继续扩展。",{"id":99,"title":39,"body":100,"description":40,"extension":197,"label":39,"meta":198,"navigation":199,"order":41,"path":38,"seo":200,"stem":201,"__hash__":202},"docsEn/docs/support-and-refund.md",{"type":101,"value":102,"toc":189},"minimark",[103,107,112,125,129,150,154,157,168,172],[104,105,106],"p",{},"Support should be visible before a user gets stuck. In ZShip, support is part of the public trust surface and part of the signed-in product flow.",[108,109,111],"h2",{"id":110},"public-support-surfaces","Public support surfaces",[113,114,115,119,122],"ul",{},[116,117,118],"li",{},"Header navigation should expose a support entry",[116,120,121],{},"Footer should expose a contact email",[116,123,124],{},"Docs should explain refunds and help expectations in plain language",[108,126,128],{"id":127},"signed-in-support-surfaces","Signed-in support surfaces",[113,130,131,138,144],{},[116,132,133,137],{},[134,135,136],"code",{},"/dashboard/tickets"," for product and account help",[116,139,140,143],{},[134,141,142],{},"/dashboard/orders"," for purchase history and refund requests",[116,145,146,149],{},[134,147,148],{},"/dashboard/subscription"," for plan status before contacting support",[108,151,153],{"id":152},"refund-guidance","Refund guidance",[104,155,156],{},"Refund handling should be predictable:",[113,158,159,162,165],{},[116,160,161],{},"explain when users should request refunds",[116,163,164],{},"point them to the correct ticket flow",[116,166,167],{},"keep plan and order information easy to inspect before they contact you",[108,169,171],{"id":170},"what-to-customize-before-launch","What to customize before launch",[113,173,174,183,186],{},[116,175,176,179,180],{},[134,177,178],{},"contactEmail"," in ",[134,181,182],{},"zship.app.json",[116,184,185],{},"support copy in pricing, docs, and dashboard pages",[116,187,188],{},"internal process for ticket response times and refund review",{"title":190,"searchDepth":191,"depth":191,"links":192},"",2,[193,194,195,196],{"id":110,"depth":191,"text":111},{"id":127,"depth":191,"text":128},{"id":152,"depth":191,"text":153},{"id":170,"depth":191,"text":171},"md",{},true,{"title":39,"description":40},"docs/support-and-refund","-K-coSrTmPcYOal6UQLr_22qBWaNVobSx3T8Nl0GoPk",{"id":204,"title":85,"body":205,"description":86,"extension":197,"label":85,"meta":285,"navigation":199,"order":41,"path":38,"seo":286,"stem":201,"__hash__":287},"docsZh/docs/support-and-refund.md",{"type":101,"value":206,"toc":279},[207,210,213,224,227,244,247,250,261,264],[104,208,209],{},"支持入口应该在用户卡住之前就可见。在 ZShip 里，支持既属于公开站点的信任入口，也属于登录后的产品路径。",[108,211,212],{"id":212},"公开支持入口",[113,214,215,218,221],{},[116,216,217],{},"头部导航应该有 support 入口",[116,219,220],{},"footer 应该展示联系邮箱",[116,222,223],{},"docs 里要用清晰语言说明退款与帮助预期",[108,225,226],{"id":226},"登录后的支持入口",[113,228,229,234,239],{},[116,230,231,233],{},[134,232,136],{},"：产品与账户问题",[116,235,236,238],{},[134,237,142],{},"：购买记录与退款申请",[116,240,241,243],{},[134,242,148],{},"：联系支持前先自查套餐状态",[108,245,246],{"id":246},"关于退款",[104,248,249],{},"退款流程应当可预测：",[113,251,252,255,258],{},[116,253,254],{},"明确告诉用户什么情况下应申请退款",[116,256,257],{},"把他们引导到正确的工单流程",[116,259,260],{},"在联系支持前，让他们能先看到清晰的订单与套餐信息",[108,262,263],{"id":263},"上线前需要自定义的地方",[113,265,266,273,276],{},[116,267,268,270,271],{},[134,269,182],{}," 中的 ",[134,272,178],{},[116,274,275],{},"pricing、docs、dashboard 里的支持文案",[116,277,278],{},"团队内部对工单响应时间与退款审核标准的约定",{"title":190,"searchDepth":191,"depth":191,"links":280},[281,282,283,284],{"id":212,"depth":191,"text":212},{"id":226,"depth":191,"text":226},{"id":246,"depth":191,"text":246},{"id":263,"depth":191,"text":263},{},{"title":85,"description":86},"3zO5on0iw3yBHK1x0H6HAb57pK9Ejhi8ts5fB_4kgHI",1791531549899]