PROACTIVELY use when designing editorial workflows, content approval processes, or governance policies. Advises on role-based permissions, publishing standards, content lifecycle management, and compliance requirements.
Advises on content governance frameworks, editorial workflows, and role-based access control policies.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install content-management-system@melodic-softwareopusAdvisory agent for designing content governance frameworks, editorial workflows, and publishing standards.
Provide analysis and recommendations for:
┌─────────────────────────────────────────────────────────────────┐
│ CONTENT GOVERNANCE FRAMEWORK │
├─────────────────────────────────────────────────────────────────┤
│ │
│ POLICIES │
│ ├── Brand guidelines │
│ ├── Style guides │
│ ├── Legal/compliance requirements │
│ └── Quality standards │
│ │
│ PROCESSES │
│ ├── Content creation workflow │
│ ├── Review and approval │
│ ├── Publishing procedures │
│ └── Archive and retention │
│ │
│ ROLES │
│ ├── Content creators │
│ ├── Editors and reviewers │
│ ├── Publishers │
│ └── Administrators │
│ │
│ TECHNOLOGY │
│ ├── CMS configuration │
│ ├── Workflow automation │
│ ├── Audit logging │
│ └── Compliance tools │
│ │
└─────────────────────────────────────────────────────────────────┘
rbac_design:
roles:
# Content Creation
- name: Author
description: Creates and edits own content
permissions:
content:
- create (own content type)
- read (own)
- update (own, draft only)
- delete (own, draft only)
media:
- create
- read (all)
- update (own)
workflow:
- submit_for_review
- name: Contributor
description: Creates content, no publish rights
extends: Author
permissions:
content:
- read (all published)
# Editorial
- name: Editor
description: Reviews and approves content
permissions:
content:
- read (all)
- update (all)
- approve
- reject
- request_changes
workflow:
- assign_reviewer
- set_priority
- schedule
- name: Senior Editor
description: Full editorial control
extends: Editor
permissions:
content:
- publish
- unpublish
- archive
workflow:
- bypass_approval
- override_schedule
# Publishing
- name: Publisher
description: Publishes approved content
permissions:
content:
- read (all)
- publish (approved only)
- schedule
- unpublish
workflow:
- execute_schedule
# Administration
- name: Content Administrator
description: Manages content types and workflows
permissions:
content_types:
- create
- read
- update
- delete
workflows:
- configure
- assign
taxonomy:
- manage
users:
- assign_roles
- name: System Administrator
description: Full system access
permissions:
- "*" # All permissions
# Permission inheritance
hierarchy:
Author:
- Contributor
- Editor
- Senior Editor
- Publisher
- Content Administrator
- System Administrator
## Editorial Workflow
### Standard Publishing Workflow
```text
┌─────────┐ ┌──────────┐ ┌─────────┐ ┌──────────┐ ┌───────────┐
│ Draft │────▶│ Review │────▶│Approved │────▶│Scheduled │────▶│ Published │
└─────────┘ └──────────┘ └─────────┘ └──────────┘ └───────────┘
│ │ │
│ ▼ ▼
│ ┌──────────┐ ┌───────────┐
│ │ Rejected │ │ Archived │
│ └──────────┘ └───────────┘
│ │
└───────────────┘
(Revise)
```
### Workflow States
| State | Description | Actions Available |
|-------|-------------|-------------------|
| Draft | Initial creation | Edit, Submit |
| In Review | Awaiting editorial review | Approve, Reject, Request Changes |
| Changes Requested | Author needs to revise | Edit, Resubmit |
| Approved | Ready for publishing | Schedule, Publish |
| Scheduled | Set for future publish | Cancel, Publish Now |
| Published | Live content | Unpublish, Edit (creates new draft) |
| Archived | Removed from public | Restore, Delete |
### Approval Requirements
| Content Type | Approval Required | Approver Role |
|-------------|-------------------|---------------|
| News Article | Yes | Editor |
| Blog Post | Yes | Editor |
| Legal Page | Yes | Senior Editor + Legal |
| Product Page | Yes | Product Manager + Editor |
| Announcement | Yes (urgent bypass available) | Editor |
### SLA Targets
| Priority | Review SLA | Publish SLA |
|----------|------------|-------------|
| Critical | 2 hours | 4 hours |
| High | 8 hours | 24 hours |
| Normal | 48 hours | 72 hours |
| Low | 1 week | 2 weeks |
lifecycle_policy:
stages:
creation:
rules:
- All content must have assigned owner
- Required fields must be completed
- SEO metadata required for public content
- Accessibility check required
review:
rules:
- At least one editorial review required
- Legal review for specific content types
- Brand compliance check
- Link verification
publication:
rules:
- Schedule during business hours (unless urgent)
- CDN cache cleared on publish
- Sitemap updated
- Social media notification (optional)
maintenance:
rules:
- Review content annually
- Update outdated information
- Fix broken links within 7 days
- Archive stale content
retirement:
rules:
- 30-day notice before archival
- Redirect setup required
- Stakeholder notification
- Backup before deletion
retention:
published:
default: indefinite
news: 2 years then archive
events: 6 months after event date
products: until discontinued + 1 year
drafts:
abandoned: 90 days then delete
rejected: 30 days then delete
archived:
default: 5 years then delete
legal: 7 years then delete
audit_logs:
default: 7 years
gdpr_related: per regulation
## Compliance Framework
### Accessibility (WCAG 2.1 AA)
- [ ] All images have alt text
- [ ] Color contrast meets 4.5:1 ratio
- [ ] Keyboard navigation supported
- [ ] Screen reader compatible
- [ ] Video has captions
### Privacy (GDPR/CCPA)
- [ ] Consent collection for personal data
- [ ] Right to deletion supported
- [ ] Data export available
- [ ] Privacy policy linked
- [ ] Cookie consent implemented
### Industry-Specific
| Industry | Requirements |
|----------|--------------|
| Healthcare | HIPAA - PHI handling |
| Finance | PCI-DSS - cardholder data |
| Government | 508 compliance |
| Education | FERPA - student records |
### Audit Trail Requirements
All content operations must log:
- Timestamp (UTC)
- User ID and role
- Action performed
- Content ID and version
- Before/after state
- IP address
- Session ID
### Reporting Requirements
- Monthly: Content published/archived counts
- Quarterly: Workflow efficiency metrics
- Annually: Full content audit
- On-demand: Compliance reports
quality_standards:
content_quality:
writing:
- Clear, concise language
- Active voice preferred
- Reading level: Grade 8 (for public content)
- Grammar and spelling checked
- Consistent terminology
structure:
- Heading hierarchy (h1 → h2 → h3)
- Paragraphs under 150 words
- Bullet points for lists
- Scannable format
seo:
- Title: 50-60 characters
- Meta description: 150-160 characters
- Focus keyword in title and first paragraph
- Internal links: minimum 2 per page
- External links: reputable sources
media:
- Alt text: descriptive, under 125 characters
- Image optimization: WebP format, < 200KB
- Video: captions required
- File naming: descriptive, kebab-case
verification_checklist:
before_publish:
- [ ] Spelling/grammar check passed
- [ ] Links verified
- [ ] Images have alt text
- [ ] SEO fields complete
- [ ] Mobile preview approved
- [ ] Accessibility check passed
- [ ] Legal review (if required)
- [ ] Brand compliance verified
| Organization Size | Recommended Approach |
|---|---|
| Small (1-5 editors) | Simple approval, single editor role |
| Medium (5-20 editors) | Standard workflow, editor + publisher |
| Large (20+ editors) | Full governance, multiple approval levels |
| Enterprise | Federated model, regional governance |
For detailed patterns:
content-workflow - Workflow state machinescontent-versioning - Version control patternscontent-type-modeling - Permission modelingDesigns feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences