Settings Reference
Every setting in Project Settings, and what Astro Editor uses when you haven’t set it. How settings work explains what’s read from your project and what’s stored. Where the settings files are is in Advanced Preferences.
Each setting lives in one place: the collection or the project. The image settings can be set for the project and changed for each collection, and a collection’s new file type falls back to your Preferences.
Collection settings
Section titled “Collection settings”| Setting | When it’s not set |
|---|---|
| Folder | Read from the collection’s glob() loader. If Astro Editor can’t read the loader or its base, <content folder>/<collection name> |
| Show files Astro skips | Off: files the loader’s pattern leaves out aren’t shown |
| Sort | Published date, newest first, with undated files at the top. Without a published date field, title |
| Type (new files) | The New file type preference. If the collection’s pattern only includes .md or only .mdx files, that type, and the setting is ignored |
| Name (new files) | {YYYY-MM-DD}: today’s date |
| Title | A text field named title |
| Description | A text field named description |
| Published date | The first date field in the schema named pubDate, date or publishedDate |
| Draft | A true/false field named draft. Without one, there’s no draft badge or filter |
| Image folder | The project’s |
| Image paths | The project’s |
| Link URLs | A relative file path |
The field settings look in the collection’s generated schema. Without one, Astro Editor uses the names above and reads them from each file’s frontmatter.
Project settings
Section titled “Project settings”| Setting | When it’s not set |
|---|---|
| MDX components folders | src/components/mdx |
| Add imports (MDX components) | Off |
| Image folder | src/assets, with each collection’s images in a folder named after it |
| Image paths | Relative to the file |
| Content folder | src/content |