# Overriding Layouts

Now, let's say you want to override the layout for a module. Go to the host application's layouts folder and create a folder called `modules` and then a folder according to the module name, in our case `simpleModule`:

```javascript
/MyApp
  + layouts 
    + modules 
       + simpleModule
```

What this does, is create the override structure that you need. So now, you can map 1-1 directly from this overrides folder to the module's layouts folder. So whatever layout you place here that matches 1-1 to the module, the parent will take precedence. Now remember this is because our layouParentLookup property is set to true. If we disable it or set it to false, then the module takes precedence first. If not found in the module, then it goes to the parent or host application and tries to locate the layout. That's it, so if I place a main.cfm layout in my parent structure, the that one will take precedence.

```javascript
/MyApp
  + layouts 
    + modules 
       + simpleModule
         + main.cfm
```

These features are great for skinning modules or just overriding view capabilities a-la-carte. So please take note of them as it is very powerful.


---

# 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://coldbox.ortusbooks.com/v5.x-1/hmvc/modules/layout-and-view-renderings/overriding-layouts.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.