FAQ Page

Open source

Full help/FAQ pages — a split accordion, a searchable grid, and grouped categories, each with a contact card.

1 of 3

resources/views/pages/faq-page-split.blade.php Blade

@props([])

{{-- Help / FAQ page — composes existing marketing blocks into a full screen. --}}
@php
    $faqs = [
        ['question' => 'How do I get started?', 'answer' => 'Create a free workspace, invite your team, and connect your first data source. Most teams are up and running in under ten minutes — no credit card required to explore.'],
        ['question' => 'Can I change or cancel my plan anytime?', 'answer' => 'Yes. Upgrade, downgrade, or cancel from your billing settings at any time. Changes take effect on your next billing cycle and we prorate automatically.'],
        ['question' => 'Where is my data stored and is it secure?', 'answer' => 'Data is encrypted in transit and at rest, hosted in regional data centers, and backed by SOC 2 controls. You can export or delete everything on demand.'],
        ['question' => 'Do you offer single sign-on (SSO)?', 'answer' => 'SSO via SAML and SCIM provisioning is available on the Business and Enterprise plans, alongside enforced 2FA and granular role-based access.'],
        ['question' => 'What kind of support is included?', 'answer' => 'Every plan includes email and in-app chat support. Business plans add priority response times, and Enterprise customers get a dedicated success manager.'],
        ['question' => 'Can I migrate from another tool?', 'answer' => 'We provide guided imports for the most common platforms plus a CSV importer. Our team will happily help map and validate your data before you go live.'],
    ];

    $contactDetails = [
        ['label' => 'Support email', 'value' => 'help@example.com', 'href' => 'mailto:help@example.com'],
        ['label' => 'Sales & billing', 'value' => '+1 (555) 010-2040', 'href' => 'tel:+15550102040'],
        ['label' => 'Status page', 'value' => 'status.example.com', 'href' => '#'],
    ];
@endphp

<div class="min-h-screen bg-background text-foreground">
    <x-blocks.header-navbar />

    <main>
        <x-blocks.faq-split
            eyebrow="Help Center"
            heading="How can we help?"
            subheading="Browse the most common questions about plans, security, and getting set up. Still stuck? Our support team typically replies within a few hours."
            supportCta="Email support"
            supportHref="mailto:help@example.com"
            :items="$faqs"
        />

        <x-blocks.contact-split
            :icons="false"
            heading="Still have questions?"
            subheading="Send us a message and a real human will get back to you within one business day."
            :details="$contactDetails"
        />
    </main>

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

Installation

terminal

php artisan ui:add pages/faq-page-split

Installs these dependencies automatically:

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

Registry contract

Install confidence

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

Registry dependencies

blocks/header-navbar blocks/faq-split blocks/contact-split 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.

faq-page-split.md

# Brok UI page: FAQ Page (`faq-page-split`)

A full help/FAQ page composing a navbar, a split FAQ accordion, a 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/faq-page-split
```

## Render it

```blade
<x-pages.faq-page-split />
```

## Use when

- A full help/FAQ page: a navbar, a split FAQ accordion, a contact section and a footer.
- It composes blocks/header-navbar, blocks/faq-split, blocks/contact-split and blocks/footer-columns.

## Avoid when

- Wanting a searchable multi-section FAQ layout; use faq-page-searchable instead. Wanting grouped FAQ categories; use faq-page-grouped instead.

## Rules

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

Ask about FAQ 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 help/FAQ page: a navbar, a split FAQ accordion, a contact section and a footer.
It composes blocks/header-navbar, blocks/faq-split, blocks/contact-split and blocks/footer-columns.

Avoid when

Wanting a searchable multi-section FAQ layout; use faq-page-searchable instead. Wanting grouped FAQ categories; use faq-page-grouped 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.faq-page-split />

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.