> For the complete documentation index, see [llms.txt](https://mariohernandez.gitbook.io/components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariohernandez.gitbook.io/components/getting-started/component-architecture.md).

# Component Architecture

I typically recommend to group components or patterns in individual folders within your Drupal theme. This not only provides organization as your catalog of components grows, but it also makes each component completely reusable and even portable as all the pieces of a component are encapsulated in a single folder. Here's an example of a typical component architecture. Your particular workflow may vary.

```
+
|--src
|  |--patterns
|     |--components
|        |--card
|           |-- card.js
|           |-- card.md
|           |-- card.scss
|           |-- card.twig
|           |-- card.json
+
```

A component is typically broken down in four parts:

* **Markup**: Markup or HTML for a component is written in [Twig templates, Drupal 8's templating engine](https://www.drupal.org/docs/theming-drupal/twig-in-drupal).
* **Data**: Demo or stock data for components is usually provided in YAML or JSON format. These are lightweight formats for storing data. In this training we will use JSON (**J**ava**S**cript **O**bject **N**otation).
* **Styles**: These are written in CSS or SCSS.
* **Behavior/interaction**: The component's behaviors are usually handled with JavaScript. Most components don't need JavaScript.
* **Annotations** (Optional): Annotations are used to document the details of a component and are typically written in markdown format (`.md`). This is extremely useful for teams because it outlines technical details of a pattern such as variable names, attributes, data structure, etc.


---

# 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://mariohernandez.gitbook.io/components/getting-started/component-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.