Skip to main content

Studio

Studio is an interactive editing mode where you chat with the Kamu assistant and see changes in a live preview. It is the fastest way to make targeted updates — fix a sentence, swap a color, add a section — without waiting for a longer build cycle.

Studio differs from the regular Chat experience: you get a real-time preview and you publish the changes yourself when you are satisfied.

Starting a session

Launch Studio from the site overview page with the Studio button. Kamu spins up a temporary editing environment and loads the latest version of your site into it.

Once the session is ready (usually under a minute), you will see two panels:

  • Kamu panel: the chat with Kamu. Type what you want to change, and Kamu edits the site directly.
  • Preview: updates automatically after each change. You can navigate between pages in the preview just like a real visitor.

On a computer the panels sit side by side. On mobile the Kamu panel is pinned to the top of the screen and the preview sits below it — you can collapse and expand the Kamu panel as needed.

Preview tools

The preview toolbar has a few tools to help you verify the site looks and works well:

  • Mobile / Tablet / Desktop buttons switch the preview width so you can see how the page looks on different device sizes.
  • Lighthouse runs Google's Lighthouse audit against the production build of your site and reports scores for performance, accessibility, best practices, and SEO. If any score drops below 98, Kamu will automatically start fixing the detected issues.
  • Accessibility (axe) checks the site is usable with screen readers and keyboard navigation.
  • Links scans the production build for broken internal links.
  • Open in new tab opens the preview in its own tab, so you can use browser devtools (e.g. F12) for deeper inspection.
Lighthouse measures the production build

Lighthouse builds an optimized (minified, bundled) version of your site before measuring. The scores reflect what real visitors get, not the dev server with its extra development overhead.

Publishing

When you are happy with the changes, press Julkaise (Publish). In the publish dialog:

  1. Write a short description of the changes (Kamu suggests a default).
  2. Build always runs before publishing so a broken site never reaches production. You can also run Accessibility and Links checks from the same dialog.
  3. Press Julkaise — or, if a check failed, Julkaise silti (Publish anyway).

After publishing, the changes reach the live site in about 30 seconds. The publish confirmation includes a link to the public site so you can verify the result.

Ending a session

Studio sessions are temporary — they use resources in the background until you end them.

  • Jatka muokkausta (Continue editing): keep editing in the same session after a publish.
  • Päätä istunto (End session): shuts the editor down immediately.
Automatic shutdown

If a session is idle for more than 15 minutes, Kotisivukamu shuts it down automatically. You will see a warning around the 13-minute mark with a one-click option to keep the session alive. The automatic shutdown keeps resource use in check.

Example requests

  • "Make the homepage headline bigger and change the background to a darker blue"
  • "Add a new service to the list: Roof renovation, starting from €5000"
  • "Fix the phone number on the contact page: 040 123 4567"
  • "Swap the hero image on the front page for a lighter one and add a caption on top"
  • "Make the navigation more compact on mobile"

How Studio compares

FeatureStudioChatWhatsApp
Real-time previewYesNoNo
You control publishingYesNo (automatic)No (automatic)
Works on mobileYesYesYes
Built-in checks (Lighthouse, a11y)YesNoNo
Best forFast targeted editsBigger changes, bloggingOn-the-go edits