Esipher - AI Site to Theme Converter

Yes: https://youtu.be/aHOtMFkEVgc covers exporting from Lovable, building it with the Esipher Build template, and converting it here, start to finish.

No. The entire conversion pipeline - extraction, parsing, asset rewriting, theme generation, and installation - runs locally within your WordPress install.

Yes, under Esipher > Connected Projects. Connect your own GitHub account (you register a free GitHub OAuth App once and paste its Client ID/Secret in - no third-party broker, same "your account, your server" model as the rest of this plugin), then connect the GitHub repo your AI builder syncs to (e.g. GitHub sync from the Lovable or Bolt.new project menu). Esipher commits a small build workflow into that repo and registers a webhook; from then on, every push builds on GitHub and Esipher flags it as "Update ready"; an administrator clicks "Apply update" to download that build and update the theme - no export, no template repo, no manual artifact download. The incoming webhook only records that a build is ready: it can never install or activate anything by itself. A "Sync now" button triggers a rebuild without waiting for your next push. This is separate from, and doesn't replace, the manual ZIP-upload flow below.

Newer Lovable projects (built on TanStack Start) produce a server app by default, not static pages, so there is nothing for Esipher to import. Esipher checks this when you connect a project and tells you. Ask Lovable: "Enable static prerendering for every page in this TanStack Start project, so that npm run build outputs a static HTML file for each page. Use prerender: { enabled: true, crawlLinks: true } and list every page in the tanstackStart pages option in vite.config.ts. Do not change the design or content." When Lovable has synced the change to GitHub, click Sync now and then Apply update.

Esipher imports what your project's build produces. On newer Lovable projects (TanStack Start), a page only becomes a real WordPress page if the project pre-builds it: it has to be in the prerender "pages" list in vite.config.ts, or be linked from a page that is built. AI builders do not always add a new page to that list. After "Apply update", Esipher lists any page that exists in your project but was not built, for example "/contact". Then ask your AI builder: "Add this page to the prerender pages list in vite.config.ts so it is built as a static page", wait for it to sync to GitHub, and click Apply update again. Sites that are a single-page app (for example Lovable projects using React Router) do not create separate WordPress pages: their pages live inside the app and open at their own address.

Esipher converts a Vite build's finished output, not a project's raw, uncompiled source. If you exported straight from Lovable or Bolt.new and have never run a build on it, use the Esipher Build template: a free, one-click GitHub Actions workflow made for this. Open that page, click "Use this template" to get your own copy, upload your export's raw .zip to it, and a build runs automatically - no installs, no command line. Download the finished result from that run's Artifacts and upload it to Esipher instead of the original file. This template is the recommended path for Lovable and Bolt.new exports; StackBlitz (build in your own browser) is a general-purpose fallback for other builders' exports.