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

# Front-End Development

In developing your user interface, the majority of your time will be spent creating content in the admin and modifying files from within your custom theme, located in the `[ContentBox Module Home]/themes` directory.

With state-of-the art development tools like [CommandBox](http://commandbox.ortusbooks.com/content/) to assist with scaffolding and dependency management and [Coldbox Elixr](https://github.com/ColdBox/elixir/wiki), it's easy to build out your theme in a fraction of the time it might otherwise take.

## Theme Directory Conventions

A typical theme directory structure might be:

###  MyAwesomeTheme

#### -  includes

*  css
*  fonts
*  js

#### -  layouts

#### -  templates

#### -  views

#### -  widgets

For more information on the theme directory structure and configuration options see [ContentBox Theme Development](https://contentbox.ortusbooks.com/developing/developing-for-contentbox/front-end-development/theme-development).

## Modularity

In addition, many front-end focused modules and libraries are available on Forgebox and can be installed from the [CommandBox](http://commandbox.ortusbooks.com/content/) CLI and used immediately in your templates, widgets and views. For example, to install a Twitter feed widget for ContentBox, simply run `box install ID=cbwidget-tweetfeed directory=widgets` from your theme directory and it will automatically be available for use in the admin. You may browse the ever-growing list of Forgebox libraries and modules on [the Forgebox site](https://www.coldbox.org/forgebox/) or run `forgebox help` from within CommandBox to begin exploring the available options.


---

# 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://contentbox.ortusbooks.com/v4.x/developing/developing-for-contentbox/front-end-development.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.