Convert a Next.js site

Site Kit converts the rendered website's content model. It does not transplant React components, Tailwind classes, server actions, route handlers, or custom application state.

Workflow

1. Inventory public routes under app/ or pages/.
2. Open the rendered site and record the real navigation and content.
3. Create one SnabbSajt page per substantial public page.
4. Fold thin pages into sections when that makes the result simpler.
5. Map reusable components to built-in section types.
6. Copy only used public images into the package assets/ directory.
7. Replace custom actions with typed page, anchor, email, phone, booking, or lead targets.
8. Validate, pack, import, and review before publishing.

Route mapping

app/page.tsx              -> slug ""
app/services/page.tsx     -> slug "services"
app/about/page.tsx        -> slug "about"
app/contact/page.tsx      -> slug "contact"
app/api/**                -> not imported
app/dashboard/**          -> not imported

Dynamic routes need a product decision. A small set of real articles can become post pages. Authenticated dashboards, databases, or application routes do not belong in a SnabbSajt site package.

Component mapping

<Hero title="Accounting without the admin" image="/team.jpg" />
<ServiceGrid services={services} />
<Testimonials items={reviews} />

maps to hero, services, and testimonials. Component props become structured content. JSX and CSS do not enter the package.

Record unsupported calculators, custom commerce, complex embeds, and app-only flows instead of hiding them inside raw HTML.