-
Notifications
You must be signed in to change notification settings - Fork 0
Common Models
IComponent could be anything from widgets, the page header or page footer.
The intention is they act as a common entry point for blocks of content to be mapped to a view.
Used by the following tag helpers:
IImage represents a single image. This image can have a sourceset, url and alt text.
Building an IImage can be done manually or using the IImageBuilder.
Used by the following tag helpers:
ILink represents an interactive element on the page. This could be an anchor tag or IModalLink which supports IModal content.
Building an ILink can be done manually or using the ILinkBuilder.
Used by the following tag helpers:
IModal represents pop up content. It can be included as a part of a IModalLink or a standalone modal which is displayed by frontend code.
Used by the following tag helpers:
ISubcomponent is an item which is used by a Component. Subcomponents do not function by themselves but they are generally self contained.
The intention is they are reusable or repeatable objects for when creating a standalone component would not make sense. Think carousel items or team member cards.
Used by the following tag helpers:
Important
Subcomponents are not the same as nested components.
A nested component can still function by itself outside of the context of component it is currently being rendered in.