Skip to content
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.

Deprecation of Storybook Adobe Experience Manager ? #158

Open
nhirrle opened this issue Dec 20, 2021 · 2 comments
Open

Deprecation of Storybook Adobe Experience Manager ? #158

nhirrle opened this issue Dec 20, 2021 · 2 comments

Comments

@nhirrle
Copy link

nhirrle commented Dec 20, 2021

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

@jzeltman
Copy link
Contributor

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.

@tripodsan
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants