Match the home page to Figma frame 253:4799

The page resembled the design but had drifted in every band. Ported it
section by section against the measured frame.

Hero (253:4800)
- Add the SHARP wordmark above the headline. The frame paints "SHARP"
  only, not the full SHARP-ER lockup the navigation carries, so this is
  the SHARP mark on its own, as vector (extracted from the brand
  guideline artwork) at its true 273px rather than an upscaled PNG.
- Drop the leading project name from the headline in both locales: the
  wordmark above now carries it, as the frame composes it.
- Stop the lead paragraph rendering by default. The frame's subheading
  node is hidden, but the code fell back to the site description, so a
  paragraph always appeared.
- Fallback CTAs become "Discover SHARP-ER" / "Explore Our Work", 24px
  apart. Both the CMS and fallback paths now render through one HeroCta,
  so an editor-authored secondary CTA gets the designed white treatment
  instead of the dark-surface outline.
- The picture loses its radius and gains the frame's two flat washes and
  wide band.

Figures band
- 253:4835 is hidden="true" in the frame, so the band and its "figures
  still being confirmed" placeholder no longer render. It appears only
  once the CMS supplies real numbers.

Launch (361:10853)
- Heading renders at Display/Small instead of Heading/H2. SectionHeader
  gains `size` since display-sm was reachable only via titleAs="h1".
- The three-paragraph story becomes the frame's single centred lead with
  its four bold runs, which needed a ProseRun copy shape - a flat string
  cannot carry emphasis.
- The captions were Card.Content links with images and action labels;
  the frame draws plain centred Heading/H2 text.
- Add the three-up photo strip that bleeds past the page and clips.
- Remove the funding line, which the frame does not draw in this band.
  EU visibility still stands via the nav badge and footer statement.

Partners (393:14754)
- Heading moves from centred to start-aligned, up to Display/Small.
- Tiles move to the sunken surface (they were lighter than the page; the
  design has them darker), lose their border, 8px -> 4px radius, padding
  on the inline start only, logo 48 -> 70px, name to Body/Large Bold.

Footer
- Black ground via a new --surface-footer token, a top rule, links up to
  Body/Large Bold 18/28 at 24px spacing, and column headings to
  Body/Small Bold on --text-tertiary.
- Keeps the real IA from ROUTE_SLUGS rather than frame 140:7814's
  labels, which name six pages that do not exist.

Tokens
- New tier-1 steps for values the design uses and the ramps lacked
  (--color-black-a20, --color-green-200-a12, --opacity-50) and tier-2
  --overlay-picture-shade / --overlay-picture-tint for the hero wash.

copy.ts now names the Figma frame as the source for the home strings.
The Arabic launch lead is rebuilt from the approved Arabic column to
carry the English frame's meaning and is marked (ar-draft) pending
client sign-off - the file has no Arabic home frame to work from.

