# Custom Component Picker

The custom component picker lets you pick Blazor components that implement `ICustomContentComponent`. It saves the fully qualified name of the component so you can render it on the front end.

<figure><img src="https://417697475-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVr2cbdfxDGZK1u2Fd59w%2Fuploads%2F4Fdp8TtRCZpwIxnntmtO%2Fcustom.png?alt=media&#x26;token=c41ac9fa-056f-4c00-9420-e93bd39a8e0d" alt=""><figcaption></figcaption></figure>

#### Example of getting value on page

```csharp
(Content!.GetValue<List<string>>("PropertyAliasHere"))
```

This returns a list of the full namespaces to the components, we have a built in component to help render custom components and it's as easy as doing this

```csharp
<RenderCustomContent 
  Content="@(Content)" 
  CustomComponents="@(Content!.GetValue<List<string>>("PropertyAliasHere"))" />
```

Where 'Content' is the current page (Or another page) that is passed to the custom components.


---

# Agent Instructions: 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:

```
GET https://aptitude.gitbook.io/zaubercms/creating-a-website/current-content-properties/custom-component-picker.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
