D8. Wireframe Structure

0. Document control

Client: EVOCEAN GmbH · Domain: https://www.evocean.com · Production date: 02.Nov.2026 · Version: 1.0.

Basis: frozen Phase 3 v1.0 from D5 v1.6, D1/D2 source observations, supplied brand guidelines and confirmed client decisions. Phase 4 authorised on 1 November 2026. These are assessment UX recommendations [+], not final marketing copy, visual design, publication approval or working forms. The uploaded files_5.zip matches all five canonical Phase 3 files byte-for-byte; the strategy-1.0 upload is an unfilled format template, not a competing architecture. No format migration is assumed.

No live changes, redirects, deletions, topic-site changes, booking activation, internal administration or production sitemap are made. Dates/prices, proof, legal text and unresolved service details stay pending. No new crawl or claim of conversion uplift.

1. Shared UX rules

Text wireframes specify section order, content blocks, CTA placement and trust positions; they are not Phase 7 visual designs or a Phase 10 prototype. Each ordered block reads top-to-bottom. On small screens keep the same content hierarchy, collapse menus with accessible disclosures, stack repeated offer items and preserve a visible next step without obscuring content. Do not use a carousel to rank or hide the six equal-priority home offers.

Use the supplied flat lockup (full version on light surfaces at the supplied minimum size; compact wordmark only where necessary), existing semantic tokens and self-hosted fonts. Gold belongs to one primary action per view, never decorative. Header/closing repeats must use neutral treatment whenever both are visible. Final layout dimensions, imagery and detailed styling belong to the later visual phase; any future media must use D2 provenance and rights validation, not invented customers.

Navigation follows D7: Services · Tools and licences · Training · Insights · About; utility Support/Contact. Empty evidence, hiring and newsletter reservations stay out of public navigation. German launches after final English and review; retained French remains discoverable as existing content, not newly translated coverage. Internal administration is never a public menu or sitemap entry.

2. Main page-type wireframes

2.1. Homepage

1. Header
   ↓
2. Customer entry
   ↓
3. Equal-priority offer paths
   ↓
4. Contextual audience paths
   ↓
5. How collaboration begins
   ↓
6. Trust position
   ↓
7. Closing and footer

2.2. About

1. Header and orientation
   ↓
2. Purpose and approach
   ↓
3. Capabilities and engagement
   ↓
4. Trust position
   ↓
5. Contact and footer

2.3. Services / service detail

1. Header and context
   ↓
2. Need and scope
   ↓
3. Delivery sequence
   ↓
4. Trust position
   ↓
5. Related offers and questions
   ↓
6. Next step and footer

2.4. Product / category and catalogue

1. Header and orientation
   ↓
2. Needs and selection
   ↓
3. Offer list
   ↓
4. Trust position
   ↓
5. Selection support and footer

2.5. Product detail

1. Header and identification
   ↓
2. Use and specification
   ↓
3. Licence and renewal path
   ↓
4. Trust position
   ↓
5. Related expertise and footer

2.6. Project / reference

1. Publication gate
   ↓
2. Approved identity and context
   ↓
3. Approach and result
   ↓
4. Trust position
   ↓
5. Next step

2.7. Contact / consultation

1. Header and purpose
   ↓
2. Contact choice
   ↓
3. Availability
   ↓
4. Details and privacy
   ↓
5. Trust position
   ↓
6. Outcome states and footer

2.8. Training / course agenda

1. Header and audience
   ↓
2. Learning scope
   ↓
3. Delivery and preparation
   ↓
4. Trust position
   ↓
5. Follow-on and enquiry

2.9. Audience / independent topic entry

1. Header and audience
   ↓
2. Need and scope
   ↓
3. Trust position
   ↓
4. Independent destination
   ↓
5. Contact and footer

2.10. Insights / resource / historical event

1. Orientation
   ↓
2. Body and source context
   ↓
3. Trust position
   ↓
4. Related current context

2.11. Retained French / public archive

1. Orientation
   ↓
2. Content and status
   ↓
3. Trust position
   ↓
4. Navigation and footer

2.12. Support / legal / conditional utility

1. Orientation
   ↓
2. Substantive content
   ↓
3. Trust position
   ↓
4. Next step and footer

3. Priority offer adaptations

4. Audience journeys and access

B2B R&D/IT: direct entry or Home → relevant service/tool/training → scope and delivery → context-led enquiry or consultation. Rational value means explain the process and fit, not fabricate ROI. Quality Leaders and HR/work get their distinct contextual topic paths; EVOLVIA remains beside engineering.

B2G visitors use the same relevant service paths with precise scope, traceability/process information and approved references if later supplied. The dedicated public-sector gap remains deferred: no new page, procurement workflow, certification claim or public-client proof. This preserves B2G access without reopening the client's deferral.

Keyboard focus, meaningful labels, accessible menu disclosure, reading order, adequate contrast and non-colour status cues apply throughout. Validate later on desktop/small screens; no functioning corporate interface is asserted in this assessment.

5. Full page-to-wireframe coverage

All 229 Phase 3 planning nodes are assigned below, including German reservations, existing French references, conditional utilities and evidence slots. These are not 229 launch-ready pages. The 242 source dispositions remain unchanged in Phase 3; documents, redirects and broken sources are not new UX pages.

6. Architecture update check

No structural changes are needed: UX refinements fit the D6 nodes and D7 navigation. D6/D7 remain unchanged; no [UPDATED] version is emitted. Deferred content, proof and translation slots remain reservations, not new public routes.

Phase 4 complete — confirm to continue.