Overview
Every project has a very specific folder structure.
| Folder | Purpose |
|---|---|
/documents/ | The content of the site, like pages, posts and products. See Documents. |
/schemas/ | The fields each type of content has, and what values they accept. See Schemas. |
/components/ | How each type of content should be rendered. See Components. |
/assets/ | Files used as they are, like images, fonts and shared CSS or JS. See Assets. |
The documents hold the content. The components decide how it looks.
A file whose name starts with . is ignored when the site is built, like a draft document or an unused component. Only assets are published as they are.
Next to the folders, a few file names are reserved at the root of a project.
| File | Purpose |
|---|---|
/logo.png | The project's logo. |
/preview.png | A preview image of the site, shown on the project's card. |
/README.md | What the project is: purpose, audience, notable pages. |
/INSTRUCTIONS.md | Project-specific rules for AI agents (tone, brand, do's and don'ts), read before they work on the project. |
/SETUP.md | How to set up and configure the project after it's created, shown to you in the editor's chat while the thread is empty. |
/MEMORY.md | Notes AI agents keep across sessions: decisions made, open threads, gotchas. |
These names only have this meaning at the root: a readme.md inside /assets/ is just an asset.
New to Fragmentor? The tutorial builds a small site from start to finish.