Article

Quick start for web-sveltekit

Go from first visit to live demo, dashboard activation, and launch-ready trust surfaces.

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

1. Verify the public funnel

Open the landing page while signed out and make sure the hero CTA can send visitors to /guest-demo or /login.
Sign in and confirm the dashboard entry opens /dashboard.
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 (or /login).
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/orders surfaces and confirm balances match the current session.
Review subscription and order status after a sandbox checkout when pay-service is configured.

Update apps/web-sveltekit/zship.app.json with the correct domain, siteUrl, tagline, and contactEmail.
Configure the footer block in apps/web-sveltekit/zship.app.json; see Footer configuration for the field-by-field reference.
Review dashboard.url and dashboard.features.* in apps/web-sveltekit/zship.app.json so the dashboard only exposes the flows your product actually supports.
Review seo.landingTitle and seo.landingDescription in apps/web-sveltekit/zship.app.json carefully — they become the homepage's primary keyword signals; audit them before you go live and before you submit the sitemap.
Configure analytics.* only when you are ready; scripts stay unloaded until consent when the banner is enabled.
Replace placeholder branding assets in static/.
Run pnpm --filter @zship/web-sveltekit check and pnpm --filter @zship/web-sveltekit build before deploy.
Review the docs pages in this help center so support and billing expectations match your product.

pnpm --filter @zship/web-sveltekit dev

Default dev port is 4329.