> For the complete documentation index, see [llms.txt](https://quantumphp.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantumphp.gitbook.io/docs/packages/asset/architecture.md).

# Architecture

Asset is a small registry package with three moving parts.

## `Asset`

`Asset` is the value object for one frontend file.

It stores:

* type (`CSS` or `JS`)
* path
* optional unique name
* optional position
* optional HTML attributes

It can also resolve its public URL and render its own HTML tag.

## `AssetManager`

`AssetManager` is the package entry point.

It keeps an in-memory store of registered assets, organizes them by type and position, and outputs rendered tags on demand.

The manager does not write files or publish assets to disk. It only tracks metadata and turns that metadata into HTML output.

## Global helpers

The helpers connect the package to the rest of the framework:

* `asset()` resolves the shared manager instance from DI
* `assets($type)` renders one asset type directly

This design makes the package easy to call from plain PHP templates without passing the manager through every layer manually.

## Lifecycle to keep in mind

1. Create one or more `Asset` objects.
2. Register them with the shared manager.
3. Render `css` or `js` output where needed.
4. Optionally call `flush()` if you need a clean registry afterward.

Because the manager is shared, lifecycle discipline matters more in tests, CLI scripts, or any long-running process than in short-lived PHP-FPM requests.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://quantumphp.gitbook.io/docs/packages/asset/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.