Andile approved the Astro + AWS rebuild: a static site served from S3 + CloudFront, edited by Claude over MCP, and discoverable by AI agents. The front end is built and live on a preview host right now — the plan below turns that preview into production.
Why this preview is faithful to AWS. Astro emits one host-agnostic dist/. Cloudflare Pages serves that exact artifact today; AWS S3 + CloudFront will serve the identical bytes in production. What you click below is what the AWS site will look and behave like — same HTML, same CSS, same content feed.
The live simulator
Every page below is the real, deployed build. Open any of them — this is the experience AWS will host.
Tactical look & feel
Editorial, not corporate-generic. A near-black forest ground, a paper reading surface, and a single electric-lime accent used once per view — for the one thing you should click. Reproduced here from the site's own v4 tokens.
Palette
Typography
Components, live from tokens
From the ReBrand Summary
Three content moves, decided this week. Each is content-as-code — a typed field or file — so it ships without touching components, and feeds straight to the agent discovery surface.
Keep the descriptor; add "Independent Capital Markets Infrastructure Orchestrator" as a supporting statement — surfaced on the hero and fed to agents.
Trusted Partnerships · Capital Markets Authority · Operational Resilience · People & Growth — added as a messaging section on Our Story. The three nav pillars still drive the IA.
The most defensible number in the deck, currently unused. Recommended into the proof bar (swapping "5 locations", which already lives on Our Story).
Held steady by decision: three service lines (not four — FinMio stays a product, AI advisory a capability), and the tagline stays a single swappable field pending ExCo.
The AWS build
The same dist/ becomes the production site; the dynamic edges — forms, consent, and MCP — run as Lambda behind API Gateway, all inside the Andile AWS account. Humans edit by talking to Claude; agents read a public discovery surface.
Delivery
The content and code can be finished now; only provisioning waits on the Andile AWS team. Nothing here deploys to Cloudflare production — Pages stays the preview host until AWS reaches parity, then we cut over.
Secondary positioning line, four brand pillars as "Why Andile", the retention stat — all host-agnostic and fed to the agent surface.
S3 (private) + CloudFront (OAC), ACM cert, DNS. CI is already written; it needs the deploy role, bucket and distribution IDs.
API Gateway + Lambda running the same portable core as dev; POPIA consent written to DynamoDB.
Public discovery (read + search) and OAuth editing (edit → PR → publish), served at mcp.andile.net. The editing side is the long pole — see below.
Generate 301s from the live WP URLs, swap placeholder copy for approved content, then flip DNS to CloudFront.
Retire the interim Cloudflare MCP connector and the superseded legacy MCP path once AWS is proven in production.
Claude's MCP connector expects dynamic client registration + PKCE. On Cloudflare that's a library we get for free; AWS has no drop-in equivalent, so this is the one genuine engineering fork.
A small Lambda + three DynamoDB tables mirror the Cloudflare provider — full dynamic-registration + PKCE control, MCP-idiomatic. Layer Google-Workspace/Cognito SSO as the editor login behind the consent screen.
Native SSO and MFA, less code — but no dynamic client registration, so the Claude client must be statically pre-registered. Simpler infra, less standard for MCP clients.
Locked this week
Keep the descriptor; add the Orchestrator line as support — not a re-lead.
FinMio stays a product, AI advisory a capability. No fourth service.
Nav-verb pillars drive IA; the four brand pillars are a messaging layer.
Discovery + OAuth editing move into the Andile AWS account. CF is interim.