Content
Featured cards
What people see first on Home: the carousel, the featured recipe and the collections.
Featured cards (Home's carousel: first card at the top; the featured recipe below is always first in the app unless a card shows the same recipe)
Featured recipe (the single recipe older app builds feature)
Changing this does not send a notification.
Collections (shelves at the top of For You, e.g. Thanksgiving favorites)
Drag a collection by its handle (⠿) to change the order they show in. The order is saved as you drop.
Send a notification
The test goes only to the accounts listed as TEST_EXTERNAL_IDS in the Worker. Leave title or message empty for the default wording. “Send to everyone” notifies every subscribed user.
Recently sent
Release notes (shown in the app's inbox)
It appears in everyone's inbox straight away, and stays there. Needs admin-setup-21.sql run once.
In the app's inbox (announcements and release notes)
App status
Turn the app off for everyone: it shows a "down for maintenance" screen the next time it opens or comes back to the foreground.
Leave a box empty to use the words shown in it. Changes show the next time the app opens or comes back to the foreground; "Save text" updates them without turning the app off or on.
App update
Send people on older builds to TestFlight. Soft: they can tap "Not now". Hard: the screen stays until they update. Needs admin-setup-14.sql.
Only builds that already contain this feature respond to it. Set the build only after it has finished processing in TestFlight.
Submissions from curators
Recipes your invited curators have sent in (their page is the curation site). Open one to read it, then approve it into the library or send it back with a note. Needs admin-setup-15.sql run once.
Messages from curators
Questions curators send from the "Contact us" part of their site. Open one to read it and reply: your reply reaches them in their notifications. Needs admin-setup-20.sql run once.
Curators
Only people listed here can submit. Adding someone here also creates their sign-in, so there is nothing to do in Supabase: send them the curation site address, their email and the password you chose. Needs the Worker set up (see the Worker's README).
Community switch
Pause the whole community, or only sharing, without releasing a new build. When it is off, the Community tab stays and shows the message below; the Home shelf, bylines and sharing are hidden. Reporting and deleting an account keep working. People see the change the next time the app opens or comes back to the foreground. Needs admin-setup-32.sql.
Leave a box empty to use the words shown in it.
Shared recipes
Recipes people share from the app. Nothing shows in the community feed until you approve it, except from people you have marked trusted (they go live at once; look at those afterwards). Needs admin-setup-29.sql.
Spotlight
What leads the Newest feed in the app. Leave it on Automatic and the app picks the cook of the week itself (whoever was cooked and posted most lately). Or choose the cook of the week and which of their recipes is the banner, or a recipe of the week, or switch it off. People see the change when they open or refresh the Community tab. Needs admin-setup-42.sql.
Live in the community
Every recipe that is live in the community right now, newest first, hidden ones too. Add to library keeps a recipe for good: it stops being tied to the person who shared it (so it stays if they remove it or delete their account), keeps its “Recipe by” credit, and leaves the Community feed, along with its yums and comments. Edit changes the live recipe; the app shows your changes the next time someone opens it, and the submission it came from is kept in step (admin-setup-40.sql), so pulling it back and approving again keeps your edits. Put back in review takes a recipe out of the app and returns it to Waiting for review, to edit or approve again. Add to library needs admin-setup-39.sql.
The shelf on Home
The "From the community" shelf is a collection, so you can move it, schedule it, hide it, and choose its recipes.
Reports
Anyone can report a community recipe. Three different reports hide it from the app until you decide.
Accounts
Find someone by their email (people who signed up with email) or by their name in the community. Then set a new password, sign them out everywhere, or delete the account. Deleting can't be undone: it removes their synced data, their pictures, everything they shared and their profile. Apple sign-ins have no password, so only sign out and delete apply to them.
People
Every recipe is reviewed unless you mark that person trusted. Trust is never automatic: only you can turn it on, and you can take it away at any time. Suspending hides everything they shared and stops them sharing.
Pending recipes
Drafts wait here and stay out of the app until you approve and publish them. Open one to edit it and add its photo, then approve.
AI recipes in the library
Every recipe made with AI is tagged, so a whole batch can come out in one click. Removing a batch deletes those recipes from the library for good (they disappear from the app on the next refresh). To look at them, select several and change or remove them together, open them in the Recipes tab.
Recipes
Library quality
Duplicates and thin recipes, found by looking at every recipe. Tap a count to see the list. Needs admin-setup-6.sql run once.
Insights
Usage (anonymous counts only: no names, accounts, searches or recipes)
Per day
Everything counted (tap one to chart it)
Counts are added up by the day (UTC). The change compares with the same number of days before. Your own test builds from Xcode are never counted.
For You
For You results (anonymous counts per shelf: no names, accounts or recipes)
How each shelf did: how often it was shown (once each time the app is opened), how often a recipe on it was opened, and what came of that: saved from the shelf, and cooked to the end (within a day of opening it from the shelf). Use it to compare two settings: put some people in an experiment (below) and look at the same shelf in each group. Needs admin-setup-43.sql.
For You tuning
The numbers behind the ranking, which the app downloads when it opens (people see a change the next time they open or refresh For You). Name only the numbers you want to change: the rest keep their defaults, and the app keeps every number inside a safe range. To compare two settings, add an experiment: a group of people (a percent of everyone) who get some numbers changed. Then read the results above.
The numbers and their defaults
Library labels
What the library holds, by cuisine and meal type, and how complete the recipes are. "Healthy" with no clear reason is the old catch-all for recipes no cuisine matched; Backend/tools/relabel-recipes.mjs takes it apart (and its --audit finds cuisines that were set wrongly long ago). Nearly every recipe carries one of eight stock photos, handed out at random; Backend/tools/match-photos.mjs finds real ones on Pexels. Needs admin-setup-43.sql and admin-setup-44.sql.