@qkix/strapi-plugin-chartkit 0.1.7 → 0.3.0

package/README.md

@@ -67,6 +67,21 @@ look right here and wrong there.
 The editor opens in a dialog. Cancel genuinely cancels: it edits a draft and
 only writes on save.
 
+### Labels are dates
+
+Turn this on and the labels stop being names and become instants: readings are
+placed by _when_ they are, so a day's gap and a fortnight's gap no longer look
+alike. Ticks then come from the calendar rather than from your rows, which is
+what lets a year of daily figures label itself with a few months instead of 365
+smeared dates.
+
+Labels have to be dates for it - ISO 8601, e.g. `2026-08-20`. One that is not is
+named in the editor rather than quietly drawn as a category again.
+
+Off by default, including for labels that look like dates: `2024` and `2025` may
+be two categories you meant to weigh equally, and re-spacing them because they
+parse would be a decision this plugin has no business making for you.
+
 ## Three ways to get the numbers in
 
 Most charts already exist as numbers somewhere, and retyping them is the worst
@@ -114,7 +129,17 @@ import { Chart } from '@qkix/chartkit-astro-renderer';
 <Chart spec={article.chart} locale="en-US" />
 ```
 
-Both produce markup at build or request time. Neither ships a runtime.
+```vue
+<script setup>
+import { Chart } from '@qkix/chartkit-vue-renderer';
+</script>
+
+<template>
+  <Chart :spec="article.chart" locale="en-US" />
+</template>
+```
+
+They all produce markup at build or request time. None ships a runtime.
 
 ## It takes your theme, including dark mode
 
@@ -142,6 +167,21 @@ SSR chart renderer. The obvious candidate, ECharts in SSR mode, writes its
 palette into the markup as literal hex values - which makes class-based dark
 mode impossible without post-processing the output.
 
+### When one chart needs to say something else
+
+Under **Colors** in the editor there is a swatch per series - per slice, on a pie
+or donut. Leave one alone and it keeps following your stylesheet; set one and
+that series overrules it, which is what picking out a single line or reddening
+the quarter that went wrong requires.
+
+Only the entries you set are stored, so highlighting one series does not freeze
+the colors of the others against your next restyle. The cross beside a swatch
+hands that series back to the site.
+
+A color set here beats the CSS on purpose. The stylesheet is the house style; a
+chart that names a color is overruling it for a reason, and a house style that
+could silently repaint it would be no override at all.
+
 ## Also a block, if you use Better Blocks
 
 <img src="https://raw.githubusercontent.com/qkix/strapi-plugins/main/packages/strapi-plugin-chartkit/docs/block.png" alt="A chart block inside a Better Blocks rich-text document" width="700" />
@@ -191,13 +231,14 @@ script, or a field that used to be a different type - it says so and goes
 | [`@qkix/chartkit-core`](https://www.npmjs.com/package/@qkix/chartkit-core)                     | the spec, the validator and the SVG renderer. No dependencies. |
 | [`@qkix/chartkit-react-renderer`](https://www.npmjs.com/package/@qkix/chartkit-react-renderer) | rendering a stored chart in React / Next.js                    |
 | [`@qkix/chartkit-astro-renderer`](https://www.npmjs.com/package/@qkix/chartkit-astro-renderer) | rendering a stored chart in Astro                              |
+| [`@qkix/chartkit-vue-renderer`](https://www.npmjs.com/package/@qkix/chartkit-vue-renderer)     | rendering a stored chart in Vue / Nuxt                         |
 | [`@qkix/chartkit-editor`](https://www.npmjs.com/package/@qkix/chartkit-editor)                 | the editing surface, and the ready-made block                  |
 
 ## Not there yet
 
-Being honest about the edges: no time axes, no tooltips or other
-interactivity, and no per-chart color overrides - palettes are set in your site's
-CSS. Data is stored with the chart rather than queried from a collection.
+Being honest about the edges: no tooltips or other interactivity. Data is stored
+with the chart rather than queried from a collection, so a chart of something
+that changes is a chart somebody has to remember to update.
 
 Issues and ideas welcome at
 [qkix/strapi-plugins](https://github.com/qkix/strapi-plugins/issues).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qkix/strapi-plugin-chartkit",
-  "version": "0.1.7",
+  "version": "0.3.0",
   "description": "Charts for Strapi v5, rendered as server-side SVG with no client-side JavaScript",
   "strapi": {
     "kind": "plugin",
@@ -43,8 +43,8 @@
     "dist"
   ],
   "dependencies": {
-    "@qkix/chartkit-editor": "^0.1.5",
-    "@qkix/chartkit-core": "^0.2.4"
+    "@qkix/chartkit-core": "^0.4.0",
+    "@qkix/chartkit-editor": "^0.3.0"
   },
   "devDependencies": {
     "@strapi/sdk-plugin": "^5.3.2",
@@ -59,9 +59,9 @@
     "styled-components": "^6.1.17",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@qkix/tsconfig": "0.0.0",
+    "@qkix/eslint-config": "0.0.0",
     "@qkix/strapi-test-harness": "0.0.0",
-    "@qkix/eslint-config": "0.0.0"
+    "@qkix/tsconfig": "0.0.0"
   },
   "peerDependencies": {
     "@strapi/admin": "^5.0.0",