Rebuild the site to the Claude Design drafts

Carries the 11 page drafts plus the shared SiteNav and SiteFooter onto the
project's own design system: tier-2 tokens, the published type roles, logical
properties throughout, and both locales.

Surfaces
- The page stands on #0B0B0A with #1D1D1B bands lifted off it, as the drafts
  do; the body previously painted the band colour, so every band was a step
  too light.
- A card is drawn one step off whatever it stands on (#1D1D1B on the ground,
  #141413 inside a band). Components paint --surface-card and a band re-points
  it for its subtree, so a card can never come out the same colour as its band.

Shell
- Nav: translucent ground with a blur, chevrons on group triggers, an accent
  rule under the current section, the drafts' compact dropdown card, and an
  EN | AR toggle in place of the globe menu.
- Footer: the drafts' four-column grid, one-line brand text, Facebook as a
  bordered button, the EU lockup, the implemented-by row and the funding
  disclaimer.

Pages
- Home: hero with counting figures, launch band, three areas of change,
  newsroom, FAQ accordion and the consortium band.
- The nine interior pages rebuilt and then audited section by section against
  their drafts.
- Applications: the three-step application form now posts real submissions to
  the Strapi `application` type, validated server-side and working without
  JavaScript.

Motion
- Every animation in the drafts, as classes in _page-kit/motion.css: staggered
  entrances, scroll-driven reveals, the drifting washes (each page carries its
  own geometry), the sheen, the counting figures and the accordion. The
  drafts' coloured hover glow is deliberately not shipped.

CMS
- New `faq` collection type behind the home page's accordion.
- `role` added to the consortium member component so an editor can supply the
  chip and the deliverable separately.

Content
- No invented figure, date, name or commitment ships: the five-working-day
  reply, the placeholder email and Facebook handle, the sample news, events,
  publications and FAQs, the invented application rules and the TBD counters
  are all withheld pending real content. Figures that survived (3 consortium
  partners, 4 areas of work, 16 human security sub-projects, Dec 2025 - Dec
  2027) are verified against docs/ and the bundled draft copy.

Verified: pnpm typecheck (web + CMS) and pnpm --filter web build pass; all 20
page/locale URLs render 200 through the built SSR handler, including with the
CMS unreachable; no raw hex or physical-direction utility in components or
routes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

apps/web/app/routes/_events-opportunities/submissions.server.ts

@@ -49,7 +49,11 @@
    `findOne` are NOT, or anyone could read everyone else's contact details.
    ========================================================================= */
 
-import type { ApplicationValues, RegistrationValues } from "./forms";
+import type {
+  ApplicationValues,
+  PathwayApplicationValues,
+  RegistrationValues,
+} from "./forms";
 import { createStrapiEntry } from "./strapi-write.server";
 
 export const EVENT_REGISTRATIONS_RESOURCE = "event-registrations";
@@ -104,3 +108,73 @@ export async function submitApplication(
     answers: { [APPLICATION_MESSAGE_KEY]: input.values.message },
   });
 }
+
+/* ---------------------------------------------------------------------------
+   GET INVOLVED - the section page's own application
+   ------------------------------------------------------------------------ */
+
+/**
+ * The keys the Get Involved form files inside `answers` (json).
+ *
+ * They are named here rather than spelled at the call site because a reviewer
+ * reads them in the admin panel: renaming one silently orphans every answer
+ * already stored under the old key.
+ *
+ * `message` is deliberately the SAME key the per-call form writes
+ * (APPLICATION_MESSAGE_KEY above), so the free-text case for applying reads
+ * out of one place whichever form it arrived through.
+ */
+export const APPLICATION_ANSWER_KEYS = {
+  /** Which of the three pathways the applicant chose. */
+  route: "route",
+  region: "regionOfOperation",
+  yearsOperating: "yearsOperating",
+  summary: APPLICATION_MESSAGE_KEY,
+} as const;
+
+export interface PathwayApplicationSubmission {
+  readonly values: PathwayApplicationValues;
+  /**
+   * documentId of the opportunity this application belongs to, when one is
+   * known. The Get Involved form is NOT tied to a single call - it is the
+   * section's general way in - so it is usually absent, and `opportunity` is
+   * optional on the content type precisely for that case. It is never guessed
+   * from "the nearest open call": an application filed against a call the
+   * applicant never named is a fabricated relation.
+   */
+  readonly opportunityId?: string;
+}
+
+/**
+ * Write a Get Involved application. The payload is the CMS whitelist and
+ * nothing more (see the header): the two extra answers the draft asks for ride
+ * inside `answers`, which is on that whitelist, so they need no migration.
+ *
+ * `attachments` is NOT sent, and the form does not offer an upload. See the
+ * header of this file and the `sanitize-submission` middleware in the CMS for
+ * why a public caller cannot supply one.
+ */
+export async function submitPathwayApplication(
+  input: PathwayApplicationSubmission,
+): Promise<void> {
+  const { values } = input;
+
+  await createStrapiEntry(APPLICATIONS_RESOURCE, {
+    ...(input.opportunityId ? { opportunity: input.opportunityId } : {}),
+    applicantName: values.fullName,
+    email: values.email,
+    organisation: optional(values.organisation),
+    answers: {
+      [APPLICATION_ANSWER_KEYS.route]: values.route,
+      // Only the answers actually given: an empty string in the admin panel
+      // reads as "answered, with nothing", which is not what happened.
+      ...(values.region
+        ? { [APPLICATION_ANSWER_KEYS.region]: values.region }
+        : {}),
+      ...(values.yearsOperating
+        ? { [APPLICATION_ANSWER_KEYS.yearsOperating]: values.yearsOperating }
+        : {}),
+      [APPLICATION_ANSWER_KEYS.summary]: values.summary,
+    },
+  });
+}