System Requirements Document for le-petit-dejeuner

1. Introduction

This document defines the requirements for a premium, modern, high-converting, fully responsive restaurant website for Le Petit Dejeuner by LPD Café, located at 191 King St E, Toronto, ON M5A 1J5, Canada. The product intent is to present a real professional hospitality website — warm, premium, editorial, appetizing, trustworthy and conversion-focused — rather than a generic restaurant template. The audience is Toronto brunch culture: local diners, King East residents and weekend visitors who judge a restaurant by its photography and taste level and who book from a phone in the evening.

The site presents only facts supplied by the restaurant: the business identity, address, phone number, 4.3 ★ rating from 2,092 Google reviews, 20–30 CAD per person price range, Belgian-Canadian breakfast/brunch/restaurant positioning, the supplied French description, the supplied menu items, the supplied opening-hours schedules and the supplied authentic review excerpts. No prices, awards, chefs, founders, history, customer names, reviews or statistics may be invented.

2. System Overview

The product is a first-party, publicly accessible marketing and conversion website. Its current delivery is a set of seven application-owned pages: Home, Our Story, Menu, Reviews, Visit Us, Contact and Privacy Policy. All seven are public with no access requirement; no account, login or identity establishment is part of the accepted scope.

The Home page is the public entry surface and carries the full homepage sequence: Hero → Story → Menu → Food Gallery → Why Us → Reviews → Hours → Location → Contact → Final CTA → Footer. The Hero is a 90–100vh cinematic background video with a glassmorphic "Plan Your Visit" reservation card. The remaining pages carry the dedicated Menu, Our Story, Reviews, Contact and Privacy Policy responsibilities.

Accepted behavior includes: a sticky desktop navigation that is transparent over the hero and becomes semi-transparent and blurred on scroll; a mobile/tablet hamburger opening a full-height menu sliding from the right; a reservation request form (not an instant-confirmation booking system); a contact request form; a responsive opening-hours component with accordion/tabs on mobile; location actions that open the supplied Google Maps link and dial the supplied phone number; and a "Read More Reviews" action leading to Google.

Narrow exclusions: no booking API is assumed, so the reservation card is a request form and must not claim instant confirmation; no holiday hours may be invented; no prices may be shown unless known; no fabricated reviews, names, awards or statistics; no dead "#" buttons; no unsupported legal claims in the Privacy Policy.

2a. Product Interpretation and Delivery Boundary

The website is delivered entirely as first-party public web pages owned by the restaurant. Every accepted destination is anonymously reachable — there is no accepted requirement for accounts, sign-in, or private state, and none is inferred, because no accepted journey requires a diner to privately own or resume durable actor-specific state. Reservation and contact submissions are one-way requests from the visitor to the restaurant; the restaurant's response happens outside the website and is not modeled as a product capability.

Reservation handling is explicitly bounded: if no booking API is connected, the reservation card remains a request form and the site must not claim instant confirmation. The small text "Reservations are subject to availability." is part of the accepted interface. Directions and review continuation are owned by external destinations (the supplied Google Maps link and Google reviews), not by first-party pages. The Privacy Policy is presented as general website policy content suitable for review, without unsupported legal claims.

Everything in this document is current scope. No future-horizon features were accepted.

2b. Source Content Inventory

The following verified facts and media are supplied by the authoritative source and must be preserved exactly.

Business facts

• Name: Le Petit Dejeuner by LPD Café
• Address: 191 King St E, Toronto, ON M5A 1J5, Canada
• Phone: +1 416-703-1560
• Rating: 4.3 ★ from 2,092 Google reviews
• Price range: 20–30 CAD/person
• Category: Belgian-Canadian breakfast, brunch and restaurant
• Description: "Brasserie dotée de murs en brique servant toute la journée des plats belgo-canadiens réconfortants à base de produits de saison."
• Google Maps: https://www.google.com/maps/place/Le+Petit+Dejeuner+by+LPD+Caf%C3%A9/@43.65072,-98.8820078,5z/data=!4m11!1m3!2m2!1zQ2FuYWRhLCBjYWbDqQ!6e5!3m6!1s0x89d4cb308fb262e3:0x68137a388b2bee04!8m2!3d43.65072!4d-79.3702891
• Social: Facebook

Supplied menu items

• Signature features: Breakfast Crepe, Scrambled Eggs & Home Fries, Poached Egg & Hollandaise, Eggs Benny, Waffle Benny, Blueberry Pancakes with Scrambled Eggs, Croque Madame, Chicken Crêpe
• Also showcased: Latte, Cappuccino, French Toast, fresh juice
• Menu categories: Breakfast, Brunch, Eggs, Waffles, Pancakes, Crepes, French Toast, Comfort Food, Dinner, Desserts, Drinks

Supplied authentic review excerpts

• "Mention spéciale pour les jus et les fruits, très frais et bien présentés."
• "Très bon service avec des serveurs souriants et attentionnés."
• "Déjeuner délicieux ! Une carte où tout donne envie d’être dégusté."

Supplied opening hours

• REGULAR — Monday: 09:00–14:30; Tuesday: Closed; Wednesday: 09:00–14:30 / 17:00–23:00; Thursday: 09:00–14:30 / 17:00–23:00; Friday: 09:00–14:30 / 17:00–23:00; Saturday: 09:00–15:00; Sunday: 09:00–15:00
• BREAKFAST — Monday: 09:00–14:30; Tuesday: Closed; Wednesday–Friday: 09:00–14:30; Saturday–Sunday: 09:00–15:00
• BRUNCH — Monday: 09:00–14:30; Tuesday: Closed; Wednesday–Friday: 09:00–14:30; Saturday–Sunday: 09:00–15:00
• HAPPY HOURS — Wednesday–Friday: 17:00–21:00; Saturday–Tuesday: Closed
• DINNER — Wednesday–Friday: 17:00–23:00; Saturday–Tuesday: Closed

Supplied media references

• chat_media/18a38fa0-dcc0-487a-a8bf-ab687b8b3f15/245ddb52_unnamed__1_.jpg — LPD Café menu board; source for supplied menu items and inspiration for layout, spacing, typography and photography sophistication.
• chat_media/18a38fa0-dcc0-487a-a8bf-ab687b8b3f15/97a69d02_unnamed__3_.jpg — food photograph (crepe with sauce and slaw); supplied food imagery.
• chat_media/18a38fa0-dcc0-487a-a8bf-ab687b8b3f15/9c8e9062_unnamed__4_.jpg — food photograph (omelette with toast and slaw); supplied food imagery.
• chat_media/18a38fa0-dcc0-487a-a8bf-ab687b8b3f15/50875f41_unnamed__5_.jpg — food photograph (Eggs Benedict with hollandaise and hash browns); supplied food imagery.
• chat_media/18a38fa0-dcc0-487a-a8bf-ab687b8b3f15/facda64a_unnamed__6_.jpg — food photograph (Eggs Benedict with juice and water on a table); supplied food imagery.

Supplied SEO values

• Title: Le Petit Dejeuner by LPD Café | Breakfast & Brunch in Toronto
• Description: Le Petit Dejeuner by LPD Café serves Belgian-Canadian comfort food, breakfast, brunch and dinner at 191 King St E in Toronto.

2c. Page Content and Component Coverage

Home

