project-portfolio 2.0.0 → 2.1.0

package/README.md

@@ -1,6 +1,6 @@
 # project-portfolio
 
-A suite of self-contained project portfolio components for Next.js App Router. Drop in a `clientSlug` and `apiBase` — each component fetches, caches, and renders everything on the server with zero client-side waterfall requests.
+A suite of self-contained project portfolio components for Next.js App Router. Drop in a `clientSlug` and `apiBase` — each component fetches, caches, and renders everything it needs with zero client-side waterfall requests.
 
 ## Requirements
 
@@ -17,39 +17,97 @@ npm install project-portfolio
 
 ---
 
-## Components
-
-### `ProjectPortfolio`
+## Quick Start
 
-A full project grid page. Fetches all projects for a client and renders them as responsive cards (1 column on mobile, 2 on tablet, 3 on desktop).
+Here is the most common full setup — a projects grid page, a detail page with similar projects, and a megamenu in the nav.
 
 ```tsx
 // app/projects/page.tsx
 import { ProjectPortfolio } from "project-portfolio"
 
-// Must be a Server Component — do NOT add "use client"
-export default async function ProjectsPage() {
+export default async function ProjectsPage({
+  searchParams,
+}: {
+  searchParams: { [key: string]: string | string[] | undefined }
+}) {
   return (
     <ProjectPortfolio
       clientSlug="your-client-slug"
       apiBase="https://your-api.com"
       basePath="/projects"
+      searchParams={searchParams}
     />
   )
 }
 ```
 
-| Prop | Type | Required | Default | Description |
-|---|---|---|---|---|
-| `clientSlug` | `string` | Yes | — | Identifies which client's projects to load |
-| `apiBase` | `string` | Yes | — | Base URL of the projects API |
-| `basePath` | `string` | No | `"/projects"` | Base path for project detail links |
-| `searchParams` | `Record<string, string \| string[] \| undefined>` | No | `{}` | Filter params forwarded to the API — pass Next.js `searchParams` directly |
-| `revalidate` | `number` | No | `60` | Cache revalidation period in seconds |
+```tsx
+// app/projects/[slug]/page.tsx
+import { ProjectDetail, SimilarProjects } from "project-portfolio"
+
+export default async function ProjectPage({ params }: { params: { slug: string } }) {
+  return (
+    <>
+      <ProjectDetail
+        slug={params.slug}
+        clientSlug="your-client-slug"
+        apiBase="https://your-api.com"
+        backPath="/projects"
+      />
+
+      {/* Hardcode the slugs you want shown — update per client request */}
+      <SimilarProjects
+        projectSlugs={[
+          "jacob-javits-convention-center",
+          "tillamook-bay-community-college",
+          "lcisd-liberty-hill-high-school",
+        ]}
+        excludeSlug={params.slug}
+        clientSlug="your-client-slug"
+        apiBase="https://your-api.com"
+        basePath="/projects"
+      />
+    </>
+  )
+}
+```
+
+```ts
+// app/api/chisel-menu/route.ts
+import { createMenuHandler } from "project-portfolio"
+
+export const GET = createMenuHandler({
+  clientSlug: "your-client-slug",
+  apiBase: "https://your-api.com",
+})
+```
+
+```tsx
+// components/Nav.tsx — "use client" component in your header
+"use client"
+import { ProjectMenuClient } from "project-portfolio"
+
+export function Nav() {
+  return (
+    <nav>
+      {/* ... other nav items ... */}
+      <ProjectMenuClient
+        dataUrl="/api/chisel-menu"
+        basePath="/projects"
+        viewAllPath="/projects"
+      />
+    </nav>
+  )
+}
+```
+
+---
 
-#### URL-driven filter integration
+## Components
+
+### `ProjectPortfolio`
 
-`ProjectPortfolio` works together with `ProjectMenu` to form a complete filter flow. When a user clicks a filter link in the megamenu, they are navigated to the project grid with filter query params appended to the URL. Pass Next.js `searchParams` to `ProjectPortfolio` so it can forward them to the API:
+A full server-rendered project grid page. Fetches all projects for a client and renders them as responsive baseball cards (1 column on mobile, 2 on tablet, 3 on desktop). Supports URL-driven filtering via `searchParams`.
 
 ```tsx
 // app/projects/page.tsx
@@ -71,12 +129,23 @@ export default async function ProjectsPage({
 }
 ```
 
