Documentation

    Documentation

    Documentation

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    1. /
    2. /Customization Guide

    Updated Jun 12, 20264 min listen

    1. /
    2. /Customization Guide

    Updated Jun 12, 20264 min listen

    1. /
    2. /Customization Guide

    Updated Jun 12, 20264 min listen

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps
    Architecture
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM architecture
    PaymentConductor architecture
    Refcodes architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Discovery Mutation Sync
    Security
    Features
    Doc System
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Web3 Wallet
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payment Integration
    PaymentConductor
    VideoConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    CLI
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Database Backend Selection
    Token Economics Setup
    Payment Gateway Integration
    AI Agent Customization
    Reference Ring deployments
    Branding
    Features
    Localization
    Themes
    Components
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Roadmap
    Examples
    Quick Start
    Authentication
    Email AI-CRM developer guide
    API Integration Examples
    Web3 Integration
    White Label
    Real World
    API Examples (cURL)
    Integrations
    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps
    Architecture
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM architecture
    PaymentConductor architecture
    Refcodes architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Discovery Mutation Sync
    Security
    Features
    Doc System
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Web3 Wallet
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payment Integration
    PaymentConductor
    VideoConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    CLI
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Database Backend Selection
    Token Economics Setup
    Payment Gateway Integration
    AI Agent Customization
    Reference Ring deployments
    Branding
    Features
    Localization
    Themes
    Components
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Roadmap
    Examples
    Quick Start
    Authentication
    Email AI-CRM developer guide
    API Integration Examples
    Web3 Integration
    White Label
    Real World
    API Examples (cURL)
    Integrations
    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps
    Architecture
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM architecture
    PaymentConductor architecture
    Refcodes architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Discovery Mutation Sync
    Security
    Features
    Doc System
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Web3 Wallet
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payment Integration
    PaymentConductor
    VideoConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    CLI
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Database Backend Selection
    Token Economics Setup
    Payment Gateway Integration
    AI Agent Customization
    Reference Ring deployments
    Branding
    Features
    Localization
    Themes
    Components
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Roadmap
    Examples
    Quick Start
    Authentication
    Email AI-CRM developer guide
    API Integration Examples
    Web3 Integration
    White Label
    Real World
    API Examples (cURL)
    Integrations
    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Docs
    Customization
    Docs
    Customization
    Docs
    Customization

    Customization Guide

    Time estimate: 1–4 hours for branding + feature toggles. Prerequisites: Quick Start completed locally.

    Ring clones share one codebase. Customization is config-first (ring-config.json, env, locales), then optional component overrides. The legacy portal layer is removed — the public home is HomeWrapper + HomeContent, not a separate portal app.

    Customization map

    Where white-label settings live

    1. ring-config.json (install-time SSOT)

    Created by ./install.sh or copied from ring-config.template.json. Merged with the template at runtime in lib/ring-config-core.ts (also exposed server-side via lib/ring-config.ts).

    Clone identity

    json
    
    {
      "clone": {
        "name": "my-ring-clone",
        "displayName": "My Platform",
        "description": "Regional opportunities network",
        "organization": "Your Org",
        "contactEmail": "contact@example.com"
      },
      "domains": {
        "production": "https://example.com",
        "development": "http://localhost:3000"
      },
      "platform": {
        "baseUrl": "https://example.com"
      }
    }

    Used for SEO (lib/seo-metadata.ts), JSON-LD, and getSiteBaseUrl().

    Branding block

    branding.logo, branding.colors, branding.darkColors, branding.fonts in the template — place assets under public/images/ (see template paths).

    Optional env overrides (lib/site-branding.ts):

    Feature flags

    Toggle modules without deleting code:

    Server checks: isFeatureEnabled() in lib/ring-config-core.ts and whitelabel/features.ts. Disable routes in navigation when turning features off.

    Matcher defaults

    Install-time AI matcher thresholds live under matcher in ring-config.json (getMatcherInstallDefaults()). Runtime DB overlay may apply for production rings — see AI customization.

    Sidebar and navigation metadata

    sidebar and navigation.links in ring-config.json feed public instance config (getPublicInstanceConfig()). Primary chrome is implemented in:

    • components/navigation/navigation.tsx
    • components/navigation/desktop-sidebar.tsx
    • components/navigation/bottom-navigation.tsx

    For a custom desktop nav variant, follow Whitelabel navigation.

    2. Home page (replaces deprecated portal)

    LayerFileRole
    Routeapp/(public)/[locale]/page.tsxStatic metadata + renders HomeWrapper
    Layout shellcomponents/wrappers/home-wrapper.tsxResponsive grid, right rail, session-aware chrome
    Hero bodycomponents/common/pages/home.tsxDaVinci hero, CTAs, feature rotator
    Copylocales/{locale}/pages.json → homePrimary hero title, subtitle, features[], right-rail strings

    Do not configure a separate “portal” app or lib/portal-config.ts — that path is deprecated. Marketing home is always HomeWrapper on /.

    Customize hero copy (fastest path)

    Edit locales/en/pages.json (mirror uk, ru):

    HomeContent reads via useTranslations('pages.home').

    Customize home layout

    • Right rail (OSS marketplace / Ringdom CTAs): HomeRightRail inside home-wrapper.tsx, strings in pages.home.rightRail
    • Deeper UX — fork home-wrapper.tsx or home.tsx; add paths to .reggie-propagate-exclude.json

    ring-config.json hero block remains for clones that read it elsewhere; the flagship home hero is i18n-driven as above.

    3. Internationalization

    • SSOT: lib/locale-config.ts
    • Messages: locales/{locale}/**/*.json, loaded by lib/i18n.ts
    • Routing: @/i18n/routing — never hand-strip locale prefixes in client code

    Full guide: Localization.

    Protected locale files (often per-clone) are listed in .reggie-propagate-exclude.json — e.g. locales/*/config.json, vendor.json, calculator.json.

    4. Theme and visual polish

    Ring uses Tailwind 4 with CSS variables for light/dark (next-themes).

    1. Set branding.colors / darkColors in ring-config.json (template documents keys aligned to shadcn tokens)
    2. Replace public/favicon.ico, public/images/logo-*.svg, apple-touch-icon.png
    3. Theme default: ring-config.json → "theme": { "default": "system" }

    Avoid editing generated design tokens in unrelated clones — prefer ring-config + env brand overrides.

    5. Payments and store (clone-level)

    • PaymentConductor processors: env vars — Payment integration
    • Store currency / tax: features.store in ring-config.json
    • WayForPay / Stripe: never commit secrets; use k8s secrets in production

    6. Web3 and tokens (optional)

    Contract addresses and treasury: env + Token economics. Set tokens.ring in ring-config.json for display metadata.

    7. Reggie propagation exclusions

    When pulling updates from ring-greenfood-live (or upstream), protect fork-specific files:

    File: .reggie-propagate-exclude.json at repo root.

    8. Verification checklist

    1. 1

      Branding — logo, favicon, NEXT_PUBLIC_BRAND_NAME, OG image on share previews

    2. 2

      Home — / hero matches pages.home in each supported locale

    3. 3

      Features — disabled modules 404 or hide from nav; no dead sidebar links

    4. 4

      Auth — login/logout, role-gated admin at /admin

    5. 5

      Build — npm run build clean; smoke tests if payments enabled

    Next steps

    Database selection

    DB_BACKEND_MODE and migration strategy

    Payment integration

    WayForPay, Stripe, webhooks

    AI customization

    Matcher tuning and agent costs

    Quick Start (new clone)

    Fork discipline: Config + locales first, component forks second, exclusions before propagation. Your clone should upgrade without merge wars.

    Customization Guide

    Time estimate: 1–4 hours for branding + feature toggles. Prerequisites: Quick Start completed locally.

    Ring clones share one codebase. Customization is config-first (ring-config.json, env, locales), then optional component overrides. The legacy portal layer is removed — the public home is HomeWrapper + HomeContent, not a separate portal app.

    Customization map

    Where white-label settings live

    1. ring-config.json (install-time SSOT)

    Created by ./install.sh or copied from ring-config.template.json. Merged with the template at runtime in lib/ring-config-core.ts (also exposed server-side via lib/ring-config.ts).

    Clone identity

    json
    
    {
      "clone": {
        "name": "my-ring-clone",
        "displayName": "My Platform",
        "description": "Regional opportunities network",
        "organization": "Your Org",
        "contactEmail": "contact@example.com"
      },
      "domains": {
        "production": "https://example.com",
        "development": "http://localhost:3000"
      },
      "platform": {
        "baseUrl": "https://example.com"
      }
    }

    Used for SEO (lib/seo-metadata.ts), JSON-LD, and getSiteBaseUrl().

    Branding block

    branding.logo, branding.colors, branding.darkColors, branding.fonts in the template — place assets under public/images/ (see template paths).

    Optional env overrides (lib/site-branding.ts):

    Feature flags

    Toggle modules without deleting code:

    Server checks: isFeatureEnabled() in lib/ring-config-core.ts and whitelabel/features.ts. Disable routes in navigation when turning features off.

    Matcher defaults

    Install-time AI matcher thresholds live under matcher in ring-config.json (getMatcherInstallDefaults()). Runtime DB overlay may apply for production rings — see AI customization.

    Sidebar and navigation metadata

    sidebar and navigation.links in ring-config.json feed public instance config (getPublicInstanceConfig()). Primary chrome is implemented in:

    • components/navigation/navigation.tsx
    • components/navigation/desktop-sidebar.tsx
    • components/navigation/bottom-navigation.tsx

    For a custom desktop nav variant, follow Whitelabel navigation.

    2. Home page (replaces deprecated portal)

    LayerFileRole
    Routeapp/(public)/[locale]/page.tsxStatic metadata + renders HomeWrapper
    Layout shellcomponents/wrappers/home-wrapper.tsxResponsive grid, right rail, session-aware chrome
    Hero bodycomponents/common/pages/home.tsxDaVinci hero, CTAs, feature rotator
    Copylocales/{locale}/pages.json → homePrimary hero title, subtitle, features[], right-rail strings

    Do not configure a separate “portal” app or lib/portal-config.ts — that path is deprecated. Marketing home is always HomeWrapper on /.

    Customize hero copy (fastest path)

    Edit locales/en/pages.json (mirror uk, ru):

    HomeContent reads via useTranslations('pages.home').

    Customize home layout

    • Right rail (OSS marketplace / Ringdom CTAs): HomeRightRail inside home-wrapper.tsx, strings in pages.home.rightRail
    • Deeper UX — fork home-wrapper.tsx or home.tsx; add paths to .reggie-propagate-exclude.json

    ring-config.json hero block remains for clones that read it elsewhere; the flagship home hero is i18n-driven as above.

    3. Internationalization

    • SSOT: lib/locale-config.ts
    • Messages: locales/{locale}/**/*.json, loaded by lib/i18n.ts
    • Routing: @/i18n/routing — never hand-strip locale prefixes in client code

    Full guide: Localization.

    Protected locale files (often per-clone) are listed in .reggie-propagate-exclude.json — e.g. locales/*/config.json, vendor.json, calculator.json.

    4. Theme and visual polish

    Ring uses Tailwind 4 with CSS variables for light/dark (next-themes).

    1. Set branding.colors / darkColors in ring-config.json (template documents keys aligned to shadcn tokens)
    2. Replace public/favicon.ico, public/images/logo-*.svg, apple-touch-icon.png
    3. Theme default: ring-config.json → "theme": { "default": "system" }

    Avoid editing generated design tokens in unrelated clones — prefer ring-config + env brand overrides.

    5. Payments and store (clone-level)

    • PaymentConductor processors: env vars — Payment integration
    • Store currency / tax: features.store in ring-config.json
    • WayForPay / Stripe: never commit secrets; use k8s secrets in production

    6. Web3 and tokens (optional)

    Contract addresses and treasury: env + Token economics. Set tokens.ring in ring-config.json for display metadata.

    7. Reggie propagation exclusions

    When pulling updates from ring-greenfood-live (or upstream), protect fork-specific files:

    File: .reggie-propagate-exclude.json at repo root.

    8. Verification checklist

    1. 1

      Branding — logo, favicon, NEXT_PUBLIC_BRAND_NAME, OG image on share previews

    2. 2

      Home — / hero matches pages.home in each supported locale

    3. 3

      Features — disabled modules 404 or hide from nav; no dead sidebar links

    4. 4

      Auth — login/logout, role-gated admin at /admin

    5. 5

      Build — npm run build clean; smoke tests if payments enabled

    Next steps

    Database selection

    DB_BACKEND_MODE and migration strategy

    Payment integration

    WayForPay, Stripe, webhooks

    AI customization

    Matcher tuning and agent costs

    Quick Start (new clone)

    Fork discipline: Config + locales first, component forks second, exclusions before propagation. Your clone should upgrade without merge wars.

    Customization Guide

    Time estimate: 1–4 hours for branding + feature toggles. Prerequisites: Quick Start completed locally.

    Ring clones share one codebase. Customization is config-first (ring-config.json, env, locales), then optional component overrides. The legacy portal layer is removed — the public home is HomeWrapper + HomeContent, not a separate portal app.

    Customization map

    Where white-label settings live

    1. ring-config.json (install-time SSOT)

    Created by ./install.sh or copied from ring-config.template.json. Merged with the template at runtime in lib/ring-config-core.ts (also exposed server-side via lib/ring-config.ts).

    Clone identity

    json
    
    {
      "clone": {
        "name": "my-ring-clone",
        "displayName": "My Platform",
        "description": "Regional opportunities network",
        "organization": "Your Org",
        "contactEmail": "contact@example.com"
      },
      "domains": {
        "production": "https://example.com",
        "development": "http://localhost:3000"
      },
      "platform": {
        "baseUrl": "https://example.com"
      }
    }

    Used for SEO (lib/seo-metadata.ts), JSON-LD, and getSiteBaseUrl().

    Branding block

    branding.logo, branding.colors, branding.darkColors, branding.fonts in the template — place assets under public/images/ (see template paths).

    Optional env overrides (lib/site-branding.ts):

    Feature flags

    Toggle modules without deleting code:

    Server checks: isFeatureEnabled() in lib/ring-config-core.ts and whitelabel/features.ts. Disable routes in navigation when turning features off.

    Matcher defaults

    Install-time AI matcher thresholds live under matcher in ring-config.json (getMatcherInstallDefaults()). Runtime DB overlay may apply for production rings — see AI customization.

    Sidebar and navigation metadata

    sidebar and navigation.links in ring-config.json feed public instance config (getPublicInstanceConfig()). Primary chrome is implemented in:

    • components/navigation/navigation.tsx
    • components/navigation/desktop-sidebar.tsx
    • components/navigation/bottom-navigation.tsx

    For a custom desktop nav variant, follow Whitelabel navigation.

    2. Home page (replaces deprecated portal)

    LayerFileRole
    Routeapp/(public)/[locale]/page.tsxStatic metadata + renders HomeWrapper
    Layout shellcomponents/wrappers/home-wrapper.tsxResponsive grid, right rail, session-aware chrome
    Hero bodycomponents/common/pages/home.tsxDaVinci hero, CTAs, feature rotator
    Copylocales/{locale}/pages.json → homePrimary hero title, subtitle, features[], right-rail strings

    Do not configure a separate “portal” app or lib/portal-config.ts — that path is deprecated. Marketing home is always HomeWrapper on /.

    Customize hero copy (fastest path)

    Edit locales/en/pages.json (mirror uk, ru):

    HomeContent reads via useTranslations('pages.home').

    Customize home layout

    • Right rail (OSS marketplace / Ringdom CTAs): HomeRightRail inside home-wrapper.tsx, strings in pages.home.rightRail
    • Deeper UX — fork home-wrapper.tsx or home.tsx; add paths to .reggie-propagate-exclude.json

    ring-config.json hero block remains for clones that read it elsewhere; the flagship home hero is i18n-driven as above.

    3. Internationalization

    • SSOT: lib/locale-config.ts
    • Messages: locales/{locale}/**/*.json, loaded by lib/i18n.ts
    • Routing: @/i18n/routing — never hand-strip locale prefixes in client code

    Full guide: Localization.

    Protected locale files (often per-clone) are listed in .reggie-propagate-exclude.json — e.g. locales/*/config.json, vendor.json, calculator.json.

    4. Theme and visual polish

    Ring uses Tailwind 4 with CSS variables for light/dark (next-themes).

    1. Set branding.colors / darkColors in ring-config.json (template documents keys aligned to shadcn tokens)
    2. Replace public/favicon.ico, public/images/logo-*.svg, apple-touch-icon.png
    3. Theme default: ring-config.json → "theme": { "default": "system" }

    Avoid editing generated design tokens in unrelated clones — prefer ring-config + env brand overrides.

    5. Payments and store (clone-level)

    • PaymentConductor processors: env vars — Payment integration
    • Store currency / tax: features.store in ring-config.json
    • WayForPay / Stripe: never commit secrets; use k8s secrets in production

    6. Web3 and tokens (optional)

    Contract addresses and treasury: env + Token economics. Set tokens.ring in ring-config.json for display metadata.

    7. Reggie propagation exclusions

    When pulling updates from ring-greenfood-live (or upstream), protect fork-specific files:

    File: .reggie-propagate-exclude.json at repo root.

    8. Verification checklist

    1. 1

      Branding — logo, favicon, NEXT_PUBLIC_BRAND_NAME, OG image on share previews

    2. 2

      Home — / hero matches pages.home in each supported locale

    3. 3

      Features — disabled modules 404 or hide from nav; no dead sidebar links

    4. 4

      Auth — login/logout, role-gated admin at /admin

    5. 5

      Build — npm run build clean; smoke tests if payments enabled

    Next steps

    Database selection

    DB_BACKEND_MODE and migration strategy

    Payment integration

    WayForPay, Stripe, webhooks

    AI customization

    Matcher tuning and agent costs

    Quick Start (new clone)

    Fork discipline: Config + locales first, component forks second, exclusions before propagation. Your clone should upgrade without merge wars.

    One Ring deployment per organization

    Token economics

    RING contracts and membership

    Architecture

    System layout and backend modes

    env
    
    NEXT_PUBLIC_BRAND_NAME=My Platform
    NEXT_PUBLIC_BRAND_TAGLINE=Your tagline
    NEXT_PUBLIC_BRAND_LOGO=/images/logo-light.svg
    NEXT_PUBLIC_BRAND_OG_IMAGE=/og-image.png
    json
    
    {
      "features": {
        "entities": { "enabled": true },
        "opportunities": { "enabled": true, "types": ["offer", "request"] },
        "store": { "enabled": true, "multiVendor": true },
        "web3": { "enabled": false },
        "ai": { "enabled": true, "matcher": true },
        "messaging": { "enabled": true }
      }
    }
    json
    
    {
      "home": {
        "hero": {
          "title": "Your headline",
          "subtitle": "One sentence value prop",
          "features": ["Bullet 1", "Bullet 2"]
        }
      }
    }
    env
    
    NEXT_PUBLIC_SUPPORTED_LOCALES=en,uk,ru
    NEXT_PUBLIC_DEFAULT_LOCALE=en
    json
    
    {
      "features": {
        "web3": {
          "enabled": true,
          "ringToken": true,
          "defaultChain": "polygon"
        }
      }
    }
    json
    
    {
      "exclude_paths": [
        "ring-config.json",
        ".env.local",
        "locales/en/config.json",
        "components/wrappers/home-wrapper.tsx"
      ]
    }

    One Ring deployment per organization

    Token economics

    RING contracts and membership

    Architecture

    System layout and backend modes

    env
    
    NEXT_PUBLIC_BRAND_NAME=My Platform
    NEXT_PUBLIC_BRAND_TAGLINE=Your tagline
    NEXT_PUBLIC_BRAND_LOGO=/images/logo-light.svg
    NEXT_PUBLIC_BRAND_OG_IMAGE=/og-image.png
    json
    
    {
      "features": {
        "entities": { "enabled": true },
        "opportunities": { "enabled": true, "types": ["offer", "request"] },
        "store": { "enabled": true, "multiVendor": true },
        "web3": { "enabled": false },
        "ai": { "enabled": true, "matcher": true },
        "messaging": { "enabled": true }
      }
    }
    json
    
    {
      "home": {
        "hero": {
          "title": "Your headline",
          "subtitle": "One sentence value prop",
          "features": ["Bullet 1", "Bullet 2"]
        }
      }
    }
    env
    
    NEXT_PUBLIC_SUPPORTED_LOCALES=en,uk,ru
    NEXT_PUBLIC_DEFAULT_LOCALE=en
    json
    
    {
      "features": {
        "web3": {
          "enabled": true,
          "ringToken": true,
          "defaultChain": "polygon"
        }
      }
    }
    json
    
    {
      "exclude_paths": [
        "ring-config.json",
        ".env.local",
        "locales/en/config.json",
        "components/wrappers/home-wrapper.tsx"
      ]
    }

    One Ring deployment per organization

    Token economics

    RING contracts and membership

    Architecture

    System layout and backend modes

    env
    
    NEXT_PUBLIC_BRAND_NAME=My Platform
    NEXT_PUBLIC_BRAND_TAGLINE=Your tagline
    NEXT_PUBLIC_BRAND_LOGO=/images/logo-light.svg
    NEXT_PUBLIC_BRAND_OG_IMAGE=/og-image.png
    json
    
    {
      "features": {
        "entities": { "enabled": true },
        "opportunities": { "enabled": true, "types": ["offer", "request"] },
        "store": { "enabled": true, "multiVendor": true },
        "web3": { "enabled": false },
        "ai": { "enabled": true, "matcher": true },
        "messaging": { "enabled": true }
      }
    }
    json
    
    {
      "home": {
        "hero": {
          "title": "Your headline",
          "subtitle": "One sentence value prop",
          "features": ["Bullet 1", "Bullet 2"]
        }
      }
    }
    env
    
    NEXT_PUBLIC_SUPPORTED_LOCALES=en,uk,ru
    NEXT_PUBLIC_DEFAULT_LOCALE=en
    json
    
    {
      "features": {
        "web3": {
          "enabled": true,
          "ringToken": true,
          "defaultChain": "polygon"
        }
      }
    }
    json
    
    {
      "exclude_paths": [
        "ring-config.json",
        ".env.local",
        "locales/en/config.json",
        "components/wrappers/home-wrapper.tsx"
      ]
    }