alinea 2.0.0-preview.12 → 2.0.0-preview.13

package/dist/picker/url/UrlPicker.js

@@ -38,6 +38,7 @@ function urlPicker(options) {
       row.url = url;
       row.href = url;
       row.title = title;
+      if (label === void 0 && title) row[ListRow.label] = title;
       row.target = target;
       row.fields = fields;
     }

package/docs/components/badge.md

@@ -79,6 +79,7 @@ export function BadgeIconsExample() {
 | --- | --- | --- | --- |
 | icon | `IconType \| ReactElement` |  |  |
 | size | `'default' \| 'sm'` | `'default'` |  |
+| color | `'default' \| 'primary'` |  | `primary` tints the badge with the accent color, eg. to name a type |
 | status | `ContentStatus` |  | Colors the badge like the matching entry status |
 | title | `string` |  |  |
 Also accepts `className` and `style`, `id` and `aria-*` labelling attributes, `data-*` attributes.

package/docs/components/button.md

@@ -132,6 +132,7 @@ export function ButtonIconsExample() {
 | aria-controls | `string` |  |  |
 | aria-current | `boolean \| 'page' \| 'step' \| 'location' \| 'date' \| 'time'` |  |  |
 | aria-keyshortcuts | `string` |  | Keyboard shortcuts that activate the button, eg. `Meta+K Control+K` |
+| draggable | `boolean` |  | Lets a press on the button start a native drag, eg. of the draggable element it is in: browsers do not drag from a button otherwise |
 | onClick | `(event: MouseEvent<HTMLButtonElement>) => void` |  |  |
 | ref | `Ref<HTMLButtonElement>` |  |  |
 Also accepts `className` and `style`, `id` and `aria-*` labelling attributes, `data-*` attributes.

package/docs/components/content-card.md

@@ -48,6 +48,7 @@ The contents of a ContentGridItem, mirroring the dashboard explorer cards
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
 | title (required) | `ReactNode` |  |  |
+| suffix | `ReactNode` |  | Shown right after the title, eg. a status icon |
 | variant | `'icon' \| 'media'` | `'icon'` | `icon` (the default) shows the icon on a neutral background, `media` previews a file: its image on the `color` placeholder, or a file icon |
 | icon | `IconType` |  | The large icon on top of the card |
 | iconColor | `string` |  | The color of the icon, eg. of the kind of file |

package/docs/components/search-field.md

@@ -31,6 +31,7 @@ A text input for search queries with a clear button. The `icon` is shown inside
 | onClear | `() => void` |  | Called when the user clears the field with the clear button or escape |
 | placeholder | `string` |  |  |
 | loading | `boolean` |  | Shows a spinner while results are being loaded |
+| variant | `'default' \| 'inline'` | `'default'` | `inline` drops the box so the field reads as the top row of the results it searches, like a command palette. The row draws its own border. |
 | name | `string` |  |  |
 | autoFocus | `boolean` |  |  |
 | onBlur | `(event: FocusEvent<HTMLInputElement>) => void` |  |  |

package/docs/components/sortable-list.md

@@ -8,7 +8,6 @@ import {
   Badge,
   type DragMoveEvent,
   SortableList,
-  SortableListHandle,
   SortableListItem,
   SortableListItemDescription,
   SortableListItemHeader,
@@ -40,7 +39,6 @@ export function SortableListExample() {
       {sections.map(section => (
         <SortableListItem key={section.id} id={section.id} role="listitem">
           <SortableListItemHeader>
-            <SortableListHandle aria-label={`Drag ${section.label}`} />
             <SortableListItemTitle>
               <Badge size="sm">{section.type}</Badge>
               <SortableListItemDescription>
@@ -60,25 +58,20 @@ export function SortableListExample() {
 `SortableList`
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
-| onReorder | `(event: DragMoveEvent) => void` |  | Enables reordering: items with an `id` can be dragged by their `SortableListHandle`, with a pointer or with the keyboard (Enter on the handle, Tab to an item, Enter to drop). Called with the key of the dragged item and the item it was dropped before or after. Items only drop within the list they were dragged from. |
-| dragType | `string` |  | Mime type the dragged items carry, defaults to `alinea/sortable-list-item` |
-Also accepts every prop of `Surface`.
+| onReorder | `(event: DragMoveEvent) => void` |  | Enables reordering: items with an `id` follow the pointer when their `SortableListItemHeader` is dragged, the other items move aside as it passes them. With focus in the header, Alt+ArrowUp and Alt+ArrowDown move an item. Called with the key of the moved item and the item it was dropped before or after. Update the order synchronously: the dropped item glides into the place it renders in right after this returns. |
+Also accepts every prop of a `<div>` element.
 
 `SortableListItem`
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
 | id | `Key` |  | Identifies the item within its list. Items with an id can be dragged when the list has `onReorder`. The id is not rendered as a DOM id. |
-| dragPreview | `ReactNode` |  | Rendered under the pointer while dragging, eg. a `SortableListDragPreview` |
+| current | `boolean` |  | Highlights the item, eg. while its settings are open next to the list |
 Also accepts every prop of a `<div>` element.
 
 `SortableListItemHeader`
-Top bar of an item, holds its handle, title and actions
+Top bar of an item, holds its title and actions. Drags the item when the list has `onReorder`, a press that does not move still clicks.
 Accepts every prop of a `<div>` element.
 
-`SortableListHandle`
-Drags its `SortableListItem` when the list has `onReorder`. Focusable in that case: press Enter to start a keyboard drag. Place it in the `SortableListItemHeader`, it shows while the header is hovered or focused.
-Accepts every prop of a `<span>` element.
-
 `SortableListItemTitle`
 Row of the toggle, badges and description of an item, fills the header
 Accepts every prop of a `<div>` element.
@@ -94,7 +87,7 @@ Accepts every prop of a `<div>` element.
 Folds the content of an item
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
-| expanded (required) | `boolean` |  | Whether the item content is shown, rotates the fold icon |
+| expanded (required) | `boolean` |  | Whether the item content is shown, picks the unfold icon |
 Also accepts every prop of `Button`.
 
 `SortableListItemContent`
@@ -112,14 +105,6 @@ A group of settings or actions in the popover of an item
 | variant | `'default' \| 'actions'` | `'default'` | `actions` removes the padding around a group of ghost buttons |
 Also accepts every prop of a `<div>` element.
 
-`SortableListDragPreview`
-Card shown under the pointer while dragging an item
-| Prop | Type | Default | Description |
-| --- | --- | --- | --- |
-| icon | `IconType` |  |  |
-| label (required) | `ReactNode` |  |  |
-Also accepts every prop of a `<div>` element.
-
 `SortableListAdd`
 Last row of the list holding the buttons that add items
 Accepts every prop of a `<div>` element.

package/docs/components/table.md

@@ -171,6 +171,7 @@ Also accepts `className` and `style`.
 | icon | `IconType` |  | Doubles as the drag handle of the row when rows can be dragged |
 | title (required) | `ReactNode` |  |  |
 | label | `ReactNode` |  | A small caption above the title, eg. the parent path |
+| suffix | `ReactNode` |  | Shown right after the title, eg. a status icon |
 Also accepts `className` and `style`.
 
 ## Accessibility

package/docs/configuration.md

@@ -96,7 +96,7 @@ Scale down JPEG, PNG and WebP uploads larger than `maxWidth` or `maxHeight` pixe
 
 ### `syncInterval`
 
-How your deployed site keeps its content fresh. The site checks the content revision of the repository and syncs right away when it changed; `syncInterval` is the fallback interval in seconds when that revision can't be determined. Defaults to `60`.
+How your deployed site keeps its content fresh. The site checks the content revision of the repository and syncs right away when it changed; `syncInterval` is the fallback interval in seconds when that revision can't be determined. Defaults to `60`. In Next.js a value you set also controls how long renders share the latest revision, which bounds how soon content pushed without the dashboard shows up; without one that is five minutes.
 
 - `0` syncs on every query.
 - `Infinity` never syncs: the site only serves the content it was built with, and new content goes live with the next deploy.

package/docs/deploy/self-host.md

@@ -111,7 +111,7 @@ Register `https://<your site><handlerUrl>?auth=login` as the redirect URL with y
 
 ## Database
 
-`database({driver, client})` stores the users and roles you manage on the Manage users screen of the dashboard, see [Roles and permissions](../roles-permissions.md). Without an `uploads` part it also stores uploaded files until they are committed. Alinea creates its tables (`alinea_user`, `alinea_user_role` and `alinea_upload`) on first use. On PostgreSQL it enables row level security on them, so they are not exposed through Supabase's API.
+`database({driver, client})` stores the users and roles you manage on the Manage users screen of the dashboard, see [Roles and permissions](../roles-permissions.md). Without an `uploads` part it also stores uploaded files until they are committed. It keeps the content files fetched from or committed to GitHub, so every server instance reads them from the database instead of fetching them from GitHub again; files no instance used for 30 days are removed. Alinea creates its tables (`alinea_user`, `alinea_user_role`, `alinea_upload` and `alinea_blob`) on first use. On PostgreSQL it enables row level security on them, so they are not exposed through Supabase's API.
 
 Pass the client of one of these packages as `client`, with its name as `driver`:
 

package/docs/deploy.md

@@ -74,17 +74,17 @@ export const GET = handler
 export const POST = handler
 ```
 
-Without a `backend` option the handler connects to Alinea Cloud. Pass `backend` to [host it yourself](deploy/self-host.md). Use the `afterCommit` hook to revalidate pages after editors publish, see [Instant publishing](instant-publishing.md).
+Without a `backend` option the handler connects to Alinea Cloud. Pass `backend` to [host it yourself](deploy/self-host.md). Static pages are revalidated in the background after editors publish, see [Instant publishing](instant-publishing.md).
 
 ### Commit hooks
 
-Two hooks on the handler run for every commit, whatever it contains. `beforeCommit` receives the changes before they are committed: inspect or rewrite them and return the mutations to commit, or return nothing to keep them as they are. `afterCommit` runs once the commit is made, with the mutations and the `sha` of the new commit: revalidate pages, notify your team or trigger a deploy.
+Two hooks on the handler run for every commit, whatever it contains. `beforeCommit` receives the changes before they are committed: inspect or rewrite them and return the mutations to commit, or return nothing to keep them as they are. `afterCommit` runs once the commit is made, with the mutations and the `sha` of the new commit: revalidate caches of your own, notify your team or trigger a deploy.
 
 File: app/(alinea)/api/cms/route.ts
 ```tsx
 import {cms} from '@/cms'
 import {createHandler} from 'alinea/next'
-import {revalidatePath} from 'next/cache'
+import {revalidateTag} from 'next/cache'
 
 const handler = createHandler({
   cms,
@@ -93,7 +93,8 @@ const handler = createHandler({
     return mutations
   },
   afterCommit({sha}) {
-    revalidatePath('/', 'layout')
+    // Pages that query content refresh on their own, revalidate your own caches
+    revalidateTag('products', 'max')
   }
 })
 

package/docs/fields.md

@@ -137,7 +137,7 @@ Field.text('Discount code', {
 })
 ```
 
-Required fields and validation messages are shown on the field while an editor works on the entry. An entry can't be published while a field fails these checks: the dashboard lists the invalid fields, and publishing through the API or the MCP server is rejected with the field paths and messages. Drafts can be saved with errors, and hidden or read-only fields are not checked.
+Required fields and validation messages are shown on the field while an editor works on the entry. When an editor publishes an entry with fields that fail these checks, the dashboard lists them so they can be fixed first, or published anyway. Writes through the API are not checked, so importers can publish content that is still incomplete. The MCP server refuses to publish invalid entries and tells the agent which fields to fix. Drafts can be saved with errors, and hidden or read-only fields are not checked.
 
 ### Shared fields
 

package/docs/index.md

@@ -129,7 +129,7 @@ The documentation of this version of Alinea, one Markdown file per page of https
   - [Tooltip](components/tooltip.md): A short description that appears when its trigger is hovered or focused. Use it to name icon-only buttons, not for information editors need to do their work.
   - [Tree](components/tree.md)
 - [Custom fields](custom-fields.md): When the built-in fields don't fit your content, create your own.
-- [Overviews](overviews.md): When an entry has children, or a root holds entries, the dashboard lists them in an overview: a table, or cards, with the title of each entry and, when they…
+- [Overviews](overviews.md): When an entry has children, or a root holds entries, the dashboard lists them in an overview: a table, or cards, with the title and status of each entry and,…
 
 ## Reference
 

package/docs/instant-publishing.md

@@ -6,38 +6,23 @@ Content goes live on every commit, without a rebuild. When an editor publishes,
 
 Every publish in the dashboard is a git commit. After the commit, the site syncs the new content sha from its own handler, so the next request that renders content reads the latest version. No build or redeploy has to finish before editors see their changes on the live site.
 
+Diagram: Publish flow: the dashboard publishes to your site's handler, which commits to git and revalidates your running site. The CI build is skipped for commits that only touch content.
+
 ## Skip builds for content-only commits
 
-Because content is synced at runtime, a commit that only changes content does not need a new deployment. On Vercel you can skip those builds with an `ignoreCommand` in `vercel.json`. The command exits successfully, which tells Vercel to skip the build, when nothing outside the `content` directory changed:
+Because content is synced at runtime, a commit that only changes content does not need a new deployment. On Vercel you can skip those builds with an `ignoreCommand` in `vercel.json`. The command exits successfully, which tells Vercel to skip the build, when nothing outside the `content` directory changed since the last deployment. Comparing against `VERCEL_GIT_PREVIOUS_SHA` covers every commit in a push, not only the last one; on the first deployment of a branch it falls back to the previous commit:
 
 File: vercel.json
 ```json
 {
-  "ignoreCommand": "git diff --quiet HEAD^ HEAD -- . ':!content'"
+  "ignoreCommand": "git diff --quiet ${VERCEL_GIT_PREVIOUS_SHA:-HEAD^} HEAD -- . ':!content' || exit 1"
 }
 ```
 
 Note (info): Adjust `content` if your content lives in a different directory.
 
-## Revalidate pages after a commit
-
-Pages that are rendered at request time pick up new content immediately. Static pages were rendered ahead of time and keep serving the old content until they are revalidated. Use the handler's `afterCommit` hook to revalidate them whenever content is published:
+## Static pages
 
-File: app/api/cms/route.ts
-```
-import {cms} from '@/cms'
-import {createHandler} from 'alinea/next'
-import {revalidatePath} from 'next/cache'
-
-const handler = createHandler({
-  cms,
-  afterCommit() {
-    revalidatePath('/', 'layout')
-  }
-})
-
-export const GET = handler
-export const POST = handler
-```
+Static pages are revalidated for you. Every page that queries content is tagged, and after each commit the handler marks those pages as stale. The next visit is still answered from the cache while Next.js rebuilds the page in the background, and the visit after that gets the new content. No visitor waits for a render, and no `revalidatePath` call is needed.
 
-`revalidatePath('/', 'layout')` marks every page as stale, so the next visit to any page renders it with the new content. Narrow it down to specific paths if you only want to revalidate the pages that changed.
+Pages rendered at request time sync on their next render. The first one after a commit can still show the previous version while the shared content sha refreshes. Content pushed to your repository without the dashboard, for example a local edit, skips the handler: pages pick it up within five minutes, or within `syncInterval` seconds when your config sets it. Use the handler's `afterCommit` hook if other caches in your app depend on content, for example your own `fetch` tags.

package/docs/overviews.md

@@ -1,6 +1,6 @@
 # Overviews
 
-When an entry has children, or a root holds entries, the dashboard lists them in an overview: a table, or cards, with the title of each entry and, when they tell the entries apart, its type, status and who edited it last. The `overview` option of a container [type](schema/type.md) or a [root](workspaces/root.md) adds your own columns, a default order, a card image and toolbar actions.
+When an entry has children, or a root holds entries, the dashboard lists them in an overview: a table, or cards, with the title and status of each entry and, when they tell the entries apart, its type and who edited it last. The `overview` option of a container [type](schema/type.md) or a [root](workspaces/root.md) adds your own columns, a default order, a card image and toolbar actions.
 
 Image: The products overview of the Oak & Loom demo, with its own columns for price, material and stock, sorted by price. (https://v2.alineacms.com/admin/file/screenshots/dashboard-overview.webp)
 
@@ -173,17 +173,16 @@ Like other views, `view` takes a component or a path to one. Use a path to keep
 
 ## Built-in columns
 
-The title is always the first column. The built-in columns follow, then the columns you define. Columns with `position: 'start'` go between the title and the built-in columns.
+The title is always the first column. The built-in columns follow, then the columns you define. Columns with `position: 'start'` go between the title and the built-in columns. Like in the sidebar, an icon after the title marks entries that are not plainly published: drafts, unpublished and archived entries.
 
 A built-in column only shows when it tells the listed entries apart. The dashboard decides this from all children of the parent, not only those on screen, so the columns don't change while scrolling or sorting:
 
 - `type`: the type of the entry. Shown when the children have more than one type, and in search results and filtered lists.
-- `status`: the publication status. Shown when the children differ in status, for example when some are drafts. A list of published entries has no status column.
 - `updated` and `author`: when the entry was last edited and by whom, read from the audit fields of the metadata field (under the key `metadata`, which `Config.document` and `Field.metadata()` add). Shown when at least one child stores that audit data, so lists of entries created before audit data was recorded don't show empty columns.
 
 The columns follow the types of the children that are there. A parent without `contains` accepts any type, but its overview only shows the columns of the types it holds.
 
-Force them on or off with `builtins`, for example `{status: true}` to always show the status, or `{type: false, updated: false, author: false}` to never show those. A column keyed `type`, `status`, `updated` or `author` replaces that built-in column in place, for example to show the writer of an article instead of the last editor. The `title` key is reserved.
+Force them on or off with `builtins`, for example `{type: true}` to always show the type, or `{type: false, updated: false, author: false}` to never show those. A column keyed `type`, `updated` or `author` replaces that built-in column in place, for example to show the writer of an article instead of the last editor. The `title` key is reserved.
 
 ## Sorting
 

package/docs/upgrading.md

@@ -149,7 +149,7 @@ File: app/(alinea)/api/cms/route.ts
 ```tsx
 import {cms} from '@/cms'
 import {createHandler} from 'alinea/next'
-import {revalidatePath} from 'next/cache'
+import {revalidateTag} from 'next/cache'
 
 const handler = createHandler({
   cms,
@@ -158,7 +158,8 @@ const handler = createHandler({
     return mutations
   },
   afterCommit({sha}) {
-    revalidatePath('/', 'layout')
+    // Pages that query content refresh on their own, revalidate your own caches
+    revalidateTag('products', 'max')
   }
 })
 

package/llms-full.txt

@@ -2093,7 +2093,7 @@ File: app/(alinea)/api/cms/route.ts
 ```tsx
 import {cms} from '@/cms'
 import {createHandler} from 'alinea/next'
-import {revalidatePath} from 'next/cache'
+import {revalidateTag} from 'next/cache'
 
 const handler = createHandler({
   cms,
@@ -2102,7 +2102,8 @@ const handler = createHandler({
     return mutations
   },
   afterCommit({sha}) {
-    revalidatePath('/', 'layout')
+    // Pages that query content refresh on their own, revalidate your own caches
+    revalidateTag('products', 'max')
   }
 })
 
@@ -2749,7 +2750,7 @@ Field.text('Discount code', {
 })
 ```
 
-Required fields and validation messages are shown on the field while an editor works on the entry. An entry can't be published while a field fails these checks: the dashboard lists the invalid fields, and publishing through the API or the MCP server is rejected with the field paths and messages. Drafts can be saved with errors, and hidden or read-only fields are not checked.
+Required fields and validation messages are shown on the field while an editor works on the entry. When an editor publishes an entry with fields that fail these checks, the dashboard lists them so they can be fixed first, or published anyway. Writes through the API are not checked, so importers can publish content that is still incomplete. The MCP server refuses to publish invalid entries and tells the agent which fields to fix. Drafts can be saved with errors, and hidden or read-only fields are not checked.
 
 ### Shared fields
 
@@ -5785,41 +5786,26 @@ Content goes live on every commit, without a rebuild. When an editor publishes,
 
 Every publish in the dashboard is a git commit. After the commit, the site syncs the new content sha from its own handler, so the next request that renders content reads the latest version. No build or redeploy has to finish before editors see their changes on the live site.
 
+Diagram: Publish flow: the dashboard publishes to your site's handler, which commits to git and revalidates your running site. The CI build is skipped for commits that only touch content.
+
 ## Skip builds for content-only commits
 
-Because content is synced at runtime, a commit that only changes content does not need a new deployment. On Vercel you can skip those builds with an `ignoreCommand` in `vercel.json`. The command exits successfully, which tells Vercel to skip the build, when nothing outside the `content` directory changed:
+Because content is synced at runtime, a commit that only changes content does not need a new deployment. On Vercel you can skip those builds with an `ignoreCommand` in `vercel.json`. The command exits successfully, which tells Vercel to skip the build, when nothing outside the `content` directory changed since the last deployment. Comparing against `VERCEL_GIT_PREVIOUS_SHA` covers every commit in a push, not only the last one; on the first deployment of a branch it falls back to the previous commit:
 
 File: vercel.json
 ```json
 {
-  "ignoreCommand": "git diff --quiet HEAD^ HEAD -- . ':!content'"
+  "ignoreCommand": "git diff --quiet ${VERCEL_GIT_PREVIOUS_SHA:-HEAD^} HEAD -- . ':!content' || exit 1"
 }
 ```
 
 Note (info): Adjust `content` if your content lives in a different directory.
 
-## Revalidate pages after a commit
-
-Pages that are rendered at request time pick up new content immediately. Static pages were rendered ahead of time and keep serving the old content until they are revalidated. Use the handler's `afterCommit` hook to revalidate them whenever content is published:
+## Static pages
 
-File: app/api/cms/route.ts
-```
-import {cms} from '@/cms'
-import {createHandler} from 'alinea/next'
-import {revalidatePath} from 'next/cache'
+Static pages are revalidated for you. Every page that queries content is tagged, and after each commit the handler marks those pages as stale. The next visit is still answered from the cache while Next.js rebuilds the page in the background, and the visit after that gets the new content. No visitor waits for a render, and no `revalidatePath` call is needed.
 
-const handler = createHandler({
-  cms,
-  afterCommit() {
-    revalidatePath('/', 'layout')
-  }
-})
-
-export const GET = handler
-export const POST = handler
-```
-
-`revalidatePath('/', 'layout')` marks every page as stale, so the next visit to any page renders it with the new content. Narrow it down to specific paths if you only want to revalidate the pages that changed.
+Pages rendered at request time sync on their next render. The first one after a commit can still show the previous version while the shared content sha refreshes. Content pushed to your repository without the dashboard, for example a local edit, skips the handler: pages pick it up within five minutes, or within `syncInterval` seconds when your config sets it. Use the handler's `afterCommit` hook if other caches in your app depend on content, for example your own `fetch` tags.
 
 ### Editing content (https://v2.alineacms.com/docs/editing-content)
 Your `cms` instance can create, update, publish and delete entries from code, for example to import content from another system or to seed a new project. Changes go through your handler, like saves in the dashboard: during development they are written to your content files.
@@ -6641,17 +6627,17 @@ export const GET = handler
 export const POST = handler
 ```
 
-Without a `backend` option the handler connects to Alinea Cloud. Pass `backend` to [host it yourself](https://v2.alineacms.com/docs/deploy/self-host). Use the `afterCommit` hook to revalidate pages after editors publish, see [Instant publishing](https://v2.alineacms.com/docs/instant-publishing).
+Without a `backend` option the handler connects to Alinea Cloud. Pass `backend` to [host it yourself](https://v2.alineacms.com/docs/deploy/self-host). Static pages are revalidated in the background after editors publish, see [Instant publishing](https://v2.alineacms.com/docs/instant-publishing).
 
 ### Commit hooks
 
-Two hooks on the handler run for every commit, whatever it contains. `beforeCommit` receives the changes before they are committed: inspect or rewrite them and return the mutations to commit, or return nothing to keep them as they are. `afterCommit` runs once the commit is made, with the mutations and the `sha` of the new commit: revalidate pages, notify your team or trigger a deploy.
+Two hooks on the handler run for every commit, whatever it contains. `beforeCommit` receives the changes before they are committed: inspect or rewrite them and return the mutations to commit, or return nothing to keep them as they are. `afterCommit` runs once the commit is made, with the mutations and the `sha` of the new commit: revalidate caches of your own, notify your team or trigger a deploy.
 
 File: app/(alinea)/api/cms/route.ts
 ```tsx
 import {cms} from '@/cms'
 import {createHandler} from 'alinea/next'
-import {revalidatePath} from 'next/cache'
+import {revalidateTag} from 'next/cache'
 
 const handler = createHandler({
   cms,
@@ -6660,7 +6646,8 @@ const handler = createHandler({
     return mutations
   },
   afterCommit({sha}) {
-    revalidatePath('/', 'layout')
+    // Pages that query content refresh on their own, revalidate your own caches
+    revalidateTag('products', 'max')
   }
 })
 
@@ -6801,7 +6788,7 @@ Register `https://<your site><handlerUrl>?auth=login` as the redirect URL with y
 
 ## Database
 
-`database({driver, client})` stores the users and roles you manage on the Manage users screen of the dashboard, see [Roles and permissions](https://v2.alineacms.com/docs/roles-permissions). Without an `uploads` part it also stores uploaded files until they are committed. Alinea creates its tables (`alinea_user`, `alinea_user_role` and `alinea_upload`) on first use. On PostgreSQL it enables row level security on them, so they are not exposed through Supabase's API.
+`database({driver, client})` stores the users and roles you manage on the Manage users screen of the dashboard, see [Roles and permissions](https://v2.alineacms.com/docs/roles-permissions). Without an `uploads` part it also stores uploaded files until they are committed. It keeps the content files fetched from or committed to GitHub, so every server instance reads them from the database instead of fetching them from GitHub again; files no instance used for 30 days are removed. Alinea creates its tables (`alinea_user`, `alinea_user_role`, `alinea_upload` and `alinea_blob`) on first use. On PostgreSQL it enables row level security on them, so they are not exposed through Supabase's API.
 
 Pass the client of one of these packages as `client`, with its name as `driver`:
 
@@ -8137,6 +8124,7 @@ export function BadgeIconsExample() {
 | --- | --- | --- | --- |
 | icon | `IconType \| ReactElement` |  |  |
 | size | `'default' \| 'sm'` | `'default'` |  |
+| color | `'default' \| 'primary'` |  | `primary` tints the badge with the accent color, eg. to name a type |
 | status | `ContentStatus` |  | Colors the badge like the matching entry status |
 | title | `string` |  |  |
 Also accepts `className` and `style`, `id` and `aria-*` labelling attributes, `data-*` attributes.
@@ -8385,6 +8373,7 @@ export function ButtonIconsExample() {
 | aria-controls | `string` |  |  |
 | aria-current | `boolean \| 'page' \| 'step' \| 'location' \| 'date' \| 'time'` |  |  |
 | aria-keyshortcuts | `string` |  | Keyboard shortcuts that activate the button, eg. `Meta+K Control+K` |
+| draggable | `boolean` |  | Lets a press on the button start a native drag, eg. of the draggable element it is in: browsers do not drag from a button otherwise |
 | onClick | `(event: MouseEvent<HTMLButtonElement>) => void` |  |  |
 | ref | `Ref<HTMLButtonElement>` |  |  |
 Also accepts `className` and `style`, `id` and `aria-*` labelling attributes, `data-*` attributes.
@@ -8868,6 +8857,7 @@ The contents of a ContentGridItem, mirroring the dashboard explorer cards
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
 | title (required) | `ReactNode` |  |  |
+| suffix | `ReactNode` |  | Shown right after the title, eg. a status icon |
 | variant | `'icon' \| 'media'` | `'icon'` | `icon` (the default) shows the icon on a neutral background, `media` previews a file: its image on the `color` placeholder, or a file icon |
 | icon | `IconType` |  | The large icon on top of the card |
 | iconColor | `string` |  | The color of the icon, eg. of the kind of file |
@@ -10628,6 +10618,7 @@ A text input for search queries with a clear button. The `icon` is shown inside
 | onClear | `() => void` |  | Called when the user clears the field with the clear button or escape |
 | placeholder | `string` |  |  |
 | loading | `boolean` |  | Shows a spinner while results are being loaded |
+| variant | `'default' \| 'inline'` | `'default'` | `inline` drops the box so the field reads as the top row of the results it searches, like a command palette. The row draws its own border. |
 | name | `string` |  |  |
 | autoFocus | `boolean` |  |  |
 | onBlur | `(event: FocusEvent<HTMLInputElement>) => void` |  |  |
@@ -10900,7 +10891,6 @@ import {
   Badge,
   type DragMoveEvent,
   SortableList,
-  SortableListHandle,
   SortableListItem,
   SortableListItemDescription,
   SortableListItemHeader,
@@ -10932,7 +10922,6 @@ export function SortableListExample() {
       {sections.map(section => (
         <SortableListItem key={section.id} id={section.id} role="listitem">
           <SortableListItemHeader>
-            <SortableListHandle aria-label={`Drag ${section.label}`} />
             <SortableListItemTitle>
               <Badge size="sm">{section.type}</Badge>
               <SortableListItemDescription>
@@ -10952,25 +10941,20 @@ export function SortableListExample() {
 `SortableList`
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
-| onReorder | `(event: DragMoveEvent) => void` |  | Enables reordering: items with an `id` can be dragged by their `SortableListHandle`, with a pointer or with the keyboard (Enter on the handle, Tab to an item, Enter to drop). Called with the key of the dragged item and the item it was dropped before or after. Items only drop within the list they were dragged from. |
-| dragType | `string` |  | Mime type the dragged items carry, defaults to `alinea/sortable-list-item` |
-Also accepts every prop of `Surface`.
+| onReorder | `(event: DragMoveEvent) => void` |  | Enables reordering: items with an `id` follow the pointer when their `SortableListItemHeader` is dragged, the other items move aside as it passes them. With focus in the header, Alt+ArrowUp and Alt+ArrowDown move an item. Called with the key of the moved item and the item it was dropped before or after. Update the order synchronously: the dropped item glides into the place it renders in right after this returns. |
+Also accepts every prop of a `<div>` element.
 
 `SortableListItem`
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
 | id | `Key` |  | Identifies the item within its list. Items with an id can be dragged when the list has `onReorder`. The id is not rendered as a DOM id. |
-| dragPreview | `ReactNode` |  | Rendered under the pointer while dragging, eg. a `SortableListDragPreview` |
+| current | `boolean` |  | Highlights the item, eg. while its settings are open next to the list |
 Also accepts every prop of a `<div>` element.
 
 `SortableListItemHeader`
-Top bar of an item, holds its handle, title and actions
+Top bar of an item, holds its title and actions. Drags the item when the list has `onReorder`, a press that does not move still clicks.
 Accepts every prop of a `<div>` element.
 
-`SortableListHandle`
-Drags its `SortableListItem` when the list has `onReorder`. Focusable in that case: press Enter to start a keyboard drag. Place it in the `SortableListItemHeader`, it shows while the header is hovered or focused.
-Accepts every prop of a `<span>` element.
-
 `SortableListItemTitle`
 Row of the toggle, badges and description of an item, fills the header
 Accepts every prop of a `<div>` element.
@@ -10986,7 +10970,7 @@ Accepts every prop of a `<div>` element.
 Folds the content of an item
 | Prop | Type | Default | Description |
 | --- | --- | --- | --- |
-| expanded (required) | `boolean` |  | Whether the item content is shown, rotates the fold icon |
+| expanded (required) | `boolean` |  | Whether the item content is shown, picks the unfold icon |
 Also accepts every prop of `Button`.
 
 `SortableListItemContent`
@@ -11004,14 +10988,6 @@ A group of settings or actions in the popover of an item
 | variant | `'default' \| 'actions'` | `'default'` | `actions` removes the padding around a group of ghost buttons |
 Also accepts every prop of a `<div>` element.
 
-`SortableListDragPreview`
-Card shown under the pointer while dragging an item
-| Prop | Type | Default | Description |
-| --- | --- | --- | --- |
-| icon | `IconType` |  |  |
-| label (required) | `ReactNode` |  |  |
-Also accepts every prop of a `<div>` element.
-
 `SortableListAdd`
 Last row of the list holding the buttons that add items
 Accepts every prop of a `<div>` element.
@@ -11323,6 +11299,7 @@ Also accepts `className` and `style`.
 | icon | `IconType` |  | Doubles as the drag handle of the row when rows can be dragged |
 | title (required) | `ReactNode` |  |  |
 | label | `ReactNode` |  | A small caption above the title, eg. the parent path |
+| suffix | `ReactNode` |  | Shown right after the title, eg. a status icon |
 Also accepts `className` and `style`.
 
 ## Accessibility
@@ -12321,7 +12298,7 @@ Field views from 1.x keep working, with deprecated APIs:
 See [Upgrading from 1.x](https://v2.alineacms.com/docs/upgrading) for the other dashboard changes.
 
 ### Overviews (https://v2.alineacms.com/docs/overviews)
-When an entry has children, or a root holds entries, the dashboard lists them in an overview: a table, or cards, with the title of each entry and, when they tell the entries apart, its type, status and who edited it last. The `overview` option of a container [type](https://v2.alineacms.com/docs/schema/type) or a [root](https://v2.alineacms.com/docs/workspaces/root) adds your own columns, a default order, a card image and toolbar actions.
+When an entry has children, or a root holds entries, the dashboard lists them in an overview: a table, or cards, with the title and status of each entry and, when they tell the entries apart, its type and who edited it last. The `overview` option of a container [type](https://v2.alineacms.com/docs/schema/type) or a [root](https://v2.alineacms.com/docs/workspaces/root) adds your own columns, a default order, a card image and toolbar actions.
 
 Image: The products overview of the Oak & Loom demo, with its own columns for price, material and stock, sorted by price. (https://v2.alineacms.com/admin/file/screenshots/dashboard-overview.webp)
 
@@ -12494,17 +12471,16 @@ Like other views, `view` takes a component or a path to one. Use a path to keep
 
 ## Built-in columns
 
-The title is always the first column. The built-in columns follow, then the columns you define. Columns with `position: 'start'` go between the title and the built-in columns.
+The title is always the first column. The built-in columns follow, then the columns you define. Columns with `position: 'start'` go between the title and the built-in columns. Like in the sidebar, an icon after the title marks entries that are not plainly published: drafts, unpublished and archived entries.
 
 A built-in column only shows when it tells the listed entries apart. The dashboard decides this from all children of the parent, not only those on screen, so the columns don't change while scrolling or sorting:
 
 - `type`: the type of the entry. Shown when the children have more than one type, and in search results and filtered lists.
-- `status`: the publication status. Shown when the children differ in status, for example when some are drafts. A list of published entries has no status column.
 - `updated` and `author`: when the entry was last edited and by whom, read from the audit fields of the metadata field (under the key `metadata`, which `Config.document` and `Field.metadata()` add). Shown when at least one child stores that audit data, so lists of entries created before audit data was recorded don't show empty columns.
 
 The columns follow the types of the children that are there. A parent without `contains` accepts any type, but its overview only shows the columns of the types it holds.
 
-Force them on or off with `builtins`, for example `{status: true}` to always show the status, or `{type: false, updated: false, author: false}` to never show those. A column keyed `type`, `status`, `updated` or `author` replaces that built-in column in place, for example to show the writer of an article instead of the last editor. The `title` key is reserved.
+Force them on or off with `builtins`, for example `{type: true}` to always show the type, or `{type: false, updated: false, author: false}` to never show those. A column keyed `type`, `updated` or `author` replaces that built-in column in place, for example to show the writer of an article instead of the last editor. The `title` key is reserved.
 
 ## Sorting
 
@@ -12876,7 +12852,7 @@ Scale down JPEG, PNG and WebP uploads larger than `maxWidth` or `maxHeight` pixe
 
 ### `syncInterval`
 
-How your deployed site keeps its content fresh. The site checks the content revision of the repository and syncs right away when it changed; `syncInterval` is the fallback interval in seconds when that revision can't be determined. Defaults to `60`.
+How your deployed site keeps its content fresh. The site checks the content revision of the repository and syncs right away when it changed; `syncInterval` is the fallback interval in seconds when that revision can't be determined. Defaults to `60`. In Next.js a value you set also controls how long renders share the latest revision, which bounds how soon content pushed without the dashboard shows up; without one that is five minutes.
 
 - `0` syncs on every query.
 - `Infinity` never syncs: the site only serves the content it was built with, and new content goes live with the next deploy.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "alinea",
-  "version": "2.0.0-preview.12",
+  "version": "2.0.0-preview.13",
   "description": "Open source, Git-based headless CMS for Next.js",
   "keywords": [
     "cms",
@@ -84,7 +84,6 @@
     "stories": "bunx --bun ladle serve",
     "tag": "bun tag.js",
     "spec": "playwright test -c .playwright/playwright.config.ts",
-    "spec:visual": "playwright test -c .playwright/playwright.visual.config.ts",
     "trace": "tsc --diagnostics --generateTrace private/trace && analyze-trace private/trace & speedscope private/trace/trace.json",
     "type": "tsc --diagnostics",
     "web": "run-p dev:check web:run",
@@ -92,7 +91,7 @@
   },
   "dependencies": {
     "@alinea/iso": "^0.3.3",
-    "@alinea/sqlite-wasm": "0.3.1",
+    "@alinea/sqlite-wasm": "0.8.1",
     "esbuild": "^0.28.0"
   },
   "peerDependencies": {

package/dist/core/db/EntryValidationError.d.ts

@@ -1,13 +0,0 @@
-import { HttpError } from '../HttpError.js';
-import { type FieldValidationError } from '../Validation.js';
-export interface EntryValidationErrorInfo {
-    entryId: string;
-    title?: string;
-    errors: Array<FieldValidationError>;
-}
-/** A published version would contain fields which fail validation */
-export declare class EntryValidationError extends HttpError {
-    info: EntryValidationErrorInfo;
-    name: string;
-    constructor(info: EntryValidationErrorInfo);
-}