Getting started
Ulika documentation
Learn how Ulika lets you edit and publish a website built with AI tools, while the code stays in your own GitHub repository.
Last updated
Ulika is a visual CMS for websites that were built with AI coding tools or by a developer. You open your real, live website in the Ulika editor, change the text, images, links and looks of what is already on the page, and press Publish. The code of the site never leaves your own GitHub repository.
These docs cover everything from connecting a first site to troubleshooting a failed build. Each page starts with a plain explanation and adds the technical detail underneath, so you can stop reading when you have what you need.
What Ulika is for#
Ulika is built for the moment after a site exists. A developer or an AI agent builds the site once. From then on, the people who own the content (marketing, owners, designers) can keep it fresh without opening a code editor and without asking a developer for every headline change.
What you can edit in the visual editor:
Text, such as headlines, paragraphs, buttons and labels.
Images.
Links.
Page SEO fields, such as the page title and description.
The look of elements, such as font, size, color, spacing and alignment.
Two things stay with you, not with Ulika:
Your code. It lives in your GitHub repository. Ulika adds a small connector through a pull request that you can read, and it never deletes anything or rewrites your Git history.
Your hosting. Your site is still built and served by your own host, such as Vercel or Netlify. Ulika asks your host to rebuild when you publish. It does not host your site.
How it works in one minute#
You give Ulika the address of your site and let it find the GitHub repository that builds it.
Ulika reads that repository (in memory, without storing your source code), finds the editable text, images and links, and prepares a small connector.
The connector arrives as a normal pull request. Once it is merged and your host has built it, the editor can open your live site and edit it in place.
When you click Publish, your site rebuilds with the new content.
The full picture is on How Ulika works.
Where to start#
| If you want to | Read |
|---|---|
| Understand the moving parts before you commit | How Ulika works |
| Check that your site and hosting are compatible | Requirements |
| Get from zero to a published edit as fast as possible | Quickstart |
| Connect a site from the browser | Connect from the dashboard |
| Connect a site from a terminal | Connect with the CLI |
| Let an AI agent connect your sites | Connect with AI agents |
Browse the documentation#
Getting started. How Ulika works, Requirements and the Quickstart.
Connect a site. The dashboard, the CLI and AI agents, plus what approving a connection means, how private previews are handled, and the GitHub App and Vercel connections.
Integrations. Short overviews of GitHub, Vercel, Netlify, Claude Code, Codex and MCP.
Editing. The editor, the style panel, sections and pages and mobile, autosave and drafts.
Publishing. Publish, history and failed builds.
Team. Roles and invitations.
Projects. Project settings and deleting a project.
Troubleshooting. Guides for connection problems, Vercel, GitHub, the CLI and the FAQ.
Security and privacy. The security overview.
CLI. The command reference and the changelog.
Was this page helpful?