Urgent.News

What's breaking now, across thousands of outlets.

Tech

Pure CSS Spider / Radar Charts Are Here in st-core.fscss v2

No SVG. No canvas. No JS charting library. st-core.fscss v2 now draws spider (radar) charts the same way it draws area and line charts: FSCSS arrays, CSS custom properties, and clip-path: polygon() . The result looks like a modern product dashboard — skills matrices, multi-axis scores, team comparisons — and the payload stays tiny. The module Source: github.com/fscss-ttr/st-core.fscss Why this…

st-core.fscss v2 now draws spider (radar) charts using only CSS arrays, custom properties, and the clip-path: polygon() function. This approach results in a lightweight, modern look without the need for SVG, canvas, or a JavaScript charting library. The charts feature token-driven colors, soft polar geometry, and composable layers that stack as plain divs.

Multi-series charts are created by adding more layers with their own accent colors. The charts utilize native CSS inheritance, making it easy to create multiple team cards or dashboards without the need for a state tree. The total CSS for a chart class is only a few kilobytes, making it much lighter than other charting libraries.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

FAQ: A Drafted Retry Block Is Not a Flake Policy

A red job came back green after a single retry. Someone pasted a model draft and called the flake gone. I do not buy that story without a real job log.

  • Retry block in GitLab CI does not replace flaky job fixes.
  • Retry key queues another job attempt, not job stability guarantee.
  • Myth suggests retry key makes job safe, but only spends failure budget.

More from Saturday 10 October →