• Information and state: Public entry surface. Hero occupies 90–100vh with a cinematic background video (coffee being poured, waffles, Eggs Benedict, pancakes, French toast, fresh ingredients, restaurant interior, guests enjoying brunch), a dark/warm overlay, and a poster/fallback image. Hero text: kicker "BREAKFAST • BRUNCH • DINNER", headline "Good mornings start here.", subcopy "Belgian-Canadian comfort food, seasonal ingredients, and all-day dining in the heart of Toronto." Trust row: 4.3 ★ and 2,092+ Google reviews. Below the hero, sections appear in the fixed order Hero → Story → Menu → Food Gallery → Why Us → Reviews → Hours → Location → Contact → Final CTA → Footer.
• Primary actions: "View Our Menu" (Menu page), "Reserve a Table" (reservation/contact section), "Get Directions" (supplied Google Maps link); "Request a Table" in the reservation card; "Discover Our Story" (Our Story page); "View Full Menu" (Menu page); "Plan Your Visit" (reservation/contact section); "Read More Reviews" (Reviews page / Google); "Get Directions" and "Call Us" (tel:+14167031560) in Location; "Send Request" in Contact; "View Menu" and "Reserve a Table" in Final CTA.
• Supporting actions: Sticky desktop nav (Logo | Home | Our Story | Menu | Reviews | Visit Us | Contact | Reserve a Table) with smooth anchor scrolling and logo linking Home; mobile/tablet hamburger opening a full-height right-sliding menu with large typography and a reservation CTA; footer Explore links (Home / Our Story / Menu / Reviews / Visit Us / Contact), Visit address, Contact phone, Facebook link, "© 2026 Le Petit Dejeuner by LPD Café. All rights reserved." and Privacy Policy link.
• Domain entities: Restaurant identity, address, phone, rating and review count, price range, menu items, opening-hours schedules, review excerpts, reservation request (Name, Email, Phone, Guests, Date, Preferred Time, Special Request), contact request (Name, Email, Phone, Guests, Date, Preferred Time, Message).
• Component responsibilities: Hero video component (autoplay, muted, loop, playsInline, cover, no controls, overlay, poster, mobile fallback, optimized/compressed); hero content stagger animation (opacity 0 + translateY 30px to visible, staggered); glassmorphic reservation card (5–10% white transparency, backdrop blur, thin border, subtle top glow and shadow; floating right on desktop, stacked on mobile) with title "Plan Your Visit", the seven fields, "Request a Table" button and small text "Reservations are subject to availability."; Story block with headline "Comfort food, made for slow mornings and good company.", the supplied copy and large restaurant photography; Signature Menu block with headline "Favourites worth waking up for." and each item showing image, name, short description and price only when known; editorial Food Gallery with smooth image reveals, clipping animations and subtle parallax plus the copy "Made fresh.", "Served with care.", "Built around good ingredients."; Why Us block with headline "More than breakfast." and pillars 01 Seasonal Ingredients, 02 Belgian-Canadian Comfort, 03 All-Day Experience, 04 Downtown Toronto (191 King St E); Reviews block with headline "Good food. Great company. Kind words.", 4.3 ★ / 2,092 Google reviews and only the supplied excerpts; responsive Hours component with accordion/tabs on mobile; Location block with headline "Find us in Toronto.", address, phone, "Get Directions" and "Call Us", falling back to a premium location card if map embedding is unavailable; Contact block with headline "Let's make your next visit delicious.", the seven fields, "Send Request" and the phone and address; Final CTA with an atmospheric restaurant image or video, headline "Your table is waiting.", the supplied copy and "View Menu" / "Reserve a Table"; Footer.
• States: Loading — hero video poster/fallback image displays before video is ready; images lazy-load. Empty — no empty state applies to static content; the reservation and contact forms present empty fields with accessible labels. Success — a submitted reservation request is acknowledged as a request subject to availability, never as an instant confirmation; a submitted contact request is acknowledged as sent. Error — form validation errors are shown inline with accessible labels; if the hero video cannot play, the poster/fallback image and mobile fallback remain. Recovery — the visitor can correct and resubmit a form; the visitor can still reach the Menu, Directions and Call actions if media fails.

Our Story

• Information and state: Dedicated page using only supplied facts. Carries the Story headline "Comfort food, made for slow mornings and good company." and the supplied copy "Le Petit Dejeuner by LPD Café brings Belgian-Canadian comfort food to Toronto, serving breakfast, brunch, and dinner with seasonal ingredients in a warm, relaxed setting.", with large restaurant photography. No founders, chefs, history or awards are presented.
• Primary actions: "Discover Our Story" destination from Home; navigation back to Home, Menu, Reviews, Visit Us and Contact.
• Supporting actions: Sticky nav and footer as on Home.
• Domain entities: Restaurant identity, supplied description, supplied copy.
• Component responsibilities: Editorial story layout with large restaurant photography; supplied description "Brasserie dotée de murs en brique servant toute la journée des plats belgo-canadiens réconfortants à base de produits de saison." where appropriate.
• States: Loading — images lazy-load with reveal treatment. Empty — not applicable. Success — page renders supplied facts only. Error — if an image fails, the text content remains complete. Recovery — navigation remains available.

Menu

• Information and state: Dedicated page organized by the supplied categories: Breakfast, Brunch, Eggs, Waffles, Pancakes, Crepes, French Toast, Comfort Food, Dinner, Desserts, Drinks. Uses supplied menu items only. Each item shows image, name, short description and price only when known.
• Primary actions: "View Full Menu" destination from Home; navigation back to Home, Our Story, Reviews, Visit Us and Contact.
• Supporting actions: Category navigation within the page; sticky nav and footer.
• Domain entities: Menu categories, menu items (Breakfast Crepe, Scrambled Eggs & Home Fries, Poached Egg & Hollandaise, Eggs Benny, Waffle Benny, Blueberry Pancakes with Scrambled Eggs, Croque Madame, Chicken Crêpe, Latte, Cappuccino, French Toast, fresh juice), item images, item names, item descriptions, prices only when known.
• Component responsibilities: Category sections; item rows or tiles with image, name, short description and optional price; no invented prices or items.
• States: Loading — item images lazy-load. Empty — a category with no supplied items is not populated with invented content. Success — supplied items render with known prices only. Error — missing item image degrades to a text-complete row. Recovery — category navigation remains usable.

Reviews

• Information and state: Dedicated page showing 4.3 rating, 2,092 reviews and only the authentic supplied excerpts: "Mention spéciale pour les jus et les fruits, très frais et bien présentés.", "Très bon service avec des serveurs souriants et attentionnés.", "Déjeuner délicieux ! Une carte où tout donne envie d’être dégusté."
• Primary actions: "Read More Reviews" leading to Reviews/Google; navigation back to Home, Our Story, Menu, Visit Us and Contact.
• Supporting actions: Sticky nav and footer.
• Domain entities: Rating 4.3 ★, review count 2,092, supplied excerpts.
• Component responsibilities: Rating summary block; excerpt list; no fabricated reviews, names, awards or statistics.
• States: Loading — static content renders immediately. Empty — not applicable; supplied excerpts are always present. Success — rating, count and excerpts display exactly as supplied. Error — if the external Google link is unavailable, the page content remains complete. Recovery — navigation remains available.

Visit Us

• Information and state: Dedicated page carrying the Location and Hours responsibilities: headline "Find us in Toronto.", address 191 King St E, Toronto, ON M5A 1J5, Canada, phone +1 416-703-1560, and the responsive hours component with REGULAR, BREAKFAST, BRUNCH, HAPPY HOURS and DINNER schedules exactly as supplied. No holiday hours are invented.
• Primary actions: "Get Directions" → supplied Google Maps link; "Call Us" → tel:+14167031560; navigation back to Home, Our Story, Menu, Reviews and Contact.
• Supporting actions: Accordion/tabs on mobile for hours; sticky nav and footer.
• Domain entities: Address, phone, Google Maps URL, five hours schedules.
• Component responsibilities: Location block with premium location card fallback if map embedding is unavailable; hours component with tabular numerals and accordion/tabs on mobile.
• States: Loading — map embed, if used, loads progressively with the location card visible meanwhile. Empty — not applicable. Success — address, phone, directions, call and all five schedules display exactly as supplied. Error — if map embedding is unavailable, the premium location card is shown. Recovery — directions and call actions remain available.

Contact

• Information and state: Dedicated page with headline "Let's make your next visit delicious.", form fields Name, Email, Phone, Guests, Date, Preferred Time, Message, button "Send Request", and the displayed phone and address.
• Primary actions: "Send Request"; navigation back to Home, Our Story, Menu, Reviews and Visit Us.
• Supporting actions: Sticky nav and footer.
• Domain entities: Contact request fields, phone, address.
• Component responsibilities: Accessible labeled form; inline validation; submission acknowledgement.
• States: Loading — form renders immediately. Empty — empty fields with accessible labels. Success — request acknowledged as sent. Error — inline validation errors with accessible labels. Recovery — the visitor can correct and resubmit.

Privacy Policy

