Project layout and modules
How a Jadpo project is laid out on disk, how one file sees declarations from another, and the naming rules every name follows.
| Project layout A project is the folder that holds |
| Source files File order and declaration order never matter. |
| Domains instead of modules Jadpo has no modules. |
| The root The files and folders a project's root may hold, and nothing else. |
| What application { } holds
|
| Domains Every project has at least one domain, and all code outside the root files lives in one. |
| Files and names Each file holds one primary declaration, named after it: |
| Sharing and promotion A type or helper used by one file lives in that file. |
| Ownership and calls replace modules A domain owns everything in it, and it is the boundary of what other code can see. |
| Imports With imports, the place every name comes from can be read from the file itself. |
| Naming Every name has one spelling, decided by what kind of thing it names. |
| Comments A line comment starts with |
| Database The identity registry in |
| What it looks like in code Sketches of how the pieces sit in their files. |
What is built says which of this works today.
Details
The exact rules, for when you hit an edge case.
| The layout in detail Every project has the same shape at every size. |
| Folders other pages describe The layout only reserves these folders; each piece has its own page. |
Markdown for agents: /docs/project-layout-and-modules.md.Built from Jadpo main at aee2e8f.