Where the data is kept
Bookings, orders and enquiries land in a space created with the app. There is nothing to sign up for.
What it is for
If you want to read back what a visitor left, it has to be written down somewhere. That somewhere is the database.
It is created together with the app. No separate account, no separate bill.
Think of one table as one spreadsheet. A row is one booking; a column is one field.
What you need
Nothing. You only have to say what you want to collect.
If the fields are unclear, copy the paper book or spreadsheet you use today. That is the most accurate source.
- Taking bookings — name, phone, date, number of people
- Taking enquiries — name, email, message
- Selling something — product, price, stock
The order to do it in
Write the fields in a sentence and send it. The builder makes the table and the form that writes to it.
Changing a field later is one more sentence. You do not open the table yourself.
How to check it worked
Enter one record in the preview. Reload the page. If it is still there, it is wired.
One of the nine pre-publish checks reads your data rules. If that check fails, publishing does not continue.
It also says what it found. Repeat that back and it gets fixed.
What it will not do
- Projects do not share a space. One project cannot read another project's data.
- A table you left open is open to everyone. Say who should be able to read it.
- Restoring goes back in code and data together. Anything a visitor left in between goes back too.
- Photos and documents do not go in here. Use file uploads.