import "./page_header.css";
import type * as React from "react";
import type { ReactNode } from "react";
import { useRender } from "@base-ui/react/use-render";
import { type StyleProps } from "./style_props";
export interface PageHeaderProps extends StyleProps {
    /** The page's name. Optional only so the SHELL can delegate to this component
     *  for a band that is description-only; a page header normally has one. */
    title?: string;
    description?: string | null;
    /** The nav row ABOVE the title — breadcrumbs, a back control, row-level status. */
    left?: ReactNode;
    /** The nav row ABOVE the title, right-aligned. */
    right?: ReactNode;
    /**
     * A control that belongs to the TITLE, rendered immediately AFTER it on the
     * title row — a panel toggle, a view switch, anything that reframes the page
     * rather than acting on it.
     *
     * The distinction from `actions` is what the control acts ON, not where it
     * looks best. `actions` are things you do to the page's CONTENT (create, sort,
     * export) and collect at the far right, where a scanning eye reaches them
     * last; `trailing` changes what is AROUND the content and stays with the title
     * it qualifies, so it is read as part of the heading rather than as one more
     * thing you can do to your list.
     *
     * It sits AFTER the title, not before, because the title is the page's first
     * word and nothing should come between the reader and it — a control ahead of
     * the heading makes the eye parse chrome before it learns where it is.
     */
    trailing?: ReactNode;
    /** Page-level actions (CTAs), rendered on the title row, right-aligned —
     *  distinct from `left`/`right`, which form a separate nav row above. */
    actions?: ReactNode;
    testID?: string;
    ref?: React.Ref<HTMLElement>;
    render?: useRender.RenderProp;
}
export declare function PageHeader(props: PageHeaderProps): React.ReactElement<unknown, string | React.JSXElementConstructor<any>>;