+| Prop | Type | Required | Default | Description |
+|---|---|---|---|---|
+| `clientSlug` | `string` | Yes | — | Identifies which client's projects to load |
+| `apiBase` | `string` | Yes | — | Base URL of the projects API |
+| `basePath` | `string` | No | `"/projects"` | Base path for project detail links |
+| `searchParams` | `Record<string, string \| string[] \| undefined>` | No | `{}` | Filter params forwarded to the API — pass Next.js `searchParams` directly |
+| `revalidate` | `number` | No | `86400` | Cache revalidation period in seconds (24 hours) |
+
+#### URL-driven filtering
+
+When a user clicks a "Browse By" filter link in the menu, they land on the grid with query params in the URL. Pass `searchParams` from the page and `ProjectPortfolio` forwards them to the API automatically.
+
 Filter URLs follow this pattern — the key matches the custom field key in the schema:
 
 ```
-/projects?type=commercial
-/projects?type=educational-facilities
-/projects?system=spacematic
+/projects?filter[type]=commercial
+/projects?filter[type]=educational-facilities
 ```
 
 When active filters are applied, a filter banner is shown above the grid with a "Clear filters" link back to `basePath`.
@@ -85,7 +154,7 @@ When active filters are applied, a filter banner is shown above the grid with a
 
 ### `ProjectPortfolioClient`
 
-A `"use client"` component that fetches all projects once on mount (module-level cached — no re-fetch on remount) and filters them locally in memory. It ships with **no filter UI** — build your own dropdowns, buttons, or search inputs and drive the component with the `filters` prop.
+A `"use client"` version of the project grid. Fetches all projects once on mount (module-level cached — no re-fetch on remount) and filters them locally in memory. Use this when you need the grid inside a client component tree, or when you want to build your own custom filter UI.
 
 ```tsx
 // Works in any component — no RSC required
@@ -102,7 +171,9 @@ export default function ProjectsPage() {
 }
 ```
 
-Wire up your own filter UI with the `filters` prop:
+#### With a custom filter UI
+
+Wire up your own dropdowns, buttons, or search inputs using the `filters` prop. Filter changes are instant — no API call on each change, all filtering happens in memory.
 
 ```tsx
 "use client"
@@ -121,7 +192,6 @@ export default function ProjectsPage() {
         <option value="educational-facilities">Educational</option>
       </select>
 
-      {/* Component receives filters and applies them in memory */}
       <ProjectPortfolioClient
         clientSlug="your-client-slug"
         apiBase="https://your-api.com"
@@ -142,19 +212,16 @@ export default function ProjectsPage() {
 | `columns` | `2 \| 3` | No | `3` | Number of columns in the project grid |
 | `font` | `string` | No | System font stack | Font family string applied to all text |
 
-**How filtering works:** Pass any `Record<string, string>` of field key/value pairs and the component filters the already-fetched project list in memory. All filter logic uses AND matching with case-insensitive comparison. The field keys must match the custom field keys in the API schema.
-
 ---
 
 ### `ProjectDetail`
 
-A full project detail page. Fetches a single project by slug and renders its gallery, custom fields, related projects, and a back link.
+A full server-rendered project detail page. Fetches a single project by slug and renders its image gallery, custom fields, and a back link.
 
 ```tsx
 // app/projects/[slug]/page.tsx
 import { ProjectDetail } from "project-portfolio"
 
