FAQ from Raber
What is Raber?
Raber is a next-generation visual editing layer for React apps—blending AI intelligence with true component fidelity. Unlike traditional CMS tools, it doesn’t replace your components with generic blocks; instead, it surfaces your *own* React code as editable, composable elements—enabling fast, safe, and scalable content delivery.
How do I get started with Raber?
Install the Raber SDK, annotate your components with editable prop schemas, and initialize the editor in your app. Within minutes, your team gains a live-editing interface for any route—no backend changes, no new frameworks, just enhanced collaboration on top of what you already built.
Does Raber require changes to my React architecture?
No. Raber works with standard React (v18+), Next.js, Remix, Vite, and more. It operates client-side, requires no server-side rendering hooks or custom data layers, and respects your existing state management, routing, and styling solutions.
How does Raber ensure security and governance?
Raber supports granular permissions (e.g., “marketing can edit hero text but not CTAs”), environment-aware publishing (staging vs. production), and optional SSO integration. All edits are validated against your component contracts—preventing invalid props or broken renders.
Can Raber handle complex, interactive components?
Absolutely. From forms with validation to embedded dashboards and animated sections—Raber preserves behavior, event handlers, and dynamic state. The editor renders components in their natural context, so interactivity remains fully functional during editing and after publishing.