> For the complete documentation index, see [llms.txt](https://docs.toomuchmedia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toomuchmedia.com/content-management/member-areas-and-tours/themes/block-types/model-view-block.md). # Model View Block *Article Topics:* [*Blocks*](/getting-started/common-topics/blocks.md)*,* [*Design*](/getting-started/common-topics/design.md) ## Overview The Model View Block allows you to display full details of a specific Model, including their thumbnail and banner, a description, related attributes and more. This Block is used alongside the [Model List Block](/content-management/member-areas-and-tours/themes/block-types/model-list-block.md) to create a seamless navigation experience between lists of models and detailed model profiles. {% embed url="" %} ## Model View Settings ### Settings Tab The **Settings** tab allows you to control which model is displayed in the block. You can filter the model using: * Specific Model ID(s). * The model ID or slug passed through the URL. You can also define which Channels with Content that a Model has been associated with are displayed. Content Sets are published to Channels, and Content Sets can have Models associated with them, so selecting the Channel will limit which Models are displayed. See the [Channels](/content-management/channels.md) article to learn more. Using specific Model ID(s) is best used when the block is placed on a special page dedicated to a single mode. For example, setting the ID to "1" will always show the model with ID "1" when a visitor goes the the page with the Model View Block on it. Setting the filter to ID or Slug in the Page Path (URL) will have the block **dynamically** display a model's details based on what the user clicked to get to the current page the block resides on. This ensures the block displays the relevant model based on how the visitor got to the page, such as from a Model List Block. ### Design Tab The Design tab allows you to control how the block looks and how visitors or members interact with it. The **Header Image and Banner** section lets you choose whether to display the model's header image or banner, and where each one is position within the block layout. The **User Interaction details to display** section gives you the option to enable features for visitors to interact with the model's profile including: * Rating the model. * Thumbs up/down. * Favorite button. These stats can be used to create a personal list of the user's favorite models on their account page, or help you determine which models to spotlight and more. ### Additional Details Tab The **Additional Details** tab lets you define which model attributes are displayed in the block, and thus on the page. You can select to include attributes such as age, gender, height, and more. Each attribute that is displayed can also include a target link using the **Display Value As** field, giving visitors a navigation option to content that is related to the attribute. ## Related Articles {% content-ref url="/pages/J6Pe6MmfmWL8KMam8usM" %} [Block Types](/content-management/member-areas-and-tours/themes/block-types.md) {% endcontent-ref %} {% content-ref url="/pages/9rDzAtObvdZezSmYfvKk" %} [Model List Block](/content-management/member-areas-and-tours/themes/block-types/model-list-block.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.toomuchmedia.com/content-management/member-areas-and-tours/themes/block-types/model-view-block.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.