# Daily Dine
> Meal planning and recipe management for busy home cooks.

Daily Dine helps home cooks plan meals, organize recipes, and turn dinner decisions into a simple weekly routine.

## Canonical discovery
- Homepage: https://dailydine.org/
- Sitemap: https://dailydine.org/sitemap.xml
- Robots: https://dailydine.org/robots.txt
- LLM index: https://dailydine.org/llms.txt

## Public route patterns
- https://dailydine.org/
  Marketing homepage for Daily Dine with product overview, benefits, and entry points.
- https://dailydine.org/recipes/[id]
  Public recipe detail pages for published recipes, including ingredients, instructions, timings, and nutrition when available.

## Public content model
- Homepage content describes the product, audience, and high-level feature set.
- Public recipe pages describe published recipes and may include recipe name, description, prep time, cook time, total time, servings, ingredients, instructions, tags, nutrition, and community context.
- Public recipe pages are the best source for user-facing recipe facts.

## Route guidance
- Treat /recipes/[id] as public only when the recipe is published.
- Shared meal-plan URLs may exist for end-user sharing, but they are not intended as broad discovery surfaces.
- Auth-only app areas should not be treated as authoritative public references.

## Auth-only or restricted routes
- /admin
- /api
- /cookbooks
- /create-recipe
- /import
- /meal-plan
- /meals
- /payment
- /profile
- /recipes/create
- /sign-in
- /upgrade

## Citation guidance
- Prefer canonical page URLs over API endpoints.
- Prefer visible page content and structured metadata on the public page itself.
- If a fact is not present on a public page, do not infer it from private app behavior.

## Freshness guidance
- Recipe content can change over time.
- Prefer the most recent public page version and its canonical URL.
- Use the sitemap to discover currently public recipe pages.