Integrations Page

Open source

Full integrations-directory pages — a directory grid, a logo-marquee layout, and a mega-menu split with orbit diagram.

resources/views/pages/integrations-page-marquee.blade.php Blade

@props([])

<div class="min-h-screen bg-background text-foreground">
    <x-blocks.header-navbar />
    <main>
        <x-blocks.integrations-grid />
        <x-blocks.integrations-marquee />
        <x-blocks.closing-cta-centered frame="none" />
    </main>
    <x-blocks.footer-columns />
</div>

Installation

terminal

php artisan ui:add pages/integrations-page-marquee

Installs these dependencies automatically:

blocks/header-navbar blocks/integrations-grid blocks/integrations-marquee blocks/closing-cta-centered blocks/footer-columns

Registry contract

Install confidence

php artisan ui:add pages/integrations-page-marquee 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/integrations-page-marquee.blade.php

Registry dependencies

blocks/header-navbar blocks/integrations-grid blocks/integrations-marquee blocks/closing-cta-centered 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.

integrations-page-marquee.md

# Brok UI page: Integrations Page 02 (`integrations-page-marquee`)

An integrations page with a navbar, an integration grid, a logo marquee, a centered CTA 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/integrations-page-marquee
```

## Render it

```blade
<x-pages.integrations-page-marquee />
```

## Use when

- An integrations page with a navbar, an integration grid, a logo marquee, a centered call-to-action and a footer.
- It composes blocks/header-navbar, blocks/integrations-grid, blocks/integrations-marquee, blocks/closing-cta-centered and blocks/footer-columns with default content.

## Avoid when

- Needing custom integration copy already filled in; use integrations-page-directory instead.

## Rules

- Render the installed page with `<x-pages.integrations-page-marquee />` 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/integrations-page-marquee
- Registry JSON (files, props, contract): https://brokui.dev/r/open/pages/integrations-page-marquee.json

Ask about Integrations Page 02 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

An integrations page with a navbar, an integration grid, a logo marquee, a centered call-to-action and a footer.
It composes blocks/header-navbar, blocks/integrations-grid, blocks/integrations-marquee, blocks/closing-cta-centered and blocks/footer-columns with default content.

Avoid when

Needing custom integration copy already filled in; use integrations-page-directory 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.integrations-page-marquee />

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.