Standards

    Found pattern

    Use this module for found-pet notices, intake checklist guidance, and safe reunification communication.

    Example

    The CTA title, contact details, and help link below are all page-local props passed to FoundListingsSection — never hardcoded in the shared component — so every real site swaps in its own intake contact info here, not by editing the module.

    Please Keep Them Safe

    If the dog is safely contained, keep holding them while owner matching is in progress. Do not hand a found dog to anyone unless ownership is verified.

    What to Include in Your Notice

    • Date, time, and exact location where the dog was found
    • Photos or short video from a safe distance
    • Estimated breed, size, color, and any collar/harness details
    • Whether the dog appears injured, frightened, or approachable
    • Your preferred contact details for owner outreach

    How Reunification Works

    • We review your found-dog details and create a local notice.
    • Owners contact us and provide identifying details for verification.
    • We coordinate the safest handoff plan for the owner and finder.

    Current Found Dog Notices

    Sample found dog notice 1

    Buddy (Found Dog Notice #SAMPLE-001)

    • Gender: Male
    • Found date: 3/26/2026
    • Found location: Eastgate, Example City 90210
    • Cross streets: Juniper Ave and 3rd St
    • Microchip: Unknown

    Friendly tan dog found near a grocery parking lot wearing a blue collar and no tags.

    Sample found dog notice 2

    Luna (Found Dog Notice #SAMPLE-002)

    • Gender: Female
    • Found date: 3/29/2026
    • Found location: North Hills, Example City 90211
    • Cross streets: Olive Dr and Canyon Rd
    • Microchip: Not Detected

    Small black-and-white dog found near a trailhead with a red harness and no owner nearby.

    Submit a Found Notice

    Use this example contact block to test your local intake flow and response messaging.

    Need first-step guidance? Visit Found a Stray guidance

    Standard

    - Use `FoundListingsSection` for all found-notice pages.

    - Keep listing data normalized in `FoundListing` objects (`pet`, `location`, `source`, `status`).

    - Use mode controls (`local`, `external`, `hybrid`) instead of page-local filtering logic.

    - Keep warnings/checklists in module props so content is reusable and no-JS readable.

    - Source/media links should open in a new tab with safe rel attributes.

    - Keep CTA contact info (title, phone, email, help link) anonymized in template/example content — real sites pass their own via props (`ctaTitle`, `phoneCta`, `emailCta`, `helpLink`), never by editing the module.

    - Use neutral styling defaults (no site-specific color branding in shared standards).

    - Use `statusFilter` plus `showReunited`/`showArchived` (both default `false`) to control found-notice lifecycle visibility — active notices show by default; reunited/archived are opt-in.

    - Cards render from normalized `FoundListing` metadata (`pet`, `location`, `status`, `source`); image and source links open safely in a new tab; internal support links use `Link` components and remain no-JS readable as anchors.

    - Use `gender` on the pet profile — matches the field name used across every other pattern (`AdoptablePetsSection`, kennel-display tools).

    - Component: `template/src/components/patterns/FoundListingsSection.tsx`