As a frontend developer, I can assemble portions of my React SPA dynamically from Magnolia content and templates.

Acceptance criteria

• Developer can define the mapping from JCR content (typically the mgnl:template property) to React component classes.
• Primarily support JSON content from the Magnolia delivery endpoint.
• Primarily support templates from the templateDefinitions endpoint.
• Developer does not have to write the logic producing a component tree; a module/function is provided with default conventions
• Supports nested components, i.e. components which have areas.

–

• Usage of the library follows React idioms such that it is easy to understand and use for a React developer.
• Implementation of the library follows React idioms such that it is easy to understand and fork and modify for a React developer.

See also:

• https://git.magnolia-cms.com/projects/INCUBATOR/repos/react-magnolia/browse/index.js
• Demo project with a tree of pages and nested components