Docs README
Welcome to JustineLonglaT-Lane Docs — the source of truth for how this ecosystem runs in real life: from local dev and Git hygiene to CI/CD, Vercel deploys, GitHub Pages, and the automation guardrails that keep all four sites healthy.
Why these docs exist
This documentation exists to make the platform predictable, repeatable, and teachable. Instead of carrying everything in my head, this site captures the decisions, patterns, and workflows that keep:
- the consulting site running smoothly,
- the docs site deployable and maintainable,
- the blog + content pipelines shippable, and
- the Nouvo Ayiti 2075 ecosystem aligned with the rest.
When something breaks, changes, or needs to scale, this is the first place I come back to.
What you’ll find here
The docs are intentionally concise and grouped by how you actually work on the platform:
- Getting Started – cloning the repos, basic tooling, and how to run things locally.
- Tooling Setup – editor settings, formatting rules, and guardrails so every repo behaves the same.
- CI/CD Pipelines – how code gets from branch to production, including GitHub Actions and Vercel hooks.
- Architecture – high-level diagrams that show how the services, deployments, and observability fit together.
- System Design – Part D – the “platform ecosystem” view, with deep dives into automation toolkit, operations, multi-site coordination, and reliability guardrails.
For a simple list of every page, use the Docs index.
How to use these docs
Treat this site like a runbook plus design record:
- New work: Start with Getting Started and the architecture diagrams, then follow the CI/CD guidance before creating new flows.
- Troubleshooting: Check CI/CD and operations sections first to confirm the current expected workflow.
- Explaining the platform: Use the Architecture and Part D pages when speaking with clients, collaborators, or recruiters.
Related sites
The docs live alongside the other pillars of the ecosystem:
- Consulting site – services, portfolio, and case studies.
- Booking / Intro call – schedule conversations directly.
- Engineering Mesh Hub – experiments, playgrounds, and deeper technical dives.
Keeping things fresh
This site is version-controlled alongside the rest of the platform. When a workflow, script, or architecture decision changes, the goal is simple: update the docs as part of the same change.
If a page feels out of date, I capture the gap, open a task or PR, and treat the docs update as a first-class deliverable — not an afterthought.