> For the complete documentation index, see [llms.txt](https://commandbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commandbox.ortusbooks.com/5.7.0/developing-for-commandbox/example-project.md).

# Example Project

## Example Project

Here is an example CommandBox module that uses an interceptor (in the `ModuleConfig.cfc`) and custom commands to help manage its settings.

**On Forgebox:**

<https://www.forgebox.io/view/commandbox-banner-customizer>

**On GitHub:**

<https://github.com/bdw429s/commandbox-banner-customizer>

## CommandBox Banner Customizer

Ever gotten tired of the same lame ASCII art every time you start the CommandBox shell in interactive mode? Well fear not, this module is for you!

### Installation

Install the module like so:

```bash
CommandBox> install commandbox-banner-customizer
```

Once you've done that, there are three module settings you can override to affect how the CLI starts up.

#### Hide the banner

```bash
CommandBox> banner off
```

Now reload the CLI and the ASCII art is gone.

#### Show the banner

```bash
CommandBox> banner on
```

Now reload the CLI and the ASCII art is back.

#### Custom banner text

```bash
CommandBox> banner text "I like spam!"
```

Now reload the CLI and your custom message will appear to greet you. Note this setting is ignored if the banner is `off`.

#### Custom banner file

Want to get all kinds of funky and create your own ASCII art of your cat? Save the exact text you want to output (can be multiple lines) into a file and specify the file path here:

```bash
CommandBox> banner file myCustomBanner.txt
```

Note this setting is ignored if the banner is `off` or if `banner text` is set. For extra credit, try including ANSI escape codes in your text file for a color-coded banner

### Advanced

All these example commands do is set config settings for you. You can also control the module settings without the `banner` commands by directly setting the config settings like so:

```bash
CommandBox> config set modules.commandbox-banner-customizer.hidebanner=true
CommandBox> config set modules.commandbox-banner-customizer.bannertext="I like spam!"
CommandBox> config set modules.commandbox-banner-customizer.bannerfilepath="C:\\myCustomBanner.txt"
```

You can see the current state of this modules settings at any time by using `config show` to print it out.

```bash
CommandBox> config show modules.commandbox-banner-customizer
```


---

# 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://commandbox.ortusbooks.com/5.7.0/developing-for-commandbox/example-project.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.