Open nhirrle opened 2 years ago
Hi Nicholas,
The project hasn't been maintained for a bit now due to several reasons. Myself and the other primary developer on the project haven't been working on it due to other obligations. But the primary reason is that the nodejs htl renderer was not able to accurately mimic the markup output that AEM provides, and as a result we were never able to get achieve parity of rendering to AEM. That obviously is a problem for developing and testing as one wouldn't want markup differences.
At this point the project would need a lot of work to update to the latest version of Storybook. Not impossible, but a decent sized task. If your team is interested in doing so, feel free :)
I've also heard that the htl nodejs renderer might be up to the task now after further development, but I can't confirm that.
I've also heard that the htl nodejs renderer might be up to the task now after further development...
(unfortunately) the htl renderer is not in active development neither, as there is not much demand.
Dear Team
We are currently setting up a new greenfield AEM-project and think about the usage of storybook to modernize Frontend-Development: Faster protoytping and more What's your recommendation for a new AEM project using Core Components, HTL Rendering and few further custom react components? In the readme.md we have seen that the project is not maintained anymore. What are the main reasons?
Thank you and best, Nicolas