# Application and module names

Source: https://zotonic.com/docs/2922/application-and-module-names

URI: https://zotonic.com/id/2922

Language: en

Use distinct, consistent names so code and assets can be found without ambiguity.

For a reusable feature:

- Directory/application: `zotonic_mod_garden`
- Main Zotonic module: `mod_garden`
- Model: `m_garden`
- Controller: `controller_garden_export`
- Filter: `filter_garden_label`
- Site-specific template: `garden_overview.tpl`

Erlang module names are global within a VM. Two sites cannot load different implementations under the same Erlang module name and expect isolation.

Actions, validators, and scomps use Zotonic's naming conventions, including the owning site/module component. Inspect an existing implementation before naming a new one. Templates can intentionally share names to participate in module-priority overrides; ordinary helper Erlang modules should not.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/2922?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/2922?language=en>)
