Skip to main content

Platform Architecture

This page describes Yamify’s platform architecture and how we scale content and docs around OpenClaw.

Canonical + URL Plan​

  • Canonical docs/tutorials live at docs.yamify.co/openclaw/... (Docusaurus)
  • Public “deploy in 1 click” pages live at yamify.co/packs/... (Next.js)

Programmatic Content Architecture​

We publish many small, specific pages that answer real error messages and “how do I…” questions. This creates strong topic authority while keeping content actionable.

Page Families​

  1. Errors (200 pages): openclaw/errors/<slug>
    • One exact error message per page (title and H1 = message)
    • Includes symptoms, root cause, fix steps, verification checklist
  2. Recipes (300 pages): openclaw/recipes/<slug>
    • Repeatable solutions built from Yamify tools (OpenClaw, n8n, Supabase, Mattermost, Qwen)
    • Includes inputs, steps, “it works” verification
  3. Skill Packs (500 pages): openclaw/packs/<slug>
    • Generated from the same pack registry used by the install flow
    • Includes what it does, required secrets, compatibility, deploy CTA

Sources of Truth (GitOps)​

  • Errors catalog: data/openclaw-errors.catalog.json
  • Recipes catalog: data/openclaw-recipes.catalog.json
  • Packs registry: data/openclaw-pack-registry.json

Templates (Required Sections)​

Errors

  • Exact error message (title + H1)
  • Common message code block
  • Fix steps (numbered)
  • Verification checklist
  • Links to related errors + relevant recipe

Recipes

  • Tool combo
  • Problem statement
  • Steps
  • “It works” verification
  • Links to relevant packs + errors

Packs

  • What it does
  • Deploy inputs: repoUrl/ref/path
  • Compatibility: provider(s), model(s)
  • Required secrets
  • “Deploy” CTA to Yamify

Internal Linking Rules​

  • Each Error links to its category index and 1–3 related errors
  • Each Recipe links to Recipes index and 1–2 packs + 1–2 errors
  • Each Pack links to Packs index and 1–3 recipes

Execution Workflow​

  • Expand catalogs from real production logs and use-cases
  • Generate pages during docs build (prebuild)
  • Keep sitemap updated for SEO and AI discovery