The one sentence version
If your idea needs to remember something between visits, a static site will not do it.
That is the whole lesson. Everything below is the consequences. Sites builds static websites, which means the pages are the same for everyone and nothing is stored. There is no database and no server side logic. That is not a gap waiting to be filled in a future release, it is what the word static means.
What that rules out
User accounts. No sign up, no log in, no password, no member area. Logging in requires somewhere to keep who you are, and there is nowhere.
Payments. No checkout, no card details, no orders. Taking money requires a server you trust doing things you can verify, and a static page is neither.
Anything a visitor types being kept. This is the one that catches people, so it gets its own box below.
An admin area. No place for somebody else to sign in and update the content. If the text needs changing, you ask ChatGPT to change it, which means you, or somebody with access to your account.
Anything personalised. No welcome back, no saved preferences, no showing different things to different visitors.
The contact form trap. You can absolutely ask for a contact form, and you will get something that looks exactly like one. On a static site there is nothing behind it to receive what people send. A form that appears to work and quietly loses every enquiry is worse than no form at all, because your visitor believes they have got in touch and you never find out they tried. Put a real email address and a phone number on the page instead.
In plain English
- Backend:
- The part of a website that runs on a server: storing things, checking passwords, taking payments. Static sites do not have one.
- Database:
- Where a site keeps information so it is still there next time. Users, orders, messages, bookings.
- Server side:
- Work done on a computer somewhere else before the page reaches you. Static sites do none of it.
- Form handling:
- The machinery that receives what somebody types into a form and does something with it. This is the part a static site is missing.
The test to run on your own idea
Go through your idea sentence by sentence and underline every verb that implies memory: save, store, remember, log in, register, book, order, submit, track, update.
Every underlined word is either something you drop, something you move off the site, or a reason to use a different tool.
Here is what I want to build: [describe it in a few sentences].
Tell me which parts of this need to store information or
remember a visitor between visits, and which parts do not.
Be strict. If a part only works with a database or a login,
say so plainly rather than suggesting a workaround.
List every point in this idea where a visitor types something,
chooses something, or expects the site to know something about
them. For each one, say what would have to be stored somewhere
for it to actually work.
Assume no database, no logins and no way to receive form
submissions. Rewrite my idea as a static site that still
achieves the main goal. Tell me honestly what I lose, and
if the main goal is impossible without a backend, say that
instead of compromising.
โ Weak prompt
Prompt
Add a members area where my clients can log in and see their documents.
Output
A convincing looking sign in page with fields for an email address and a password, and a members page behind it.
It looks right and it protects nothing. There is no store of who your clients are and no server checking anything, so the page behind it is not actually private. A lock that does not lock is worse than an open door, because you will trust it.
โ Good prompt
Prompt
I want clients to reach their documents, but I know this is a static site with no logins. Give me a static alternative that achieves as much of that as possible, and tell me plainly what it cannot do.
Output
A suggestion such as a simple page explaining how documents are sent, with the files themselves delivered by email or through a tool built for the job, plus a clear statement that no part of the site is private.
You end up with something honest that works, and an accurate picture of where the real solution has to live.
Checkpoint
If any part of your idea has to remember something between visits, that part cannot live on a static site, and a form that looks like it works but stores nothing is the trap to watch for.
When to use something else
You need a backend. Logins, stored data, real form submissions. A standalone builder like Lovable can add those, and that course is free.
You need to take money. Use a platform built for selling, where somebody else is responsible for handling card details properly.
Somebody non-technical needs to edit it weekly. A content management system exists precisely so that people who did not build the site can change the words on it.
You are in the UK, the EEA or Switzerland. Sites is unavailable to you regardless of the plan you pay for, which is the flattest limit of all. The Lovable course has no such restriction.
None of this makes Sites a bad tool. It makes it a specific one. A tool that says clearly what it does not do is far easier to trust than one that quietly does it badly.
๐ Quiz
Question 1 of 4Why can a static site not have user logins?