Content & Appearance

Future control plane for public pages, navigation, copy, SEO, and brand selection.

Content & Appearance Control Layer

Future control plane for everything public-facing in RFA OS. Today this is configuration only — no draft/preview/publish runtime yet. The Admin surface visualizes the registry so the owner can verify scope before MP8+ activates it.

NOT_RUNTIME_IMPLEMENTEDADMIN_UI_SCAFFOLDEDCONTENT_CONFIG_READYAPPEARANCE_CONFIG_READY

Public surfaces

CONTENT_CONFIG_READY

Landing, marketing, docs, login surface registry.

Navigation

CONTENT_CONFIG_READY

Header, sidebar, footer link sets per locale.

Hero copy

CONTENT_CONFIG_READY

Headline / sub / Persian slogan / CTA pair.

Call-to-action library

CONTENT_CONFIG_READY

Buttons + link CTAs the future Admin can swap.

Footer

CONTENT_CONFIG_READY

Legal lines, doctrine note, owner attribution.

Logo / brand selection

APPEARANCE_CONFIG_READY

Pick logo variant per surface (light/dark/icon).

Design tokens

APPEARANCE_CONFIG_READY

Colors / radius / spacing — registered palette only.

SEO metadata

CONTENT_CONFIG_READY

Title / description / OG / canonical per surface.

Language content

CONTENT_CONFIG_READY

Per-locale strings in en/fa/ar/tr; RTL aware.

Draft / preview / publish

FUTURE_DRAFT_PREVIEW_PUBLISH

Future workflow: draft → preview → publish.

Out of scope

  • Prompt body editing (PPB-protected — bodies are never in the repo).
  • Routing logic / scoring rules / provider keys.
  • Real publish to a public URL — there is no public URL in MP7.
  • User-facing AI calls — RFA_AI_LIVE_CALLS_ENABLED stays false.