Content management
The collection browser is Studio’s home screen. Browse and manage entries across your content collections, switch branches, monitor deployment status, and jump into the editor of your choice — all from a single view.
Collection browser
Section titled “Collection browser”The collection browser displays all entries in the currently selected collection. Switch between Grid and List views from the toolbar depending on how you prefer to scan your content.
| Toolbar control | What it does |
|---|---|
| Collection selector | Dropdown listing every collection from src/content/config.ts, with entry counts |
| Search | Live filter on entry slug, filename, and title (debounced) |
| Locale selector | When i18n is enabled with multiple locales, switches the locale you’re viewing |
| Deployment status | Compact badge showing the latest production deployment state (Live / Deploying / Failed) with a link to the deployments page |
| Branch selector | Switch the working branch — see Branches and environments |
| View toggle | Grid or list |
| New entry | Opens the quick-create modal |
Each entry card or row shows the title, the resolved preview URL (auto-detected from your Astro route patterns), an excerpt, a status badge (Published, Draft, Modified, New, or Deleted), the last-modified date if present in the schema, the file size, and — when i18n is enabled — a row of locale badges indicating which translations exist.
Creating entries
Section titled “Creating entries”Click New entry to open the quick-create modal. Enter a title — Studio derives the slug automatically, normalising whitespace and trimming to 60 characters. You can override the slug; a small Auto button re-syncs it from the title if you change your mind.
When you submit, Studio writes a new entry to the current branch with smart defaults populated from the collection schema:
titleis set from your inputdraftis set totrueso new entries don’t ship until you’re ready- Any field with
format: 'date-time'(or a field nameddate,pubDate,publishDate,updatedDate) is set to the current timestamp - Required string, boolean, number, and array fields get type-appropriate placeholder values
After creation you’re taken straight into the entry’s editor to add body content and fill in any remaining fields.
Editing entries
Section titled “Editing entries”Click any entry to open it in the editor associated with your selection. Card actions on each entry (visible on hover) let you:
- Code editor — jumps directly to the underlying Markdown / MDX file in the code editor
- Duplicate — creates a
{slug}-copyclone, marked as a draft, and opens it for editing - Translate — when i18n is enabled, copies the entry to a missing locale so you can translate it
- Delete — removes the entry from the current branch after a confirmation dialog
Unpublished changes and revert
Section titled “Unpublished changes and revert”When you’re on a non-production branch, the browser compares the branch against production and shows a banner — for example, “3 unpublished changes on feature/redesign” — with a Review button that opens the change summary.
Entries that differ from production are tagged with one of three status badges:
| Badge | Meaning |
|---|---|
| Modified | The file exists on both branches and has changed |
| New | The file exists only on the working branch |
| Deleted | The file was removed on the working branch |
For any entry with one of those statuses, an extra Revert action appears on the card. It restores the file from the production branch:
- A modified or deleted entry is overwritten with the production-branch copy
- A new entry is removed from the working branch
Revert is a one-way operation and can’t be undone from Studio — the production branch is the source of truth. For the full branching model, see Branches and environments.
Deployment status
Section titled “Deployment status”The toolbar shows a compact badge for the latest deployment of the production branch:
- Live — last build completed successfully
- Deploying… — a build is in progress
- Failed or another conclusion — the most recent build did not succeed
Clicking the badge opens the deployments view for the project, where you can inspect build history.
Preview URLs
Section titled “Preview URLs”Studio reads your Astro src/pages/ directory to detect dynamic route patterns and resolve a preview URL for every entry:
| Route file | Generated URL pattern |
|---|---|
src/pages/blog/[...slug].astro |
/blog/{slug} |
src/pages/[...slug].astro |
/{slug} |
src/pages/[lang]/[...slug].astro |
/{lang}/{slug} |
Each entry card displays its resolved URL beneath the title so you can see where the entry will live on the published site.
Next steps
Section titled “Next steps”- Visual editor — Live preview with click-to-edit authoring
- AI assistant — Use Studio’s AI tools to generate, refine, and restructure content
- Code editor — Edit project files directly in Studio’s Monaco-powered code editor