# Ordio Page Type Quick Reference Guides

This document provides quick-reference guides for each major Ordio page type. For comparison pages, see `guides/comparison-pages/COMPARISON_PAGES_GUIDE.md`.

**New page publication (OG, carousels, registry):** [WEBSITE_PAGE_PUBLICATION_INDEX.md](../content/WEBSITE_PAGE_PUBLICATION_INDEX.md) — non-blog shipping checklist and page-family matrix.

**Full Site Context:** This guide covers all 108 pages across 10 page types. For comprehensive site analysis, see `docs/full-site/` directory.

## Table of Contents

- [Product Pages](#product-pages)
- [Industry Pages](#industry-pages)
- [Tools Pages](#tools-pages)
- [Templates Pages](#templates-pages)
- [Download Pages](#download-pages)
- [Webinar Pages](#webinar-pages)
- [Pillar Pages](#pillar-pages)
- [Product Updates Pages](#product-updates-pages)
- [Static Pages](#static-pages)
- [Homepage](#homepage)
- [Cross-Page-Type Relationships](#cross-page-type-relationships)

---

## Product Pages

**Files:** `v2/pages/product_*.php`, `v2/css/product-pages.css`  
**Rule:** `.cursor/rules/product-pages.mdc`  
**Data / SEO hub (10 Funktionen):** [FEATURE_PAGES_CONTENT_INDEX.md](../content/pages/product-pages/FEATURE_PAGES_CONTENT_INDEX.md) — registry `feature-*`, orchestrator, synthesis, FAQ workflow.

### Purpose

Market Ordio features (Schichtplanung, Zeiterfassung, Abwesenheiten, Lohnabrechnung) with benefit-driven copy and clear CTAs.

### Key Elements

- Hero with feature name, value prop, primary CTA
- Benefits list (outcome-focused, du tone)
- Product screenshots or demo video
- Social proof (testimonials, ratings, customer logos)
- Comparison table (Ordio vs. manual/competitor)
- FAQ section
- Secondary CTAs throughout
- **`/schichtplan` Nano promo:** optional WebGL2 liquid-metal background — see [`docs/systems/shared-components/SCHICHTPLAN_NANO_LIQUID_METAL_WEBGL.md`](../systems/shared-components/SCHICHTPLAN_NANO_LIQUID_METAL_WEBGL.md) (fallbacks, minify, smoke test).

### Required Schema

- **SoftwareApplication:** name, description, offers (€89/Standort/Monat), aggregateRating (4.9/5, 54 reviews), featureList, screenshot
- **Service:** serviceType, provider, areaServed (Deutschland)
- **WebPage + BreadcrumbList**

### Copy Guidelines

- Du tone throughout
- Lead with benefits, not features ("erfasst du Arbeitszeiten gesetzeskonform" not "Zeiterfassung-Feature")
- Mention Ordio naturally once per major section
- Keep paragraphs short (2-3 sentences)
- Active voice, present tense

### CSS Classes

`.product-feature`, `.pricing-card`, `.demo-section`, `.product-comparison-table`, `.testimonial-card`, `.product-cta`, `.product-screenshot`, `.integration-badge`, `.feature-icon`, `.product-stat`, `.benefits-list`, `.product-faq`, `.product-video`

### Validation Checklist

- [ ] Hero has clear value prop and primary CTA
- [ ] Benefits list uses du tone and outcome language
- [ ] Comparison table highlights Ordio advantages
- [ ] FAQ answers objections, mentions Ordio once
- [ ] Schema validates (SoftwareApplication, Service)
- [ ] Meta tags complete (title, description, canonical, OG, Twitter)
- [ ] CTAs prominent and correctly linked
- [ ] No layout shifts (CLS), images have dimensions

---

## Industry Pages

**Files:** `v2/pages/industry_*.php`  
**Rule:** `.cursor/rules/industry-pages.mdc`

### Purpose

Target specific verticals (Gastronomie, Einzelhandel, Pflege, Handwerk, Freizeit/Kultur) with tailored messaging and use cases.

### Key Elements

- Hero with industry name, value prop specific to vertical pain points
- Industry challenges section (common problems Ordio solves)
- Use cases / customer stories from that vertical
- Feature highlights relevant to industry
- Customer logos/testimonials from same industry
- FAQ addressing industry-specific concerns

### Required Schema

- **Industry:** name, description, industryCode (NACE/WZ), parentIndustry, subIndustries, typicalChallenges, regulatoryRequirements, customerCount, marketShare
- **Service:** name ("Ordio für [Industry]"), provider, serviceType, areaServed
- **WebPage + BreadcrumbList**

### Industry-Specific Messaging

**Gastronomie:**

- Pain points: Schichtbetrieb, saisonale Schwankungen, Trinkgeldabrechnung
- Compliance: ArbZG, Mindestlohn, Jugendschutz

**Einzelhandel:**

- Pain points: Standortübergreifende Planung, Filialleiter-Entlastung, saisonale Bedarfe
- Compliance: ArbZG, Ladenschlussgesetz, Mindestlohn

**Pflege:**

- Pain points: 24-Stunden-Dienste, Fachkräftemangel, Dokumentationspflicht
- Compliance: ArbZG, Pflegegesetze, Fachkraftquote

**Handwerk:**

- Pain points: Projektplanung, Baustellen-Koordination, Überstunden
- Compliance: ArbZG, Mindestlohn, Arbeitszeiterfassung

**Freizeit/Kultur:**

- Pain points: Event-basierte Planung, Saisonalität, wechselnde Standorte
- Compliance: ArbZG, Mindestlohn, Jugendschutz

### Validation Checklist

- [ ] Hero addresses industry-specific pain points
- [ ] Challenges section lists authentic vertical problems
- [ ] Use cases feel real and relevant to industry
- [ ] FAQ answers industry-specific objections
- [ ] Schema validates (Industry, Service)
- [ ] Industry terminology used correctly
- [ ] Customer logos/testimonials from same vertical

---

## Tools Pages

**Files:** `v2/pages/tools_*.php`, `v2/css/tools-pages.css`  
**Rule:** `.cursor/rules/tools-pages.mdc`

### Purpose

Provide interactive calculators (Arbeitstage-Rechner, Kostenrechner, Brutto-Netto-Rechner) with real-time calculations and export.

### Key Elements

- Hero with tool name and value prop
- Calculator form with inputs, selects, toggles, radio groups
- Real-time calculation results display
- Export functionality (Excel, PDF, CSV)
- How-To or FAQ section
- Dotted background pattern (radial-gradient)

### Required Schema

- **HowTo:** name, description, step array (each with name, text, url), totalTime
- **WebPage + BreadcrumbList**

### Form Patterns

- Number inputs with validation (min/max, step)
- Select dropdowns (styled with custom arrow)
- Radio groups (horizontal button-style)
- Toggle switches for boolean options
- Input with addon (e.g., "€" or "%" suffix)

### CSS Classes

`.calculator-form`, `.form-group`, `.input-with-addon`, `.radio-group`, `.radio-item`, `.toggle-container`, `.toggle-switch`, `.toggle-slider`

### Export Guidelines

- **Excel:** Follow Ordio branding (no purple, relevant brand colors, proper column widths, no header borders)
- **PDF:** Include Ordio logo and branding
- **CSV:** Simple format for data portability

### Validation Checklist

- [ ] Calculator works with valid inputs
- [ ] Validation triggers on invalid inputs (visual feedback)
- [ ] Real-time calculation updates correctly
- [ ] Export functionality works (Excel, PDF, CSV)
- [ ] Responsive layout works (desktop, tablet, mobile)
- [ ] Form inputs have consistent heights (3rem desktop, 3.5rem mobile)
- [ ] Schema validates (HowTo)
- [ ] Dotted background pattern present

---

## Templates Pages

**Files:** `v2/pages/templates_*.php`, `v2/css/templates-pages.css`  
**Rule:** `.cursor/rules/templates-pages.mdc`

### Purpose

Provide customizable Excel/PDF templates (Dienstplan, Schichtplan) with interactive customizers and multi-format export.

### Key Elements

- Hero with template name and value prop
- Interactive customizer UI (opening hours, roles, breaks, costs)
- Real-time preview of template
- Multi-format export (Excel, PDF, Ordio-CSV)
- How-To or FAQ section
- Lead capture integration (optional gating)

### Required Schema

- **DigitalDocument:** name, description, fileFormat (array), encodingFormat, author, publisher, datePublished, dateModified
- **HowTo:** for customizer usage
- **WebPage + BreadcrumbList**

### Customizer Patterns

- Time pickers for opening hours
- Role/position inputs (add/remove dynamically)
- Break duration inputs
- Cost calculation inputs (hourly rates)
- Color pickers for template styling (optional)

### Export Guidelines

- **Excel:** Follow Ordio branding (no purple, relevant brand colors, consistent styling, proper column widths, no header borders)
- **PDF:** Ordio branding (logo, colors), clean layout
- **Ordio-CSV:** Format compatible with Ordio import

### Validation Checklist

- [ ] Customizer UI works (all inputs functional)
- [ ] Real-time preview updates correctly
- [ ] Excel export follows Ordio branding guidelines
- [ ] PDF export includes Ordio logo and clean layout
- [ ] CSV export format compatible with Ordio
- [ ] Responsive layout works
- [ ] Schema validates (DigitalDocument, HowTo)

---

## Download Pages

**Files:** `v2/pages/download_*.php`  
**Rule:** `.cursor/rules/download-pages.mdc`

### Purpose

Provide gated content (PDFs, guides, checklists) with HubSpot form integration for lead capture.

### Key Elements

- Hero with content title and value prop
- Content preview or description
- HubSpot form for lead capture
- File delivery mechanism (direct download or email)
- Success/confirmation state

### Required Schema

- **DigitalDocument:** name, description, fileFormat ("application/pdf"), author, publisher, datePublished, dateModified, about
- **WebPage + BreadcrumbList**

### Form Integration

- Use `include '../base/include_form-gated-content.php'`
- Required fields: email, firstname, lastname (minimum)
- GDPR-compliant (checkbox for consent)
- Form validation (client-side + server-side)

### File Delivery

- **Direct download:** File in `v2/download/` directory, trigger on form success
- **Email delivery:** Send email with download link, link expires after 24-48 hours

### Validation Checklist

- [ ] Hero clearly describes content value
- [ ] Form fields appropriate for content type
- [ ] Form validation works (client-side + server-side)
- [ ] GDPR consent checkbox present
- [ ] File download or email delivery works
- [ ] Success confirmation displays correctly
- [ ] Schema validates (DigitalDocument)

---

## Webinar Pages

**Files:** `v2/pages/webinar_*.php`  
**Rule:** `.cursor/rules/webinar-pages.mdc`

### Purpose

Promote events with registration forms, Event schema, and calendar file (.ics) downloads.

### Key Elements

- Hero with webinar title, date/time, and value prop
- Agenda or topics covered
- Speaker information (optional)
- Registration form (HubSpot integration)
- Calendar download (.ics file)

### Required Schema

- **Event:** name, description, startDate (ISO 8601 with timezone!), endDate, eventStatus, eventAttendanceMode ("OnlineEventAttendanceMode"), location (VirtualLocation with URL), organizer, offers (price: "0"), performer (speakers)
- **WebPage + BreadcrumbList**

### Calendar File (.ics)

```
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Ordio//Webinar//DE
BEGIN:VEVENT
UID:[unique-id]@ordio.com
DTSTAMP:[timestamp]
DTSTART:[start-datetime]
DTEND:[end-datetime]
SUMMARY:[Webinar Title]
DESCRIPTION:[Webinar Description]
LOCATION:[Webinar URL]
STATUS:CONFIRMED
SEQUENCE:0
END:VEVENT
END:VCALENDAR
```

### Validation Checklist

- [ ] Hero includes webinar title, date/time (with timezone!), value prop
- [ ] Agenda clearly lists topics covered
- [ ] Registration form works (validation, submission)
- [ ] GDPR consent checkbox present
- [ ] Calendar download (.ics) works and is valid
- [ ] Confirmation message displays after registration
- [ ] Schema validates (Event) – verify timezone in dates!

---

## Pillar Pages

**Files:** `v2/pages/pillar_*.php`  
**Rule:** `.cursor/rules/pillar-pages.mdc`

### Purpose

Comprehensive SEO content hubs (Dienstplan, Zeiterfassung) with extensive copy, internal links, and FAQ schema.

### Key Elements

- Hero with pillar topic and value prop
- Comprehensive content sections (what, why, how, benefits, challenges)
- Internal links to related pages (product, tools, comparisons, industry)
- FAQ section with FAQ schema
- Secondary CTAs throughout

### Required Schema

- **Article:** headline, description, author, publisher, datePublished, dateModified, articleBody (optional), mainEntityOfPage
- **FAQPage:** same data as the visible FAQ (`v2/data/misc-faqs/pillar_*.json` + `render-faq-json.php`); emit **after** `footer.php` via [`include-marketing-faq-jsonld.php`](../../v2/components/include-marketing-faq-jsonld.php)—do **not** duplicate FAQPage in `<head>` `@graph`
- **WebPage + BreadcrumbList**

### Content Structure

1. Hero – topic introduction, value prop
2. What is [Topic]? – definition, overview
3. Why is [Topic] important? – benefits, challenges
4. How to [Action]? – step-by-step guide
5. Best practices – tips, recommendations
6. Common mistakes – pitfalls to avoid
7. Tools & resources – internal links
8. FAQ – common questions with detailed answers
9. CTA – soft pitch to Ordio

### Internal Linking Strategy

Link to: product pages, tools, templates, industry pages, comparison pages, other pillar pages

### Validation Checklist

- [ ] Hero introduces pillar topic clearly
- [ ] Content is comprehensive and well-structured (1500+ words)
- [ ] Internal links relevant and functional
- [ ] FAQ section addresses common questions
- [ ] Schema validates (Article, FAQPage)
- [ ] Meta tags complete and SEO-optimized
- [ ] Copy is du tone, readable, keyword-optimized
- [ ] Ordio mentions natural (once per major section)

---

## Static Pages

**Files:** `v2/pages/static_*.php`  
**Rule:** `.cursor/rules/static-pages.mdc`

### Purpose

Legal (Imprint, Privacy, Terms), pricing, customers, about, partner pages with specific compliance and accuracy requirements.

### Page-Specific Requirements

**Legal Pages (Imprint, Privacy, Terms):**

- **⚠️ HIGH PROTECTION** – legal text changes require explicit approval
- Accurate company information (address, registration, VAT)
- GDPR-compliant privacy policy
- Clear terms of service
- Last updated date

**Pricing Page:**

- Current pricing (€89/Standort/Monat standard)
- Feature comparison table
- Add-on pricing (if applicable)
- Free trial CTA
- No hidden fees messaging

**Customers Page:**

- Customer logos (with permission)
- Testimonials or case studies
- Industry diversity showcase
- Social proof (number of customers, ratings)

**About Page:**

- Company story and mission
- Team information (optional)
- Company values
- Contact information

**Partner Page:**

- Partner logos and descriptions
- Integration information
- Benefits of partnerships

### Required Schema

- **AboutPage:** for About page
- **ContactPage:** for Contact/Imprint
- **WebPage + BreadcrumbList** for all

### Validation Checklist

- [ ] Legal pages accurate and compliant (if touched)
- [ ] Pricing current and correct
- [ ] Customer logos have permission
- [ ] Contact information accurate
- [ ] Schema validates (appropriate for page type)
- [ ] Meta tags complete
- [ ] Copy is du tone (where appropriate)

---

## Homepage

**Files:** `v2/pages/landingpage*.php`, `v2/pages/start*.php`  
**Rule:** `.cursor/rules/homepage.mdc`

### Purpose

Primary entry point with hero messaging, value propositions, social proof, and multiple CTAs optimized for conversion and performance.

### Key Elements

- Hero section with headline, subheadline, primary CTA, hero image/video
- Value propositions (3-5 key benefits)
- Social proof (customer logos, testimonials, ratings, statistics)
- Feature highlights (with icons/images)
- Use cases or industry showcase
- Pricing teaser or CTA
- FAQ section (optional)
- Multiple CTAs throughout

### Required Schema

- **WebSite:** name ("Ordio"), url, potentialAction (SearchAction)
- **Organization:** name ("Ordio GmbH"), url, logo, description, contactPoint, sameAs (social media), address, foundingDate
- **WebPage + BreadcrumbList**

### Hero Best Practices

- Clear, benefit-driven headline (what Ordio does, who it's for)
- Subheadline with key differentiator
- Primary CTA above fold ("Kostenlos testen", "Jetzt starten")
- Hero image/video showing product in action
- Social proof (ratings, customer count) near CTA

### Performance Targets

- **LCP:** < 2.5s
- **FID:** < 100ms
- **CLS:** < 0.1
- **PageSpeed score:** > 90

### Performance Optimization

- Preload hero image with `fetchpriority="high"`
- Inline critical CSS
- Defer non-critical CSS and JavaScript
- Optimize images (WebP, srcset, dimensions)
- Lazy-load below-fold images

### Validation Checklist

- [ ] Hero headline clear and benefit-driven
- [ ] Primary CTA prominent above fold
- [ ] Value props outcome-focused, du tone
- [ ] Social proof authentic and visible
- [ ] Performance optimized (LCP, CLS, PageSpeed)
- [ ] Schema validates (WebSite, Organization, WebPage)
- [ ] Meta tags complete and SEO-optimized
- [ ] All CTAs functional and correctly linked

---

## General Guidelines (All Page Types)

### Du Tone

- Use informal "du" pronouns (not formal "Sie")
- Conversational and friendly language
- Active voice, present tense

### Ordio Mentions

- Mention Ordio naturally once per major section
- Integrate into context (not forced "Mit Ordio kannst du..." every paragraph)
- Implicit in CTAs (no need to say "Ordio" in button text)

### Competitor Language

- Never praise competitors
- Position Ordio as smarter choice
- Neutral or factual competitor descriptions

### Performance

- Preload hero images with `fetchpriority="high"`
- All images have explicit `width` and `height`
- Use WebP format with `srcset`
- Lazy-load below-fold images
- Defer non-critical scripts

### Accessibility

- All images have descriptive `alt` attributes
- Headings follow hierarchy (H1 → H2 → H3)
- Color contrast meets WCAG AA (4.5:1)
- Focus states visible on all interactive elements
- Keyboard navigation works
- Touch targets minimum 44x44px

### SEO

- Title < 60 characters, includes year, keyword, "Ordio"
- Description 155-160 characters, du tone, benefit-driven
- Canonical URL absolute and correct
- Open Graph + Twitter Card tags complete
- Schema markup valid and complete

---

## Cross-Page-Type Relationships

Understanding how different page types relate to each other is crucial for effective internal linking and content strategy.

### Product Pages Relationships

**Should Link To:**

- **Blog Content** (3-5 links): Educational articles addressing user questions
- **Tools** (2-3 links): Relevant calculators and utilities
- **Templates** (1-2 links): Downloadable resources
- **Comparisons** (1-2 links): Competitive positioning pages
- **Industries** (1-2 links): Relevant industry pages

**Should Receive Links From:**

- Industry pages (2-3 links per industry page)
- Tools pages (1-2 links per tool page)
- Comparison pages (2-3 links per comparison page)
- Pillar pages (2-3 links per pillar page)
- Blog posts (contextual links)

### Industry Pages Relationships

**Should Link To:**

- **Products** (2-3 links): Relevant product pages
- **Blog Content** (3-5 links): Industry-specific articles
- **Tools** (1-2 links): Industry-relevant calculators

**Should Receive Links From:**

- Product pages (1-2 links per product page)
- Pillar pages (2-3 links per pillar page)
- Blog posts (industry-specific content)

### Tools Pages Relationships

**Should Link To:**

- **Products** (1-2 links): Relevant product pages
- **Pillar Pages** (1 link): Comprehensive guides
- **Blog Content** (1-2 links): Related articles

**Should Receive Links From:**

- Product pages (2-3 links per product page)
- Pillar pages (3-5 links per pillar page)
- Blog posts (contextual links)

### Templates Pages Relationships

**Should Link To:**

- **Products** (1-2 links): Relevant product pages
- **Pillar Pages** (1 link): Comprehensive guides
- **Blog Content** (1-2 links): Related articles

**Should Receive Links From:**

- Product pages (1-2 links per product page)
- Pillar pages (1-2 links per pillar page)
- Blog posts (contextual links)

### Comparison Pages Relationships

**Should Link To:**

- **Products** (2-3 links): Relevant product pages
- **Blog Content** (1-2 links): Educational articles

**Should Receive Links From:**

- Product pages (1-2 links per product page)
- Blog posts (contextual links)

### Pillar Pages Relationships

**Should Link To:**

- **Products** (2-3 links): Relevant product pages
- **Tools** (3-5 links): Related calculators
- **Templates** (1-2 links): Downloadable resources
- **Blog Content** (10-15 links): Cluster content
- **Industries** (2-3 links): Relevant industry pages
- **Comparisons** (1-2 links): Competitive positioning

**Should Receive Links From:**

- All cluster blog posts (1-2 links per post)
- Tools pages (1 link per tool page)
- Templates pages (1 link per template page)

### Download Pages Relationships

**Should Link To:**

- **Blog Content** (1-2 links): Related articles

**Should Receive Links From:**

- Blog posts (contextual links)
- Pillar pages (1-2 links per pillar page)

### Webinar Pages Relationships

**Should Link To:**

- **Blog Content** (1-2 links): Related articles

**Should Receive Links From:**

- Blog posts (contextual links)
- Pillar pages (1-2 links per pillar page)

### Best Practices

1. **Contextual Linking:** Place links naturally within content, not forced
2. **Descriptive Anchor Text:** Use keyword-rich, descriptive anchor text
3. **Conversion Focus:** Link from educational content to conversion pages
4. **User Journey:** Support user journey from discovery to conversion
5. **Link Density:** Balance link density (not too many, not too few)

For detailed relationship analysis, see `docs/full-site/PAGE_TYPE_RELATIONSHIPS.md`.  
For linking strategy, see `docs/full-site/FULL_SITE_LINKING_STRATEGY.md`.

---

## Quick Reference Table

| Page Type | Primary Schema        | Key Focus                   | Common Pitfall                       |
| --------- | --------------------- | --------------------------- | ------------------------------------ |
| Product   | SoftwareApplication   | Benefit-driven copy         | Feature lists without benefits       |
| Industry  | Industry, Service     | Vertical-specific messaging | Generic copy, wrong terminology      |
| Tools     | HowTo                 | Calculator logic + export   | Missing validation, broken export    |
| Templates | DigitalDocument       | Customizer + export         | Excel branding violations            |
| Downloads | DigitalDocument       | Gated content + forms       | Missing GDPR consent                 |
| Webinars  | Event                 | Registration + calendar     | Wrong timezone in dates              |
| Pillars   | Article, FAQPage      | SEO content + links         | Thin content, broken links           |
| Static    | Varies                | Legal/pricing accuracy      | Changing legal text without approval |
| Homepage  | WebSite, Organization | Conversion + performance    | Slow LCP, vague headline             |

---

For detailed workflows and prompt patterns, see `docs/ai/cursor-playbook.md`.  
For validation workflows, see `docs/ai/validation-workflows.md`.  
For comparison pages specifically, see `guides/comparison-pages/COMPARISON_PAGES_GUIDE.md`.  
For full site analysis and architecture, see `docs/full-site/` directory.

## Product Updates Pages

**Files:** `v2/pages/produkt_updates*.php`, `v2/pages/post.php`, `v2/api/produkt-updates-upload.php`  
**Rule:** `.cursor/rules/product-updates.mdc`  
**Admin:** `v2/pages/produkt_updates_admin.php`

### Purpose

Announce new features, improvements, and bug fixes to customers. Maintain a public changelog demonstrating product velocity.

### Key Pages

- Main: `/produkt-updates` - Current month's updates
- Month: `/produkt-updates/[month-slug]` - Monthly archive
- Post: `/produkt-updates/[post-slug]` - Individual feature/improvement

### Admin Panel

- Access: `/produkt-updates-admin`
- Features: CRUD operations, image upload, bulk actions, search/filter, Quill.js editor
- Security: Session-based auth, input sanitization, file upload validation

### Data Structure

- JSON file (SSOT): `v2/data/produkt-updates/produkt_updates.json` (override: env `ORDIO_PRODUKT_UPDATES_ROOT`)
- Images: `v2/data/produkt-updates/images/` (public URL `/produkt-updates/bilder/`)
- Sample JSON in repo: `v2/data/samples/produkt_updates.sample.json` (not SSOT; SSOT is `v2/data/produkt-updates/produkt_updates.json`)
- Backups: `v2/data/backups/`

### Required Schema

- Main: CollectionPage, ItemList
- Month: CollectionPage (month-specific)
- Post: Article, WebPage, BreadcrumbList

### Documentation

- User Guide: `v2/admin/produkt-updates/USER_GUIDE.md`
- Code Documentation: `v2/admin/produkt-updates/CODE_DOCUMENTATION.md`
- Testing Summary: `docs/PRODUCT_UPDATES_TESTING_SUMMARY.md`
- Cursor Rules: `.cursor/rules/product-updates.mdc`

### Support

Contact: hady@ordio.com