Press slash to focus this field, or Escape to return home.
How do you use Lovable?
ToolsLovable is where a React idea gets to exist quickly: prototypes, and the host this very site runs on.
It is the fastest route I know from a thought to a working page with a database behind it. The output is a real repository, synced two ways with GitHub, so a prototype that earns it can be taken over and finished properly.
This site is a Lovable project, which makes it the honest test case. The pages you are reading are plain HTML files answered straight off the edge; the React application it generated never runs for any of them. That is a deliberate use of the platform as a host.
The editor understands the React side of a project. Static HTML sitting in the public directory is invisible to it, which is why the page work here happens locally, in the repository, by hand.
The rules I hold
Identify the stack before applying any rule
The platform changed its default stack on 13 May 2026, and several rules that are correct on one stack break the application on the other. The stack check comes before everything.
Push to main
Feature branches are invisible to the platform, so work on one silently diverges from what its editor believes the project to be.
A pushed commit is final
Force-pushing, rebasing or amending one rewrites history on the platform's side and can take project history with it.
Stage explicit paths, one at a time
The platform's own agent commits into the same repository. Staging blindly sweeps its work into mine.
Readable content goes in the HTML
Anything only assembled by JavaScript is invisible to the crawlers this whole site is built to satisfy.
The live address moves only on an explicit publish
The preview rebuilds asynchronously and can sit several commits behind main. Verifying against the wrong artifact is the easiest mistake here.
Every deploy waits for an explicit go
That holds for me and for any agent acting on my behalf.