Verified: typecheck and build green, no raw hex or tier-1 token in
components/routes, no physical-direction utility, 141 i18n keys at
parity, both locales rendered and checked for RTL mirroring.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-09-14 12:38:05 +02:00
co-authored by Claude Opus 5
parent 20b384039c
commit 8464c24fb1
9 changed files with 735 additions and 197 deletions
+60 -31
View File
@@ -1,24 +1,39 @@
/* ============================================================================
APPROVED DRAFT COPY - EN / AR
PAGE COPY - EN / AR
----------------------------------------------------------------------------
SOURCE
docs/SHARPER_Website_Draft_Section_EN_AR.docx (sections 1, 2 and 9)
docs/SHARPER Home Page .docx (the launch story)
Both documents carry the English AND the Arabic, so nothing below is a
machine translation of the other column except where a comment says so.
Home page Figma frame 253:4799 "Home-en" is the source of truth.
The headline (I253:4800;228:2609), the launch heading
(I361:10853;361:11147), the one-paragraph launch lead
with its four bold runs (I361:10853;349:8838) and the
three captions are transcribed from that frame, NOT
from docs/SHARPER Home Page .docx - the design condenses
the draft, and the draft itself is headed "Placeholder
text for design purposes - not final copy".
Everything else docs/SHARPER_Website_Draft_Section_EN_AR.docx
(sections 1, 2 and 9), which carries both columns, so
no string below is a machine translation of the other
except where a comment says so.
TRANSLATION STATUS
The Figma file has NO Arabic home frame - only the navigation and the
footer are drawn in Arabic - so the Arabic home strings marked (ar-draft)
are rebuilt from the approved Arabic column of the docx to carry the
English Figma meaning. They are NOT client-approved wording and should be
signed off before launch.
WHY IT LIVES IN THE CODE
This is page prose, not UI chrome, so it does not belong in the i18n
catalogue (which holds labels only). It is the FALLBACK: every field is
overridden by the matching Strapi field the moment an editor fills it in,
and the pages read `cms ?? draft`. Until then this is what renders, which
is exactly what the draft document is for.
and the pages read `cms ?? draft`.
WHAT IS DELIBERATELY ABSENT
Figures. The draft marks every number "TBD" and says they must not be
published until confirmed, so there is no statistic anywhere in this file;
the home page renders `statsPending` instead, and real figures arrive
through the CMS `stats` component.
published until confirmed, so there is no statistic anywhere in this file.
Figma hides the home page's figures band outright (frame 253:4835 is
hidden="true"), so the band renders only once the CMS `stats` component
supplies real numbers, and nothing stands in for it until then.
========================================================================= */
import type { Locale } from "~/i18n";
@@ -35,14 +50,19 @@ export interface ConsortiumCopy {
readonly role: string;
}
/**
* A run of prose that may carry emphasis. Figma sets four phrases of the launch
* lead in Bold on a lighter base run (349:8838), which a flat string cannot
* express - a plain string is the base weight, `{ em }` is the bold run.
*/
export type ProseRun = string | { readonly em: string };
export interface HomeCopy {
readonly heroHeadline: string;
readonly statsHeading: string;
/** Rendered in place of the figures while they are unconfirmed. */
readonly statsPending: string;
readonly launchHeading: string;
readonly launchParagraphs: readonly string[];
readonly fundingNote: string;
/** One paragraph, as the design draws it - not the full three-part story. */
readonly launchLead: readonly ProseRun[];
readonly mechanismsHeading: string;
readonly mechanisms: readonly string[];
readonly partnersHeading: string;
@@ -108,17 +128,22 @@ export interface PageCopy {
const EN: PageCopy = {
home: {
heroHeadline: "SHARP-ER Project Officially Launches in Libya",
/* The frame's wordmark above the headline carries the project name, so
the headline itself does not repeat it (figma I253:4800;228:2609). */
heroHeadline: "Project Officially Launches in Libya",
statsHeading: "SHARP-ER in numbers",
statsPending:
"The project’s figures are still being confirmed in the official fact sheet. They will be published here once verified.",
launchHeading: "The Journey of the SHARP-ER Launch",
launchParagraphs: [
"On Tuesday, June 30, the SHARP-ER project officially launched, bringing together representatives from the European Union Delegation, the Ministry of Youth, the Ministry of Local Governance, the Ministry of Women’s Affairs, civil society organizations, partners, and stakeholders from across Libya.",
"The event marked an important start for the project, including the launch of the SHARP-ER website and the opening of the Expression of Interest (EOI). Participants also learned more about the project’s objectives, upcoming opportunities, and activities focused on strengthening collaboration, partnerships, and local capacities.",
"Thank you to everyone who joined us and contributed to this milestone. We look forward to working together to support locally driven initiatives and create meaningful, lasting impact across Libya.",
launchHeading: "The Journey of SHARP-ER Launch",
launchLead: [
"The SHARP-ER project officially launched on ",
{ em: "Tuesday, June 30" },
", joining representatives from the ",
{ em: "European Union Delegation" },
", key ",
{ em: "Libyan Ministries" },
", and ",
{ em: "local civil society partners" },
". The event marked the launch of the project’s official website and the Call for Expression of Interest (EOI).",
],
fundingNote: "This project is funded by the European Union in Libya.",
mechanismsHeading: "What the launch set in motion",
mechanisms: [
"Building local capacity and skills",
@@ -249,17 +274,21 @@ const EN: PageCopy = {
const AR: PageCopy = {
home: {
heroHeadline: "انطلاق مشروع SHARP-ER رسميًا في ليبيا",
/* (ar-draft) matches the English frame: the wordmark names the project. */
heroHeadline: "انطلاق المشروع رسميًا في ليبيا",
statsHeading: "SHARP-ER بالأرقام",
statsPending:
"لا تزال أرقام المشروع قيد التأكيد في ورقة الحقائق الرسمية، وسيتم نشرها هنا فور اعتمادها.",
launchHeading: "مسيرة إطلاق مشروع SHARP-ER",
launchParagraphs: [
"انطلقت يوم الثلاثاء 30 يونيو رسميًا فعاليات مشروع SHARP-ER خلال حدث الإطلاق الذي جمع ممثلين عن بعثة الاتحاد الأوروبي، ووزارة الشباب، ووزارة الحكم المحلي، ووزارة شؤون المرأة، إلى جانب منظمات المجتمع المدني والشركاء والجهات الفاعلة من مختلف أنحاء ليبيا.",
"وشكّل الحدث بداية مهمة للمشروع، حيث تم إطلاق الموقع الإلكتروني الرسمي، والإعلان عن فتح باب التعبير عن الاهتمام (EOI)، إلى جانب استعراض أهداف المشروع والفرص والأنشطة القادمة. وتركّز هذه الأنشطة على تعزيز التعاون والشراكات وبناء القدرات على المستوى المحلي.",
"نتوجه بالشكر إلى جميع المشاركين على حضورهم ومساهماتهم القيّمة. ونتطلع إلى العمل معًا خلال المرحلة المقبلة لدعم المبادرات المحلية وتحقيق أثر مستدام في مختلف أنحاء ليبيا.",
launchLead: [
"انطلقت رسميًا فعاليات مشروع SHARP-ER يوم ",
{ em: "الثلاثاء 30 يونيو" },
"، بمشاركة ممثلين عن ",
{ em: "بعثة الاتحاد الأوروبي" },
"، وعدد من ",
{ em: "الوزارات الليبية" },
"، إلى جانب ",
{ em: "شركاء المجتمع المدني المحليين" },
". وشهد الحدث إطلاق الموقع الإلكتروني الرسمي للمشروع والدعوة للتعبير عن الاهتمام (EOI).",
],
fundingNote: "المشروع ممول من الاتحاد الأوروبي في ليبيا.",
mechanismsHeading: "ما الذي أطلقه هذا الحدث",
mechanisms: [
"بناء القدرات والمهارات المحلية",
+102 -12
View File
@@ -98,6 +98,13 @@ export interface SectionHeaderProps {
eyebrow?: string;
lead?: string;
titleAs?: "h1" | "h2" | "h3";
/**
* Type role of the title. "h2" is the Heading/H2 role every inner page uses;
* "display" is Display/Small - the home page draws its band headings at the
* same 44/52 as the hero (figma 361:11147, 393:14570) while keeping them
* <h2> in the outline, which `titleAs` alone cannot express.
*/
size?: "h2" | "display";
/** Figma centres the home page's section headers; inner pages read start. */
align?: "start" | "center";
className?: string;
@@ -109,11 +116,13 @@ export function SectionHeader({
eyebrow,
lead,
titleAs = "h2",
size = "h2",
align = "start",
className,
}: SectionHeaderProps) {
const Title = titleAs;
const centred = align === "center";
const display = size === "display" || titleAs === "h1";
return (
<header
@@ -131,7 +140,7 @@ export function SectionHeader({
id={id}
className={cx(
"text-[var(--text-primary)]",
titleAs === "h1" ? "heading-h1 md:display-sm" : "heading-h2",
display ? "heading-h1 md:display-sm" : "heading-h2",
)}
>
{title}
@@ -150,14 +159,50 @@ export function SectionHeader({
HERO
------------------------------------------------------------------------ */
export interface PageHeroWordmark {
src: string;
/**
* Empty when the headline already names the project - the lockup is then
* decorative and a screen reader would otherwise read the name twice.
*/
alt: string;
/** Intrinsic pixels of the asset, for the aspect ratio the browser reserves. */
width: number;
height: number;
/** Drawn width in CSS pixels. Figma 253:4800 draws the hero lockup at 419. */
drawnWidth: number;
}
export interface PageHeroMedia {
src: string;
alt: string;
width?: number;
height?: number;
}
/**
* How the picture is drawn.
* "rounded" - a 16:9 card with the surface radius. The default, and what the
* inner pages have always rendered.
* "banner" - the home treatment (figma 253:4800): square corners, a wide
* band, and the two flat washes the frame paints over the photo.
*/
export type PageHeroMediaTreatment = "rounded" | "banner";
export interface PageHeroProps {
title: string;
eyebrow?: string;
lead?: string;
/**
* Brand lockup drawn above the headline. Only the home hero carries one
* (figma 253:4800, a 419x58 wordmark 48px above the headline row).
*/
wordmark?: PageHeroWordmark;
/** Buttons, rendered inline-end of the headline on wide viewports. */
actions?: ReactNode;
/** Wide picture below the headline row, as in Figma 253:4800. */
media?: { src: string; alt: string; width?: number; height?: number };
media?: PageHeroMedia;
mediaTreatment?: PageHeroMediaTreatment;
className?: string;
}
@@ -171,13 +216,32 @@ export function PageHero({
title,
eyebrow,
lead,
wordmark,
actions,
media,
mediaTreatment = "rounded",
className,
}: PageHeroProps) {
return (
<section className={cx("pt-2xl pb-3xl md:pt-3xl md:pb-4xl", className)}>
<section className={cx("pt-2xl md:pt-3xl", className)}>
<Container className="flex flex-col gap-2xl">
{wordmark ? (
/* A graphic dimension, not a spacing value - sized the way Brand.tsx
and the footer size their lockups, with the intrinsic box on the
element so the browser reserves the right height. */
<img
src={wordmark.src}
alt={wordmark.alt}
width={wordmark.width}
height={wordmark.height}
loading="eager"
decoding="async"
draggable={false}
style={{ maxWidth: `${wordmark.drawnWidth}px` }}
className="block h-auto w-full"
/>
) : null}
<div className="flex flex-col gap-lg lg:flex-row lg:items-end lg:justify-between">
<div className="flex max-w-[46rem] flex-col gap-sm">
{eyebrow ? (
@@ -196,21 +260,47 @@ export function PageHero({
</div>
{actions ? (
<div className="flex flex-wrap items-center gap-md lg:justify-end">
<div className="flex flex-wrap items-center gap-lg lg:justify-end">
{actions}
</div>
) : null}
</div>
{media ? (
<img
src={media.src}
alt={media.alt}
{...(media.width ? { width: media.width } : {})}
{...(media.height ? { height: media.height } : {})}
fetchPriority="high"
className="aspect-[16/9] w-full max-w-full rounded-surface object-cover"
/>
mediaTreatment === "banner" ? (
/* Figma draws a 1244x700 picture inside an 800px frame that clips
it, so what the page actually shows is a wide band. The band is
kept at 16:9 on a phone, where a 2.9:1 strip would be a sliver.
The two washes are flat fills in the frame, not gradients: a
mint tint over a shade, both painted on the photograph. */
<div className="relative w-full overflow-hidden">
<img
src={media.src}
alt={media.alt}
{...(media.width ? { width: media.width } : {})}
{...(media.height ? { height: media.height } : {})}
fetchPriority="high"
className="aspect-[16/9] w-full object-cover md:aspect-[1244/425]"
/>
<span
aria-hidden="true"
className="pointer-events-none absolute inset-0 bg-[var(--overlay-picture-shade)]"
/>
<span
aria-hidden="true"
className="pointer-events-none absolute inset-0 bg-[var(--overlay-picture-tint)]"
/>
</div>
) : (
<img
src={media.src}
alt={media.alt}
{...(media.width ? { width: media.width } : {})}
{...(media.height ? { height: media.height } : {})}
fetchPriority="high"
className="aspect-[16/9] w-full max-w-full rounded-surface object-cover"
/>
)
) : null}
</Container>
</section>