[{"data":1,"prerenderedAt":280},["ShallowReactive",2],{"docs-nav-en":3,"docs-nav-zh":59,"docs-page-en-ai-playground":95,"docs-page-zh-ai-playground":195,"landing-footer-friend-links":277},[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":34,"body":97,"description":35,"extension":189,"label":34,"meta":190,"navigation":191,"order":36,"path":33,"seo":192,"stem":193,"__hash__":194},"docsEn/docs/ai-playground.md",{"type":98,"value":99,"toc":182},"minimark",[100,112,117,120,139,143,167,171],[101,102,103,107,108,111],"p",{},[104,105,106],"code",{},"/dashboard/ai-playground"," is the canonical AI entry point in ",[104,109,110],{},"web-nuxt",".",[113,114,116],"h2",{"id":115},"why-it-matters","Why it matters",[101,118,119],{},"The template previously had multiple AI paths. The recommended product flow is now to send users to the AI playground, because it already understands:",[121,122,123,127,130,133,136],"ul",{},[124,125,126],"li",{},"auth state",[124,128,129],{},"guest sessions",[124,131,132],{},"available credits",[124,134,135],{},"API key lifecycle",[124,137,138],{},"generation history and provider-specific inputs",[113,140,142],{"id":141},"recommended-user-path","Recommended user path",[144,145,146,156,161,164],"ol",{},[124,147,148,149,152,153],{},"Start from ",[104,150,151],{},"/guest-demo"," or ",[104,154,155],{},"/dashboard",[124,157,158,159],{},"Open ",[104,160,106],{},[124,162,163],{},"Generate the first result",[124,165,166],{},"Upgrade to a full account or a higher plan when usage grows",[113,168,170],{"id":169},"what-product-teams-should-avoid","What product teams should avoid",[121,172,173,176,179],{},[124,174,175],{},"Do not ask first-time users to paste a manual API key before they understand the product.",[124,177,178],{},"Do not expose multiple competing AI entry points unless each one has a clearly different audience.",[124,180,181],{},"Do not separate credits, AI generation, and account state into unrelated pages without a guided default path.",{"title":183,"searchDepth":184,"depth":184,"links":185},"",2,[186,187,188],{"id":115,"depth":184,"text":116},{"id":141,"depth":184,"text":142},{"id":169,"depth":184,"text":170},"md",{},true,{"title":34,"description":35},"docs/ai-playground","ye_Y6oJlTnPHcazhzvUWd-8j4H4Mz0141jjf953YkgI",{"id":196,"title":79,"body":197,"description":80,"extension":189,"label":79,"meta":274,"navigation":191,"order":36,"path":33,"seo":275,"stem":193,"__hash__":276},"docsZh/docs/ai-playground.md",{"type":98,"value":198,"toc":269},[199,207,210,213,230,233,255,258],[101,200,201,203,204,206],{},[104,202,106],{}," 现在是 ",[104,205,110],{}," 中统一的 AI 入口。",[113,208,209],{"id":209},"为什么要统一到这里",[101,211,212],{},"模板之前存在多条 AI 路径。现在推荐把用户统一带到 AI Playground，因为它已经理解：",[121,214,215,218,221,224,227],{},[124,216,217],{},"当前登录状态",[124,219,220],{},"访客会话",[124,222,223],{},"当前积分余额",[124,225,226],{},"API Key 生命周期",[124,228,229],{},"生成记录与模型差异化输入",[113,231,232],{"id":232},"推荐的用户路径",[144,234,235,244,249,252],{},[124,236,237,238,240,241,243],{},"从 ",[104,239,151],{}," 或 ",[104,242,155],{}," 进入",[124,245,246,247],{},"打开 ",[104,248,106],{},[124,250,251],{},"完成第一次生成",[124,253,254],{},"当使用增长时，再升级成正式账户或更高套餐",[113,256,257],{"id":257},"产品上应避免的做法",[121,259,260,263,266],{},[124,261,262],{},"不要在用户还没理解产品前，就先要求他们粘贴手动 API Key",[124,264,265],{},"不要同时暴露多条语义重复的 AI 入口，除非它们面向完全不同的人群",[124,267,268],{},"不要把积分、AI 生成与账户状态拆成彼此孤立的页面，却又没有默认引导路径",{"title":183,"searchDepth":184,"depth":184,"links":270},[271,272,273],{"id":209,"depth":184,"text":209},{"id":232,"depth":184,"text":232},{"id":257,"depth":184,"text":257},{},{"title":79,"description":80},"g4g9mZCPGWsNWLX-Qqn_-3N_Xgk5P8tTVxP3iD8nBXc",{"code":278,"data":279},200,[],1777195974407]