Andrea redesign 1: Step 3 handoff

Historical Step 3 record. The deployment happened later; see the redesign story and verified cutover. Intermediate verification and remaining work below refer to this stage.

Date: 2026-09-24 (America/Bogota). Branch: jm/andrea-redesign-1.

This handoff records the implemented local contract for the portfolio landing and architecture experience. Read the redesign plan and shared foundation for the full product, routing, and visual context. This is a local implementation handoff. It does not authorize production deployment or production data changes.

Route and content contract

Route	Language	Required content
/	Spanish	Andrea's supplied draft introduction and two linked destination tiles: Arquitectura and Guanza
/en	English	Equivalent introduction and the same destinations localized to Architecture and Guanza
/arquitectura	Spanish	Biography, studies and services/methodology draft; email and LinkedIn; project demonstrations with labeled galleries
/en/arquitectura	English	Equivalent architecture content and controls in English

The shared frame's AZ. link returns to the localized home. Architecture and Guanza links use the localized routes. Links crossing to the independently deployed storefront remain ordinary anchors. Spanish is the unprefixed default; English uses /en first. These portfolio routes do not select or change the commerce market.

Andrea's supplied landing copy is draft review text, not approved final biography: “Bienvenidos a mi mundo. Soy arquitecta con maestría en diseño de espacios y experiencias culturales. Me enfoco en el diseño conceptual y en la psicología de los espacios. Aquí encontrarás piezas ideales para tu espacio o puedes contratar directamente mis servicios y tener el hogar de tus sueños.” Keep the matching English copy easy to revise and do not add credentials, roles, awards, clients, or project claims without Andrea's approval.

Demonstration imagery and provenance

Architecture demonstration projects and their gallery boards are illustrative placeholders, not a portfolio of Andrea's completed work. The four SVG boards under apps/portfolio/public/architecture-demo/ are in-repository conceptual graphics, not photographs or representations of built work. Label them clearly in both languages, including in accessible text where the project context could otherwise be mistaken for real work. General architecture imagery already in the portfolio has used Unsplash-hosted stock photographs; these are not Andrea's project images. Confirm the exact image sources, license terms, and attribution requirements before any production publication, and prefer Andrea-approved originals for the final portfolio.

The repository also contains existing portrait and Guanza/catalog image files under apps/portfolio/public/. Their filenames or presence do not establish photographer, creator, model, usage, or publication rights. Preserve a source, permission, and attribution record for each approved production asset. The redesign screenshots listed in the main plan are visual references, not production artwork. Do not extract or present screenshot imagery as final high-resolution project work.

Content needed from Andrea

• Approval or revision of the introduction in Spanish and English.
• Final biography, exact degree wording, study dates if desired, and preferred description of methodology and services.
• Approved portrait and collage assets, their sources/rights, credits, and preferred alternative text.
• For each real project: title, location, year, type, Andrea's role, summary, ordered original boards, image dimensions, captions, alt text, and credits.
• Which projects may be published and any client, privacy, or image-use limits.
• Confirmation of the public email and LinkedIn destinations in the foundation contact contract.

Until those materials are supplied, keep projects explicitly marked as demonstrations and avoid presenting sample dates, locations, typologies, or roles as Andrea's history. Do not infer missing facts from reference websites.

Contact handoff and release state

The public architecture email and LinkedIn URL are documented in the shared foundation. The architecture WhatsApp contact handoff remains pending the lead's integration decision and a server-side, origin-validated destination. Do not put a WhatsApp phone number or direct number-bearing link in rendered HTML or client code. No real contact messages should be sent during local verification.

No production deployment, VPS change, DNS/proxy change, or catalog mutation is part of this Step 3 handoff. Preview indexing restrictions remain in force. The legacy /portfolio pages still render their old content during the transition; redirect cleanup belongs to the later integration gate.

Local verification

The portfolio production build and 12 rendered-route tests passed locally. ESLint passed with image-optimization warnings, including existing image tags; these are not blocking errors. At 1440 × 900, the architecture contact links fit in the opening desktop section. At 375 × 850, the landing and architecture routes have no horizontal overflow. The gallery was exercised in a browser: inline controls change only the current board; the modal opens over an inert background, advances boards, closes with Escape, and restores the triggering button and exact prior scroll position. The mobile modal fits its viewport. This is a focused visual and interaction check, not a full accessibility audit. An additional direct tsc --noEmit check remains blocked by missing ambient Cloudflare worker types in the unchanged db/index.ts and worker/index.ts; the project build and route tests are the current passing quality gates.