• Information and state: Clean, ad-safe page containing Information Collected, Use of Information, Contact/Reservation Requests, Cookies & Analytics, Third Parties, Retention, Security, User Rights, Children's Privacy and Policy Updates, and including exactly "Last updated: September 2026." Presented as general website policy content suitable for review, without unsupported legal claims.
• Primary actions: Navigation back to Home, Our Story, Menu, Reviews, Visit Us and Contact.
• Supporting actions: Sticky nav and footer.
• Domain entities: Policy sections, update line.
• Component responsibilities: Sectioned policy content with readable typography.
• States: Loading — static content renders immediately. Empty — not applicable. Success — all ten sections and the exact update line display. Error — not applicable. Recovery — navigation remains available.

3. Functional Requirements

FR-1 — Premium responsive restaurant website (explicit) As a Prospective Diner, I should experience a premium, modern, high-converting, fully responsive restaurant website for Le Petit Dejeuner by LPD Café that feels like a real professional hospitality website rather than a generic template.

• Trigger/input: visiting the site on mobile portrait/landscape, tablet or desktop.
• Observable result: the site renders as a warm, premium, editorial, appetizing, trustworthy and conversion-focused hospitality site with no horizontal overflow.
• Access state: public, no access requirement.
• Failure/recovery: if a viewport-specific layout fails, content remains readable and controls remain touch-friendly.
• Continuation: the visitor proceeds to the Menu, reservation, directions or call actions.

FR-2 — Reference-image-informed original design (explicit) As a Prospective Diner, I should see an original design informed by the attached reference images for layout, spacing, typography, photography and sophistication.

• Trigger/input: page render.
• Observable result: layout, spacing, typography and photography sophistication reflect the references while remaining an original design.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues browsing.

FR-3 — Business facts presentation (explicit) As a Prospective Diner, I should see the business facts: Le Petit Dejeuner by LPD Café, 191 King St E, Toronto, ON M5A 1J5, Canada; +1 416-703-1560; 4.3 ★ from 2,092 Google reviews; 20–30 CAD/person; Belgian-Canadian breakfast, brunch and restaurant.

• Trigger/input: page render.
• Observable result: the facts appear exactly as supplied.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor uses the facts to decide to visit.

FR-4 — Supplied description (explicit) As a Prospective Diner, I should see the supplied description "Brasserie dotée de murs en brique servant toute la journée des plats belgo-canadiens réconfortants à base de produits de saison."

• Trigger/input: page render.
• Observable result: the description appears exactly as supplied.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues to the Story or Menu.

FR-5 — Warm premium Toronto brasserie aesthetic (explicit) As a Prospective Diner, I should experience a warm, premium Toronto brasserie aesthetic combining boutique café, European editorial design and high-end food photography.

• Trigger/input: page render.
• Observable result: the aesthetic is applied consistently across pages.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues browsing.

FR-6 — Specified colors (explicit) As a Prospective Diner, I should see the specified colors used: Deep Espresso #241A17, Cream #F7F1E8, Terracotta #B76545, Muted Gold #C7A46A, Charcoal #151210, White #FFFDF9.

• Trigger/input: page render.
• Observable result: the palette is applied as specified.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues browsing.

FR-7 — Specified typography (explicit) As a Prospective Diner, I should see elegant serif headlines (Playfair Display/Cormorant Garamond) with modern sans-serif UI/body (Inter/Manrope).

• Trigger/input: page render.
• Observable result: headline and body typefaces match the specification.
• Access state: public.
• Failure/recovery: if a font fails to load, text remains readable.
• Continuation: the visitor continues browsing.

FR-8 — Whitespace, typography, borders, photography, gradients (explicit) As a Prospective Diner, I should see generous whitespace, sophisticated typography, subtle borders/shadows, premium photography and tasteful gradients, with no generic templates, excessive cards, neon colors, clutter or gimmicky animation.

• Trigger/input: page render.
• Observable result: the listed qualities are present and the listed anti-patterns are absent.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues browsing.

FR-9 — Sticky desktop navigation (explicit) As a Prospective Diner, I should use a sticky desktop nav ordered Logo | Home | Our Story | Menu | Reviews | Visit Us | Contact | Reserve a Table, transparent over the hero and semi-transparent with a blurred background on scroll, where the logo links Home and main links smoothly scroll to sections or dedicated pages where appropriate.

• Trigger/input: scrolling past the hero; clicking a nav item.
• Observable result: the nav transitions from transparent to semi-transparent blurred; the selected destination opens or the section scrolls into view.
• Access state: public.
• Failure/recovery: if smooth scrolling is unavailable, the destination still resolves.
• Continuation: the visitor continues from the destination.

FR-10 — Mobile/tablet navigation (explicit) As a Prospective Diner, I should open a hamburger that reveals a full-height menu sliding from the right with smooth animation, large typography and a reservation CTA, with no horizontal overflow.

• Trigger/input: tapping the hamburger.
• Observable result: the full-height menu slides in from the right with large typography and a reservation CTA; no horizontal overflow occurs.
• Access state: public.
• Failure/recovery: the menu remains keyboard-accessible and dismissible.
• Continuation: the visitor selects a destination or the reservation CTA.

FR-11 — Cinematic fullscreen hero video (explicit) As a Prospective Diner, I should see a 90–100vh hero with a cinematic background video — not a static image — showing coffee being poured, waffles, Eggs Benedict, pancakes, French toast, fresh ingredients, restaurant interior and guests enjoying brunch.

• Trigger/input: page load.
• Observable result: the hero occupies 90–100vh and plays the cinematic background video.
• Access state: public.
• Failure/recovery: the poster/fallback image and mobile fallback display if video cannot play.
• Continuation: the visitor reads the hero content and acts.

FR-12 — Hero video attributes (explicit) As a Prospective Diner, I should see the hero video autoplay, muted, loop, playsInline, cover, with no controls, a dark/warm overlay, a poster/fallback image, a mobile fallback and optimized/compressed media.

• Trigger/input: page load.
• Observable result: the video plays with the specified attributes and overlay; the poster and mobile fallback are present.
• Access state: public.
• Failure/recovery: the poster/fallback image and mobile fallback cover video failure.
• Continuation: the visitor continues to hero actions.

FR-13 — Hero text (explicit) As a Prospective Diner, I should see the hero text "BREAKFAST • BRUNCH • DINNER", the headline "Good mornings start here." and the subcopy "Belgian-Canadian comfort food, seasonal ingredients, and all-day dining in the heart of Toronto."

• Trigger/input: page load.
• Observable result: the kicker, headline and subcopy display exactly as supplied.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor selects a hero action.

FR-14 — Hero buttons (explicit) As a Prospective Diner, I should use the hero buttons "View Our Menu", "Reserve a Table" and "Get Directions".

• Trigger/input: clicking a hero button.
• Observable result: "View Our Menu" opens the Menu page; "Reserve a Table" reaches the reservation/contact section; "Get Directions" opens the supplied Google Maps link.
• Access state: public.
• Failure/recovery: no dead "#" buttons; each action resolves to a real destination.
• Continuation: the visitor continues from the destination.

FR-15 — Hero trust indicators (explicit) As a Prospective Diner, I should see the hero trust indicators 4.3 ★ and 2,092+ Google reviews.

• Trigger/input: page load.
• Observable result: the rating and review count display exactly as supplied.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor may continue to the Reviews page.

FR-16 — Hero load animation (explicit) As a Prospective Diner, I should see hero content animate on load from opacity 0 + translateY 30px to visible position with staggered timing.

• Trigger/input: page load.
• Observable result: hero elements enter with the specified stagger.
• Access state: public.
• Failure/recovery: under prefers-reduced-motion, content appears at its final state.
• Continuation: the visitor reads the hero and acts.

FR-17 — Hero reservation card (explicit) As a Prospective Diner, I should see a hero reservation card that floats on the right on desktop and stacks on mobile, glassmorphic with 5–10% white transparency, backdrop blur, a thin border, a subtle top glow and a shadow.

• Trigger/input: page load at desktop or mobile width.
• Observable result: the card floats right on desktop and stacks on mobile with the specified glassmorphic treatment.
• Access state: public.
• Failure/recovery: if backdrop blur is unsupported, the card remains legible.
• Continuation: the visitor completes the reservation request.

FR-18 — Reservation card content (explicit) As a Prospective Diner, I should see the reservation card titled "Plan Your Visit" with fields Name, Email, Phone, Guests, Date, Preferred Time, Special Request, the button "Request a Table" and the small text "Reservations are subject to availability."

