# Content Management Constraints


**Last Updated:** 2025-11-20

Important information about what content can and cannot be managed from this codebase.

## WordPress CMS Content

**Blog Content Location:** `/insights/*` (except pillar pages)

**Managed by:** WordPress CMS

**Cannot Edit From This Codebase:**

- Blog post content
- Blog post titles, meta descriptions
- Blog post internal links
- Blog post schema markup
- Blog post images and media

**Can Manage From This Codebase:**

- Blog theme files
- Blog header/footer includes
- Blog sidebar widgets
- Blog navigation structure
- Blog template files

## Actionable Recommendations

### ✅ Can Implement Directly (This Codebase)

**Product Pages:**

- Add links TO blog posts
- Add links TO tools, templates, comparisons
- Edit product page content
- Update product page schema

**Industry Pages:**

- Add links TO blog posts
- Add links TO products, tools
- Edit industry page content
- Update industry page schema

**Tools Pages:**

- Add links TO blog posts
- Add links TO products, pillar pages
- Edit tool page content
- Update tool page schema

**Tillar Pages:**

- Edit pillar page content (managed here)
- Add links TO blog posts
- Add links TO products, tools, templates
- Update pillar page schema

**Comparison Pages:**

- Add links TO blog posts
- Add links TO products
- Edit comparison page content
- Update comparison page schema

**Templates Pages:**

- Add links TO blog posts
- Add links TO products, pillar pages
- Edit template page content

**Download Pages:**

- Add links TO blog posts
- Edit download page content

**Webinar Pages:**

- Add links TO blog posts
- Edit webinar page content

**Static Pages:**

- Edit static page content
- Add links TO blog posts

### ❌ Requires WordPress CMS Access

**Blog Posts:**

- Edit blog post content
- Add links FROM blog posts to other pages
- Update blog post meta tags
- Update blog post schema
- Add images to blog posts

**Blog Categories:**

- Edit category pages
- Update category structure

**Blog Archives:**

- Edit archive pages
- Update archive structure

## Implementation Workflow

### For Recommendations Requiring Blog Post Edits

1. **Document Required Changes**

   - List specific blog posts needing updates
   - Document exact links to add
   - Provide anchor text recommendations
   - Note priority level

2. **Coordinate with Content Team**

   - Share recommendations document
   - Request WordPress CMS access or coordination
   - Provide implementation guidelines

3. **Track Implementation**
   - Mark blog post recommendations as "Requires CMS Access"
   - Track completion status
   - Verify links after implementation

### For Recommendations Actionable in This Codebase

1. **Implement Directly**

   - Edit PHP files in `v2/pages/`
   - Add links to blog posts
   - Update content and schema
   - Test changes

2. **Document Changes**
   - Note what was changed
   - Document new links added
   - Update analysis if needed

## Priority Classification

### High Priority - Actionable Here

- Product pages → Blog links (can add TO blog posts)
- Industry pages → Product links (can add TO products)
- Tools pages → Pillar links (can add TO pillar pages)
- Pillar pages → Tools links (can add TO tools)
- Comparison pages → Product links (can add TO products)

### Medium Priority - Requires CMS Access

- Blog posts → Product links (requires WordPress CMS)
- Blog posts → Pillar links (requires WordPress CMS)
- Blog posts → Tool links (requires WordPress CMS)
- Blog post content updates (requires WordPress CMS)

### Low Priority - Nice to Have

- Blog posts → Template links (requires WordPress CMS)
- Blog posts → Download links (requires WordPress CMS)
- Blog post schema updates (requires WordPress CMS)

## Recommendations Summary

**Immediate Action (This Codebase):**

- Add 36-60 product → blog links
- Add 10-15 industry → product links
- Add 13 tools → pillar links
- Add 6-10 pillar → tools links

**Requires WordPress CMS:**

- Add blog → product links (coordinate with content team)
- Add blog → pillar links (coordinate with content team)
- Update blog post content (coordinate with content team)

## Notes for AI Agents

When making recommendations:

1. **Check Content Location:**

   - If URL starts with `/insights/` and is NOT a pillar page → WordPress CMS
   - If URL is pillar page (`/insights/dienstplan` or `/insights/zeiterfassung`) → This codebase
   - All other pages → This codebase

2. **Recommendation Format:**

   - ✅ "Can implement: Add link TO blog post from product page"
   - ❌ "Requires CMS: Add link FROM blog post to product page"

3. **Implementation Priority:**
   - Prioritize recommendations actionable in this codebase
   - Document CMS-required recommendations for content team
   - Provide clear implementation guidelines for both

## Related Documentation

- `FULL_SITE_LINKING_STRATEGY.md` - Linking recommendations (note CMS constraints)
- `CONTENT_STRATEGY.md` - Content recommendations (note CMS constraints)
- `PAGE_TYPE_RELATIONSHIPS.md` - Relationship analysis (note CMS constraints)