Platform Engineering · Multi-Site Architecture

Platform Architecture & Multi-Site Deployment: Building the JustineLonglaT-Lane Engineering Ecosystem

What started as a single personal website grew into a resilient, observable, multi-site platform: marketing, docs, blogs, projects, and the Nouvo Ayiti 2075 foundation — all operating on clean DNS, disciplined CI/CD, and a unified content engine.

Stable DNS & SSLMulti-environment CI/CDResend Email Infrastructure

Sites

Marketing, Docs, Blogs, Projects, Foundation

Environments

Preview · Development · Production

Infra

Vercel · GitHub Actions · Azure Blob · Resend

Domains

jutellane.com · *.jutellane.com · nouvoayiti2075.com

Context: From Personal Site to Platform

The JustineLonglaT-Lane Ecosystem didn't start as a platform initiative. It started as a simple personal presence — a single site. Over time, real engineering needs emerged:

Marketing site for consulting and services.
Documentation hub for tools and reference material.
Blog site for deep-dive technical content.
Project case studies for concrete engineering stories.
Nouvo Ayiti 2075 foundation site for mission-driven work.
A multi-language content engine serving global audiences.

This case study captures the platform-level engineering that stitched all of this together: DNS, environments, deployments, storage, email, and content governance.

DNS & Domain Architecture

Resolved conflicts between root domain and multiple subdomains.
Separated Vercel-managed and GitHub Pages–managed DNS cleanly.
Fixed A vs CNAME record mistakes and redirect loops.
Verified SPF, DKIM, MX, and Return-Path for Resend email delivery.

Multi-Environment CI/CD Workflow

Preview, development, and production environments wired to branches.
GitHub Actions enforcing linting, type checks, and formatting gates.
Release tags mapped to stable production deployments.
PR builds validating changes end-to-end before merging.

Vercel Runtime & Routing Architecture

Eliminated ENOTFOUND and module resolution errors.
Fixed duplicate and catch-all routes across nested segments.
Resolved H-runtime blocking static exports where static was required.
Standardized /public asset paths and image usage across sites.

Storage & Email Infrastructure

Azure Blob Storage configured for shared assets and documents.
Resend wired to the /join endpoint for transactional email.
Admin notifications and user confirmations implemented.
Rate limiting and throttling added to protect endpoints.

High-Level Architecture Flow

At a glance, the platform can be visualized as a set of flows from DNS to content and infrastructure:

              +---------------------------+
              |         Users            |
              +-------------+------------+
                            |
                            v
                +-----------+-----------+
                |       IONOS DNS      |
                +-----------+-----------+
                            |
     +----------------------+----------------------------+
     |                      |                            |
     v                      v                            v
+----+------+       +-------+--------+           +------+--------+
| jutellane |       | docs.jutellane |           | blogs.jutellane |
|   .com    |       |      .com      |           |       .com      |
+----+------+       +-------+--------+           +------+--------+
     |                      |                            |
     v                      v                            v
+----+----------------------+----------------------------+--------+
|                    Vercel / Static Hosting                     |
+----+----------------------+----------------------------+--------+
     |                      |                            |
     v                      v                            v
  Marketing           Documentation                 Blog & Projects
  (Next.js)             (Static / HTML)               (Static / HTML)

     +-----------------------------------------------------------+
     |             Shared Services & Integrations                |
     | - Azure Blob Storage (assets, docs)                       |
     | - Resend (/join endpoint, notifications, confirmations)   |
     | - GitHub Actions (CI/CD, tags, PR builds)                 |
     +-----------------------------------------------------------+

Delivery Timeline

Early 2025

Phase 1 — From Single Site to Ecosystem

Started from a single personal site and grew into a multi-site ecosystem: marketing, docs, blogs, projects, and Nouvo Ayiti 2075 foundation.

Spring 2025

Phase 2 — DNS, Environments & CI/CD

Stabilized DNS, defined subdomain responsibilities, and introduced preview/dev/prod environments backed by GitHub Actions.

Summer 2025

Phase 3 — Storage, Email & Content Governance

Brought Azure Blob Storage and Resend together with strict content metadata conventions and posting formats across all sites.

Ongoing

Phase 4 — Platform Reliability & Observability

Continuous refinement of logging, rate limiting, and rollout patterns to support future subdomains and services safely.

Outcomes

The result is more than a collection of websites — it's a cohesive engineering platform.

A unified engineering ecosystem spanning marketing, docs, blogs, projects, and foundation sites.
Predictable, branch-based deployment flows through GitHub Actions and Vercel.
Stable DNS and SSL coverage across all domains and subdomains.
A consistent content and metadata model for projects and long-form posts.
A scalable foundation ready for new services, subdomains, and automations.

Explore the Ecosystem

This architecture powers multiple independent yet connected sites:

Jutellane Marketing Site Documentation Hub Blog & Project Case Studies Nouvo Ayiti 2075 Foundation