@umriss-ui/charts 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -29,6 +29,18 @@ interface was still expected to move before `0.3.0`.
 
 ---
 
+## 0.8.1 – Found by search (Sep. 2026)
+
+### Fixed
+
+- **The package's description and keywords say what it is in the words a
+  search uses**, and the demo it links to addresses every page by a path
+  (`…/charts/<page>/`) instead of a hash, with the page's text readable before
+  the demo starts. Old `#/<page>` links still land. Nothing in the package's
+  code changed.
+
+---
+
 ## 0.8.0 – Working time (Sep. 2026)
 
 ### Changed

package/README.md

@@ -1,6 +1,6 @@
 # @umriss-ui/charts
 
-Canvas-based charts for data-dense applications: few chart kinds, each one drawn
+React canvas charts for data-dense dashboards: few chart kinds, each one drawn
 properly. Lines, areas, bars, scatters, state bands and matrices compose into
 one chart on shared axes — together with the instruments a monitoring screen is
 made of: limit lines and bands, a control chart, a Pareto and a working-time

package/docs/llms-full.md

@@ -1,6 +1,6 @@
-# @umriss-ui/charts 0.8.0
+# @umriss-ui/charts 0.8.1
 
-> Canvas charts for data-dense applications - few chart kinds, drawn well, fast.
+> React canvas chart library for data-dense dashboards - line, area, bar, scatter, control and Pareto charts. Few chart kinds, drawn well, fast.
 
 Install with `pnpm add @umriss-ui/charts`. This text is generated from the package's demo (https://romanhaendler.github.io/umriss-ui/charts/): every page with its import line, its examples - the source exactly as it runs, with the package name where the demo imports its own source - its props tables generated from the code, and what it deliberately does not do. The pages index stands in https://romanhaendler.github.io/umriss-ui/charts/llms.txt.
 
@@ -523,7 +523,7 @@ What to know before the first chart.
 
 Install the package, draw a first chart and size it in its container. Read this once before the component pages; everything after it assumes it.
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/getting-started
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/getting-started/
 
 Install with `pnpm add @umriss-ui/charts`; React 18 or 19 is the only peer, and the package depends on nothing else. The stylesheet comes with the JavaScript, so there is nothing to import - `@umriss-ui/charts/styles.css` is there for setups that link stylesheets by hand.
 
@@ -633,7 +633,7 @@ Holds the rows and draws the series on shared axes, one chart for every kind a s
 import { Chart } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/chart
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/chart/
 
 Series and axes are children, and their order in the JSX is the drawing order and the colour order. The marks are drawn on canvas; axes, legend and tooltip are elements a screen reader and a test can read (ADR-0001).
 
@@ -975,7 +975,7 @@ What a value is measured against: extent, ticks and labels, several axes per sid
 import { XAxis, YAxis, workingCalendar } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/axis
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/axis/
 
 Every scale is linear. Categories are numbers 0, 1, 2 … with a `tickFormat` that names them (ADR-0002); a working calendar maps time before it is drawn and marks every seam it took out (ADR-0001).
 
@@ -1262,7 +1262,7 @@ Joins the readings of a series into a course (a line chart, a trend). Reach for
 import { Line } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/line
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/line/
 
 A missing reading breaks the line; nothing is drawn across a gap. With `step` a value holds until the next one, for things logged only when they change.
 
@@ -1422,7 +1422,7 @@ A filled course (an area chart): down to zero for a quantity, between two edges
 import { Area } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/area
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/area/
 
 Without `baseline` the foot is 0 and stays in the y extent. A range's lower edge is the `baseline` accessor of the same series, not a second series - where either edge is missing, the fill has a hole.
 
@@ -1545,7 +1545,7 @@ Bars on the numeric x axis (a bar or column chart): one per category, grouped si
 import { Bar } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/bar
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/bar/
 
 A category is a position the axis places and a `tickFormat` names (ADR-0002). A bar's foot is 0, so one series carries both signs.
 
