Entity runtime presets
This page inventories the current runtime entity presets and the current canonical card surfaces in Ikabud as of March 2026. Presets attach capability bundles to existing entities; cards are the canonical list-card fragments and practical card patterns those capabilities produce.
How to read this page
- Entity presets are live runtime bundles loaded from
config/entity-presets. - Canonical card surfaces are the current list-card fragments rendered by the canonical entity list contract.
- Entity card presets are still a draft contract, so this page separates live runtime features from planned composition metadata.
Live runtime entity presets
ecommerce — E-Commerce Product
Target: product in the commerce context.
- pricing — base price, currency, and sale-price state.
- inventory — stock tracking, SKU, and stock status.
- media_gallery — gallery media for product-led presentation.
Use this when the entity is a first-class storefront product and the card or detail view needs price, stock, and cart-oriented behavior.
business — Business Service
Target: service in the business context.
- inquiry — service enquiry CTA and form field defaults.
- booking — appointment-style booking defaults.
- media_gallery — supporting visuals for service presentation.
Use this when the service is consultative or bookable and does not need explicit sell-through pricing by default.
education — Online Course
Target: course in the guidance context.
- pricing — optional course pricing support.
- lessons_index — course contents / lesson sequencing.
- progress_tracking — learner progress state.
Use this when the entity is course-like and needs curriculum structure plus learner progress.
portfolio — Portfolio Item
Target: showcase-style content where media and inquiry matter more than commerce inventory.
- media_gallery — visual showcase support.
- inquiry — contact or project CTA.
Use this for case studies, featured work, or portfolio pieces that should lead to a conversation rather than a cart flow.
service-commerce — Sellable Service
Target: service in the business context with a stronger commerce posture.
- pricing — explicit sellable service pricing.
- inquiry — contact CTA for service qualification.
- booking — scheduled service engagement.
- media_gallery — supporting visuals.
Use this when a service needs both consultative actions and a visible price anchor.
course-commerce — Sellable Course
Target: course in the guidance context with commerce-style enrollment.
- pricing — paid enrollment or sell-through pricing.
- lessons_index — structured course contents.
- progress_tracking — learner progress state.
- media_gallery — richer course marketing visuals.
Use this when the course needs both learning structure and commerce-friendly presentation.
Canonical card surfaces available today
list-card-pricing
Approved variants: featured, minimal.
This fragment renders inline price and sale-state summaries inside canonical entity list cards.
list-card-inventory
Approved variants: compact.
This fragment renders stock availability and compact inventory state for list cards.
list-card-progress
Approved variants: inline.
This fragment renders learner progress summaries in list cards when progress tracking is active.
list-card-action
Approved variants: default runtime fragment only.
This fragment renders the card-level CTA path, typically the buy / action area when pricing and cart behavior are active.
Practical card patterns
Product card
Media, title, excerpt, pricing, inventory, and action make up the most complete commerce-oriented card. This is the clearest fit for the ecommerce preset.
Service card
Media, title, excerpt, and service actions define the service-oriented card. Add visible pricing when using service-commerce; keep the focus on inquiry and booking when using business.
Course card
Title, excerpt, pricing, and learner progress define the most useful course-oriented card. Add richer media when using course-commerce; keep lesson sequencing primarily in the detail view.
Portfolio card
Media-first presentation, a concise title and excerpt, and an inquiry path make the strongest portfolio card. This is the best fit for the portfolio preset.
Draft entity card preset direction
The repository documents a draft entity card preset contract for named card compositions. That registry is not a live runtime API yet, so the current runtime truth is the preset inventory above plus the canonical list-card fragments above.
Bottom line: presets configure capability bundles, while cards describe how canonical list rendering exposes pricing, inventory, progress, and actions for each entity style.