Recipes and the Recipe Library
Audience: User, Org Admin, Support, Developer Related: Importing And Discovery · Editing And Cache · Sharing · Social Import · Ai Image Generation
The Recipe Library stores organization-scoped recipes captured from normal web pages, social sources, photos or screenshots, manual entry, shared recipes, and supported import formats. Users can search, filter, view, edit, share, rate, archive, restore, refresh, and assign recipes to meal plans or displays.
Recipe records are database-backed. Generated PDF, PNG, editable-content, thumbnail, and Made It artifacts remain managed cache or media files with database metadata.
Core user tasks
- Add a recipe from a URL, social source, image, manual entry, share, or supported import.
- Search and filter the Recipe Library.
- Edit recipe metadata, ingredients, instructions, units, notes, layout, and orientation.
- Build or refresh PDF and display cache artifacts.
- Share, plan, shop, assign, cook, rate, archive, restore, or delete a recipe according to dependencies and permissions.
More information
- Importing and Discovery — Add recipes from normal URLs, images, manual entry, discovery, and supported import formats.
- Social Recipe Import — Capture and review recipe evidence from supported social-media sources.
- Editing and Cache — Edit recipe content and manage PDFs, display images, thumbnails, and other cache artifacts.
- Recipe Sharing — Create and manage recipe share links, invitations, acceptance, expiration, and dependencies.
- AI Recipe Image Generation — Generate, review, accept, retain, and clean up AI-created recipe images.
Canonical Recipe Types
Recipe Type now uses one server-side taxonomy across Admin, Mobile, API Tester, social/AI extraction, and the Chrome Extension. Selection lists are sorted by the current display label so future localized labels can determine their natural order, with Other deliberately pinned to the bottom. The normalization design deliberately keeps Blackcap's established meal-period categories instead of adding overlapping synonyms such as Main, Main Course, Main Dish, and Entrée.
| Current type | Keep/Rename | Canonical type | Reason |
|---|---|---|---|
| Breakfast | Keep | Breakfast | Established and useful. |
| Lunch | Keep | Lunch | Established; avoids forcing lunch recipes into an Entrée synonym. |
| Dinner | Keep | Dinner | Established Blackcap default. |
| Side | Rename | Side Dish | Clearer requested terminology. |
| Snack | Keep | Snack | Distinct lightweight category. |
| Dessert | Keep | Dessert | Distinct established category. |
| Drink (legacy/API example) | Rename | Beverage | Broad category covers cocktails/mocktails without extra overlap. |
| — | Add | Appetizer | Requested and distinct. |
| — | Add | Salad | Broad, useful library category. |
| — | Add | Soup / Stew | Broad, useful library category. |
| — | Add | Sauce / Condiment | Covers sauces, dressings, marinades, dips/spreads without multiplying overlapping types. |
| — | Add | Bread / Baked Good | Useful broad baking category distinct from Dessert. |
| — | Add | Other | Explicit fallback for recipes outside the concise taxonomy. |
The canonical taxonomy defines the allowed values, not a permanent visible sort sequence. User-facing selectors sort by the current display label so localized labels can determine the natural order, while Other always remains last. AI/social structured extraction is constrained to the canonical values and the server validates new recipe writes. The compatibility migration maps historical Side to Side Dish and Drink to Beverage; it does not collapse unrelated existing categories silently.