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