-
#lazyweb I need help: is there a tool to organize a design system (before development) so that higher order components can declare their dependencies to other components/elements? e.g.: COMPONENT X # seen in: - component A - component B # includes: - component Y
-
This would allow to map components and inclusions and help prioritize development. It also helps in covering whether some components require different types of data based on their context/inclusion. It might be a simple whim -- one could go agile and forget about it
-
but I searched and couldn't find much. PatternLab does this, but *after* the development. Bonus: a loose integration with Trello