# Erlang applications, Zotonic modules, and sites

Source: https://zotonic.com/docs/2919/erlang-applications-zotonic-modules-and-sites

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

Language: en

These terms describe different parts of the system.

::: {.aside}
Putting a package on the code path is different from activating its Zotonic module for a particular site. Use [Application startup and per-site module activation](/id/2926) to understand this distinction when a compiled feature is missing.
:::

An **Erlang application** is a package described by a `.app` file, normally generated from `src/<name>.app.src`. It can provide modules and an OTP application callback.

A **Zotonic module** is functionality that can be activated for a site. Its main Erlang module declares attributes such as `-mod_title` and `-mod_depends`.

A **site** is a named website with its own configuration and runtime context. Several sites share the same Erlang VM and loaded code, while module activation and site data are site-specific.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/2919?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/2919?language=en>)
