# Product Pages Documentation Enhancement Plan

**Last Updated:** 2026-01-08

Plan for enhancing product pages documentation with complete content extracted from PHP files and aligned with feature documentation.

## Current Status

**Documentation Files:** 13/13 exist (100%)
**Content Completeness:** ~30% (many "To be documented" placeholders)
**Enhancement Needed:** High priority

## Gaps Identified

### Common Gaps Across All Pages

1. **CTAs** - "To be documented" (should extract from PHP includes)
2. **Use Cases** - "To be documented" (should reference feature docs)
3. **Messaging** - "Key messages to be documented" (should extract from page content)
4. **SEO Keywords** - "To be documented" (should extract from meta tags and schema)
5. **Content Strategy** - Missing detailed messaging approach
6. **Schema Documentation** - Missing schema markup details
7. **Maintenance** - Generic "Feature updates, Product changes" (needs specifics)

## Enhancement Approach

### Phase 1: Extract Content from PHP Files

For each product page:

1. **Extract Meta Tags**
   - Title, description, keywords
   - OG tags, Twitter cards
   - Canonical URL

2. **Extract Schema Markup**
   - SoftwareApplication schema
   - Service schema
   - WebPage schema
   - BreadcrumbList schema
   - FAQPage schema (if present)

3. **Extract Hero Section**
   - Headline
   - Description
   - CTA buttons (from include_ctabuttons.php)

4. **Extract Feature Sections**
   - Section headings
   - Key benefits
   - Feature highlights

5. **Extract FAQs**
   - Questions and answers from schema or page content

### Phase 2: Enhance Documentation Files

For each documentation file:

1. **Complete Page Structure Section**
   - Hero with actual CTAs
   - Complete feature sections list
   - Use cases (reference feature docs)

2. **Complete Content Strategy**
   - Messaging approach (extracted from page content)
   - SEO keywords (from meta tags and schema)
   - Conversion strategy (CTA placement and hierarchy)

3. **Add Schema Documentation**
   - Document all schema types used
   - List required fields
   - Note update requirements

4. **Enhance Maintenance Section**
   - Specific update triggers
   - Review schedule
   - Update checklist

5. **Add Technical Details**
   - File structure
   - Dependencies
   - Integration points

## Enhancement Priority

### P0 - Core Product Pages (High Traffic)

1. **Schichtplanung** (`product_schichtplan_neu.php` — `/schichtplan`; archived: `product_shiftplan.php`)
   - Core feature, high traffic
   - **Effort:** 1-2 hours

2. **Zeiterfassung** (`product_timetracking.php`)
   - Core feature, high traffic
   - **Effort:** 1-2 hours

3. **Lohnabrechnung** (`product_payroll.php`)
   - Core feature, high conversion
   - **Effort:** 1-2 hours

**P0 Total:** 3-6 hours

### P1 - Supporting Product Pages

4. **Abwesenheiten** (`product_absences.php`)
5. **Dokumentenmanagement** (`product_documents.php`)
6. **Digitale Personalakte** (`product_personnelfile.php`)
7. **Checklists** (`product_checklists.php`)
8. **Events** (`product_events.php`)
9. **App Store** (`product_appstore.php`)

**P1 Total:** 6-9 hours (1-1.5 hours each)

### P2 - Variant Pages

10. **Payroll (Alt)** (`product_payroll_alt.php`)
11. **Payroll (Neu)** (`product_payroll_neu.php`)
12. **Webinar** (`product_webinar.php`) - Note: Moved to webinar-pages
13. **Payroll Webinar** (`product_payroll_webinar.php`) - Note: Moved to webinar-pages

**P2 Total:** 2-3 hours

## Total Estimated Effort

- **P0:** 3-6 hours
- **P1:** 6-9 hours
- **P2:** 2-3 hours
- **Total:** 11-18 hours

## Enhancement Template

### Enhanced Page Structure Section

```markdown
### Hero Section

- **Headline:** [Extracted from PHP]
- **Description:** [Extracted from PHP]
- **Primary CTA:** "Kostenlos testen" → `/kostenlos-testen` (from include_ctabuttons.php)
- **Secondary CTA:** "Demo ansehen" → `/demo` (if present)
- **Callback Button:** Yes/No (from $showCallbackButton variable)
```

### Enhanced Content Strategy Section

```markdown
### Messaging

**Primary Message:** [Extracted from hero description]
**Value Proposition:** [From meta description]
**Key Benefits:** [From feature sections]
**Differentiators:** [From comparison points]

### SEO Focus

**Primary Keyword:** [From title/meta]
**Secondary Keywords:** [From schema featureList, content analysis]
**Long-tail Keywords:** [From FAQ questions]
**Target Intent:** Informational → Commercial (conversion path)

### Conversion Strategy

**CTA Hierarchy:**
1. Primary: "Kostenlos testen" (above fold, hero)
2. Secondary: "Demo ansehen" (throughout page)
3. Tertiary: "Mehr erfahren" (soft CTAs)

**CTA Frequency:** Every 2-3 sections
**Conversion Path:** Hero → Benefits → Social Proof → FAQ → Final CTA
```

### Enhanced Schema Documentation

```markdown
## Schema Markup

### SoftwareApplication Schema

**Required Fields:**
- name: "Ordio [Feature Name]"
- applicationCategory: "BusinessApplication"
- offers.price: "89"
- offers.priceCurrency: "EUR"
- aggregateRating.ratingValue: "4.9"
- aggregateRating.reviewCount: "54"
- featureList: [7-8 specific features]

**Update Requirements:**
- Pricing: Update if pricing changes
- Ratings: Update quarterly
- FeatureList: Update when features added/removed
- softwareVersion: Update with major releases
```

## Related Documentation

- [Product Features Documentation](../../product-features/) - Reference for use cases
- [Product Pages Inventory](PRODUCT_PAGES_INVENTORY.md) - Complete page list
- [Cursor Rules - Product Pages](../../../../.cursor/rules/product-pages.mdc) - Page patterns
- [Documentation Templates](../../../DOCUMENTATION_TEMPLATES.md) - Standard templates