Skip to content

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 1 ingested; the remaining 9 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.
  • @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.
  • concepts/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.
  • concepts/mime-type-as-first-class-metadata — always declare MIME types on addressable content; applies beyond MCP.
  • concepts/resource-subscribe-capability — the MCP protocol edge for push update notifications on resource change.
  • concepts/resource-annotations — optional resource metadata (audience, priority, lastModified) used by clients for filtering and sorting.
  • patterns/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.
  • patterns/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-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 (patterns/expose-resource-as-tool-for-agent-discoverability, patterns/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".
Last updated · 476 distilled / 1,218 read