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

# Conventions

Discover the major conventions of the ColdBox framework

The core conventions delineate the contract between ColdBox and **you** for file/directory locations and more. Below is a table of the core conventions:

## Directory/File Conventions

* **/config** - Where configuration files are stored
  * **/Coldbox.bx** (or `.cfc` for CFML) - Your application configuration object (*optional* )
  * **/CacheBox.bx** (or `.cfc` for CFML) - Your application CacheBox configuration (*optional* )
  * **/Router.bx** (or `.cfc` for CFML) - Your application URL Router (*optional* )
  * **/Scheduler.bx** (or `.cfc` for CFML) - Your application global task scheduler (optional)
  * **/WireBox.bx** (or `.cfc` for CFML) - Your application WireBox Configuration (*optional* )
* **/handlers** - This holds the app's event handlers (controller layer)
* **/includes** - For public assets, helpers and i18n resources
  * **/css** - This can hold your CSS (optional)
  * **/js** - This can hold your JavaScript (optional)
* **/layouts** - Your HTML layouts (view layer)
* **/models** - This holds your app's classes (model layer)
* **/modules** - This holds the CommandBox tracked modules
* **/modules\_app** - This holds your app's modules
* **/tests** - Your test harness, including unit and integration testing
  * **/specs** - Where your test bundles go
* **/views** - Your HTML views will go here (view layer)

## Execution Conventions

ColdBox also has several execution conventions. This means that we have a convention or a default for the event, action, and layout to be used if you do not tell it what to use:

<table data-header-hidden><thead><tr><th width="179">Convention</th><th width="199.33333333333331">Default Value</th><th>Description</th></tr></thead><tbody><tr><td><strong>Convention</strong></td><td><strong>Default Value</strong></td><td><strong>Description</strong></td></tr><tr><td>Default Event</td><td><code>main.index</code></td><td>The default event to execute when no event is specified</td></tr><tr><td>Default Action</td><td><code>index()</code></td><td>The default action to execute in an event handler controller if none is specified</td></tr><tr><td>Default Layout</td><td><code>layouts/Main.bxm</code> (or <code>.cfm</code> for CFML)</td><td>The default system layout to use</td></tr></tbody></table>


---

# 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://coldbox.ortusbooks.com/getting-started/conventions.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.