[{"data":1,"prerenderedAt":305},["ShallowReactive",2],{"docs-nav-en":3,"docs-nav-zh":54,"docs-page-en-billing-and-credits":86,"docs-page-zh-billing-and-credits":206},[4,10,16,22,27,32,37,43,48],{"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":24,"description":25,"order":26},"/docs/auth-and-guest-mode","Auth and guest mode","Understand login, guest access, account conversion, and where each path should lead users.","4",{"path":28,"title":29,"label":29,"description":30,"order":31},"/docs/ai-playground","AI playground","The canonical AI entry in web-nuxt and how it relates to credits, keys, and guest access.","5",{"path":33,"title":34,"label":34,"description":35,"order":36},"/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":38,"title":39,"label":40,"description":41,"order":42},"/docs/analytics","Analytics providers in web-nuxt","Analytics","Optional analytics support for GA4, Plausible, and Microsoft Clarity.","7",{"path":44,"title":45,"label":45,"description":46,"order":47},"/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":49,"title":50,"label":51,"description":52,"order":53},"/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",[55,59,63,66,69,72,75,79,82],{"path":5,"title":56,"label":57,"description":58,"order":9},"web-nuxt 模板概览","模板概览","说明 web-nuxt 当前已经具备什么，以及主要改动入口在哪里。",{"path":11,"title":60,"label":61,"description":62,"order":15},"web-nuxt 快速开始","快速开始","从首次访问到真实演示、仪表盘激活路径与对外发布前检查清单。",{"path":17,"title":64,"label":64,"description":65,"order":21},"计费与积分","说明定价、积分、订阅与订单历史在 Nuxt 模板中的关系。",{"path":23,"title":67,"label":67,"description":68,"order":26},"登录与访客模式","说明登录、访客访问、账户升级以及这些路径应该把用户带到哪里。",{"path":28,"title":70,"label":70,"description":71,"order":31},"AI Playground","说明 web-nuxt 中统一 AI 入口与积分、API Key、访客会话之间的关系。",{"path":33,"title":73,"label":73,"description":74,"order":36},"支持与退款","说明用户应该去哪里求助、退款如何处理，以及公开站点应暴露哪些信任入口。",{"path":38,"title":76,"label":77,"description":78,"order":42},"web-nuxt 的 Analytics 支持","数据分析","说明 web-nuxt 目前如何接入 GA4、Plausible 和 Clarity。",{"path":44,"title":80,"label":80,"description":81,"order":47},"Footer 配置","通过 zship.app.json 配置 Footer 的品牌文案、联系邮箱、社交链接、导航栏目、法律声明与版权信息。",{"path":49,"title":83,"label":84,"description":85,"order":53},"内置 Docs 系统说明","Docs 系统","说明 web-nuxt 当前基于 Nuxt Content 的站内文档能力，以及如何继续扩展。",{"id":87,"title":18,"body":88,"description":20,"extension":200,"label":19,"meta":201,"navigation":202,"order":21,"path":17,"seo":203,"stem":204,"__hash__":205},"docsEn/docs/billing-and-credits.md",{"type":89,"value":90,"toc":188},"minimark",[91,95,100,129,133,148,152,166,170,175,178,182],[92,93,94],"p",{},"ZShip uses credits as the product-level spending unit and plans as the commercial packaging around those credits.",[96,97,99],"h2",{"id":98},"what-users-can-do","What users can do",[101,102,103,111,117,123],"ul",{},[104,105,106,107],"li",{},"Compare plans on ",[108,109,110],"code",{},"/pricing",[104,112,113,114],{},"Review current balance on ",[108,115,116],{},"/dashboard/credits",[104,118,119,120],{},"Inspect active subscription status on ",[108,121,122],{},"/dashboard/subscription",[104,124,125,126],{},"Review previous purchases on ",[108,127,128],{},"/dashboard/orders",[96,130,132],{"id":131},"how-the-flow-works","How the flow works",[134,135,136,139,142,145],"ol",{},[104,137,138],{},"The visitor chooses a plan on the pricing page.",[104,140,141],{},"Checkout is created through the pay-service proxy.",[104,143,144],{},"Successful payment updates subscription state and the credit ledger.",[104,146,147],{},"Dashboard pages read the latest balance and order records from the same backend state.",[96,149,151],{"id":150},"what-to-validate-before-launch","What to validate before launch",[101,153,154,157,160,163],{},[104,155,156],{},"Pricing labels and descriptions match the plans configured in the pay service.",[104,158,159],{},"Credit amounts are easy to understand from a user perspective.",[104,161,162],{},"Refund expectations are documented and linked from support.",[104,164,165],{},"The support team knows which cases should go through tickets versus payment provider portals.",[96,167,169],{"id":168},"common-launch-questions","Common launch questions",[171,172,174],"h3",{"id":173},"when-should-i-send-users-to-pricing","When should I send users to pricing?",[92,176,177],{},"Send users to pricing when they run out of credits, need a higher plan, or want to understand what each tier unlocks.",[171,179,181],{"id":180},"where-should-refund-requests-go","Where should refund requests go?",[92,183,184,185,187],{},"Use the support flow documented in ",[108,186,34],{},". The dashboard order history already exposes refund requests as a product-level action.",{"title":189,"searchDepth":190,"depth":190,"links":191},"",2,[192,193,194,195],{"id":98,"depth":190,"text":99},{"id":131,"depth":190,"text":132},{"id":150,"depth":190,"text":151},{"id":168,"depth":190,"text":169,"children":196},[197,199],{"id":173,"depth":198,"text":174},3,{"id":180,"depth":198,"text":181},"md",{},true,{"title":18,"description":20},"docs/billing-and-credits","kvoMcrbAYYAkYOZbghs9Qln_nRUoYaWk_PwVzwHRA4Y",{"id":207,"title":64,"body":208,"description":65,"extension":200,"label":64,"meta":302,"navigation":202,"order":21,"path":17,"seo":303,"stem":204,"__hash__":304},"docsZh/docs/billing-and-credits.md",{"type":89,"value":209,"toc":293},[210,213,216,239,242,256,259,273,276,280,283,287],[92,211,212],{},"ZShip 以前台的积分作为产品消耗单位，再用套餐和订阅来承载商业化。",[96,214,215],{"id":215},"用户能做什么",[101,217,218,224,229,234],{},[104,219,220,221,223],{},"在 ",[108,222,110],{}," 对比套餐",[104,225,220,226,228],{},[108,227,116],{}," 查看当前积分余额",[104,230,220,231,233],{},[108,232,122],{}," 查看订阅状态",[104,235,220,236,238],{},[108,237,128],{}," 查看购买记录",[96,240,241],{"id":241},"一次完整链路如何工作",[134,243,244,247,250,253],{},[104,245,246],{},"用户在定价页选择套餐",[104,248,249],{},"通过支付服务代理创建结账流程",[104,251,252],{},"支付成功后更新订阅状态与积分账本",[104,254,255],{},"仪表盘相关页面读取同一套后端数据并展示结果",[96,257,258],{"id":258},"上线前应重点确认",[101,260,261,264,267,270],{},[104,262,263],{},"套餐文案与支付后台配置保持一致",[104,265,266],{},"用户能清楚理解每个套餐对应多少积分",[104,268,269],{},"退款预期在支持文档中有明确说明",[104,271,272],{},"支持团队知道哪些问题走工单，哪些问题交给支付门户处理",[96,274,275],{"id":275},"常见产品决策",[171,277,279],{"id":278},"什么时候该把用户带去-pricing","什么时候该把用户带去 pricing？",[92,281,282],{},"当用户积分不足、套餐不匹配，或者需要先理解商业模式时，都应该把他们带到 pricing。",[171,284,286],{"id":285},"退款入口应该放在哪里","退款入口应该放在哪里？",[92,288,289,290,292],{},"建议统一走 ",[108,291,73],{}," 文档说明的路径。订单页已经提供了产品侧的退款申请动作。",{"title":189,"searchDepth":190,"depth":190,"links":294},[295,296,297,298],{"id":215,"depth":190,"text":215},{"id":241,"depth":190,"text":241},{"id":258,"depth":190,"text":258},{"id":275,"depth":190,"text":275,"children":299},[300,301],{"id":278,"depth":198,"text":279},{"id":285,"depth":198,"text":286},{},{"title":64,"description":65},"ourIIrZpOEvZ7fbh8tDtnP-nMU6Dpayq-8-EDLh7wA8",1777105304345]