Contact Page

Open source

Full contact pages — a split form with map, method cards with FAQ, and a centered split form.

1 of 3

resources/views/pages/contact-page-split-map.blade.php Blade

@props([])

{{-- Contact page — composes existing marketing blocks into a full screen. --}}
<div class="min-h-screen bg-background text-foreground">
    <x-blocks.header-navbar />

    <main>
        <x-blocks.contact-split
            eyebrow="Get in touch"
            heading="Let's build something worth talking about"
            subheading="Tell us about your brand, your timeline and your goals. A studio lead will reply within one business day."
            :details="[
                ['label' => 'Email', 'value' => 'studio@northbound.agency', 'href' => 'mailto:studio@northbound.agency', 'icon' => 'mail'],
                ['label' => 'Phone', 'value' => '+1 (415) 555-0142', 'href' => 'tel:+14155550142', 'icon' => 'phone'],
                ['label' => 'Studio', 'value' => '420 Bryant Street, Floor 3, San Francisco', 'href' => null, 'icon' => 'pin'],
            ]"
        />

        <x-blocks.contact-map
            eyebrow="Find us"
            heading="Stop by the studio"
            subheading="We host workshops, pitch sessions and the occasional happy hour. Book a visit and we'll have the coffee ready."
            address="420 Bryant Street, Floor 3"
            addressLine2="San Francisco, CA 94107"
        />
    </main>

    <x-blocks.footer-columns />
</div>

Installation

terminal

php artisan ui:add pages/contact-page-split-map

Installs these dependencies automatically:

blocks/header-navbar blocks/contact-split blocks/contact-map blocks/footer-columns

Registry contract

Install confidence

php artisan ui:add pages/contact-page-split-map writes only the generated targets below. The CLI validates each file hash before writing and prompts before replacing local changes unless --force is used.

Version: 1.0.3
License: open
Stability: stable
Contract: v1
Foundation: ≥ 1.0.0

Type	Generated target
blade	resources/views/pages/contact-page-split-map.blade.php

Registry dependencies

blocks/header-navbar blocks/contact-split blocks/contact-map blocks/footer-columns

Package dependencies

composer: jml/brok:^0.2

Use with AI

A brief for your coding agent: what the page is, the install command, how to render it, its props and the rules. Copy it, or open a prompt about this page in an assistant.

contact-page-split-map.md

# Brok UI page: Contact Page (`contact-page-split-map`)

A full contact page composing a navbar, a split contact section with details and form, a map contact section and a footer.

Brok UI is a Laravel Blade registry. `ui:add` copies this page into the app as plain Blade the app owns; it composes installed `<brok:*>` primitives and semantic design tokens.

## Install

```bash
php artisan ui:add pages/contact-page-split-map
```

## Render it

```blade
<x-pages.contact-page-split-map />
```

## Use when

- A full contact page: a navbar, a split contact section with details and a form, a map contact section and a footer.
- It composes blocks/header-navbar, blocks/contact-split, blocks/contact-map and blocks/footer-columns.

## Avoid when

- Wanting a method-cards layout with an FAQ; use contact-page-method-cards instead. Wanting a centered navbar and compact contact strip; use contact-page-centered instead.

## Rules

- Render the installed page with `<x-pages.contact-page-split-map />` and pass data through its props; edit the copied file only for structural changes.
- Keep the semantic design tokens (`bg-background`, `text-muted-foreground`); never swap in raw colour utilities.
- Keep the `data-slot` attributes and the logical (start/end) spacing so the markup still mirrors under `dir="rtl"`.

## Links

- Docs: https://brokui.dev/pages/contact-page-split-map
- Registry JSON (files, props, contract): https://brokui.dev/r/open/pages/contact-page-split-map.json

Ask about Contact Page in

Working in Claude Code, Cursor or Codex? Give the agent the whole registry through the MCP server or the Brok UI skill.

Guidance

Use when

A full contact page: a navbar, a split contact section with details and a form, a map contact section and a footer.
It composes blocks/header-navbar, blocks/contact-split, blocks/contact-map and blocks/footer-columns.

Avoid when

Wanting a method-cards layout with an FAQ; use contact-page-method-cards instead. Wanting a centered navbar and compact contact strip; use contact-page-centered instead.

Anti-patterns

Do not replace semantic props with conflicting utility classes.
Do not remove labels, focus styles, or state attributes.

Usage

Render the page as a component, or wire it to a route. Pass data where useful:

resources/views/welcome.blade.php Blade

<x-pages.contact-page-split-map />

Built from blocks & primitives

This page composes installed <brok:*> primitives and semantic design tokens only — it does not reimplement any primitive. Re-theme it (light, dark, admin, customer) by editing CSS variables; flip the preview to RTL to confirm it mirrors.

Source

The exact, editable file ui:add writes into your app. The preview above renders this same source — there are no preview-only pages.