Skill: garchi-render-content

Scope

• ✅ Build or improve the code needed to fetch and render Garchi CMS content (pages, sections, data items).
• ✅ Integrate Garchi CMS into an existing codebase without breaking conventions.
• ❌ Do not manage CMS content (create pages/sections/assets/templates) unless the user explicitly asks. Prefer MCP tools for CMS actions.

Always (non-negotiable rules)

1. Preserve Visual Editor attributes
   • For every section component, forward unknown/extra props/attributes to the root element (outermost wrapper).
   • Framework-agnostic rule: “Unknown attributes must not be dropped; attach them to the root/host element.”
   • Patterns:
     • React/Preact/Solid: spread ...other on root
     • Vue: v-bind="$attrs" on root
     • Svelte: spread ...$$restProps on root
     • Angular: preserve/pass through host attributes; do not strip unknown attrs
     • Web Components: keep attrs on host or forward to outer wrapper
     • Laravel Blade: ensure attributes are passed to the root element of the section component {{ $attributes->merge()}}