Projects Concept

Projects are containers for organizing your Markdown and MDX files into logical groups.

What is a Project?

A project provides:

• Isolated storage: Each project has its own GCS bucket
• File namespace: Files are unique within a project
• Statistics tracking: Automatic file count and size tracking
• Organization: Group related files together

Project Architecture

User Account
├── Project: Blog Articles
│   ├── GCS Bucket: markdown-api-user123-proj1
│   │   ├── post-1.md
│   │   ├── post-2.md
│   │   └── drafts/post-3.md
│   └── Stats: 3 files, 15 KB
├── Project: Documentation
│   ├── GCS Bucket: markdown-api-user123-proj2
│   │   ├── getting-started.md
│   │   └── api-reference.mdx
│   └── Stats: 2 files, 8 KB
└── Project: Default
    ├── GCS Bucket: markdown-api-user123-default
    └── Stats: 0 files, 0 bytes

Default Project

Every account gets a default project automatically:

• Created on first login
• Named “Default Project”
• Cannot be deleted
• Ideal for quick testing

Use Cases

Content Management

Project: "Blog 2025"
- All blog posts for 2025
- Drafts and published posts
- Categories as file prefixes

Client Work

Project: "Client ABC"
- All content for specific client
- Isolated from other clients
- Easy to manage and bill

Agent Workspaces

Project: "Agent Memory"
- Conversation history
- Agent state
- Context storage

Best Practices

1. Descriptive names: Use clear project names
2. Logical grouping: Group related files
3. One project per purpose: Don’t mix unrelated content
4. Regular cleanup: Delete unused projects

See Also

• Projects API - API reference
• Files Concept - Learn about files