adobe / adobe/aem-project-archetype
New Frontend Module: React Web Components (non SPA)
- Dominant language
- JavaScript
- Stars
- 596
- Forks
- 431
- Avg merge
- 10d 6h
- Merged PRs (30d)
- 1
Description
Would be nice to have an option to generate the project with a frontend module that follows react web components approach (non SPA)
Two options:
1. Extension of general frontend module so that we can still use existing approach for standard content components + react web components approach for specific, frontend complex components.
2. Only react web components approach
https://github.com/adobe/react-webcomponent
https://github.com/adobe/aem-react-core-wcm-components-examples/tree/master/react-webcomponents-example-project
Contributor guide
Research direction
Start by reviewing the linked adobe/react-webcomponent repository and the react-webcomponents-example-project. Compare the two proposed generation options and determine the expected archetype entry points from those examples; done means the project generator supports the agreed non-SPA React Web Components setup with documented generated output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100