> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/13.latest/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/grid-layout/render-grid-in-template.md).

# Rendering Grid In a Template

## Using @Html.GetGridHtml

To render a property based on the grid inside a template you should use the HtmlHelper extension:

```csharp
@Html.GetGridHtml(Model, "propertyAlias")
```

This will render the grid item with the alias "propertyAlias" from the current page models' content.

This will by default use the view `/views/partials/grid/bootstrap3.cshtml` you can also use other provided grid template rendering files - for example, the built-in bootstrap2.cshtml view by overloading this helper:

```csharp
@Html.GetGridHtml(Model, "propertyAlias", "bootstrap3")
```

You can create your own custom grid rendering file for your favorite or custom grid framework implementation. Tip: copy one of the existing files as a starting point. By convention, if you create your `mycustomrenderer.cshtml` file in `/views/partials/grid` you can render the grid property like so:

```csharp
@Html.GetGridHtml(Model, "propertyAlias", "mycustomrenderer")
```

Possible paths where you can add the custom Grid layout views:

```none
/Views/grid/mycustomrenderer.cshtml
/Views/Shared/grid/mycustomrenderer.cshtml
/Views/Partials/grid/mycustomrenderer.cshtml
/Views/MacroPartials/grid/mycustomrenderer.cshtml
/Views/Render/grid/mycustomrenderer.cshtml
/Views/Shared/grid/mycustomrenderer.cshtml
/Pages/Shared/grid/mycustomrenderer.cshtml
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/13.latest/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/grid-layout/render-grid-in-template.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.