General principles
This website's graphical architecture is inspired by the principles of Brad Frost's Atomic Design. This method distinguishes five levels of graphic organisation:
- Page
-
The “highest” graphical organisation level is the “page”, which corresponds to the conjunction of every other organizational elements to form a whole unit on which user experience can be measured.
Example: In this website, a “page” typically corresponds to an HTML document associated to a specific route.
Note:
At a “higher” organizational level, we could for instance consider the “website”, just as we could talk about the organization of pages inside a book. However, I consider that these organizational levels “above” that of the “page” are not “graphical”, but require other analytical frameworks.
- Template
-
The “template” prescribes how the different elements are composed in each page.
Example: In our case, the “templates” describe principles such as the position of a navbar on top of the viewport, the presence of links in the footer, and so on. Technically, the “templates” are made possible thanks to Twig's concept of blocks, built with the
{extends}instruction. - Organism
-
An “organism” is a graphical unit of the user interface which gathers multiple functional elements into one coherent group.
Example: the navbar on top of the page, the footer, or the “cards” design.
- Molecule
-
A “molecule” corresponds to one functional unit of the graphical interface, which answers one specific use case.
Example: a line of a form, a button, etc.
- Atom
-
Finally, “atoms” correspond to elementary units of the language (ie. made of a sole HTML element with no children, or with only text nodes), which can be articulated together to form “molecules”.
Example: an
<input>field, which can form a molecule when combined with a<label>in a form row.
Image: Paris, Bibliothèque nationale de France, Mélanges Colbert 60, f. 107r,
6/20/26