This video shows the move from a blocked Wix workflow to a local static website with 214 HTML pages, GitHub and Netlify.
The interesting part is not only that the website was built in two days. The real shift was changing the working model: stop trying to operate a closed website builder through AI, and move to a local, versioned, inspectable structure.
Wix is not framed as useless. It was the wrong environment for this AI workflow. Browser control created friction, while Claude Code could work directly with files, structure, repeated page patterns and SEO metadata.
The result connects directly to the current site strategy: own the content on the domain, keep it bilingual, avoid tracking by default, and use GitHub plus Netlify as a simple, controllable publishing path.
| Aspect | In the video | Why it matters |
|---|---|---|
| Starting point | Wix website | A lot of effort, limited control for AI-assisted work |
| Failed attempt | AI browser control | The AI operates the interface but fights the system |
| Turning point | Build locally | Files, structure and repeated patterns become directly editable |
| Implementation | Claude Code | Pages, templates and responsive layouts come together faster |
| Hosting | GitHub + Netlify | Low recurring cost and clear deployment logic |
| Lesson | Control over builder lock-in | For AI-assisted sites, an open file structure can be stronger |
Not automatically. Wix can be fine for simple pages. When many structured pages, custom SEO logic and AI-assisted maintenance matter, a local static setup can be more flexible.
Every change is versioned and the live site follows the repository state. That is easier to audit than a visual builder where many changes are hard to trace.
You need technical judgment and careful checks. The video is not an autopilot story. It is a workflow where AI does work, while decisions remain controlled.
Static pages make metadata, internal links, schema and bilingual structure explicit. That is the basis for search engines and AI systems to reference the content cleanly.
There is no manual English subtitle track for this video. This page uses an editorial summary instead of publishing automatic captions as a transcript.
The opening explains why the old Wix site no longer matched the way Lukas wanted to work. The issue is control, speed and whether a builder becomes friction for AI-assisted maintenance.
Claude Code analyzes the existing site and makes the needed structure visible. A website frustration turns into an actual rebuild plan.
The attempt to edit Wix through browser control runs into practical friction. The AI can click, but the closed system remains hard to control.
The turning point is building locally. Instead of operating Wix, the AI works directly with files, which makes structure, repetition and control clearer.
Claude Code creates the first landing page quickly. The important part is not only speed, but that the result can be inspected and iterated locally.
The site scales into many static HTML pages. This is where repeatable structure matters, especially for bilingual pages and similar content patterns.
The final website is shown as a real site, not a mockup. Responsive layout, German and English pages and a clearer offer structure become visible.
GitHub and Netlify replace the monthly builder subscription. The benefit is not only price, but versioning and predictable publishing.
SEO and GEO are treated as part of the build process. Metadata, structure and machine-readable information are created with the site, not bolted on later.
The conclusion compares effort, cost and control with Wix. The new site is cheaper, easier to maintain and better suited to AI-assisted work.
I work 1:1 with freelancers, consultants, coaches and small teams on practical AI workflows, automation and custom tools. The first call is free and takes 15 minutes.
Book a free strategy call