How studioraketa/raketa-cms works
Project type and purpose
• This is a React‐based CMS framework published as the npm package @raketa-cms/raketa-cms.
• It provides a block-based page builder (“AdminBuilder”) and a runtime page renderer (“PageRender”) that can be dropped into any React or Next.js app.
• The repository also includes an example Next.js application (/example) showing how to integrate the library, and a starter Next.js template (/starters/nextjs) to speed up adoption.
File structure
• Root
• src/ : core CMS code (components, contexts, dialogs, forms, helpers, pickers)
• example/ : demonstration Next.js app integrating AdminBuilder and PageRender
• starters/nextjs/ : a full-blown Next.js boilerplate with CMS integration and custom storage glue
• config files: ESLint, Prettier, Travis CI, .tool-versions (language manager)
• Core modules in src/ group naturally:
• Components (Canvas.js, Container.js, List.js, etc.)
• Contexts (BuilderContext, HostContext, LibraryContext)
• Dialogs (Reorder, Settings) & Forms (text, textarea, select, link, button, custom)
• Utility libraries (helpers/, lib/)
• Example shows two “pages”:
• /admin renders AdminBuilder.js to let editors drag/drop/configure widgets
• / renders PageRender.js to display the live page
README for additional insights
• The CMS is data-driven: pages are JSON blobs with a widgets array.
• Each widget is defined by a quartet: Widget (frontend view), Config (metadata), Defaults, Admin (settings schema).
• Container settings are globally configurable and applied to every widget.