# Project organization

> For the complete documentation index, see [llms.txt](https://doc.ibexa.co/en/5.0/llms.txt).

An Ibexa DXP project follows Symfony's directory structure to organize files in the project.

Ibexa DXP is a Symfony application and follows the project structure used by Symfony.

You can see an example of organizing a project in the [companion repository](https://github.com/ezsystems/ezplatform-ee-beginner-tutorial/tree/v3-master) for the [Beginner tutorial](https://doc.ibexa.co/en/5.0/tutorials/page_and_form_tutorial/page_and_form_tutorial/index.md).

## PHP code

The project's PHP code (for example, controllers or event listeners) should be placed in the `src` folder.

Reusable libraries should be packaged so that they can be managed with Composer.

## Templates

Project templates should go into the `templates` folder.

They can then be referenced in code without any prefix, for example `templates/full/article.html.twig` can be referenced in Twig templates or PHP as `full/article.html.twig`.

## Assets

Project assets should go into the `assets` folder. They can be referenced as relative to the root, for example `assets/js/script.js` can be referenced as `js/script.js` from templates.

All project assets are accessible through the `assets` path.

## Configuration

You project's configuration is placed in the respective files in `config/packages`. For more information, see [Configuration](https://doc.ibexa.co/en/5.0/administration/configuration/configuration/index.md).

### Importing configuration from a bundle

If you're keeping some of your code in a bundle, dealing with core bundle semantic configuration can be tedious if you maintain it in the main `config/packages/ibexa.yaml` configuration file.

You can import configuration from a bundle by following the Symfony tutorial [How to Import Configuration Files/Resources](https://symfony.com/doc/7.4/service_container/import.html).

## Versioning a project

The recommended method is to version the whole project repository.