Templates
What are Templates?
Unlike a component or a block — which are meant to be reused, unmodified, in many places — a template is a full page composition tied to a specific context: specific columns, specific actions, specific data shape. It's not something you install and reuse; it's a realistic starting point you eject once and adapt for that one screen.
Templates ship with static, mock data — no API wiring — and are ejected via the same registry mechanism as components and blocks, as a registry:page item.
A template ejects as a single page file. It imports the blocks it is composed of (Layout, Header, TableView, etc.) from @mercadoeletronico/eds-next, which it declares as an npm dependency, instead of copying their source into your project. That keeps the ejected page small and lets design system updates reach it through npm. When you do want to own and adapt a block's source, eject that block on its own.
Available Templates
Transações
A transactions list screen: header, side navigation, filter bar, and a paginated table with status badges.
Documentos
The document chassis in read mode, driven by a Section/SectionField schema: the base every document page below is a payload for.
Pré-Pedido
The three pre-order screens: create as a single progressive-unlock page, edit and read on the document chassis. One registry item per mode.
Contrato
A contract read screen on the document chassis: fourteen sections, the balance and its consumption in the Forehead, and the approval history.
Pedido
An order read screen, with an items section that switches between a summary grid and per-item detail.
Cotação
An RFQ read screen: phase rail, invited suppliers with their answer states, items with their subitems, and the negotiation rounds.