Your first site
A seeded install gives you a site, a superadmin, an Administrators group and a root node — then you create your first real page in the Site Tree.
pnpm seed put four things in the database: one site row (its slug, domain, default locale and theme taken from kywi.config.ts), one superAdmin user, an Administrators group with that user in it, and a root content node — a published Home page. That's what you're looking at the first time you log in, not a blank install.
Where you land
The whole admin is one host page, and its sidebar is assembled per role rather than per site. There is no top-level "Content" item — the Site Tree is how every page is actually reached, from Home down. See Finding your way around the admin.
Creating the first real page
Add it from the Site Tree. Its slug is derived from the title once, at creation — that first save is the moment to set the slug you actually want, since renaming the title later never moves the page. See Shaping the site tree and Slugs, paths, and moving a page.
Giving it a layout
A page is regions of sections made of columns of modules, and you build that structure in the admin's Layout tab or directly on the page through the same editor — only the canvas differs. See Regions, sections, columns and modules, The Layout tab vs. Design on site, and Turning on edit mode.
Publishing
In coupled mode only
A published page renders publicly because the scaffold generated app/(site)/[[...slug]]/page.tsx — the file a headless or decoupled project doesn't have. In those two modes there is no public page to go and look at; the site exists as content and an API. See Coupled, headless, decoupled.
Before you run thisUsing the site MCP server.
Create a page titled "About" under the home page, give it a layout with a heading and a paragraph introducing the site, and publish it.What you should get
/about/, carrying a heading module and a text module — check it by visiting the path or asking the agent to report it back to you.