Page Templates and Layouts

Description

Page Templates and Layouts give each Dotabase reusable, prefilled starting points for new rows while keeping templates out of row search and counts.

A row template stores body content, schema-checked initial properties, and an optional registered layout key in a table separate from live rows. Creating a row from it copies the starting values once through ordinary row services. When the Dotabase schema evolves, reconciliation removes stale assumptions so a template cannot keep seeding properties that no longer exist.

User Story

As a team lead, I create every incident from the same response scaffold without polluting the incident list with template rows. I save the standard body, initial status, and supported layout as a template. A responder selects it when creating an incident and then edits the resulting row normally. I walk away with consistent starting structure, while the template itself never appears as an incident or overwrites the responder's later work.

Extension Surface

Configurable: users save templates and select registered layout keys; the storage contract and key syntax are fixed.

packages/dotabases/src/row-templates/service.ts exposes lifecycle operations for tenant-owned template data. Users configure supported content and keys; they cannot attach executable creation hooks through this surface.

Capabilities & Limits

• Capability: Executes the scoped workflow described above through the cited live implementation paths.
• Capability: Preserves typed validation and applicable tenant, schema, lifecycle, or service boundaries.
• Limit: Templates seed new rows but do not continuously overwrite later edits. The feature supports template create, update, list, delete, schema reconciliation, prefilled bodies and properties, and layout selection. It cannot keep instances synchronized, bypass property validation, or preserve values for deleted schema keys. Layout rendering still belongs to the application that recognizes the stored key.

Implementation Map

• packages/dotabases/src/row-templates/service.ts
• packages/dotabases/src/row-templates/reconcile-properties.ts
• packages/db/src/schema/dotabase-row-templates.ts

Related Features

Can be bundled by Dotabase Templates and configures Dotabase Workspaces.

Operationally, these relationships preserve a clear ownership boundary around Page Templates and Layouts. Neighboring features can invoke, supply, or consume its results, but `packages/dotabases/src/row-templates/service.ts` remains the grounded implementation authority for this capability. That distinction prevents the catalog claim from widening into adjacent rendering, transport, or governance work. Teams can therefore combine the feature with the named dependencies while still diagnosing configuration, validation, and lifecycle behavior at the package boundary that owns it.