Deployment

This documentation app is a Next.js (App Router) project in the bstocks-docs folder. It is linked to the Vercel project bstocks-docs under the team nessaonsols-projects (project id prj_Fl8FzeJZGJ7ejKmDIBYq7g5sqW8z). Production traffic is served at https://docs.bstocker.finance (and also https://bstocker.finance / https://bstocks-docs.vercel.app).

App structure: src/app hosts routes — / redirects to /docs, /docs lists sections, /docs/[slug] renders each article from src/lib/docs.ts, and /api/chat powers the floating Docs Assistant. Components live under src/components/docs. Brand assets (for example logo-dark.svg) sit in public/. Framework is declared for Vercel in vercel.json (framework: nextjs).

Local development: from the bstocks-docs directory run npm install, then start the app with npm run dev (or, on Windows paths that contain &, node .\node_modules\next\dist\bin\next dev --port 3000). Open http://localhost:3000 — the home route redirects to /docs. Keep the original downloaded marketing HTML/assets in the parent folder; they are reference material and are not overwritten by the Next app.

Linking & deploy: authenticate with the Vercel CLI (npx vercel login), then vercel link --yes --scope nessaonsols-projects --project bstocks-docs. Preview: npx vercel --scope nessaonsols-projects. Production: npx vercel --prod --scope nessaonsols-projects. Production aliases include docs.bstocker.finance. Preview deployments get unique *.vercel.app URLs and do not replace production until you promote or redeploy with --prod.

Domain & DNS: bstocker.finance is registered on Vercel with Vercel nameservers (ns1.vercel-dns.com / ns2.vercel-dns.com). The subdomain docs.bstocker.finance was added to project bstocks-docs and verified as configured correctly. Because DNS is on Vercel, no external registrar A/CNAME records were required for the subdomain. If nameservers were third-party, you would typically add a CNAME for docs pointing at the Vercel DNS target shown in the dashboard.

Environment variables: AI Gateway is intended to authenticate via Vercel OIDC after link / vercel env pull (local .env.local may contain VERCEL_OIDC_TOKEN — never commit .env*). Optional override: AI_GATEWAY_API_KEY. The chat route uses model openai/gpt-5.4 through the AI SDK string model API (Gateway). If Production has no env/OIDC/gateway credits, the docs UI still works but /api/chat may error until Gateway access is configured for the project.

AI agent: DocsAssistant (client) uses useChat + DefaultChatTransport against POST /api/chat. The server streams with streamText and a system prompt grounded in DOCS_KNOWLEDGE_BASE from this same docs content — so new sections (including Deployment) automatically become assistant context after deploy.

Wallet keys (educational demo): A public address alone can receive funds; the private key authorizes spending. Publishing a private key means anyone who reads the page can fully control that wallet. The sample material in the box below is intentional for teaching — it is not a production deployer, treasury, or funded ops wallet.

Once you create a wallet as above you can create a test token — see Mintable Token Example in the box above.

• Project: bstocks-docs · Team: nessaonsols-projects · Live: https://docs.bstocker.finance
• Stack: Next.js App Router + Tailwind + Vercel AI SDK (/api/chat) + AI Gateway
• Local: npm install → next dev → http://localhost:3000/docs
• Preview: npx vercel --scope nessaonsols-projects
• Production: npx vercel --prod --scope nessaonsols-projects
• Domain: docs.bstocker.finance on Vercel DNS (subdomain of bstocker.finance)
• Env: VERCEL_OIDC_TOKEN (via vercel env pull) or AI_GATEWAY_API_KEY — do not commit secrets
• Educational wallet (boxed panel on this page) — treat as burned / teaching-only