> For the complete documentation index, see [llms.txt](https://docs.gutenbricks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gutenbricks.com/getting-started/next-configure-page-template-to-render.md).

# Next: Configure Page Template to render

After creating your first GutenBricks page, you may want to view it on the frontend. Did you notice the blocks are not rendered in full-width?

{% embed url="<https://youtu.be/31RnLzJ9trc>" %}

After the block is created from the template, you need to choose the right template to render it on the front-end. There are four different methods:

* **GutenBricks' Built-in Template** - GutenBricks comes with a default page template that renders blocks in full page width. You can also change the name of the template on the settings page.

<figure><img src="https://115503993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVRpgq7lelxP9PFleE0QT%2Fuploads%2FgSxpa0xGkQOKGPYeV3Yx%2FScreenshot%202024-06-30%20at%201.56.22%E2%80%AFAM.png?alt=media&amp;token=ec6ce347-2ab3-4611-9c47-b3bfad75e029" alt="" width="375"><figcaption></figcaption></figure>

* **GutenBricks - Page Template** - Create a template and set its type to 'GutenBricks - Page Template.' This can be particularly useful if clients want to choose their own page template for rendering a page.
* **The good old Single Template** - Create a 'Single' type template, add a Post Content element, and set its data source to 'WordPress.' This way, the WordPress content will be rendered within the Post Content element.
* **Child Theme** - Choose 'Render with WordPress,' and it will be rendered using the Bricks Builder default template-parts/posts.php. For this option, you will need to create a child theme.

<figure><img src="https://115503993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVRpgq7lelxP9PFleE0QT%2Fuploads%2FV8cnfXvBfmDcqupsOQ5f%2FScreenshot%202024-06-30%20at%201.48.28%E2%80%AFAM.png?alt=media&amp;token=19f1dffd-8241-413f-a56b-e2e9a89e8559" alt=""><figcaption><p>This is what you might see after viewing your first GutenBricks page. This is because WordPress is using Bricks Builder's default post template to render the page.</p></figcaption></figure>

### **Setting up GutenBricks - Page Template**

You can let your clients select different templates by creating a 'GutenBricks - Page Template.' If you watched [the tutorial by Paul from WPTuts](https://www.youtube.com/watch?v=keFz6mVEIao), you already know how to use Post Content to render WordPress content.

\
Here is how to set up GutenBricks - Page Template:

1. When you create a new Bricks template choose "GutenBricks - Page Template" as its type

<figure><img src="https://115503993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVRpgq7lelxP9PFleE0QT%2Fuploads%2FXPpdPqD7KVMNPDY7OlV6%2FScreenshot%202024-04-29%20at%202.53.59%E2%80%AFPM.png?alt=media&amp;token=8c57cac5-00b3-4b61-9185-6f1c6c1eb313" alt="" width="315"><figcaption></figcaption></figure>

2. Inside the template, add a Post Content element and set its data source to WordPress.

<figure><img src="https://115503993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVRpgq7lelxP9PFleE0QT%2Fuploads%2F5TyRQCAww6oE5J3M5XTm%2FScreenshot%202024-06-30%20at%201.53.55%E2%80%AFAM.png?alt=media&amp;token=b184a562-5f91-4ea0-9db1-1c3b5d1b5d3a" alt="" width="542"><figcaption></figcaption></figure>

3. The 'GutenBricks - Page Template' will be visible for your clients to choose from within the Gutenberg editor.

<figure><img src="https://115503993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVRpgq7lelxP9PFleE0QT%2Fuploads%2FIeAVvfeNVeYAqsdiDJpb%2FScreenshot%202024-06-30%20at%202.00.32%E2%80%AFAM.png?alt=media&amp;token=24addef9-94e4-460d-a03d-718f2a082ba2" alt="" width="375"><figcaption></figcaption></figure>