-// Must be a Server Component — do NOT add "use client"
 export default async function ProjectPage({ params }: { params: { slug: string } }) {
   return (
     <ProjectDetail
@@ -175,51 +242,52 @@ export default async function ProjectPage({ params }: { params: { slug: string }
 | `apiBase` | `string` | Yes | — | Base URL of the projects API |
 | `backPath` | `string` | No | `"/projects"` | Path for the back navigation link |
 | `backLabel` | `string` | No | `"All Projects"` | Label for the back navigation link |
-| `revalidate` | `number` | No | `60` | Cache revalidation period in seconds |
+| `revalidate` | `number` | No | `86400` | Cache revalidation period in seconds (24 hours) |
 
 ---
 
-### `ProjectMenu`
+### `GalleryCarousel`
 
-A compact megamenu component. Shows featured projects as list-style cards on the left and "Browse By" filter links on the right. Designed to be dropped directly into a navigation megamenu dropdown.
+A `"use client"` image carousel with previous/next arrows, a counter badge, and a scrollable thumbnail strip. Used internally by `ProjectDetail` but can also be used standalone if you fetch your own project data.
 
 ```tsx
-// components/navigation/MegaMenu.tsx
-import { ProjectMenu } from "project-portfolio"
+"use client"
+import { GalleryCarousel } from "project-portfolio"
 
-// Must be a Server Component — do NOT add "use client"
-export async function ProjectsMegaMenu() {
+// `media` is the array of image objects returned by the projects API
+export function ProjectGallery({ media, title }: { media: Media[]; title: string }) {
   return (
-    <ProjectMenu
-      clientSlug="your-client-slug"
-      apiBase="https://your-api.com"
-      basePath="/projects"
-      subtitle="Our systems are installed in every geographic region of the U.S. and in a variety of applications."
-      maxProjects={6}
+    <GalleryCarousel
+      images={media}
+      projectTitle={title}
     />
   )
 }
 ```
 
+The parent component is responsible for injecting the `.chisel-gallery-main-img` CSS class to control the main image height:
+
+```css
+.chisel-gallery-main-img {
+  height: 400px; /* adjust to your layout */
+}
+@media (min-width: 768px) {
+  .chisel-gallery-main-img {
+    height: 560px;
+  }
+}
+```
+
 | Prop | Type | Required | Default | Description |
 |---|---|---|---|---|
-| `clientSlug` | `string` | Yes | — | Identifies which client's projects to load |
-| `apiBase` | `string` | Yes | — | Base URL of the projects API |
-| `basePath` | `string` | No | `"/projects"` | Base path for project detail links |
-| `viewAllPath` | `string` | No | Same as `basePath` | Path for the "View All Projects" link |
-| `subtitle` | `string` | No | — | Description paragraph shown above the project cards |
-| `font` | `string` | No | System font stack | Font family string applied to all inline styles |
-| `maxProjects` | `number` | No | `6` | Maximum number of projects to display |
-| `revalidate` | `number` | No | `86400` | Cache revalidation period in seconds (24 hours) |
-| `noCache` | `boolean` | No | `false` | Disable caching entirely — useful for development |
-
-The filter options in the right sidebar are driven automatically by the `is_filterable` fields returned from the API schema — no manual configuration needed.
+| `images` | `Media[]` | Yes | — | Array of media objects from the projects API |
+| `projectTitle` | `string` | Yes | — | Used as the alt text fallback for the main image |
 
 ---
 
 ### `SimilarProjects`
 
-A standalone similar projects section. Fetches all projects for a client, filters to the same type as the current project, and renders up to 3 matching cards. Designed to be placed after `ProjectDetail` on a project detail page.
+A server-rendered similar projects section. Fetches all projects for a client, filters to those matching the provided field values, excludes the current project, and renders up to 3 matching results. Designed to be placed after `ProjectDetail` on a project detail page.
 
 ```tsx
 // app/projects/[slug]/page.tsx
@@ -245,32 +313,176 @@ export default async function ProjectPage({ params }: { params: { slug: string }
 }
 ```
 
-`filters` accepts any combination of custom field key/value pairs — all must match (AND logic). `excludeSlug` optionally removes the current project from results.
+#### Deriving filters from the current project
+
+In most real-world cases you want to match similar projects based on the current project's own field values. Fetch the project first, then pass its field values as filters:
+
+```tsx
+// app/projects/[slug]/page.tsx
+import { ProjectDetail, SimilarProjects } from "project-portfolio"
+
+async function getProject(slug: string, clientSlug: string, apiBase: string) {
+  const res = await fetch(
+    `${apiBase}/api/v1/clients/${clientSlug}/projects/${slug}?api_key=YOUR_API_KEY`,
+    { next: { revalidate: 86400 } }
+  )
+  return res.ok ? (await res.json())?.data : null
+}
+
+export default async function ProjectPage({ params }: { params: { slug: string } }) {
+  const project = await getProject(params.slug, "your-client-slug", "https://your-api.com")
+  const projectType = project?.custom_field_values?.type ?? null
+
+  return (
+    <>
+      <ProjectDetail slug={params.slug} clientSlug="your-client-slug" apiBase="https://your-api.com" />
+      {projectType && (
+        <SimilarProjects
+          filters={{ type: projectType }}
+          excludeSlug={params.slug}
+          clientSlug="your-client-slug"
+          apiBase="https://your-api.com"
+          basePath="/projects"
+        />
+      )}
+    </>
+  )
+}
+```
+
+#### Manually specifying projects (recommended for quick setup)
+
+Pass `projectSlugs` to hand-pick exactly which projects appear, in the order you specify. This overrides `filters` entirely — useful when you want to curate the section rather than rely on field matching, or when you need a reliable result quickly without worrying about field values matching.
+
+This is the recommended approach for most client sites. The slugs are hardcoded in the page file. If a client wants different projects shown, update the slugs and redeploy.
+
+```tsx
+// app/projects/[slug]/page.tsx
+import { ProjectDetail, SimilarProjects } from "project-portfolio"
+
+export default async function ProjectPage({ params }: { params: { slug: string } }) {
+  return (
+    <>
+      {/* All your other page content above */}
+      <ProjectDetail
+        slug={params.slug}
+        clientSlug="your-client-slug"
+        apiBase="https://your-api.com"
+        backPath="/projects"
+      />
+
+      {/* Similar projects hardcoded — update slugs per client request */}
+      <SimilarProjects
+        projectSlugs={[
+          "jacob-javits-convention-center",
+          "tillamook-bay-community-college",
+          "lcisd-liberty-hill-high-school",
+        ]}
+        excludeSlug={params.slug}
+        clientSlug="your-client-slug"
+        apiBase="https://your-api.com"
+        basePath="/projects"
+      />
+    </>
+  )
+}
+```
+
+> `excludeSlug` is still respected even in `projectSlugs` mode — if the current page's slug appears in the list it is automatically removed so a project never links to itself.
+
+To update which projects appear, find the `projectSlugs` array in the page file and swap in the new slugs. Project slugs are visible in the URL when browsing the portfolio: `/projects/jacob-javits-convention-center` → slug is `jacob-javits-convention-center`.
+
+#### Card variant
+
+Use `variant="card"` to render the same baseball-card style used in `ProjectPortfolio` instead of the default list style:
+
+```tsx
+<SimilarProjects
+  filters={{ type: "commercial" }}
+  excludeSlug={params.slug}
+  clientSlug="your-client-slug"
+  apiBase="https://your-api.com"
+  basePath="/projects"
+  variant="card"
+/>
+```
 
 | Prop | Type | Required | Default | Description |
 |---|---|---|---|---|
+| `clientSlug` | `string` | Yes | — | Identifies which client's projects to load |
+| `apiBase` | `string` | Yes | — | Base URL of the projects API |
 | `filters` | `Record<string, string>` | No | `{}` | Key/value pairs to filter projects by custom field values. All filters must match (AND logic) |
 | `excludeSlug` | `string` | No | — | Slug of a project to exclude from results (e.g. the current project) |
+| `basePath` | `string` | No | `"/projects"` | Base path for project detail links |
+| `projectSlugs` | `string[]` | No | — | Explicit list of project slugs to show, in order. When provided, overrides `filters` entirely. e.g. `["jacob-javits", "tillamook-bay"]` |
+| `maxItems` | `number` | No | `3` | Maximum number of projects to show |
+| `variant` | `"list" \| "card"` | No | `"list"` | `"list"` uses the border-bottom separator style; `"card"` renders full baseball-card style matching `ProjectPortfolio` |
+| `font` | `string` | No | System font stack | Font family string applied to all inline styles |
+| `revalidate` | `number` | No | `86400` | Cache revalidation period in seconds (24 hours) |
+
+---
+
+### `ProjectMenu`
+
+A server-rendered megamenu component. Shows featured projects as compact cards on the left and "Browse By" filter links on the right. Designed to be dropped directly into a navigation dropdown.
+
+```tsx
+// components/MegaMenu.tsx
+import { ProjectMenu } from "project-portfolio"
+
+// Must be a Server Component — do NOT add "use client"
+export async function ProjectsMegaMenu() {
+  return (
+    <ProjectMenu
+      clientSlug="your-client-slug"
+      apiBase="https://your-api.com"
+      basePath="/projects"
+      subtitle="Our systems are installed in every geographic region of the U.S."
+      maxProjects={6}
+    />
+  )
+}
+```
+
+#### With a curated menu
+
+Pass `menuId` to show a specific curated set of projects instead of all projects. The Browse By filters on the right always reflect the full schema regardless of which menu is active. Available menu IDs can be retrieved from `GET /api/v1/clients/{clientSlug}/menus`.
+
+```tsx
+<ProjectMenu
+  clientSlug="your-client-slug"
+  apiBase="https://your-api.com"
+  menuId="main-nav"
+  basePath="/projects"
+/>
+```
+
+| Prop | Type | Required | Default | Description |
+|---|---|---|---|---|
 | `clientSlug` | `string` | Yes | — | Identifies which client's projects to load |
 | `apiBase` | `string` | Yes | — | Base URL of the projects API |
+| `menuId` | `string` | No | — | ID of a curated menu. When provided, fetches from `/menus/{menuId}` instead of all projects. Filters always shown regardless. |
 | `basePath` | `string` | No | `"/projects"` | Base path for project detail links |
-| `maxItems` | `number` | No | `3` | Maximum number of projects to show |
+| `viewAllPath` | `string` | No | Same as `basePath` | Path for the "View All Projects" link |
+| `subtitle` | `string` | No | — | Description paragraph shown above the project cards |
 | `font` | `string` | No | System font stack | Font family string applied to all inline styles |
-| `revalidate` | `number` | No | `60` | Cache revalidation period in seconds |
+| `maxProjects` | `number` | No | `6` | Maximum number of projects to display |
+| `revalidate` | `number` | No | `86400` | Cache revalidation period in seconds (24 hours) |
+| `noCache` | `boolean` | No | `false` | Disable caching entirely — useful for development |
 
 ---
 
 ### `ProjectMenuClient` + `createMenuHandler`
 
-`ProjectMenuClient` is a `"use client"` component that works in any React tree — no RSC, no `Suspense` wrapper, no server file needed. It fetches its own data and caches it in memory for the lifetime of the page session so the API is never called twice on a hover/re-hover.
+`ProjectMenuClient` is a `"use client"` megamenu component. Use it when your nav or header is a client component. It fetches and caches data on first mount so the API is never called twice on re-hover or remount.
 
-There are two ways to use it:
+There are two ways to set it up:
 
 ---
 
-**Option 1 — `dataUrl` + `createMenuHandler` (recommended for production)**
+#### Option 1 — `dataUrl` + `createMenuHandler` (recommended for production)
 
-Set up one API route once. The data is server-cached for 24 hours — most users never trigger a call to the upstream API at all.
+Create one API route once. The data is server-cached for 24 hours — most users never trigger a call to the upstream API at all.
 
 ```ts
 // app/api/chisel-menu/route.ts
@@ -282,29 +494,66 @@ export const GET = createMenuHandler({
 })
 ```
 
+For a curated menu, pass `menuId` to the handler:
+
+```ts
+// app/api/chisel-menu/route.ts
+export const GET = createMenuHandler({
+  clientSlug: "your-client-slug",
+  apiBase: "https://your-api.com",
+  menuId: "main-nav",
+})
+```
+
+Then pass `dataUrl` to the component:
+
 ```tsx
-// In your nav/header — works in any "use client" component
+// components/Nav.tsx
+"use client"
 import { ProjectMenuClient } from "project-portfolio"
 
-<ProjectMenuClient
-  dataUrl="/api/chisel-menu"
-  basePath="/projects"
-  viewAllPath="/projects"
-/>
+export function Nav() {
+  return (
+    <ProjectMenuClient
+      dataUrl="/api/chisel-menu"
+      basePath="/projects"
+      viewAllPath="/projects"
+      subtitle="Explore our portfolio of projects."
+      maxProjects={6}
+    />
+  )
+}
 ```
 
 ---
 
-**Option 2 — Direct fetch (quick setup / non-Next.js environments)**
+#### Option 2 — Direct fetch (quick setup / non-Next.js environments)
 
-No API route needed. The component fetches directly from the upstream API on first mount and caches the result in memory for the session.
+No API route needed. The component fetches directly from the upstream API on first mount and caches the result in memory for the session. Note: this exposes the API call to the client browser.
 
 ```tsx
+"use client"
 import { ProjectMenuClient } from "project-portfolio"
 
+export function Nav() {
+  return (
+    <ProjectMenuClient
+      clientSlug="your-client-slug"
+      apiBase="https://your-api.com"
+      basePath="/projects"
+      viewAllPath="/projects"
+    />
+  )
+}
+```
+
+With a curated menu:
+
+```tsx
 <ProjectMenuClient
   clientSlug="your-client-slug"
   apiBase="https://your-api.com"
+  menuId="main-nav"
   basePath="/projects"
   viewAllPath="/projects"
 />
@@ -314,22 +563,23 @@ import { ProjectMenuClient } from "project-portfolio"
 
 | Prop | Type | Required | Default | Description |
 |---|---|---|---|---|
-| `dataUrl` | `string` | No | — | URL of a local API route created with `createMenuHandler()`. Recommended for production |
+| `dataUrl` | `string` | No* | — | URL of a local API route created with `createMenuHandler()`. Recommended for production |
 | `clientSlug` | `string` | No* | — | Client slug for direct fetch mode |
 | `apiBase` | `string` | No* | — | API base URL for direct fetch mode |
+| `menuId` | `string` | No | — | ID of a curated menu. Fetches from `/menus/{menuId}` for projects. Filters are always shown regardless. |
 | `basePath` | `string` | Yes | — | Base path for project detail links |
 | `viewAllPath` | `string` | Yes | — | Path for the "View All Projects" link |
-| `subtitle` | `string` | No | — | Description shown above the project cards |
+| `subtitle` | `string` | No | — | Description shown above the project cards (hidden on mobile) |
 | `font` | `string` | No | System font stack | Font family string |
-| `maxProjects` | `number` | No | `6` | Maximum number of projects to display |
+| `maxProjects` | `number` | No | `6` | Maximum number of projects to display (capped at 3 on mobile) |
 
-*One of `dataUrl` or `clientSlug + apiBase` must be provided. Pre-fetched `projects`, `schema`, `filterOptions`, `filterFieldKey`, and `fieldOptionsMap` can also be passed directly for SSR usage.
+*One of `dataUrl` or `clientSlug + apiBase` must be provided.
 
 ---
 
-## Important: Server Component Usage
+## Server vs Client Components
 
-All top-level components (`ProjectPortfolio`, `ProjectDetail`, `ProjectMenu`, `SimilarProjects`) are **async Server Components**. They must be rendered in a server context:
+All top-level components except `ProjectMenuClient`, `ProjectPortfolioClient`, and `GalleryCarousel` are **async Server Components**. They must be rendered in a server context:
 
 ```tsx
 // CORRECT
@@ -337,58 +587,63 @@ export default async function Page() {
   return <ProjectPortfolio clientSlug="..." apiBase="..." />
 }
 
-// WRONG — causes infinite client-side fetch loop
+// WRONG — causes a runtime error
 "use client"
 export default function Page() {
   return <ProjectPortfolio clientSlug="..." apiBase="..." />
 }
 ```
 
-If a parent component uses `"use client"`, these components cannot be rendered inside it directly. Pass them as children from a server component instead.
+If your parent component uses `"use client"`, use the client variants instead (`ProjectMenuClient`, `ProjectPortfolioClient`) or pass the server components as `children` from a server parent.
+
+| Component | Type | Use when |
+|---|---|---|
+| `ProjectPortfolio` | Server | Page-level grid, URL-driven filters |
+| `ProjectPortfolioClient` | Client | Inside a client tree, custom filter UI |
+| `ProjectDetail` | Server | Project detail page |
+| `GalleryCarousel` | Client | Standalone image gallery |
+| `ProjectMenu` | Server | Server-rendered nav dropdown |
+| `ProjectMenuClient` | Client | Client-rendered nav/header |
+| `SimilarProjects` | Server | After `ProjectDetail` on detail pages |
 
 ---
 
 ## Caching
 
-Data is cached at multiple levels depending on which component is used.
-
-**Server Components (`ProjectMenu`, `ProjectPortfolio`, `ProjectDetail`, `SimilarProjects`)**
-1. **Per-render** — `React.cache()` deduplicates duplicate calls within the same render pass
-2. **Cross-request** — `next: { revalidate: 86400 }` (24 hours) caches responses in Next.js's Data Cache across all users and sessions
-
-**`ProjectMenuClient` with `createMenuHandler` (recommended)**
-3. **Server-side route cache** — the `/api/chisel-menu` route is cached by Next.js for 24 hours. The upstream API is called at most once per day regardless of traffic
-4. **Module-level client cache** — after the first fetch within a session, the result is held in memory. Re-hovering the menu or remounting the component never triggers another network request
-
-**`ProjectMenuClient` with direct fetch / `ProjectPortfolioClient`**
-4. **Module-level client cache only** — the upstream API is called once per session per user (on first mount), then cached in memory for the rest of that page session. Filter changes on `ProjectPortfolioClient` never trigger a fetch — filtering is done entirely in memory
+| Component | Server Cache | Client Cache |
+|---|---|---|
+| `ProjectMenu` (RSC) | 24h via `next.revalidate` | — |
+| `ProjectMenuClient` + `createMenuHandler` | 24h (route handler) | Per-session module cache |
+| `ProjectMenuClient` (direct fetch) | None | Per-session module cache |
+| `ProjectPortfolio` (RSC) | 24h via `next.revalidate` | — |
+| `ProjectPortfolioClient` | None | Per-session module cache |
+| `ProjectDetail` (RSC) | 24h via `next.revalidate` | — |
+| `SimilarProjects` (RSC) | 24h via `next.revalidate` | — |
 
-**Bypassing the cache**
+#### Bypassing the cache
 
 | Method | Scope | Use case |
 |---|---|---|
 | `?bust=1` on `/api/chisel-menu` | Single request | Dev/testing after a CMS change |
 | `CHISEL_CACHE_BYPASS=true` env var | Entire deployment | Staging environments |
-| `revalidateTag("chisel-menu-{clientSlug}")` | Server cache only | CMS webhook on content publish |
+| `revalidateTag("chisel-menu-{clientSlug}")` | Server cache | CMS webhook on content publish |
 | `noCache: true` on `ProjectMenu` | Single render | Debug during development |
 
 ```ts
-// CMS webhook example — invalidate server cache immediately on publish
+// CMS webhook — invalidate server cache on publish
 import { revalidateTag } from "next/cache"
 revalidateTag("chisel-menu-your-client-slug")
-```
 
-No third-party caching libraries are required.
+// For a curated menu, the tag includes the menuId
+revalidateTag("chisel-menu-your-client-slug-main-nav")
+```
 
 ---
 
 ## Publishing to npm
 
 ```bash
-# Log in to npm
 npm login
-
-# Build and publish
 cd package
 npm run build
 npm publish --access public

package/dist/GalleryCarousel.d.ts

@@ -1,6 +1,7 @@
 import type { Media } from "./types";
-export declare function GalleryCarousel({ images, projectTitle, }: {
+export interface GalleryCarouselProps {
     images: Media[];
     projectTitle: string;
-}): import("react/jsx-runtime").JSX.Element | null;
+}
+export declare function GalleryCarousel({ images, projectTitle, }: GalleryCarouselProps): import("react/jsx-runtime").JSX.Element | null;
 //# sourceMappingURL=GalleryCarousel.d.ts.map