> 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/v3.x/developing/developing-for-contentbox/front-end-development/managing-assets.md). # Managing Assets By default the `includes` directory of your theme is used to store your static assets. Because these assets are called from your customized theme, however, you may use any directory conventions you prefer. If you plan to use customized paths or CDN links in your template, it's best to create a setting in your `Theme.cfc` which will then be configured through the admin. ## AddAsset() Method for CSS and JS In the Front End of the Website, the Theme takes over the rendering. To ensure all Assets are added correctly from various modules, for every theme, we recommend using the htmlHelper's `addAsset()` method. Since the SuperType ( which all ColdBox items inherit from ) implements addAsset() you can call it directly from almost any file in your application. `addAsset( "#prc.cbroot#/includes/css/#css#.css" );` You might have noticed, that even in the [Admin Asset Management methods explained here](/v3.x/developing/developing-for-contentbox/back-end-development/js-and-css-assets.md), the actual implementation of the cssFullAppendList and cssAppendList use the addAsset to add the CSS to the head of the HTML page. *This applies to both CSS and JS. The main downside to this approach is that all assets added with addAsset are added to the head. The order of the assets is not strictly ( or easily ) controlled either.* ### Better Asset Management coming soon We recommend using a similar approach to the admin, using an array, and outputting in the theme. We will be standardizing an approach soon, so all themes can easy implement these features, with a single line `cbhelper` method. --- # 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/v3.x/developing/developing-for-contentbox/front-end-development/managing-assets.md?ask=&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.