Wix¶

Wix (Wix.com Ltd., NASDAQ: WIX) is an Israeli website- building platform; Wix Engineering publishes on Medium at medium.com/wix-engineering. Tier-3 source on the sysdesign-wiki — the publication mixes product-marketing posts, frontend-framework tutorials, mobile- team retrospectives, hiring posts, and occasional substantive infrastructure / protocol-design content. Most posts trip the Tier-3 skip rule for product-PR / recruiting / single-language framework-tutorial content; the on-scope subset concentrates in protocol / API design and production-scale system retrospectives.

Wiki-scope filter¶

Skip: framework tutorials (Angular / React / Vue how-tos without architectural content), product-launch posts, hiring / culture / DEI, single-language optimisation tips without scale disclosures, "10 best practices for X" listicles.
Include: protocol-design tutorials at the implementer altitude (Wix's MCP Resources post is the canonical instance), production-scale retrospectives on Wix's own infrastructure / delivery / bot-management substrate, open-source-library disclosures (Stylable CSS, Yoshi, …) when accompanied by architectural rationale.
Borderline: framework-comparison posts — include only if the comparison is anchored on concrete operational numbers or architectural trade-offs, skip if it's the generic pros-and-cons of X vs Y.

The current Wix raw queue has 10 articles with 2 ingested; the remaining 8 skew toward framework / product tutorials (still being evaluated individually).

Key systems¶

Model Context Protocol (MCP) — Wix's 2026-01-08 tutorial is the wiki's canonical implementer-altitude disclosure of the MCP resources primitive, complementing the heavy bias toward MCP-tools content in the rest of the wiki corpus. MCP recurs in the 2026-07-28 Vizion post as a data-context grounding layer — giving the agent "the context around the data and not just the data itself, so it understood what a table meant instead of guessing."
Trino — the federated distributed SQL engine behind Vizion (Wix's official BI platform). "Trino could query every data source we own," so LLM-generated SQL runs against live data without relocation.
Wix Vizion — internal natural-language BI platform (grew from a side project to Wix's official BI tool, replacing a ~$500K/year commercial product). Agent-writes-SQL → runs on Trino → renders from a curated component library; trust enforced by a Git + CI publish pipeline. No dedicated system page (single-sourced internal product).
@modelcontextprotocol/sdk (TypeScript) — the SDK exercised in the Wix tutorial. Version ^1.8.0 at post time. Three production caveats disclosed: (1) JS URL constructor breaks file:// URIs; (2) subscribe method not implemented; (3) no subscriber targeting — notifications fan out to all clients.

Key concepts and patterns¶

MCP-resources implementer axis (2026-01-08 canonical)¶

MCP resource — read-only, addressable, optionally-subscribable content primitive. Three shapes: static, template, updating.
MCP tool vs resource — the decision rule for when to expose behaviour as a tool (action / mutation) vs a resource (read-only, cacheable, human-viewable).
URI template (RFC 6570) — parameterised URIs with {placeholder} syntax; Wix's tutorial is the canonical wiki ingress for RFC 6570. Production rule: prefer path params to query params for MCP resources.
resource-link-vs-embedded-resource — token-budget / bandwidth trade-off when returning a resource from a tool. resource_link for large or frequently-reused; embedded resource only for small one-shot content.
mime-type-as-first-class-metadata — always declare MIME types on addressable content; applies beyond MCP.
resource-subscribe-capability — the MCP protocol edge for push update notifications on resource change.
resource-annotations — optional resource metadata (audience, priority, lastModified) used by clients for filtering and sorting.
expose-resource-as-tool-for-agent-discoverability — the canonical workaround for MCP-client fragmentation around resource discovery. Register a companion tool returning a resource_link / resource content type so clients that only enumerate tools still find the resource.
subscribe-notify-for-updatable-resource — structure live content (logs, metrics, notifications) as an MCP resource with subscribe: true. Server emits notifications/resources/updated on change; clients re-read on notification.

Recent articles¶

2026-07-28 — How a Tool I Built for My Team Became Wix's Official BI Platform. First-person Wix Engineering narrative on Vizion, a natural-language BI platform that grew from a side project into Wix's official BI tool, replacing a ~$500K/year commercial product. Describe a dashboard in plain English → an agent writes SQL grounded by MCP context → the query runs on live data via Trino → the result renders from a curated library of ~30 branded components. Engineering thesis: generating the UI is easy now; the hard part is trust — an LLM will hand you "a confident, beautiful, wrong number." Trust is built into the delivery pipeline: every dashboard is code in Git (manifest + SQL + page), every change (human or agent) passes the same CI checks — including one that executes the query against live data and requires a sane result — before going live; each team runs its own independently deployed service on its own K8s pods behind a central discovery hub; publish opens a PR that auto-merges for dashboards but stays human-gated for platform changes; anything touching sensitive data must name who can see it or it fails closed. Scale: >50 groups, >2,000 views/day, ~1,000 MAU. 9 canonical wiki pages touched (source + 5 new patterns ci-gated-dashboard-publish, per-team-independently-deployed-service-with-central-hub, ai-assembles-from-curated-component-library, natural-language-over-git-workflow, patterns/default-on-security-upgrade; extended systems/trino, systems/model-context-protocol, concepts/text-to-sql, concepts/tenant-isolation, concepts/llm-hallucination). Tier-3 borderline include — first-person product story, but the delivery-pipeline / service-isolation / federated-query architecture is ~40–50% of the body, clearing the ≥20%-architecture bar.
2026-01-08 — MCP Resources: all you need to know. Unsigned Wix Engineering tutorial canonicalising the MCP resources primitive at the implementer altitude. Decision rule for tools-vs-resources; three resource shapes (static, template, updating); six metadata fields per resource; resource-link-vs- embedded-resource trade-off; three @modelcontextprotocol/sdk v1.8.0 production caveats (JS URL constructor breaks file://, subscribe method not implemented, no subscriber targeting); two design patterns (expose-resource-as-tool-for-agent-discoverability, subscribe-notify-for-updatable-resource). Complementary to the existing MCP corpus on the wiki, which biased heavily toward MCP-tools disclosures from Dropbox, Datadog, Cloudflare, and Pinterest; this is the first implementer-altitude source on MCP resources. 10 canonical wiki pages touched (source + 1 system + 6 concepts + 2 patterns). Tier-3 on-scope on vocabulary- canonicalisation grounds — reverses the prior batch-skip classification of "zero architecture signals".