Types as modules

A type of the profile (3 passages, no note) is a folder that carries everything the type (note: Type) needs: its declaration (17 passages, no note), its labels (44 passages, no note) per interface (21 passages, no note) language (40 passages, no note), its note template (4 passages, no note) and, when the generic page is not enough, the components (46 passages, no note) that render (24 passages, no note) it. The core types (4 passages, no note) are written that way and the default profile (note: Profile) is assembled from them, so that the format (16 passages, no note) the engine (13 passages, no note) ships is the format a team extends it with: a project (note: Project) keeps its own modules (27 passages, no note) in a folder its profile names, a plugin (note: Plugin) contributes modules through a contribution point (note: Contribution point) of the plugin API, and the build (note: Build) merges (27 passages, no note) them before the keys (46 passages, no note) of the project profile (9 passages, no note), plugins first, refusing a module of a core type, which is extended through the profile, and two modules of one type. The site (note: Site) never learns a type slug (4 passages, no note): the entity page (note: Entity page) exposes the declaration of the type and every attribute (note: Attribute) of the note (note: Note), declared and not, and a dedicated component for a type, an attribute or a mapped section (note: Section) is resolved (8 passages, no note) by name, the project theme (note: Theme) first, then the module, then the generic page, which remains (6 passages, no note) correct when nothing specific is said.

• Entity page
• Gallery index
• Plugin API
• Build
• Declarative profile