• Trigger/input: viewing and completing the card.
• Observable result: the title, seven fields, button and small text display exactly as supplied.
• Access state: public.
• Failure/recovery: inline validation errors are shown with accessible labels.
• Continuation: the visitor submits the request.

FR-19 — Reservation request, not instant confirmation (explicit) As a Prospective Diner, I should submit a reservation request that is understood to be subject to availability, and the site must not claim instant confirmation when no booking API is connected.

• Trigger/input: submitting the reservation card.
• Observable result: the submission is acknowledged as a request subject to availability; no instant confirmation is claimed.
• Access state: public.
• Failure/recovery: if submission fails, the visitor can correct and resubmit.
• Continuation: the visitor may also use the Contact form, Call Us or Get Directions.

FR-20 — Homepage order (explicit) As a Prospective Diner, I should experience the homepage in the order Hero → Story → Menu → Food Gallery → Why Us → Reviews → Hours → Location → Contact → Final CTA → Footer.

• Trigger/input: scrolling the Home page.
• Observable result: sections appear in the specified order.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor reaches the footer and its links.

FR-21 — Story section (explicit) As a Prospective Diner, I should see the Story headline "Comfort food, made for slow mornings and good company." with the supplied copy and large restaurant photography, and the CTA "Discover Our Story".

• Trigger/input: scrolling to the Story section; clicking "Discover Our Story".
• Observable result: the headline, copy and large photography display; the CTA opens the Our Story page.
• Access state: public.
• Failure/recovery: if photography fails, the text remains complete.
• Continuation: the visitor continues to the Our Story page or the Menu.

FR-22 — Signature Menu section (explicit) As a Prospective Diner, I should see the Signature Menu headline "Favourites worth waking up for." featuring Breakfast Crepe, Scrambled Eggs & Home Fries, Poached Egg & Hollandaise, Eggs Benny, Waffle Benny, Blueberry Pancakes with Scrambled Eggs, Croque Madame and Chicken Crêpe, and also showcasing Latte, Cappuccino, French Toast and fresh juice.

• Trigger/input: scrolling to the Signature Menu section.
• Observable result: the headline and all listed items display.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor opens the full Menu page.

FR-23 — Menu item fields and price rule (explicit) As a Prospective Diner, I should see each menu item with image, name and short description, and a price only when known — prices are never invented.

• Trigger/input: viewing menu items.
• Observable result: image, name and short description display; price appears only where known.
• Access state: public.
• Failure/recovery: if an item image fails, the name and description remain.
• Continuation: the visitor continues browsing the menu.

FR-24 — Signature Menu CTA (explicit) As a Prospective Diner, I should use the Signature Menu CTA "View Full Menu" to reach the Menu page.

• Trigger/input: clicking "View Full Menu".
• Observable result: the Menu page opens.
• Access state: public.
• Failure/recovery: no dead "#" button.
• Continuation: the visitor browses the Menu page.

FR-25 — Editorial food gallery (explicit) As a Prospective Diner, I should see an editorial food gallery featuring waffles, Eggs Benedict, French toast, pancakes, coffee, fresh fruit and restaurant atmosphere, with smooth image reveals, clipping animations and subtle parallax.

• Trigger/input: scrolling through the gallery.
• Observable result: images reveal with clipping animations and subtle parallax.
• Access state: public.
• Failure/recovery: under prefers-reduced-motion, reveals and parallax are removed and images appear at final state.
• Continuation: the visitor continues to Why Us.

FR-26 — Food gallery copy (explicit) As a Prospective Diner, I should see the gallery copy "Made fresh.", "Served with care." and "Built around good ingredients."

• Trigger/input: scrolling through the gallery.
• Observable result: the three lines display exactly as supplied.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues to Why Us.

FR-27 — Why Us section (explicit) As a Prospective Diner, I should see the Why Us headline "More than breakfast." with four pillars — 01 Seasonal Ingredients (Comfort food built around fresh, seasonal ingredients), 02 Belgian-Canadian Comfort (Belgian classics and Canadian comfort food), 03 All-Day Experience (Breakfast, brunch and selected dinner service), 04 Downtown Toronto (191 King St E) — and the CTA "Plan Your Visit".

• Trigger/input: scrolling to Why Us; clicking "Plan Your Visit".
• Observable result: the headline, four pillars and CTA display; the CTA reaches the reservation/contact section.
• Access state: public.
• Failure/recovery: no dead "#" button.
• Continuation: the visitor submits a reservation or contact request.

FR-28 — Reviews section (explicit) As a Prospective Diner, I should see the Reviews headline "Good food. Great company. Kind words.", the 4.3 ★ / 2,092 Google reviews summary and only authentic supplied excerpts, with the CTA "Read More Reviews".

• Trigger/input: scrolling to Reviews; clicking "Read More Reviews".
• Observable result: the headline, rating, count and supplied excerpts display; the CTA leads to Reviews/Google.
• Access state: public.
• Failure/recovery: no fabricated reviews, names, awards or statistics are ever shown.
• Continuation: the visitor continues to the Reviews page or Google.

FR-29 — Opening hours component (explicit) As a Prospective Diner, I should see a clean responsive hours component using accordion/tabs on mobile, showing REGULAR, BREAKFAST, BRUNCH, HAPPY HOURS and DINNER schedules exactly as supplied, with no invented holiday hours.

• Trigger/input: viewing the hours component; switching tabs or accordion panels on mobile.
• Observable result: the five schedules display exactly as supplied; mobile presents accordion/tabs.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor plans a visit using the hours.

FR-30 — Location section (explicit) As a Prospective Diner, I should see the Location headline "Find us in Toronto." with the address and phone, and the buttons "Get Directions" (supplied Google Maps link) and "Call Us" (tel:+14167031560); if map embedding is unavailable, a premium location card is shown.

• Trigger/input: scrolling to Location; clicking "Get Directions" or "Call Us".
• Observable result: the address and phone display; directions open the supplied Google Maps link; call dials +1 416-703-1560; a premium location card appears if embedding is unavailable.
• Access state: public.
• Failure/recovery: the premium location card covers map-embedding failure.
• Continuation: the visitor navigates to the restaurant or calls.

FR-31 — Contact section (explicit) As a Prospective Diner, I should see the Contact headline "Let's make your next visit delicious." with form fields Name, Email, Phone, Guests, Date, Preferred Time, Message, the button "Send Request", and the displayed phone and address.

• Trigger/input: completing and submitting the contact form.
• Observable result: the headline, seven fields, button, phone and address display; the request is sent.
• Access state: public.
• Failure/recovery: inline validation errors are shown with accessible labels; the visitor can correct and resubmit.
• Continuation: the visitor may also call or get directions.

FR-32 — Final CTA section (explicit) As a Prospective Diner, I should see the Final CTA using an atmospheric restaurant image or video with the headline "Your table is waiting.", the copy "Join us for breakfast, brunch, dinner, coffee, and good moments in downtown Toronto." and the buttons "View Menu" and "Reserve a Table".

• Trigger/input: scrolling to the Final CTA; clicking a button.
• Observable result: the headline, copy and buttons display; "View Menu" opens the Menu page and "Reserve a Table" reaches the reservation/contact section.
• Access state: public.
• Failure/recovery: no dead "#" buttons.
• Continuation: the visitor opens the Menu or submits a reservation request.

FR-33 — Footer (explicit) As a Prospective Diner, I should see the footer with the restaurant name, "Belgian-Canadian comfort food in the heart of Toronto.", Explore links (Home / Our Story / Menu / Reviews / Visit Us / Contact), Visit address 191 King St E, Toronto, ON M5A 1J5, Canada, Contact phone +1 416-703-1560, a Facebook social link, and the bottom line "© 2026 Le Petit Dejeuner by LPD Café. All rights reserved." plus a Privacy Policy link.

• Trigger/input: scrolling to the footer; clicking a footer link.
• Observable result: all footer content displays; each link resolves to its destination.
• Access state: public.
• Failure/recovery: no dead "#" buttons.
• Continuation: the visitor navigates to any footer destination.

FR-34 — Dedicated pages (explicit) As a Prospective Diner, I should reach dedicated Menu, Our Story, Reviews, Contact and Privacy Policy pages.

• Trigger/input: navigating from the nav, footer or in-page CTAs.
• Observable result: each dedicated page opens with its own content.
• Access state: public.
• Failure/recovery: navigation remains available from every page.
• Continuation: the visitor continues within the destination page.

