What does SvelteKit add to Svelte?
Svelte builds the pieces people see and use. SvelteKit gives the project a way to turn files into pages, load information for those pages and run code on the server.
A class site could give each class its own address and add a booking page that receives the visitor’s request. You still decide what the form asks for and where a confirmed booking lives.
Where does a booking form send its information?
A SvelteKit form action receives the form on the server. It can check that the class exists and that a seat is still available before writing the booking to the data store you connected.
A normal HTML form can submit without browser JavaScript. You can add JavaScript later for a smoother response. Keep the seat and access checks on the server either way. If two visitors request the last seat, the storage operation needs a rule that permits only one confirmation.
What do you pay for and what can move?
SvelteKit’s source is available under its project license. Your running bill depends on the host and the services you connect, such as a database or email sender.
An adapter prepares your project for its host. An entirely generated site can be served as files. A page that runs a form action when the visitor submits it needs a host and adapter that can run the server code. When changing hosts, move your source and choose the new adapter. Check how your records, environment settings and messages move separately.
How can you rehearse one booking before deploying?
Draw the class page, the form handler and the place that saves a reservation. Use invented names and do the entire exercise on paper.
- Trace an available seatMark one seat open. Follow one submission to the handler, then to one saved reservation. Write the confirmation the visitor sees.
- Trace a conflictSend a second fictional request for the same seat. Write the response that lets the visitor choose another class, and leave the saved reservation unchanged.