[{"data":1,"prerenderedAt":348},["ShallowReactive",2],{"docs-nav-en":3,"docs-nav-zh":59,"docs-page-en-ai-playground":95,"docs-page-zh-ai-playground":231,"landing-footer-friend-links":345},[4,10,16,22,27,32,37,42,48,53],{"path":5,"title":6,"label":7,"description":8,"order":9},"\u002Fdocs\u002Fintroduction","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},"\u002Fdocs\u002Fquick-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},"\u002Fdocs\u002Fbilling-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},"\u002Fdocs\u002Fskills-and-vibe-coding","Skills and vibe coding for web-nuxt","Skills & vibe coding","Use repo skills to customize apps\u002Fweb-nuxt with prompt-driven edits instead of starting from a blank spec.",{"path":28,"title":29,"label":29,"description":30,"order":31},"\u002Fdocs\u002Fauth-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},"\u002Fdocs\u002Fai-playground","AI workspace","The user-facing Chat, Studio, and Usage surfaces in web-nuxt.","5",{"path":38,"title":39,"label":39,"description":40,"order":41},"\u002Fdocs\u002Fsupport-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},"\u002Fdocs\u002Fanalytics","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},"\u002Fdocs\u002Ffooter-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},"\u002Fdocs\u002Fdocs-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\u002Fweb-nuxt。",{"path":28,"title":76,"label":76,"description":77,"order":31},"登录与访客模式","说明登录、访客访问、账户升级以及这些路径应该把用户带到哪里。",{"path":33,"title":79,"label":79,"description":80,"order":36},"AI 工作区","说明 web-nuxt 面向用户的 Chat、Studio 与 Usage 产品面。",{"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":225,"label":34,"meta":226,"navigation":227,"order":36,"path":33,"seo":228,"stem":229,"__hash__":230},"docsEn\u002Fdocs\u002Fai-playground.md",{"type":98,"value":99,"toc":218},"minimark",[100,108,130,135,138,161,168,172,203,207],[101,102,103,107],"p",{},[104,105,106],"code",{},"web-nuxt"," exposes a complete AI workspace instead of routing every workflow into one playground:",[109,110,111,118,124],"ul",{},[112,113,114,117],"li",{},[104,115,116],{},"\u002Fdashboard\u002Fai-chat"," is the persistent conversational product surface, including history and multi-turn continuation.",[112,119,120,123],{},[104,121,122],{},"\u002Fdashboard\u002Fai-playground"," is AI Studio for image, video, audio, and other structured generation workflows.",[112,125,126,129],{},[104,127,128],{},"\u002Fdashboard\u002Fusage"," combines Chat and provider generation usage, including image, video, audio, requests, tokens, credits, daily activity, and model breakdown.",[131,132,134],"h2",{"id":133},"why-it-matters","Why it matters",[101,136,137],{},"All three surfaces share the same session lifecycle, so they already understand:",[109,139,140,143,146,149,152,155,158],{},[112,141,142],{},"auth state",[112,144,145],{},"guest sessions",[112,147,148],{},"available credits",[112,150,151],{},"API key lifecycle",[112,153,154],{},"conversation and generation history",[112,156,157],{},"provider-specific inputs",[112,159,160],{},"user-scoped usage and billing data",[101,162,163,164,167],{},"Site owners can keep the native Workers AI binding or configure any HTTPS OpenAI-compatible Base URL and API Key in the admin AI upstream settings. The credential remains server-side in ",[104,165,166],{},"node10-ai-service","; users only see enabled models, never the upstream key.",[131,169,171],{"id":170},"recommended-user-path","Recommended user path",[173,174,175,185,194,197],"ol",{},[112,176,177,178,181,182],{},"Start from ",[104,179,180],{},"\u002Fguest-demo"," or ",[104,183,184],{},"\u002Fdashboard",[112,186,187,188,190,191,193],{},"Open ",[104,189,116],{}," for conversational work or ",[104,192,122],{}," for generation",[112,195,196],{},"Continue previous conversations or create the first result",[112,198,199,200,202],{},"Review ",[104,201,128],{}," before upgrading to a full account or a higher plan",[131,204,206],{"id":205},"what-product-teams-should-avoid","What product teams should avoid",[109,208,209,212,215],{},[112,210,211],{},"Do not ask first-time users to paste a manual API key before they understand the product.",[112,213,214],{},"Do not collapse Chat and structured generation into competing interfaces; keep each entry point tied to a distinct job.",[112,216,217],{},"Do not separate credits, AI generation, and account state into unrelated pages without a guided default path.",{"title":219,"searchDepth":220,"depth":220,"links":221},"",2,[222,223,224],{"id":133,"depth":220,"text":134},{"id":170,"depth":220,"text":171},{"id":205,"depth":220,"text":206},"md",{},true,{"title":34,"description":35},"docs\u002Fai-playground","yL8iQ1gm3L6Nd3gbBNqbfL12Nfb5tf7NIGt1-bvW1Wo",{"id":232,"title":79,"body":233,"description":80,"extension":225,"label":79,"meta":342,"navigation":227,"order":36,"path":33,"seo":343,"stem":229,"__hash__":344},"docsZh\u002Fdocs\u002Fai-playground.md",{"type":98,"value":234,"toc":337},[235,240,257,260,263,286,292,295,323,326],[101,236,237,239],{},[104,238,106],{}," 现在提供完整的 AI 工作区，而不是把所有任务都导向一个 Playground：",[109,241,242,247,252],{},[112,243,244,246],{},[104,245,116],{}," 是正式的持久化对话产品面，支持历史记录与多轮续聊",[112,248,249,251],{},[104,250,122],{}," 是 AI 创作室，承载图像、视频、音频等结构化生成流程",[112,253,254,256],{},[104,255,128],{}," 合并对话与 Provider 生成用量，覆盖图片、视频、音频、请求、Token、积分、每日活动和模型明细",[131,258,259],{"id":259},"为什么要统一到这里",[101,261,262],{},"三个产品面共用同一套会话生命周期，因此都能理解：",[109,264,265,268,271,274,277,280,283],{},[112,266,267],{},"当前登录状态",[112,269,270],{},"访客会话",[112,272,273],{},"当前积分余额",[112,275,276],{},"API Key 生命周期",[112,278,279],{},"对话与生成记录",[112,281,282],{},"模型差异化输入",[112,284,285],{},"按用户隔离的用量与计费数据",[101,287,288,289,291],{},"站长可以继续使用原生 Workers AI Binding，也可以在管理端 AI 上游配置中填写任意 HTTPS OpenAI 兼容 Base URL 与 API Key。凭证只保存在 ",[104,290,166],{}," 服务端，用户只能看到已启用模型，不会接触上游密钥。",[131,293,294],{"id":294},"推荐的用户路径",[173,296,297,306,314,317],{},[112,298,299,300,302,303,305],{},"从 ",[104,301,180],{}," 或 ",[104,304,184],{}," 进入",[112,307,308,309,311,312],{},"对话任务进入 ",[104,310,116],{},"，生成任务进入 ",[104,313,122],{},[112,315,316],{},"继续历史对话或完成第一次生成",[112,318,319,320,322],{},"在 ",[104,321,128],{}," 查看消耗，再按需升级正式账户或更高套餐",[131,324,325],{"id":325},"产品上应避免的做法",[109,327,328,331,334],{},[112,329,330],{},"不要在用户还没理解产品前，就先要求他们粘贴手动 API Key",[112,332,333],{},"不要把 Chat 与结构化生成塞进语义重复的界面；每个入口应对应明确任务",[112,335,336],{},"不要把积分、AI 生成与账户状态拆成彼此孤立的页面，却又没有默认引导路径",{"title":219,"searchDepth":220,"depth":220,"links":338},[339,340,341],{"id":259,"depth":220,"text":259},{"id":294,"depth":220,"text":294},{"id":325,"depth":220,"text":325},{},{"title":79,"description":80},"getVUvnx8bc7stptdz8rkxONLnCJAGs-3nF2i-lo6uI",{"code":346,"data":347},200,[],1789925885775]