Architecture

Changelog — 2026-10-30. Four-piece shape aligned to home.md teaser-card order per Phase 2 piece-set-drift fix: Your own design, built for how dojos run → Pages and content you own → SEO equity on your own domain → Found by AI assistants. The retired “shared foundation across dojos” piece (specialist-stack-economics argument) moves back to internal materials (battle-card, sales conversations) and is no longer a public-surface piece. Content portability and SEO equity now carry distinct boundaries — portability names ownership and exit rights; SEO equity names brand-domain authority accumulation. Red earn-mark unchanged on the capability-ceiling piece’s leg-claim topic sentence per §8.5 r3. AI-answer piece keeps honest-footing register per §8.5 r3. “Prospective member” → “prospective practitioner” propagated per register discipline (practitioners train, members pay; GMS product-level “memberships / billing / scheduling” references stay as-is).

A dojo website is doing more work than it used to. It has to show up when someone searches for your gym, tell a prospective practitioner what the dojo stands for, and — increasingly — be readable by the AI assistants a prospective practitioner is asking “where to train BJJ in Tokyo” before they ever Google anything.

There are two reasonable ways to meet that work. Let your gym management system (GMS) host your website alongside your schedule and signup — one bill, one login, no decisions to make. Or split it: website on a layer built for how dojos run, operational backend on the GMS where it belongs. The four sections below are the four places where that choice stops being a matter of taste and starts being a matter of what a website is supposed to deliver for your business.

Your own design, built for how dojos run

This is the piece of the architecture where what a bundled-builder website is built to do stops matching what a brand-ambitious dojo actually needs. A bundled builder ships a fixed block picker with no HTML embed primitive, a single site-wide meta title and description shared across every page, and a vendor placeholder as the social-share image on every page you don’t override. A website built for how dojos run handles the specific jobs: bilingual EN/JA at the URL level with proper hreflang, per-page meta title / description / Open Graph image, and content schemas for instructor lineage, federation presence, and an alert banner the dojo can change itself on a Tuesday before class without opening a ticket. The gap matters most at the brand-ambitious tier — dojos whose website is doing specific work (a bilingual audience, federation-presence editorial, a design language that is not someone else’s template) the bundled layer was not built to do.

Pages and content you own

Your dojo’s website lives in two places: a git repository that holds the code, and a Sanity CMS workspace that holds the content. Both are addressable with your login. Both export to standard formats — markdown for content, JSON for structured data, source for code — any day you choose to export them. A bundled builder’s content, by contrast, lives in a vendor tenancy you reach through the vendor’s admin; the exit path, when the vendor offers one, is typically a scheduled CSV of member records rather than a portable copy of your pages, their images, and their structured content. If Digital Dojo stops operating tomorrow, the website keeps running, the content keeps saving, and the repository is readable by any developer you hand it to. Leave the GMS; the website stays. Leave Digital Dojo; the code and the content leave with you. Ownership here is a structural fact of where the content is written and where the repository is addressable — not a vendor promise about export tools.

SEO equity on your own domain

Five years of search equity accrue to the domain a search engine indexes your content on — not the one your browser bar shows. A bundled builder will map yourdojo.com to its platform, so the browser bar reads right; the canonical URL in the page’s <head> still points at the vendor’s subdomain, and that is where Google’s index lands the equity. A general-fitness GMS whose website layer is a set of iframe widgets has the same shape: the widget content renders from the vendor’s subdomain, and the vendor controls the canonical URL for the content Google indexes. On a website built for how dojos run, the pages render as native HTML from your own domain; the canonical URL on every page is a URL you control; the search equity accrues to yourdojo.com. For a brand-ambitious dojo whose five-year horizon includes being found by prospective practitioners through search — in another city, in another country, or in another language — this is where the website decision compounds the longest. (See Brand domain vs. vendor subdomain for the full receipt.)

Found by AI assistants

A prospective practitioner asking an AI assistant where to train BJJ in Tokyo this week is reading pre-rendered HTML, structured data emitted at build time, and — on sites that publish one — a plain-text index of what the site covers. The retrieval layer that AI assistants build their answers from is still forming; which specific protocols the next three years settle on is not something anyone can tell you with full certainty. What is already clear is the structural shape: content that renders on the server rather than booting client-side in a browser, structured data at the page level, and an index an AI can read without executing JavaScript. A website built for how dojos run ships those three things by default; a bundled-builder website that renders content client-side and emits no page-level structured data is not architecturally in the room for that conversation yet, regardless of which specific protocols the retrieval layer settles on. (See When an AI answers “where to train BJJ in Tokyo” for the full argument.)

Where this architecture already runs

Axis Jiu-Jitsu Tokyo runs on exactly this architecture — we built it there first, with the head instructor reviewing every call. See the Axis Jiu-Jitsu Tokyo case study for how the four pieces came together on one dojo’s actual site.

Talk about your dojo

If any of the four pieces above answers a question you have been sitting on, write to marc@niolacontentsystems.com — or send an inquiry.