The Multi-Site Era
March 12 – April 10, 2026 • The Umbrella Widens
The original 19 days had proven the architecture. What came next was the harder question: would it carry weight beyond mensprayerbreakfast.com? Could the Gold Standard, the soft-delete topology, the chapter import workflow — could all of it be lifted onto a different domain, with different content, different users, and still hold? The answer came in two waves.
ntwrk.net — The Local IT Business
John's service business comes home
ntwrk.net was John's own IT and service business — customer accounts, invoices, jobs, the whole service center. It had been running on its own legacy stack for years. Bringing it under WebCoPilot meant proving the platform could absorb a complete operational system, not just a content site.
The Service Center module was rebuilt. Customer records came over from QuickBooks Desktop exports. The OrgChart system — with its EntityType / EntityID polymorphic pattern — was wired into the customer view. SMS came online through Twilio (a 10DLC verification still pending, but the infrastructure was real). A second datasource pattern was formalized: DSN for the site, DSN2 for the org chart, Billing_DSN for shared customer data.
A lesson burned into memory: when John says "we're working on ntwrk.net," all work stays in ntwrk.net scope. No more cross-contamination between projects. The rule got its own user-memory file.
edsonmfg.net — A Manufacturing Legacy
A different industry, the same architecture
Then came Edson Manufacturing — a metal fabrication and rivet company with decades of history, marketing literature in PDFs, a deck of capability slides, and a story to tell. This one was about marketing, branding, and presentation. A whole new theme — navy and gold, slide-style sections with eyebrow tags and ultra-light headings — was built and stored in Color_Scheme='edsonmfg_theme'.
Seven pages went live: home, Products, Capabilities, History, Contact, Inventory, Rivetology. The same Layout_Pages + Pages + Widgets trinity that ran a church-platform homepage now ran an industrial manufacturer's product catalog. The platform had become a true CMS — not just a single-site tool.
The Deployment Golden Rules
Written in blood, kept in memory
Three sites running on shared infrastructure forced a discipline that one site never demanded. The deployment order became scripture: SC.exe first (remote service control), schema validation second (count tables in INFORMATION_SCHEMA after every script), files third, IIS recycle fourth, ColdFusion restart fifth, smoke test last. About 13 minutes per site — 8 automated, 5 manual.
And one absolute prohibition: no Unicode in CFM files. Em-dashes, smart quotes, en-dashes — all became garbled Latin characters when ColdFusion rendered them. ASCII or HTML entities only. A whole class of bugs simply stopped happening.
By the end of this period, WebCoPilot was no longer a website — it was a platform with three live sites, a documented deployment procedure, scoped project rules, and a memory system that remembered which path belonged to which project.
The dream that began as a single church platform had become an architecture — one that could carry an IT business, a manufacturer, and a ministry all at once. The pattern held. The standards held. The dreamer had built something that scaled.