# Wrapper Route

The objective of the WrapperRoute is to define a template for reuse. It is based on the template design pattern.

**Objective** 

The main objective of this tutorial is to teach you how to create your route wrapper, structure it, and configure it correctly to give your design more stability, avoid compilation errors, and make it more dynamic or responsive.

**Steps** 

1. Create the necessary components and containers for the structure (Header and footer, to name a few)
2. Create a frame, that will be the container.
3. All these elements will be an auto layout.
4. Open the Uncodie plugin.
5. On the Components screen, select WrapperRoute within the Component type.
6. In the attributes, url will be the address that the WrapperRoute will display and is required, and the parent will be the WrapperRoute that contains it.
7. Done, set your content as wrapper content and save.

**Use cases** 

The wrapper route is used when you need a template to reuse throughout your project.

**When not to use**

You don't need to use the wrapper route when you don't have layers or auto-layouts that you need to reuse.

**Common problems**

* If the route wrapper may have problems compiling when:
* The configuration made to your wrapper route in the plugin is not correct.
* Another WrapperRoute with the same name
* Does not contain Wrapper Content

{% embed url="<https://www.youtube.com/watch?v=QxRJWGfW5YU>" %}

\ <br>


---

# 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://docs.uncodie.com/1.0/tutorials/components/wrapper-route.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.