Content Repository
What the content repository is
Section titled “What the content repository is”Every piece of content your team creates in CMP lives in the content repository — a central store for drafts, approved content, images, videos, documents, and brand assets. Think of it as the single source of truth for everything your content operation produces.
The repository is not just file storage. It understands what each item is, who created it, what stage it is in, and how it relates to campaigns, brand guidelines, and publishing targets.
What the repository stores
Section titled “What the repository stores”The content repository manages two categories of items:
Structured content
Section titled “Structured content”These are the articles, blog posts, social media copy, and other text-based content your team creates in CMP’s editor. Each piece of structured content includes:
- Body content — Rich text with headings, lists, inline images, and links
- Metadata — Title, description, tags, categories, target audience, and SEO fields
- Workflow state — Current stage, assignee, approval history
- Campaign association — Which campaign the content belongs to
- Version history — Every saved revision, with the ability to compare or restore
Digital assets
Section titled “Digital assets”Assets are the files that support content production — images, videos, PDFs, design files, and brand resources:
| Asset type | Supported formats | Typical use |
|---|---|---|
| Images | JPEG, PNG, WebP, SVG, GIF | Blog headers, social graphics, product photos |
| Video | MP4, MOV, WebM | Embedded video content, social clips |
| Documents | PDF, DOCX, PPTX | Downloadable resources, reference materials |
| Design files | AI, PSD, Sketch, Figma links | Source files for creative team collaboration |
| Brand assets | Logos, fonts, color palettes | Ensuring consistent brand application |
How the repository organizes content
Section titled “How the repository organizes content”CMP uses a combination of folders, tags, and smart filters to keep content findable as your library grows.
Folders provide a hierarchical structure. Most teams organize by campaign, content type, or business unit. A folder might contain all assets for a product launch, or all blog posts for Q2.
Tags add a flexible layer on top of folders. A single asset can carry multiple tags — “product-launch,” “social,” “approved” — making it discoverable through different search paths.
Smart filters let you create saved views based on combinations of metadata: all images tagged “hero” that are approved and unused, or all blog drafts assigned to a specific author that are overdue.
How CMP’s repository differs from CMS media management
Section titled “How CMP’s repository differs from CMS media management”Both CMP and CMS store digital assets, but they serve different purposes at different stages of the content lifecycle.
| Capability | CMP repository | CMS media library |
|---|---|---|
| Primary purpose | Content production and collaboration | Content delivery to site visitors |
| Who uses it | Writers, designers, marketers, reviewers | Editors, developers |
| Workflow awareness | Assets carry approval status and campaign context | Assets are available or not — no workflow stages |
| Version control | Full version history with comparison and rollback | Version history focused on published state |
| Tagging | Flexible, team-managed tags for internal organization | Structured metadata aligned to site taxonomy |
| Access control | Role-based access tied to teams and campaigns | Permission model tied to content tree structure |
| Brand guidelines | Built-in brand compliance checking | No native brand enforcement |
Asset lifecycle in the repository
Section titled “Asset lifecycle in the repository”Assets move through a lifecycle that mirrors the content workflow:
- Upload — Team members add assets via drag-and-drop, bulk upload, or direct capture from integrated tools
- Organize — Assets are tagged, placed in folders, and associated with campaigns or content items
- Review — Brand managers or creative leads verify that assets meet guidelines (correct dimensions, approved messaging, proper logo usage)
- Approve — Approved assets become available for use in content across the team
- Use — Authors embed approved assets in content items during production
- Archive — After a campaign ends or assets become outdated, they move to an archive state — still accessible but no longer surfaced in active searches
Search and discovery
Section titled “Search and discovery”The repository includes full-text search across file names, tags, descriptions, and embedded metadata. AI-powered features enhance discovery:
- Visual similarity search — Find images that look similar to a reference image
- Auto-tagging — Automatically suggest tags based on image content analysis
- Duplicate detection — Flag assets that appear to be duplicates of existing files
Rights and permissions
Section titled “Rights and permissions”Not every team member should access every asset. The repository supports:
- Team-based access — Restrict folders or asset collections to specific teams
- Campaign-scoped visibility — Limit asset visibility to campaign participants
- Download controls — Allow viewing but restrict downloading of source files
- Expiration dates — Assets with licensing restrictions can carry expiration dates, with automatic notifications before rights lapse