Sterling: A palette and components for data stories

Note: This analysis is based entirely on the self-reported project description provided by the author. No independent verification or historical data exists for this project.

• The description states that Sterling is an open-source palette and plug-and-play React/MDX figure system for data stories.
• It includes:
  • A reusable SterlingFigure shell for titles, subtitles, legends, sources, attribution, and responsive widths.
  • 28 D3/SVG visualization primitives (e.g., bars, scatterplots, violins, correlograms, dendrograms, Manhattan plots, expression matrices, maps).
  • Light, dark, and print-aware palettes with customizable ramps.
  • Features such as image copy, PNG export, mobile-native sharing, and CSV export of processed data rows.
  • Localized UI in English/Spanish and accessible chart labels.

Inference: The system is built using React, MDX, D3, SVG, CSS custom properties, TypeScript, and R scripts for data transformation. It integrates with npm and supports package installation.

• The author positions Sterling as a tool to solve the gap between finding interesting data and publishing it in a consistent, shareable way.
• Key claims:
  • “A blog should not need to reinvent its visual language every time it publishes data.”
  • “Sterling is my attempt to make those requirements feel editorial rather than bureaucratic.”
  • “It brings source, attribution, sharing, and processed data into the figure itself instead of treating them as afterthoughts.”

Inference: The positioning evolved from a personal problem-solving effort (during YouTube live series) into a structured system aimed at improving reproducibility, consistency, and usability in data storytelling.

• Not evidenced.
• The description does not identify specific customer segments or personas.
• It is implied that the target audience includes data visualization engineers, researchers, content creators, or analysts who publish visualizations regularly.
• However, no explicit segmentation or buyer persona is described.

Absence of evidence: No stated ICP, customer types, or use cases beyond the author’s own workflow.

• Not evidenced.
• The project is described as open-source and published on npm.
• There is no mention of monetization, pricing tiers, subscriptions, or paid features.
• No indication of whether Sterling will ever be commercialized or if there are plans for a freemium model.

Absence of evidence: No business model or pricing information provided.

• Built with:
  • React, MDX, D3, SVG, CSS custom properties, TypeScript
  • R scripts for data transformation
  • Node.js, npm, GitHub Actions, Vite
  • AI tools: GPT-5.6 (Sol High and Terra High), Claude Opus 4.8, OpenAI Codex
• Uses:
  • GitHub for version control
  • Lucide React icons
  • Tailwind CSS
  • TopoJSON, HTML-to-image, JSON, Web Share API
• Delivered as an npm package with documentation and smoke tests
• Supports localization (English/Spanish), accessibility features, and export fidelity

Claim: The system is designed for portability and reusability across platforms and tools.

• Not evidenced.
• No mention of downloads, user engagement, or adoption metrics.
• The author describes a solo development process and internal testing.
• A small consumer smoke test is mentioned but not quantified.
• No evidence of external users, feedback loops, or product iteration history.

Absence of evidence: No traction data, customer base, or usage statistics available.

• Not evidenced.
• The description does not reference competitors or similar tools in the space.
• It is unclear how Sterling compares to existing open-source or commercial visualization libraries (e.g., D3.js, Plotly, Tableau, Power BI, Matplotlib).
• No discussion of market positioning or differentiation.

Absence of evidence: No competitive landscape or comparison data provided.

• Solo development risk: The project is built by a single individual (Cynthia Castillo), which raises concerns about long-term maintenance, scalability, and support.
• AI dependency: Heavy reliance on AI tools for implementation may create fragility if those tools change or become unavailable.
• Open-source sustainability: As an open-source tool, there is no clear path to monetization or funding, which could limit future development.
• Lack of adoption evidence: Without external usage or feedback, it's unclear whether Sterling addresses a real market need or solves a problem widely felt by others.

Inference: The lack of traction and customer validation suggests early-stage uncertainty around product-market fit.

1. What specific problems are you trying to solve for users beyond your own workflow?
2. Have you received any feedback from other developers or data professionals who have tried Sterling?
3. How do you plan to sustain development and maintenance of the project long-term?
4. Are there any plans to monetize or commercialize Sterling in the future?
5. What are the key technical challenges that remain unresolved or under-tested?
6. How does Sterling handle edge cases in data visualization (e.g., missing values, outliers)?
7. Is there a roadmap for expanding chart types or integrating with other ecosystems (R, Python, etc.)?