Original working file
START-HERE.txt
Code and working example pages keep their original identifiers and sample text. The lesson and file guidance explain them in your language.
PRACTICAL ROUTE
Run a supplied email project with an assistant, send a controlled confirmation and verify its arrival in your inbox.
Your role: Provide private account values, trigger only your own tests and check actual delivery.
1. Use the supplied project and ask your coding assistant to carry out the implementation. You do not need to write HTML, JavaScript or SQL yourself.
2. Follow the current lesson steps, configure only your own permitted accounts and check the result in the actual page/provider.
3. Keep expected results and observed results separate. Record the exact blocked step if you cannot run a live check.
The detailed setup below is available to you and your assistant. Code explanations and extra implementation exercises are optional; important access/privacy checks are still part of the practical lesson.
--- REQUIRED SETUP (CODE READING IS OPTIONAL) ---
This is a separate practice project. public/ is the website folder; netlify/functions/ contains server-only functions. Install Node and Netlify CLI for local function testing, or deploy this project to your own Netlify account. Put real credentials in server environment variables, never in public/ or Git. No provider request runs just by opening these files. Account steps and real delivery must be checked in your own account.
Configure RESEND_API_KEY, MAIL_FROM, TEST_RECIPIENT and an unguessable LAB_TOKEN (at least 24 characters) on the server. Enter the practice code when testing; do not put it in the shipped JavaScript. Use a verified sender. The caller cannot choose the recipient. This small owner-only lab is not a public bulk-mail service; add durable abuse limits before opening it to untrusted traffic.
For exact local commands and private environment names, read run-locally.txt and server-env.example.txt.