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
Following a similar pattern, we should build an index for data visualization. This should showcase all existing charting components, with maintainer info etc, but also allow submission of other charts and under different frameworks.
Should be able to submit entries in a similar way (via .yml file)
Should include thumbnail, title, description, link to website guidance for that chart, link to code (where available).
Filter categories should be the same (even if actual filter items might be different - e.g. different maintainer list).
_NB: If end point is possible integration of this index and the component index, in a single "catalog" of resources, then database scheme should be consistent/compatible.
@joshblack, @andreancardona - anything in terms of pitfalls that we should be aware of? @aagonzales - could we use the same design template for this (at least for initial pass)
The text was updated successfully, but these errors were encountered:
Following a similar pattern, we should build an index for data visualization. This should showcase all existing charting components, with maintainer info etc, but also allow submission of other charts and under different frameworks.
So should model, very similarly, to https://www.carbondesignsystem.com/community/component-index.
Should be able to submit entries in a similar way (via .yml file)
Should include thumbnail, title, description, link to website guidance for that chart, link to code (where available).
Filter categories should be the same (even if actual filter items might be different - e.g. different maintainer list).
_NB: If end point is possible integration of this index and the component index, in a single "catalog" of resources, then database scheme should be consistent/compatible.
@joshblack, @andreancardona - anything in terms of pitfalls that we should be aware of?
@aagonzales - could we use the same design template for this (at least for initial pass)
The text was updated successfully, but these errors were encountered: