import { type ElementType, type ReactElement, type ReactNode } from "react";
import type { NavTree } from "../../docs/types.js";
/**
 * Props for {@link DocsSidebar}.
 */
export interface DocsSidebarProps {
    /** The navigation tree for the current language (from `docs.getNavTree(lang)`). */
    nav: NavTree;
    /**
     * The current page's URL path (e.g. from Next's `usePathname()`), matched against each item's
     * `href` to highlight the active page and pick which tab's groups to show. Omit on a page with no
     * active item (e.g. the index), where the first tab is shown.
     */
    activePath?: string | undefined;
    /** The render language, used to localize the built-in nav label. */
    lang?: string | undefined;
    /** Element used for nav links. Defaults to `"a"`; pass `next/link` for client-side nav. */
    linkComponent?: ElementType;
    /** Accessible label for the `<nav>` and the mobile toggle text. Defaults to the `lang` translation of "Documentation". */
    label?: string | undefined;
    /**
     * Optional override for how a page's `icon` name is rendered. Receives the front-matter `icon`
     * value (or `undefined`) and returns the icon node. Defaults to the built-in icon set.
     */
    renderIcon?: ((name: string | undefined) => ReactNode) | undefined;
    /**
     * Extra content pinned below the nav groups - the drawer's footer. Meant for the chrome the top
     * bar cannot fit on a phone: a language picker, a theme toggle, a secondary link.
     *
     * SHOWN BY THE KIT'S OWN STYLESHEET, and only when the top bar has given up on the controls: on
     * a phone, or at any width where `DocsNavbar` measures itself too narrow to hold its `actions`
     * (it sets `data-cramped`, and the same rule that hides them there reveals this). So pass the
     * SAME nodes to both slots and let the stylesheet pick - exactly one copy is ever displayed.
     *
     * Which also means you should NOT hide your content here behind your own class: hiding the CHILD
     * leaves this slot's border and margin behind as an empty ruled box under the nav.
     */
    footer?: ReactNode;
    /**
     * The brand lockup for the DRAWER's header - normally the same logo + name you give
     * `DocsNavbar`. Falls back to {@link DocsSidebarProps.label} (the word "Documentation") when
     * omitted.
     *
     * Worth passing: an open drawer covers the left of the screen including the top bar, so it is
     * the only thing the reader can see, and a lockup is what tells them whose docs they are in.
     * Ignored outside drawer mode, where the navbar's own brand is still on screen.
     */
    brand?: ReactNode;
    /**
     * Whether the drawer carries a search field above the nav groups. Defaults to `true`.
     *
     * Drawer-only - it never appears in the desktop sidebar column, where the navbar's own search
     * box is already on screen. Requires a {@link import("./DocsSearchProvider.js").DocsSearchProvider}
     * like the rest of drawer mode.
     */
    showSearch?: boolean | undefined;
    /** Placeholder for the drawer's search field. Defaults to the `lang` translation. */
    searchPlaceholder?: string | undefined;
}
/**
 * The docs left navigation: the ordered groups of pages for the active tab (the tab that owns the
 * current page, from `activePath`), with the active page highlighted. The top-level tab switcher is
 * {@link import("./DocsTabs.js").DocsTabs} and search is the ⌘K palette owned by
 * {@link import("./DocsSearchProvider.js").DocsSearchProvider}; navigating to a page in another tab
 * swaps these groups automatically.
 *
 * A client component (the drawer needs state). It receives the already-computed, serialisable
 * `NavTree` from a server component; links use your `linkComponent` for client-side navigation.
 *
 * BELOW THE LAYOUT BREAKPOINT it becomes an off-canvas DRAWER opened by the hamburger in
 * {@link import("./DocsNavbar.js").DocsNavbar} - which is why it must sit under the same
 * {@link import("./DocsSearchProvider.js").DocsSearchProvider} as the navbar (it already wraps the
 * whole docs app, so this needs no wiring). Rendered WITHOUT that provider it falls back to its
 * original self-contained inline toggle, so a standalone consumer still has a way to reach the nav.
 *
 * @param props - see {@link DocsSidebarProps}.
 * @returns the sidebar `<aside>`.
 */
export declare function DocsSidebar({ nav, activePath, lang, linkComponent: Link, label, renderIcon, footer, brand, showSearch, searchPlaceholder, }: DocsSidebarProps): ReactElement;