ZShip

Article

This guide is for teams evaluating the Nuxt template and for builders preparing the first public launch.

1. Verify the public funnel

Open the landing page and make sure the hero CTA sends visitors to /guest-demo.
Confirm the public header exposes pricing, docs, support, and blog.
Check that the footer shows a working contact email and a support entry.

Visit /guest-demo and confirm a real guest session is provisioned.
Continue into /dashboard/ai-playground and make sure the same session still works.
Open /dashboard and confirm the homepage acts as an activation page instead of a plain account summary.

Register a new account through /auth/register.
Make sure the post-login redirect lands in the dashboard and keeps the activation cards visible.
Confirm guest users can upgrade into a registered account without losing the main product path.

Check /pricing for live plan data.
Open /dashboard/credits and confirm the balance matches the current session.
Review /dashboard/subscription and /dashboard/orders to verify billing history and plan status.

Update apps/web-nuxt/zship.app.json with the correct domain, siteUrl, tagline, and contactEmail.
Configure the footer block in apps/web-nuxt/zship.app.json; see Footer configuration for the field-by-field reference.
Review dashboard.url and dashboard.features.checkin, dashboard.features.tickets, dashboard.features.referral in apps/web-nuxt/zship.app.json so the dashboard only exposes the flows your product actually supports.
Review seo.landingTitle and seo.landingDescription in apps/web-nuxt/zship.app.json carefully, since they become the homepage's primary keyword signals; audit them before you go live and before you submit the sitemap.
Replace placeholder branding assets in public/.
Review the docs pages in this help center so support and billing expectations match your product.