What is ReciGit?
ReciGit is a public beta recipe workspace for saving recipes, comparing changes, creating twists, and suggesting careful improvements.
FAQ
Short answers for cooks, recipe owners, and early testers.
ReciGit is a public beta recipe workspace for saving recipes, comparing changes, creating twists, and suggesting careful improvements.
A dish page is the shared workspace for one dish, such as Carbonara or Lasagna. It groups recipes, twists, cook reports, evidence, and curator notes so cooks can compare approaches instead of creating disconnected duplicates.
A recipe is the main workspace. A saved change records an improvement to that recipe. A twist is a different direction from another recipe, such as a new diet, technique, ingredient set, or goal.
Start with the closest dish page. If you only changed a timing note, step, or small ingredient detail, suggest a change on the nearest recipe. If your approach is genuinely different, add your take and describe what kind of recipe it is. If you cooked one, leave a cook report.
A suggestion is a proposed improvement to an existing recipe. Use it when the recipe is basically right, but a step, ingredient, timing note, or explanation could be better.
A cook report is a real test from someone who cooked or reviewed the recipe. Cook reports can include ratings, notes, changes, whether the cook would repeat it, and evidence photos.
New recipe creation starts with a dish page and shows the closest existing recipes before the editor opens. That gives cooks a chance to suggest a small change, cook and review the nearest recipe, or add a clearly different take instead of creating another copy.
The best recipe on a dish page should earn its place through real cooking evidence. ReciGit looks at cook reports, different cooks, useful photos, recent tests, ratings for taste and clarity, and curator context. Saves help people return to favorites, but they are not treated as quality votes.
Saves are lightweight interest signals, not quality votes. Cook reports include whether someone cooked the recipe, ratings for taste, clarity, repeatability, accuracy, notes about changes, and optional evidence photos. Rankings use cooked reports with a conservative prior so one perfect report or one weak save cannot dominate a dish page.
Not yet reviewed means no cooked report yet. Needs more cooks means early evidence exists but is thin. Cooked means at least one real cook. Repeated means multiple independent cooks. Community proven means strong repeated evidence with photos and high scores. Curator pick means a dish curator has added a note after review.
No. New experiments can be visible, but they stay in a lower-confidence state until real cooks submit reports.
The private review queue helps curators notice likely duplicates, stale recipes that need a fresh cook, suspicious reports, and evidence photos that may need a look. High-impact actions such as hiding content or marking duplicates are reviewed by protected admins and dish moderators.
Guests can read public recipes, dish pages, comparisons, and collections. Signed-in users can create recipes, twists, suggestions, collections, comments, and cook reports. Recipe owners can edit recipes, restore saved changes, and accept or reject suggestions. Curators keep dish pages clean by reviewing duplicates, notes, visibility, and evidence.
Public recipes and collections can be browsed by anyone. Private recipes and collections are intended to be visible only to their owner, with server-side Supabase policies enforcing access.
Recipe images and cook-report evidence photos use the Supabase recipe image bucket. Signed-in cooks can upload JPG, PNG, or WebP evidence photos, or attach an image URL.
No. Recipe content is user-generated and may contain mistakes. ReciGit does not guarantee nutrition, allergy, health, or food-safety accuracy.
Send feedback, bug reports, privacy questions, or deletion requests through the feedback page.
Send feedback