FR-35 — Menu page categories (explicit) As a Menu Explorer, I should browse the Menu page organized by Breakfast, Brunch, Eggs, Waffles, Pancakes, Crepes, French Toast, Comfort Food, Dinner, Desserts and Drinks, using supplied menu items only.

• Trigger/input: opening the Menu page and selecting a category.
• Observable result: the eleven categories display with supplied items only.
• Access state: public.
• Failure/recovery: no invented items or prices appear.
• Continuation: the visitor chooses dishes and proceeds to reserve or visit.

FR-36 — Our Story page facts (explicit) As a Prospective Diner, I should read an Our Story page that uses only supplied facts, with no invented founders, chefs, history or awards.

• Trigger/input: opening the Our Story page.
• Observable result: only supplied facts are presented.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues to the Menu or Visit Us.

FR-37 — Reviews page content (explicit) As a Review Reader, I should see the Reviews page showing the 4.3 rating, 2,092 reviews and the authentic supplied excerpts.

• Trigger/input: opening the Reviews page.
• Observable result: the rating, count and supplied excerpts display exactly as supplied.
• Access state: public.
• Failure/recovery: no fabricated reviews, names, awards or statistics appear.
• Continuation: the visitor follows "Read More Reviews" to Google or proceeds to reserve.

FR-38 — Privacy Policy content (explicit) As a Privacy-Conscious Visitor, I should read a clean, ad-safe Privacy Policy page containing Information Collected, Use of Information, Contact/Reservation Requests, Cookies & Analytics, Third Parties, Retention, Security, User Rights, Children's Privacy and Policy Updates, and including exactly "Last updated: September 2026."

• Trigger/input: opening the Privacy Policy page.
• Observable result: all ten sections and the exact update line display.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor returns to the reservation or contact form with understanding.

FR-39 — Privacy Policy framing (explicit) As a Privacy-Conscious Visitor, I should read the Privacy Policy as general website policy content suitable for review, without unsupported legal claims.

• Trigger/input: reading the Privacy Policy page.
• Observable result: the content is presented as general website policy content suitable for review.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor continues browsing.

FR-40 — Motion system (explicit) As a Prospective Diner, I should experience elegant motion: page-load fade + slide-up, staggered text, scroll image reveals, subtle parallax, image hover zoom, button micro-interactions, smooth anchor scrolling and a navigation blur transition, all respecting prefers-reduced-motion.

• Trigger/input: page load, scrolling, hovering and clicking.
• Observable result: the listed motions occur; under prefers-reduced-motion they are disabled.
• Access state: public.
• Failure/recovery: reduced-motion preference removes motion without removing content.
• Continuation: the visitor continues browsing.

FR-41 — Responsive behavior (explicit) As a Prospective Diner, I should use a mobile-first site optimized for mobile portrait/landscape, tablets and desktop, with the hero and form stacked on mobile, simplified galleries, readable typography, touch-friendly controls and no horizontal overflow.

• Trigger/input: resizing or using different devices.
• Observable result: layout adapts as specified with no horizontal overflow.
• Access state: public.
• Failure/recovery: content remains readable and controls remain touch-friendly at every breakpoint.
• Continuation: the visitor completes their task on any device.

FR-42 — Performance (explicit) As a Prospective Diner, I should experience lazy-loaded images, compressed media, optimized video, responsive images, optimized fonts, minimized JavaScript and GPU-friendly animations, with the hero video having a poster and mobile fallback.

• Trigger/input: page load and scroll.
• Observable result: media loads lazily and efficiently; the hero video has a poster and mobile fallback.
• Access state: public.
• Failure/recovery: the poster and mobile fallback cover slow or failed video loading.
• Continuation: the visitor continues browsing without waiting.

FR-43 — SEO (explicit) As a Prospective Diner, I should find the site with the title "Le Petit Dejeuner by LPD Café | Breakfast & Brunch in Toronto" and the description "Le Petit Dejeuner by LPD Café serves Belgian-Canadian comfort food, breakfast, brunch and dinner at 191 King St E in Toronto.", with semantic headings, descriptive alt text and Restaurant/LocalBusiness structured data including address, phone, hours and menu URL.

• Trigger/input: search engine crawl or social preview.
• Observable result: the exact title and description are used; semantic headings, alt text and structured data are present.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor arrives on the site.

FR-44 — Accessibility (explicit) As a Prospective Diner, I should use semantic HTML, keyboard navigation, visible focus states, accessible labels/forms, strong contrast, alt text, reduced-motion support and accessible mobile navigation.

• Trigger/input: keyboard or assistive-technology use.
• Observable result: all listed accessibility provisions are present.
• Access state: public.
• Failure/recovery: focus remains visible and navigation remains operable.
• Continuation: the visitor completes their task.

FR-45 — Functional links (explicit) As a Prospective Diner, I should use working CTAs: View Menu → Menu page; Reserve → reservation/contact section; Directions → supplied Google Maps; Call → +1 416-703-1560; Our Story → About; Reviews → Reviews/Google; Contact → Contact; Privacy → Privacy Policy, with no dead "#" buttons.

• Trigger/input: clicking any CTA.
• Observable result: each CTA resolves to its stated destination.
• Access state: public.
• Failure/recovery: no dead "#" buttons exist anywhere.
• Continuation: the visitor continues from the destination.

FR-46 — Content rule (explicit) As a Prospective Diner, I should see only facts supplied in the prompt, with no invented prices, awards, chefs, history, customer names, reviews or statistics.

• Trigger/input: reading any page.
• Observable result: only supplied facts appear.
• Access state: public.
• Failure/recovery: not applicable.
• Continuation: the visitor trusts the presented information.

FR-47 — First-screen impression (explicit) As a Prospective Diner, I should see the restaurant experience, food, Toronto identity, social proof and clear actions to view the menu, reserve, call or get directions immediately on the first screen.

• Trigger/input: page load.
• Observable result: the first screen shows the experience, food, Toronto identity, social proof and the clear actions.
• Access state: public.
• Failure/recovery: if video fails, the poster/fallback preserves the first-screen impression.
• Continuation: the visitor selects an action.

4. User Personas

Prospective Diner (required_inference) A Toronto visitor or local planning a meal at Le Petit Dejeuner. Their product context is the public site as a decision and conversion surface: they arrive on the Home page, read the hero, story, signature menu, food gallery, why-us pillars, reviews and hours, and decide whether to visit. Their primary goal is an informed decision and a submitted table request. Their distinct accepted responsibilities are reading the homepage sequence in order, submitting the reservation card (Name, Email, Phone, Guests, Date, Preferred Time, Special Request), submitting the contact form (Name, Email, Phone, Guests, Date, Preferred Time, Message), and using Get Directions or Call Us to reach 191 King St E. Their relevant inputs and decisions are party size, date, preferred time, special request and message. They interact with the restaurant as the counterparty that receives the request; the site itself is the only first-party participant. Their observable success is a submitted table request that is understood to be subject to availability rather than instantly confirmed, plus a working route to directions or a phone call. What makes this role distinct is that it spans the whole conversion path — from first-screen impression to a submitted request — rather than a single page.

Menu Explorer (required_inference) A diner who goes to the dedicated Menu page to review the supplied categories (Breakfast, Brunch, Eggs, Waffles, Pancakes, Crepes, French Toast, Comfort Food, Dinner, Desserts, Drinks) and the supplied items with images, names, short descriptions and prices only where known. Their primary goal is choosing dishes before visiting. Their distinct accepted responsibility is browsing categories and items without encountering invented prices or items. Their relevant inputs are the category they select and the items they compare. They interact with the restaurant as the party that serves those dishes. Their observable success is finding the dishes they want, with prices shown only where known. What makes this role distinct is that its work is menu evaluation rather than reservation or social-proof checking.

Review Reader (required_inference) A prospective guest who opens the dedicated Reviews page to check the 4.3 star rating, 2,092 Google reviews and the authentic supplied excerpts before committing to a visit, then follows the Read More Reviews link to Google. Their primary goal is trusting the restaurant based only on authentic supplied social proof. Their distinct accepted responsibility is reading the rating, count and excerpts and continuing to Google. Their relevant inputs are the rating, the review count and the three supplied excerpts. They interact with the restaurant as the reviewed party and with Google as the external destination. Their observable success is a confident decision to visit or reserve. What makes this role distinct is that its decision rests on third-party social proof rather than on the menu or the story.

