You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We created a storybook project so we could use ROOS (and other NL Design projects) for reference. The project is not maintained or updated at the moment. It also is not actively used, as most of us use the (official) ROOS storybook.
What do we want to do with the project?
Some options: a) we could archive it for now and remove the gh pages deployment
b) we could put auto-update in place to keep security issues away
c) we just leave it as is
d) yet another option
Preference for option a since:
We already use the official ROOS Storybook
Maintaining a parallel system creates unnecessary overhead
We do not need to spend time on re-evaluating this issue
Description
We created a storybook project so we could use ROOS (and other NL Design projects) for reference. The project is not maintained or updated at the moment. It also is not actively used, as most of us use the (official) ROOS storybook.
What do we want to do with the project?
Some options:
a) we could archive it for now and remove the gh pages deployment
b) we could put auto-update in place to keep security issues away
c) we just leave it as is
d) yet another option
Preference for option a since:
Technical Implementation
The text was updated successfully, but these errors were encountered: