The moment a site needs a memory
The portfolio you built in lesson 4 has a contact form. Here is an uncomfortable question: where do the messages go?
Heads up: this lesson links to Lovable through an affiliate link, so LearnAI earns a commission if you subscribe. It costs you nothing extra, and it is what keeps these courses free. We tell you where these tools fall short too, including who should not use them.
If the site is nothing but pages, the honest answer is nowhere. The form looks real, the button says Send, and the enquiry evaporates. That is the exact point at which a website stops being a document and starts being an application, and it needs a behind-the-scenes part.
In plain English
- Front end:
- Everything the visitor sees and clicks. Pages, pictures, buttons. It forgets everything the moment the tab closes.
- Backend:
- The behind-the-scenes part that stores and remembers information, and does work the visitor never sees.
- Database:
- A spreadsheet your website can read from and write to on its own, at any hour, with no one opening a file.
- Authentication:
- Letting people sign up and log in with a password. The bouncer on the door, checking names against a list.
- Server side:
- Work done on a computer you control instead of on the visitor's device, so nobody can look at how it happens.
What the behind-the-scenes part actually does
Three jobs, in plain language.
It remembers. A database keeps information after the visitor closes the tab: enquiries, bookings, posts, uploaded photos.
It knows who is who. Signing up, logging in, staying logged in, seeing only your own things. The bouncer with the list.
It does the work visitors must not see. Anything happening on a visitor's own device can be picked apart by them. Sending an email, charging a card, using a secret key that unlocks another company's service: that has to happen on a computer you control.
Traditionally you assemble all of it yourself: rent the storage, decide what you are keeping, connect the pages to it, handle logins, hide your secret keys. It is where most first solo projects quietly die.
What Lovable Cloud does
Lovable Cloud is that whole layer, run for you and wired into your project automatically. Storage, logins, file uploads and the invisible work, all switched on when you ask for them in a message.
In practice you say "save contact form submissions and let me view them," and it happens: a place to keep them, the form connected to it, messages that stick around. You never decided a storage layout or copied a secret address between screens.
Cloud is not a separate product you have to learn separately. You still talk to it through the same message box, just with messages about information instead of layout.
Example one: a contact form that remembers
This is the smallest useful version of the whole idea, and it is the right first step.
Give this project a place to store information.
Store contact form submissions in a table called enquiries with these fields: name, email, event date, message, and the date and time it arrived.
When someone submits the form, save it, then replace the form with a confirmation message. If saving fails, show a clear error and keep everything the visitor typed.
A table is one sheet of that spreadsheet: each enquiry is a row, each field a column.
That last sentence matters more than it looks. Ask for the failure case explicitly or you will get a form that only behaves when everything goes right, which is not the situation you need it to behave in.
Then give yourself somewhere to read them:
Add a private page at /enquiries that lists all saved enquiries newest first, showing name, email, event date and message. Require someone to be logged in to see it, and do not link to it from the public menu.
That /enquiries bit is just an address on your own site, tacked on the end, like amaphoto.com/enquiries.
Checkpoint
Lovable Cloud provides the storage, the logins and the invisible work, so a form can actually keep what people send without you assembling any of it.
Example two: a members area
The other common jump is accounts. A photographer wants clients to log in and see their own gallery. A coach wants a members area behind a password.
Add sign up and log in with an email address and a password.
Visitors can sign up and log in. After logging in they land on a page at /account showing only the galleries belonging to their own account. Anyone who opens /account without being logged in gets sent to the login page.
Add a log out button in the header, visible only when someone is signed in.
Two habits will save you a lot of pain here.
Say who can see what, every single time. "Only their own galleries" is a security requirement, not a nicety. Leave it out and you can end up with a page that quietly fetches everybody's information and simply does not draw the other rows on screen. Not the same as keeping it private.
Test as a second person. Sign up a fresh account and confirm it cannot see the first account's things. Do this yourself. Do not assume.
Everything Lovable writes needs checking, layout included, but here the stakes are higher: a layout mistake looks bad, a permissions mistake shows one customer another customer's information. If your site will hold anything sensitive, get someone who knows security to look before you go live.
The billing bit, stated plainly
Cloud is billed by how much you use it, on top of your Lovable plan. It is not covered by your monthly credits. There is usually a small allowance to start you off, and beyond that you pay for what you store and how often it gets fetched.
For a portfolio collecting a handful of enquiries a month, this is small. For a site with real visitors and real data it is a cost that grows as you succeed, so watch it from the start rather than discovering it in month four. Building the feature costs credits too, so it is charged twice in a sense: once to build, then continuously to run.
None of this is a reason to avoid Cloud. It is a reason to know the number before you commit.
If you have finished the portfolio, giving that contact form a memory is the natural next hour of work.
Give your project a memory๐ Quiz
Question 1 of 4What happens to contact form submissions on a site that is nothing but pages?