Privacy-Conscious Visitor (required_inference) A site visitor who opens the Privacy Policy page to read the sections on Information Collected, Use of Information, Contact/Reservation Requests, Cookies & Analytics, Third Parties, Retention, Security, User Rights, Children's Privacy and Policy Updates before submitting personal details through the reservation or contact form. Their primary goal is understanding how their submitted information is handled. Their distinct accepted responsibility is reading the policy sections and the exact "Last updated: September 2026." line before submitting. Their relevant inputs are the policy content and their own willingness to submit personal details. They interact with the restaurant as the party that receives and handles their information. Their observable success is submitting a reservation or contact request with understanding of how the information is handled. What makes this role distinct is that its concern is data handling rather than food, hours or social proof.

5. Core User Flows

Flow 1 — Prospective Diner: first-screen impression and reservation request (Home)

1. The Prospective Diner opens the Home page on a phone or desktop. The 90–100vh hero plays the cinematic background video (coffee being poured, waffles, Eggs Benedict, pancakes, French toast, fresh ingredients, restaurant interior, guests enjoying brunch) with a dark/warm overlay, a poster/fallback image and a mobile fallback.
2. Hero content animates in from opacity 0 + translateY 30px with staggered timing: the kicker "BREAKFAST • BRUNCH • DINNER", then the headline "Good mornings start here.", then the subcopy "Belgian-Canadian comfort food, seasonal ingredients, and all-day dining in the heart of Toronto.", then the buttons, then the trust row showing 4.3 ★ and 2,092+ Google reviews.
3. The diner sees the restaurant experience, food, Toronto identity, social proof and the clear actions on the first screen.
4. The diner chooses an action: "View Our Menu" (Menu page), "Reserve a Table" (reservation/contact section) or "Get Directions" (supplied Google Maps link).
5. If reserving, the diner uses the "Plan Your Visit" card — floating right on desktop, stacked on mobile, glassmorphic with 5–10% white transparency, backdrop blur, thin border, subtle top glow and shadow — and enters Name, Email, Phone, Guests, Date, Preferred Time and Special Request.
6. The diner clicks "Request a Table". The small text "Reservations are subject to availability." is visible, and the site does not claim instant confirmation.
7. Observable result: the request is submitted as a request subject to availability.
8. Failure/recovery: if a field is invalid, an inline accessible error appears and the diner corrects and resubmits; if the video cannot play, the poster/fallback image and mobile fallback preserve the first screen.
9. Continuation: the diner may also use the Contact form, "Call Us" (tel:+14167031560) or "Get Directions".

Flow 2 — Prospective Diner: homepage sequence to story and menu (Home → Our Story / Menu)

1. The diner scrolls the Home page in the fixed order Hero → Story → Menu → Food Gallery → Why Us → Reviews → Hours → Location → Contact → Final CTA → Footer.
2. In Story, the diner reads "Comfort food, made for slow mornings and good company." with the supplied copy and large restaurant photography, then clicks "Discover Our Story" to open the Our Story page.
3. In the Signature Menu, the diner reads "Favourites worth waking up for." and the featured items — Breakfast Crepe, Scrambled Eggs & Home Fries, Poached Egg & Hollandaise, Eggs Benny, Waffle Benny, Blueberry Pancakes with Scrambled Eggs, Croque Madame, Chicken Crêpe — plus Latte, Cappuccino, French Toast and fresh juice, each with image, name, short description and price only when known.
4. The diner clicks "View Full Menu" and the Menu page opens.
5. Observable result: the diner has read the story and the signature items and reached the full Menu page.
6. Failure/recovery: if an item image fails, the name and description remain; no price is invented.
7. Continuation: the diner browses the Menu page or returns to reserve.

Flow 3 — Prospective Diner: gallery, why-us and hours planning (Home)

1. The diner scrolls into the editorial Food Gallery featuring waffles, Eggs Benedict, French toast, pancakes, coffee, fresh fruit and restaurant atmosphere; images reveal with smooth clipping animations and subtle parallax, and the copy "Made fresh.", "Served with care." and "Built around good ingredients." appears.
2. The diner continues to Why Us, reading "More than breakfast." with 01 Seasonal Ingredients, 02 Belgian-Canadian Comfort, 03 All-Day Experience and 04 Downtown Toronto (191 King St E), then clicks "Plan Your Visit" to reach the reservation/contact section.
3. The diner continues to the Hours component and checks REGULAR, BREAKFAST, BRUNCH, HAPPY HOURS and DINNER; on mobile the schedules are presented as accordion/tabs.
4. Observable result: the diner has seen the food experience, the four pillars and the exact schedules, and has a route to reserve.
5. Failure/recovery: under prefers-reduced-motion the reveals and parallax are removed and images appear at final state; no holiday hours are shown.
6. Continuation: the diner reserves, calls or gets directions.

Flow 4 — Prospective Diner: location and contact (Home → Visit Us / Contact)

1. The diner scrolls to Location and reads "Find us in Toronto." with 191 King St E, Toronto, ON M5A 1J5, Canada and +1 416-703-1560.
2. The diner clicks "Get Directions" and the supplied Google Maps link opens, or clicks "Call Us" and tel:+14167031560 dials.
3. If map embedding is unavailable, a premium location card is shown instead.
4. The diner scrolls to Contact, reads "Let's make your next visit delicious.", and completes Name, Email, Phone, Guests, Date, Preferred Time and Message.
5. The diner clicks "Send Request"; the phone and address remain displayed on the page.
6. Observable result: the contact request is sent and the diner has a working route to the restaurant.
7. Failure/recovery: if a field is invalid, an inline accessible error appears and the diner corrects and resubmits.
8. Continuation: the diner may also open the Visit Us page for hours and directions.

Flow 5 — Prospective Diner: final CTA and footer (Home)

1. The diner reaches the Final CTA with an atmospheric restaurant image or video, the headline "Your table is waiting." and the copy "Join us for breakfast, brunch, dinner, coffee, and good moments in downtown Toronto."
2. The diner clicks "View Menu" to open the Menu page or "Reserve a Table" to reach the reservation/contact section.
3. The diner continues to the footer and sees the restaurant name, "Belgian-Canadian comfort food in the heart of Toronto.", the Explore links (Home / Our Story / Menu / Reviews / Visit Us / Contact), the Visit address, the Contact phone, the Facebook link, "© 2026 Le Petit Dejeuner by LPD Café. All rights reserved." and the Privacy Policy link.
4. Observable result: every footer link resolves to a real destination; no dead "#" buttons exist.
5. Failure/recovery: not applicable.
6. Continuation: the diner navigates to any footer destination.

Flow 6 — Menu Explorer: browsing the Menu page

1. The Menu Explorer opens the Menu page from the nav, the "View Full Menu" CTA or the footer.
2. The explorer selects among Breakfast, Brunch, Eggs, Waffles, Pancakes, Crepes, French Toast, Comfort Food, Dinner, Desserts and Drinks.
3. For each item the explorer sees image, name and short description, and a price only when known.
4. Observable result: the explorer identifies the dishes they want without encountering invented prices or items.
5. Failure/recovery: if an item image fails, the name and description remain; a category with no supplied items is not populated with invented content.
6. Continuation: the explorer proceeds to reserve, call or get directions.

Flow 7 — Review Reader: checking social proof (Reviews)

1. The Review Reader opens the Reviews page from the nav, the "Read More Reviews" CTA or the footer.
2. The reader sees the 4.3 rating, 2,092 reviews and the authentic supplied excerpts: "Mention spéciale pour les jus et les fruits, très frais et bien présentés.", "Très bon service avec des serveurs souriants et attentionnés." and "Déjeuner délicieux ! Une carte où tout donne envie d’être dégusté."
3. The reader clicks "Read More Reviews" and continues to Reviews/Google.
4. Observable result: the reader has based their trust only on authentic supplied social proof.
5. Failure/recovery: no fabricated reviews, names, awards or statistics are ever shown; if the external link is unavailable, the page content remains complete.
6. Continuation: the reader returns to reserve a table or get directions.

Flow 8 — Privacy-Conscious Visitor: reading the policy before submitting (Privacy Policy → Contact / reservation)

