PartnersSection
Introduce partner organizations with logos, descriptions, categories, featured placements, and website links.
PartnersSection uses the reusable UI logo collection to present a network of collaborators. Partner names remain visible when logo data is missing.
Beta API maturity: Beta.
Installation
import {
PartnersSection,
type BusinessPartner,
type PartnersSectionVariant,
} from "@puzzle-ui/pieces";Variant previews
All ten variants have an individual preview, with fictional partners from creative, technology, and hospitality contexts.
grid - Show partner details in a responsive grid.
logo-wall - Let partner identities form a logo wall.
featured - Put a featured partner first.
categories - Group partner organizations by category.
cards - Include a short description for each partner.
network - Present a broad ecosystem of collaborators.
split - Use an even two-column partner layout.
carousel - Browse partner logos in a scrollable rail.
ecosystem - Show the role each partner plays.
minimal - Keep the partner presentation understated.
API
| Prop | Type | Description |
|---|---|---|
variant | PartnersSectionVariant | grid (default), logo-wall, featured, categories, cards, network, split, carousel, ecosystem, or minimal. |
items | readonly BusinessPartner[] | Partners with unique IDs and names; optional image, description, category, website link, and featured state. |
featuredPartner | BusinessPartner | string | Optional partner object or ID moved to the lead position. |
BusinessPartner.external | boolean | Opens a partner website in a new context with noopener noreferrer. |
| Shared section props | MarketingSectionBaseProps | Heading, actions, root element, native section attributes, and children. |
Required and default values
Requiredness follows the exported TypeScript type. A dash means no component-level default is applied; variant-specific requirements are described in the API table above.
| Prop | Required | Default |
|---|---|---|
variant | No | "grid" |
items | Yes | — |
featuredPartner | No | — |
Usage
<PartnersSection
variant="categories"
title="Our partners"
items={[
{
id: "fieldwork",
name: "Fieldwork Studio",
description: "Independent brand and digital studio.",
category: "Creative",
href: "https://example.com/fieldwork",
external: true,
},
]}
/>Accessibility and rendering
Logo collections are labeled lists. Supply informative alternative text for logos; when an image is unavailable, the partner name is shown instead. The carousel variant is keyboard-focusable and uses native horizontal scrolling. Links are native anchors and external links are protected with noopener noreferrer. The component does not fetch partner data and renders on the server.
Customization
Use the component's className and documented slots to adapt the composition. Prefer a caller-provided ReactNode for media, actions, or controls rather than adding domain behavior to the section.
import type { ComponentProps } from "react";
import { PartnersSection } from "@puzzle-ui/pieces";
type PartnersSectionProps = ComponentProps<typeof PartnersSection>;
export function CustomizedSection(props: PartnersSectionProps) {
return <PartnersSection {...props} className={[props.className, "brand-section"].filter(Boolean).join(" ")} />;
}Responsive behavior
Use the preview device selector to review mobile, tablet, and desktop widths. The built-in variant controls section structure; ensure application-provided media, form controls, and children can shrink or wrap without horizontal overflow. Use the existing responsive breakpoints in scoped CSS when the consuming layout needs a product-specific adjustment.
Theme support
The section consumes semantic variables from @puzzle-ui/theme and inherits active or scoped themes. Wrap the application with Theme, and use semantic roles such as text, surface, border, and primary for local overrides. Avoid hard-coded colors, spacing, radii, and shadows.
.brand-section {
color: var(--puzzle-color-text);
background: var(--puzzle-color-surface);
border-color: var(--puzzle-color-border);
}Composition
Compose this section with the UI primitives named in its API and use the documented slots for consumer-owned controls or media. Keep data fetching, routing, validation, permissions, and persistence in the application. The children slot is intended for additional content that belongs with this section, not as a substitute for its typed data model.
TypeScript example
The package exports this component from its root. Derive a wrapper's exact prop type from the public component rather than widening it:
import type { ComponentProps } from "react";
import { PartnersSection } from "@puzzle-ui/pieces";
type PartnersSectionProps = ComponentProps<typeof PartnersSection>;
export function SectionWrapper(props: PartnersSectionProps) {
return <PartnersSection {...props} />;
}Framework compatibility
The section is router-independent. Static compositions can be server-rendered; place callback-driven interactions in the framework's client boundary. See Next.js and TanStack Start integration for runnable framework examples and SSR guidance.