connectrader documentation
The engineering behind the websites.
This library documents how we actually build, publish, optimize, stage, and hand off websites. The examples come from production patterns across our repositories, with client identities kept out of the technical discussion.
It exists for two reasons. It gives developers a durable standard to build against, and it gives buyers a way to inspect the thinking behind the work instead of taking a generic claim about custom development on faith.
Architecture & Engineering
How we structure Next.js sites, choose rendering boundaries, control dependencies, and keep business websites understandable as they grow.
Explore Architecture & EngineeringMDX & Content Systems
How we turn readable MDX files into indexed production pages with durable URLs, controlled metadata, image policy, validation, and internal linking.
Explore MDX & Content SystemsPerformance
The architectural and delivery decisions behind fast, stable pages, from server rendering and JavaScript budgets to images, fonts, third-party scripts, and mobile viewport behavior.
Explore PerformanceTechnical SEO
How we control crawlability, canonicals, structured data, sitemaps, modification dates, route families, internal links, and nonproduction indexing.
Explore Technical SEOConversion & Data
How forms, consent, provider handoffs, gated resources, error handling, and data minimization fit into a marketing website without creating unnecessary application infrastructure.
Explore Conversion & DataDelivery & Operations
How we stage, deploy, secure, validate, hand off, and maintain websites so production remains reproducible and clients retain real ownership.
Explore Delivery & OperationsStart here
The core technical arguments
These are the documents that best explain the difference between a site that merely renders and a site engineered for search, performance, ownership, and long-term maintenance.
How connectrader websites are structured
How we separate routes, reusable components, MDX content, metadata, and deployment concerns so a business website stays understandable as it grows.
Read the guideMDX & Content SystemsThe connectrader MDX content standard
How we structure long-form website content so writers can work in readable documents while the application still gets reliable metadata, routing, images, schema, and build-time validation.
Read the guidePerformanceWhy our sites are unusually fast
Why our sites tend to perform well: server-first rendering, narrow JavaScript boundaries, controlled media, restrained third parties, and less unnecessary runtime work.
Read the guideTechnical SEOOur technical SEO foundation
The technical SEO baseline we expect before content strategy can compete: crawlable HTML, stable URLs, canonicals, schema, sitemaps, and release checks.
Read the guideConversion & DataWhy consent should live next to the action
When a form needs consent, we put the decision in the actual submission flow so the record and the interface agree about what the visitor accepted.
Read the guideDelivery & OperationsOur deployment workflow
Why meaningful changes start on branches, become real preview deployments, pass production builds and audits, and only then reach the public site.
Read the guideThe documentation is part of the proof.
Portfolio work shows what shipped. These documents show why the implementation looks the way it does, which tradeoffs we made, and what a future developer inherits when the project changes hands.
Beyond the docs
Inspect the rest of the proof system
Documentation explains individual decisions. These surfaces show the build process, release standard, ownership model, measurement rules, and reproducible implementation evidence around those decisions.
How We Build
The full path from information architecture through launch, measurement, iteration, and handoff.
OpenMeasurement Methodology
How we define leads, attributable outcomes, time windows, limitations, and public result claims.
OpenRelease Quality Gate
What has to pass before we consider a production build ready to ship.
OpenWebsite Ownership Standard
The ownership, portability, source access, and handoff principles behind our custom website work.
OpenEngineering Lab
Reproducible implementation notes and tests drawn from patterns in production repositories.
OpenTechnical Buyer FAQ
Straight answers about custom code, ownership, SEO migrations, CMS choices, performance, and handoff.
Open