1. The Privacy-Conscious Visitor opens the Privacy Policy page from the footer.
2. The visitor reads Information Collected, Use of Information, Contact/Reservation Requests, Cookies & Analytics, Third Parties, Retention, Security, User Rights, Children's Privacy and Policy Updates, and sees exactly "Last updated: September 2026."
3. The visitor understands the content as general website policy content suitable for review, with no unsupported legal claims.
4. Observable result: the visitor understands how submitted information is handled.
5. Failure/recovery: not applicable.
6. Continuation: the visitor returns to the reservation card or the Contact form and submits a request with understanding.

Flow 9 — Prospective Diner: mobile navigation (any page)

1. On mobile or tablet, the diner taps the hamburger.
2. A full-height menu slides in from the right with smooth animation, large typography and a reservation CTA; no horizontal overflow occurs.
3. The diner selects a destination or the reservation CTA.
4. Observable result: the selected destination opens or the reservation/contact section is reached.
5. Failure/recovery: the menu remains keyboard-accessible and dismissible.
6. Continuation: the diner completes their task on the destination page.

6. Visuals Colors and Theme

The creative direction is authoritative for this section: Editorial swagger for a brasserie that takes breakfast seriously, with Tobias van Schneider as the muse. The headline idea is editorial minimalism with swagger — enormous display type, warm off-white and deep espresso grounds, one hot accent, full-bleed photography that breathes, sparse chrome and sharp corners.

Color tokens (light mode)

• Background: #F7F1E8 (Cream)
• Surface: #FFFDF9 (White)
• Text: #241A17 (Deep Espresso)
• Primary: #241A17 (Deep Espresso)
• Accent: #B76545 (Terracotta)
• Muted: #C7A46A (Muted Gold)
• Deep ground: #151210 (Charcoal) and #241A17 (Deep Espresso)

Two grounds alternate by section like editorial spreads: Cream #F7F1E8 for Story, Menu, Hours and Contact (warm, paper-like), and Deep Espresso #241A17 / Charcoal #151210 for the Hero, the Food Gallery, the Final CTA and the Footer (photography glows against it). Text on cream is Espresso #241A17; text on espresso is Cream #F7F1E8 or White #FFFDF9. Terracotta #B76545 is the single hot accent — used for the primary CTA fill, the section index numerals, the active nav underline and the star rating, never as decoration on more than ~8% of any screen. Muted Gold #C7A46A is the secondary hairline/accent for rules, kickers, small-caps labels and the reservation card's top glow. Surfaces are #FFFDF9 with a 1px #241A17 at 12% hairline border; no drop shadows except the one glass reservation card. Terracotta on Espresso passes AA for large text; Cream on Espresso is used for body.

Typography

• Headings: Playfair Display at 600–700 weight, optical-size large, tracking tightened to -0.02em, tight leading (0.95–1.02) so multi-line headlines stack as a solid type block. Headlines are sentence case, never all-caps — the swagger comes from scale, not shouting. One exception: kickers and section labels are Manrope 500, uppercase, 0.18em tracking, 12–13px, in Muted Gold. Italic Playfair is reserved for one word per headline (e.g. "Good mornings start here.") as the editorial gesture.
• Body: Manrope.
• Type scale: 1.5 ratio display scale, clamp-based. Hero H1: clamp(44px, 9vw, 132px). Section H2: clamp(34px, 5.2vw, 76px). Feature H3: clamp(22px, 2.4vw, 34px). Body: 17px mobile / 18px desktop, line-height 1.65. Small caps labels: 12px. Menu item name: 20px Playfair 600; menu item description: 15px Manrope 400 in Espresso at 72%. Numerals (prices, hours, 4.3) set in Manrope 600 with tabular-nums.

Shape language Sharp corners everywhere — 0px radius on images, buttons, inputs and section boundaries. The single exception is the hero reservation card at 2px, which reads as a deliberate object rather than a rounded app tile. Structure comes from 1px hairline rules (Espresso at 12% on cream, Cream at 18% on espresso) used as full-width section dividers and as the left edge of menu rows — the rule is the ornament. Images are hard-cropped rectangles in asymmetric sizes (4:5 portrait, 3:2 landscape, 1:1 square) that butt against each other with 0–2px gaps, like a printed spread. Buttons are rectangles with 1px borders; the primary is a solid Terracotta block with Espresso text. No pills, no soft shadows, no rounded cards.

Spacing rhythm Asymmetric editorial grid: 12 columns on desktop with content deliberately starting at column 2 or 5. Sections alternate ground colour (cream → espresso → cream) so scroll reads as turning pages. Mobile collapses everything to a single column with 24px gutters.

Imagery style High-end food and hospitality photography, treated as editorial: macro food shots (a pour of hollandaise, waffle grid, coffee crema, cut fruit) at 1:1 and 4:5, and full-bleed atmospheric frames of the brick-walled room and guests mid-brunch. Warm colour grade, deep shadows, natural window light, no white studio backdrops, no flat-lay clichés on marble. Hero is a cinematic muted looping video (coffee pour → waffles → Eggs Benedict → pancakes → French toast → interior → guests) with a poster frame, a 720p mobile source, and a static poster fallback for reduced-motion and slow connections. Overlays: linear-gradient(rgba(21,18,16,0.35), rgba(36,26,23,0.78)) over the hero video, and a 20% espresso scrim over gallery images on hover so captions stay legible.

7. Signature Design Concept

The public entry is a full-bleed 92vh cinematic video hero, Espresso-graded, with the reservation card as a real object in the frame rather than a floating UI panel. Composition is asymmetric: the left 58% holds the type stack starting at the 2nd column — the Terracotta kicker "BREAKFAST • BRUNCH • DINNER" in 12px Manrope 500 uppercase with 0.18em tracking, then "Good mornings start here." set in Playfair Display at clamp(44px, 9vw, 132px) with "here." in italic, running to four lines and deliberately ending near the viewport edge; below it the subcopy at 18px capped to a 46ch measure, then three buttons in a row (solid Terracotta "View Our Menu", 1px cream-outlined "Reserve a Table", text-with-arrow "Get Directions"), then a hairline rule and the trust row — "4.3 ★" in Playfair 600 at 28px beside "2,092+ Google reviews" in Manrope 13px uppercase. The right 34% holds the "Plan Your Visit" glass card, top-aligned with the headline's cap height, 5–10% white fill, backdrop-blur(18px), 1px rgba(255,253,249,0.28) border, a Muted Gold top glow line and a soft shadow, containing the seven fields in a 2-column interior grid (Name/Email full width, Phone/Guests/Date/Time paired, Special Request full width) and the Terracotta "Request a Table" button. On mobile the video shortens to 100svh, the card stacks below the buttons in normal flow, and the H1 drops to 44px — nothing is cropped or overlapped at 375px.

The signature moves that carry the concept across the site: a four-line Playfair Display hero headline at up to 132px that runs the full left column and ends with one italic word ("here."), set directly on the video with no card, no gradient blob and no centred stack — the type is the composition; the menu as an editorial ledger rather than a card grid, with full-width rows carrying a 96px square food crop, Playfair item name, Manrope description, right-aligned tabular price and a hairline rule that slides 8px right on hover, readable at 375px with the thumbnail retained; alternating cream/espresso "spreads" where Story, Menu, Why Us, Hours and Contact sit on Cream #F7F1E8 while the Food Gallery, Final CTA and Footer drop to Espresso #241A17, with full-width 1px hairline rules as the only transition ornament; the three gallery lines — "Made fresh." / "Served with care." / "Built around good ingredients." — set in Playfair italic and physically dropped into the negative space between hard-cropped gallery images, with a Terracotta index numeral above each, so the copy is part of the collage rather than a caption block; and Why Us as a numbered band of four 100px Terracotta numerals (01–04) on Espresso, each with a Manrope label and one line of copy, separated by full-height hairlines — a data-plate treatment that makes a soft subject feel precise.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

