> For the complete documentation index, see [llms.txt](https://aptitude.gitbook.io/zaubercms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aptitude.gitbook.io/zaubercms/extending-zaubercms/blocklisteditor/content-block-preview.md).

# Content Block Preview

If you want to customise what the user will see in the BlockListEditor you can use 

```csharp
IContentBlockPreview
```

This allows you to display the picked content however you wish in the admin, instead of the default UI. All you have to do is create a Blazor component and implement IContentBlockPreview like so.

```csharp
@implements ZauberCMS.Core.Content.Interfaces.IContentBlockPreview

@if (Content != null)
{
    <div class="fs-6">
        @((MarkupString)(Content.GetValue<string>("Content") ?? string.Empty))
    </div>
}

@code {
    [Parameter] public Content? Content { get; set; }
    [Parameter] public ContentType? ContentType { get; set; }
    public string ContentTypeAlias => "RTEBlock";
}
```

The above is an example of pulling data from the Rich Text Editor and displaying it to the user. The important part is making sure I **set the ElementTypeAlias to match the content type** being used on this content.

As this is Blazor, you could reuse the Content Block that you would use in the front end, for example, this Content Block Preview is exactly the same code as the Content Block I should on the front end of the site, to save duplication, I could simply do the following (**Where RTEBlock is my IContentBlock component**)

```csharp
@implements ZauberCMS.Core.Content.Interfaces.IContentBlockPreview

@if (Content != null)
{
    <RTEBlock Content="@Content" />
}

@code {
    [Parameter] public Content? Content { get; set; }
    [Parameter] public ContentType? ContentType { get; set; }
    public string ContentTypeAlias => "RTEBlock";
}
```

To get the data is the same as querying data in the front end:

{% content-ref url="/pages/3WRKOGBqfUMeQeOvRWEF" %}
[Querying Data](/zaubercms/creating-a-website/querying-data.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://aptitude.gitbook.io/zaubercms/extending-zaubercms/blocklisteditor/content-block-preview.md?ask=<question>&goal=<endgoal>
```

`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.