Skip to main content

Center Website with v0 — Quick Guide

For whom: New editors, no programming knowledge needed.
Goal: A website preview in v0 that shows real data from the cockpit — and a package for IT to take it online.

Details: later v0 Website A-Z and Instructions for Copying.

What / Why / Who / Where​

WhatDesign website layout in v0; shops, news, colors come from the cockpit (public interface).
WhyOnce data in the cockpit — uniform everywhere (website, apps, later social).
WhoYou: v0 + texts + instructions. IT/Agency: GitHub, Vercel, live domain.
Where (cockpit)Center → Tab Website · Website Management → Frontend Channels (v0)
Where (v0)v0.dev (company account)

Checklist (in order)​

  • 1. Clarify access — Cockpit login, v0 account (company), note Center slug from IT/colleague
  • 2. Check cockpit (5 min.) — Center selected · Website active · at least a few shops/news published, if the page should not be empty
  • 3. Read v0 A-Z — Sections A-C: v0 Website A-Z → (account, terms, cockpit pre-check)
  • 4. Insert instructions — Copy parts A-J from v0 + Cockpit (How to) into v0 (Cockpit D = Workflow is mandatory). IT helps the first time.
  • 5. Enter slug in part A — replace HIER_SLUG_EINTRAGEN with your Center slug
  • 6. Describe website in v0 — Screenshots or text: “Bright homepage, shop tiles, news section …” — no made-up shop names (only cockpit data)
  • 7. Check preview — Are shops/news loading? If empty → fill in cockpit first, don’t invent in v0
  • 8. Hand over to IT — Code export / Vercel · Cockpit: Center Website → Frontend Channels (v0) (Navigation) · Go-Live DNS (IT)
Reminder

v0 = Appearance. Cockpit = Facts. Missing news can be created in the cockpit — v0 will then display them automatically.

How to test (without live domain)​

  1. Open v0-Preview — do you see logo/colors and lists?
  2. Create a test news in the cockpit, publish it, and update in v0 — does it appear?
  3. Ask IT: Is the API base correct (https://dashboard.cockpit-os.de or test URL)?

What you don't need on the first day​

TopicWhy to wait
Claude / MCPFor content in the cockpit — not for the first v0 draft → Claude later
Developer NavbarAPI contracts, MEC checklists — IT only
All 10 instructions at onceCore: A, B, C, D, E (+ J after the first deploy). F/G/H/I only if planning, multi-center, or signage topic

Next pages​

Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/content-creator-handbuch/onboarding-center-website-v0