Management of Dev Resource links is critical in our design systems. We are developing a multi-brand design system at Thryv that supports both React and Vue.js, and need to add resource links to a composed Storybook which documents a lot of components.
- Dev resource links are not editable from branches. We have our main file set to view-only so that design contributors have to branch to work for system integrity. They can’t add the dev resource links as part of their definition of done, putting the weight of that responsibility on the owner(s).
- Dev resource links can’t be automated easily for repititious components like illustrations that may all use a shared resource, but each component needs a link (and yes, I understand variants -- they are not appropriate for this circumstance). Between being an Electron app and lacking standard accessibility controls, hidden buttons that reveal on hover, and the links themselves changing positions after being saved, it’s challenging to work with something like Applescript.
- Dev resource links have been updated to be progressively disclosed if there are more than two. If using a main documentation link > 2 dev resource links, that means that only 1 link is exposed when in dev mode.
It would be really nice to have the ability to
- Select a group of components and add or modify the dev resource links for them
- Have some automation tools for things like dev resource links
- Be able to edit dev resource links from design mode