Charts are product components, not decorative embeds.
The chart layer needs family breadth, dataset modeling, interaction, theming, animation, screenshots, and reference coverage.
Breadth
Large chart catalog
Line, bar, area, pie, scatter, heatmap, financial, relationship, map, component, dynamic, and 3D-oriented families.
Product fit
Dashboards and analytics
Build monitoring, finance, operations, reporting, planning, and decision-support views without leaving Fission.
Design
Theme-aware visuals
Charts consume the design system palette, typography, backgrounds, dark mode, and interaction rules.
Chart architecture
Start with the data story, then choose the visual form.
Production charts need the right family, typed data, interaction behavior, theme integration, and tests that prove the rendered output.
Catalog
Choose a family deliberately
The reference catalog groups chart families and variants so dashboards can use the right visual form for comparison, trend, distribution, hierarchy, geography, or topology.
Series and datasets define how data enters the chart, including static sets, streaming updates, and larger histories that should not be loaded all at once.