https://main.d3s11vys5486vu.amplifyapp.com/

Recipes: https://docs.google.com/spreadsheets/d/10ET148sQZWhNGN9odosCUUFr3-pceh4zSnLPEmcbyrw/edit#gid=0

1. Drop the image file into the images/ folder in this repo (commit + push it).
2. Add an Image column to the Google Sheet (if it doesn't exist yet) and put the filename (e.g. carbonara.jpg) in that column for the matching dish row.
3. The published CSV picks up the new column automatically — no code changes needed per photo.

If a filename is missing or wrong, the image is just hidden (no broken-image icon), so a typo won't break the page.

A Google Form feeds the same spreadsheet the site already reads from, for URLs you want to come back to and transcribe properly later.

Set up steps (one-time):

1. Create a form at forms.google.com titled something like "Save a Recipe Link."
2. Add fields: Dish name (Short answer, required), Source URL (Short answer, required — under the "..." menu choose Response validation -> Text -> URL to catch typos), Notes (Paragraph, optional).
3. In the form's "Responses" tab, click the green Sheets icon -> "Select existing spreadsheet" -> pick this recipe spreadsheet. Google Forms creates a new tab for responses automatically (e.g. "Form Responses 1") — rename that tab to Incoming so it's clear these are unprocessed entries, separate from the main recipe tab.
4. Click Send on the form, click the link icon, and copy the URL (optionally check "Shorten URL").
5. Paste that URL into SAVE_LINK_FORM_URL in js/renderer.js (already done for the current form; only needed if the form is recreated).
6. Test it: submit a dummy entry, confirm it lands in the Incoming tab, then click "+ Save a link for later" on the live site to confirm the link opens the form.

When you're ready to actually cook one of the saved links, transcribe it into the main recipe tab (with full Ingredients/Procedure/Image) and delete the row from Incoming.

In the Google Sheet, enter one ingredient per line within the Ingredients cell — type an ingredient, press Alt+Enter (Windows) or Option+Enter (Mac) to start a new line in the same cell, then the next ingredient, and so on. This is more flexible than comma-separating on one line, since each line can contain its own commas (e.g. 2 cups flour, sifted) without breaking anything.

Older rows written as a single comma-separated line (e.g. 2 eggs, 100g pancetta, 50g parmesan) still work — the site only switches to newline-splitting when it detects a line break in the cell — so there's no need to reformat existing recipes.

The Procedure cell works the same way: one step per line, or the older single-line format with steps separated by ; . Leading step numbers (1., 2)) are stripped either way.