• Focal subject: the cinematic muted looping hero video — coffee being poured, waffles, Eggs Benedict, pancakes, French toast, fresh ingredients, restaurant interior and guests enjoying brunch — graded Espresso with a linear-gradient(rgba(21,18,16,0.35), rgba(36,26,23,0.78)) overlay.
• Input → transformation → outcome thesis: on load, the hero content enters as a staggered sequence — kicker, then H1 line-by-line, then subcopy, then buttons, then trust row — each from opacity 0 / translateY 30px, 700ms cubic-bezier(0.16,1,0.3,1), 90ms stagger; the outcome is a composed first frame in which the type stack and the "Plan Your Visit" card are fully legible over the moving video.
• Motion vocabulary: expressive but unhurried. Scroll reveals are clip-path wipes (inset(0 0 100% 0) → inset(0)) on images, 900ms, with a 40–60px counter-parallax between adjacent gallery images. The nav transitions from fully transparent to rgba(36,26,23,0.72) + backdrop-blur(14px) over 300ms once past 80px. Hover: images scale to 1.04 inside a fixed frame (overflow hidden, 600ms), buttons invert fill/border in 180ms, menu rows shift their hairline rule 8px right. Mobile nav slides in from the right over 420ms with the links staggering in behind it.
• Composed first frame: left 58% type stack (Terracotta kicker, four-line Playfair headline ending in italic "here.", 46ch subcopy, three buttons, hairline rule, trust row) and right 34% glass "Plan Your Visit" card top-aligned with the headline's cap height.
• Reduced-motion state: all motion is disabled under prefers-reduced-motion — content appears at final state, parallax and wipes are removed, hover becomes a border-colour change, and the hero shows the static poster fallback instead of the video.

9. Non-Functional Requirements

NFR-1 — Responsive design (explicit) The site must be mobile-first and optimized for mobile portrait/landscape, tablets and desktop; the hero and form stack on mobile, galleries simplify, typography stays readable, controls stay touch-friendly, and no horizontal overflow occurs. Rationale: explicit responsive requirement in the source.

NFR-2 — Performance (explicit) Images must lazy-load, media must be compressed, video must be optimized, images must be responsive, fonts must be optimized, JavaScript must be minimized, and animations must be GPU-friendly; the hero video must have a poster and a mobile fallback. Rationale: explicit performance requirement in the source.

NFR-3 — SEO (explicit) The site must use the exact title "Le Petit Dejeuner by LPD Café | Breakfast & Brunch in Toronto" and description "Le Petit Dejeuner by LPD Café serves Belgian-Canadian comfort food, breakfast, brunch and dinner at 191 King St E in Toronto.", with semantic headings, descriptive alt text and Restaurant/LocalBusiness structured data including address, phone, hours and menu URL. Rationale: explicit SEO requirement in the source.

NFR-4 — Accessibility (explicit) The site must use semantic HTML, keyboard navigation, visible focus states, accessible labels/forms, strong contrast, alt text, reduced-motion support and accessible mobile navigation. Rationale: explicit accessibility requirement in the source.

NFR-5 — Reduced motion (explicit) All motion must respect prefers-reduced-motion. Rationale: explicit constraint in the source.

NFR-6 — No horizontal overflow (explicit) No horizontal overflow may occur at any supported viewport. Rationale: explicit constraint in the source.

NFR-7 — Hero video fallback (explicit) The hero video must have a poster and a mobile fallback. Rationale: explicit constraint in the source.

NFR-8 — Content integrity (explicit) Only facts supplied in the prompt may be used; prices, awards, chefs, history, customer names, reviews and statistics must never be invented. Rationale: explicit content rule in the source.

NFR-9 — Functional links (explicit) Every CTA must resolve to a real destination; dead "#" buttons are prohibited. Rationale: explicit constraint in the source.

NFR-10 — Reservation honesty (explicit) If no booking API is connected, the reservation card must remain a request form and the site must not claim instant confirmation; "Reservations are subject to availability." must be shown. Rationale: explicit constraint in the source.

NFR-11 — Privacy Policy framing (explicit) The Privacy Policy must be presented as general website policy content suitable for review, without unsupported legal claims, and must include exactly "Last updated: September 2026." Rationale: explicit constraint in the source.

NFR-12 — Design restraint (explicit) The design must avoid generic templates, excessive cards, neon colors, clutter and gimmicky animation. Rationale: explicit constraint in the source.

10. Tech Stack

• Frontend: React with a modern component-based implementation, delivering the seven public pages and the shared sticky navigation, mobile slide-in menu and footer. (Default — not specified by user)
• Styling: CSS with the specified palette tokens, Playfair Display and Manrope typefaces, clamp-based type scale, 0px-radius shape language and 1px hairline rules. (Default — not specified by user)
• Motion: CSS transitions and IntersectionObserver-driven reveals for page-load fade + slide-up, staggered text, scroll image reveals, subtle parallax, image hover zoom, button micro-interactions, smooth anchor scrolling and the navigation blur transition, all gated by prefers-reduced-motion. (Default — not specified by user)
• Media: Optimized/compressed hero video with poster frame, 720p mobile source and static poster fallback; lazy-loaded responsive images for menu items, gallery and story photography. (Default — not specified by user)
• Backend: Python/FastAPI service to receive reservation requests and contact requests and to serve the site. (Default — not specified by user)
• Storage: Appropriate storage for submitted reservation and contact requests. (Default — not specified by user)
• Deployment: Docker/docker-compose for the application and its storage. (Default — not specified by user)

No booking API is assumed; the reservation card is implemented as a request form.

11. Assumptions and Constraints

Assumptions

1. No booking API is connected, so the reservation card is a request form and the site does not claim instant confirmation. (explicit)
2. Reservation and contact submissions are received by the restaurant; the restaurant's response occurs outside the website and is not modeled as a product capability. (required_inference)
3. Map embedding may be unavailable, in which case a premium location card is shown. (explicit)
4. The supplied menu items are the complete set available for the Menu page and the Signature Menu section. (explicit)
5. Prices are shown only where known; where no price is supplied, no price is displayed. (explicit)
6. The supplied review excerpts are the only review text shown. (explicit)
7. The supplied opening-hours schedules are the only hours shown; no holiday hours are added. (explicit)
8. The site is publicly accessible with no account, login or identity establishment. (required_inference)

Constraints

1. Never invent prices; show price only when known. (explicit)
2. Never fabricate reviews, names, awards or statistics; use only authentic supplied excerpts. (explicit)
3. Do not invent holiday hours. (explicit)
4. Our Story page: use only supplied facts; do not invent founders, chefs, history or awards. (explicit)
5. Menu page: use supplied menu items only. (explicit)
6. Only use facts supplied in the prompt; never invent prices, awards, chefs, history, customer names, reviews or statistics. (explicit)
7. If no booking API is connected, make it a reservation request form and do not claim instant confirmation. (explicit)
8. Reservations are subject to availability. (explicit)
9. Privacy Policy must include exactly "Last updated: September 2026." (explicit)
10. Do not make unsupported legal claims in the Privacy Policy; present it as general website policy content suitable for review. (explicit)
11. Never use dead "#" buttons; every CTA must work. (explicit)
12. Avoid generic templates, excessive cards, neon colors, clutter and gimmicky animation. (explicit)
13. Respect prefers-reduced-motion. (explicit)
14. No horizontal overflow. (explicit)
15. Hero video must have a poster and mobile fallback. (explicit)
16. Hero must use a cinematic background video, not a static image. (explicit)

12. Glossary

• Le Petit Dejeuner by LPD Café — The restaurant at 191 King St E, Toronto, ON M5A 1J5, Canada; Belgian-Canadian breakfast, brunch and restaurant.
• Reservation request — A submission of Name, Email, Phone, Guests, Date, Preferred Time and Special Request through the "Plan Your Visit" card, subject to availability and not an instant confirmation.
• Contact request — A submission of Name, Email, Phone, Guests, Date, Preferred Time and Message through the Contact form.
• Signature Menu — The homepage section headlined "Favourites worth waking up for." featuring the supplied items.
• Food Gallery — The editorial gallery featuring waffles, Eggs Benedict, French toast, pancakes, coffee, fresh fruit and restaurant atmosphere.
• Why Us — The homepage section headlined "More than breakfast." with the four numbered pillars.
• Hours component — The responsive component showing REGULAR, BREAKFAST, BRUNCH, HAPPY HOURS and DINNER schedules, using accordion/tabs on mobile.
• Premium location card — The fallback presentation shown when map embedding is unavailable.
• Read More Reviews — The CTA leading from the Reviews section or page to Reviews/Google.
• prefers-reduced-motion — The user preference that disables motion; content appears at final state, parallax and wipes are removed, and hover becomes a border-colour change.