@@ -1728,7 +1728,7 @@ Single readings as points, joined by nothing (a scatter plot, dots). Reach for i
 import { Scatter } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/scatter
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/scatter/
 
 #### Examples
 
@@ -1817,7 +1817,7 @@ What something was doing over time, as a band of coloured segments (a status tim
 import { StateBand } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/stateband
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/stateband/
 
 The accessor returns a state's place in `states`, which fixes the order, the name and the colour in one place (ADR-0007). Each segment runs to the next reading; a `null` leaves a hole, never a colour for unknown.
 
@@ -1959,7 +1959,7 @@ One value per cell across two axes (a heatmap), coloured by its limits or along
 import { Matrix, DEFAULT_GRADIENT } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/matrix
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/matrix/
 
 A cell without a value stays a hole, not a zero. The tooltip carries the value as text, since colour alone carries no number.
 
@@ -2050,7 +2050,7 @@ The limits a course is read against (a threshold, a reference line): a line abov
 import { LimitLine, LimitBand } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/limitline
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/limitline/
 
 A limit's tone follows its `severity`, never a colour of its own. The model is the one `@umriss-ui/core` uses for its verdicts, so a chart and a tile agree (ADR-0006).
 
@@ -2234,7 +2234,7 @@ Centre line, control limits and the rule violations of a process (an SPC or Shew
 import { ControlChart, controlLimits, violations } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/controlchart
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/controlchart/
 
 Control limits are computed from a named reference window, never from what happens to be visible; specification limits are chosen and drawn with `LimitLine` (ADR-0008).
 
@@ -2372,7 +2372,7 @@ Causes sorted by weight with a cumulative line (a Pareto chart). Reach for it af
 import { pareto } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/pareto
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/pareto/
 
 `pareto()` sorts, adds up and folds the tail into one entry that stands last whatever its size; the bars, the line and the second axis are yours to compose.
 
@@ -2437,7 +2437,7 @@ What a hover reports and what the colours mean (a hover card, a key), and the va
 import { Tooltip, Legend, DataTable } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/tooltip
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/tooltip/
 
 The crosshair snaps to a reading, never between two. A legend without `onToggle` only explains; with it, it switches series on and off, and the state stays yours.
 
@@ -2731,7 +2731,7 @@ Millions of points, measured in this browser rather than claimed: the time to pr
 import { Chart } from "@umriss-ui/charts";
 ```
 
-Demo page: https://romanhaendler.github.io/umriss-ui/charts/#/benchmark
+Demo page: https://romanhaendler.github.io/umriss-ui/charts/benchmark/
 
 A hover redraws only the overlay layer, so the frame rate stays up over a million points. The figures in `packages/charts/docs/capabilities.md` come from here.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@umriss-ui/charts",
-  "version": "0.8.0",
-  "description": "Canvas charts for data-dense applications - few chart kinds, drawn well, fast.",
+  "version": "0.8.1",
+  "description": "React canvas chart library for data-dense dashboards - line, area, bar, scatter, control and Pareto charts. Few chart kinds, drawn well, fast.",
   "license": "MIT",
   "author": "Roman Händler",
   "homepage": "https://romanhaendler.github.io/umriss-ui/charts/",
@@ -15,11 +15,18 @@
   },
   "keywords": [
     "react",
-    "components",
-    "ui",
-    "umriss",
+    "react-charts",
     "charts",
-    "canvas"
+    "chart-library",
+    "canvas",
+    "line-chart",
+    "bar-chart",
+    "scatter-plot",
+    "control-chart",
+    "pareto",
+    "dashboard",
+    "typescript",
+    "umriss"
   ],
   "type": "module",
   "files": [
@@ -63,7 +70,7 @@
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
     "@umriss-ui/demo": "0.0.0",
-    "@umriss-ui/core": "0.11.0"
+    "@umriss-ui/core": "0.14.1"
   },
   "scripts": {
     "props": "node --disable-warning=ExperimentalWarning --experimental-strip-types demo/props.ts",