Closed jeffchew closed 4 years ago
On Aug 26, Jeff-Chew commented: @hahnrob I'm dropping this down to a low priority. Even if we do this work, the masthead and footer have functionality that would need a developer to create these components manually in HTML anyway. The only place I'd see this as useful would possibly be in the patterns package where there's low/no actual functionality, and even then the Drupal team is already expecting to absorb patterns as React code.
I'm thinking of moving this out to later this year or even next year.
cc: @linda-carotenuto @Wonil-Suh1
On Aug 26, hahnrob commented: @Jeff-Chew If you do decide to move this work out beyond sprint 24, lets put it in the icebox pipeline with the icebox label.
We've marked this issue as stale because there hasn't been any activity for 30 days. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.
Closing this, I feel that this might be more trouble than it is worth for now.
Jeff-Chew created the following on Jul 08:
User Story
This story captures the research to see if it is a viable to autogenerate vanilla JS components from react components. This would reduce the time necessary to create the non-React components for the IBM.com library.
Acceptance Criteria
Original issue: https://github.ibm.com/webstandards/digital-design/issues/1194