@fusion.dev/helix-docs 0.108.2 → 0.109.1

package/content/introduction.mdx

@@ -62,6 +62,7 @@ each framework.
 | `@fusion.dev/helix-headless` | You want the behavior and none of the styling |
 | `@fusion.dev/helix-theme` | You are generating or validating a theme |
 | `@fusion.dev/helix-icons` | You are drawing an icon outside a component |
+| `@fusion.dev/helix-map` | You are drawing a map with MapLibre, Leaflet, or a renderer of your own. See [Maps](./maps) |
 | `@fusion.dev/helix-core` | You are building a new Helix component |
 
 React uses the elements directly. Helix ships a `jsx.d.ts` that types every

package/content/metrics.mdx

@@ -403,7 +403,7 @@ stripped column shows the bytes we removed.
 | `@fusion.dev/helix-icons` | 150,162 | 21 | 50,346 | `svgo` |
 | `@fusion.dev/helix-styles` | 102,108 | 6 | 0 | none |
 | `@fusion.dev/helix-theme` | 465,413 | 8 | 4,703 | none |
-| `@fusion.dev/helix` | 14,189,471 | 870 | 368,333 | `@fusion.dev/helix-core`, `@fusion.dev/helix-headless`, `@fusion.dev/helix-styles` |
+| `@fusion.dev/helix` | 14,191,826 | 870 | 370,788 | `@fusion.dev/helix-core`, `@fusion.dev/helix-headless`, `@fusion.dev/helix-styles` |
 
 ## Not measured yet
 

package/content/recipes.mdx

@@ -112,7 +112,7 @@ In prose:
 
 See [Typography](./typography).
 
-Two Markdown constructs need components, because HTML alone cannot hold what
+Three Markdown constructs need components, because HTML alone cannot hold what
 they need:
 
 - **Fenced code** becomes `helix-code-block`, with the fence's language as its
@@ -121,8 +121,13 @@ they need:
   tone. `NOTE` becomes `tone="info"`, `TIP` becomes `success`, `WARNING` becomes
   `warning`, and `CAUTION` becomes `danger`. `IMPORTANT` has no tone. Each
   callout is headed by its kind, as GitHub shows it.
+- **Tables** become `helix-table`. A `<table>` squeezes its columns to fit, so
+  a narrow screen breaks a value such as `eu-central-1` across lines. The
+  header row becomes the table's columns, each aligned as the Markdown aligned
+  it. A column of short values stays whole, a column of sentences wraps, and a
+  table wider than the screen scrolls in its own box.
 
-The `rehype` plugin from `@fusion.dev/helix/rehype` makes both changes in the
+The `rehype` plugin from `@fusion.dev/helix/rehype` makes all three changes in the
 tree your Markdown library has already built. It parses nothing, so your
 library, its dialect, and your sanitizing stay yours. Add it to any pipeline
 that reaches rehype, such as `remark` with `remark-rehype`, `react-markdown`, or
@@ -141,10 +146,13 @@ const html = await unified()
 
 Code that a highlighter colored before the plugin ran keeps its colors. Pass
 `fences: false` if your page draws its own code blocks, `alerts: false` to keep
-alerts as quotes, and `headings` to name each kind in your page's language.
+alerts as quotes, `tables: false` to keep tables as HTML, and `headings` to
+name each kind in your page's language. A table with a caption, a cell that
+spans more than one column or row, or a heading cell outside its header row
+stays HTML, because the grid cannot draw it as written.
 
 > [!NOTE]
-> The plugin changes only these two constructs. If the Markdown comes from your
+> The plugin changes only these three constructs. If the Markdown comes from your
 > users, sanitize it in your pipeline before the plugin runs.
 
 Prose spaces each component the same as the element it replaces.

package/dist/sources.generated.js

@@ -2070,6 +2070,7 @@ each framework.
 | \`@fusion.dev/helix-headless\` | You want the behavior and none of the styling |
 | \`@fusion.dev/helix-theme\` | You are generating or validating a theme |
 | \`@fusion.dev/helix-icons\` | You are drawing an icon outside a component |
+| \`@fusion.dev/helix-map\` | You are drawing a map with MapLibre, Leaflet, or a renderer of your own. See [Maps](./maps) |
 | \`@fusion.dev/helix-core\` | You are building a new Helix component |
 
 React uses the elements directly. Helix ships a \`jsx.d.ts\` that types every
@@ -3156,7 +3157,7 @@ stripped column shows the bytes we removed.
 | \`@fusion.dev/helix-icons\` | 150,162 | 21 | 50,346 | \`svgo\` |
 | \`@fusion.dev/helix-styles\` | 102,108 | 6 | 0 | none |
 | \`@fusion.dev/helix-theme\` | 465,413 | 8 | 4,703 | none |
-| \`@fusion.dev/helix\` | 14,189,471 | 870 | 368,333 | \`@fusion.dev/helix-core\`, \`@fusion.dev/helix-headless\`, \`@fusion.dev/helix-styles\` |
+| \`@fusion.dev/helix\` | 14,191,826 | 870 | 370,788 | \`@fusion.dev/helix-core\`, \`@fusion.dev/helix-headless\`, \`@fusion.dev/helix-styles\` |
 
 ## Not measured yet
 
@@ -3904,7 +3905,7 @@ In prose:
 
 See [Typography](./typography).
 
-Two Markdown constructs need components, because HTML alone cannot hold what
+Three Markdown constructs need components, because HTML alone cannot hold what
 they need:
 
 - **Fenced code** becomes \`helix-code-block\`, with the fence's language as its
@@ -3913,8 +3914,13 @@ they need:
   tone. \`NOTE\` becomes \`tone="info"\`, \`TIP\` becomes \`success\`, \`WARNING\` becomes
   \`warning\`, and \`CAUTION\` becomes \`danger\`. \`IMPORTANT\` has no tone. Each
   callout is headed by its kind, as GitHub shows it.
+- **Tables** become \`helix-table\`. A \`<table>\` squeezes its columns to fit, so
+  a narrow screen breaks a value such as \`eu-central-1\` across lines. The
+  header row becomes the table's columns, each aligned as the Markdown aligned
+  it. A column of short values stays whole, a column of sentences wraps, and a
+  table wider than the screen scrolls in its own box.
 
-The \`rehype\` plugin from \`@fusion.dev/helix/rehype\` makes both changes in the
+The \`rehype\` plugin from \`@fusion.dev/helix/rehype\` makes all three changes in the
 tree your Markdown library has already built. It parses nothing, so your
 library, its dialect, and your sanitizing stay yours. Add it to any pipeline
 that reaches rehype, such as \`remark\` with \`remark-rehype\`, \`react-markdown\`, or
@@ -3933,10 +3939,13 @@ const html = await unified()
 
 Code that a highlighter colored before the plugin ran keeps its colors. Pass
 \`fences: false\` if your page draws its own code blocks, \`alerts: false\` to keep
-alerts as quotes, and \`headings\` to name each kind in your page's language.
+alerts as quotes, \`tables: false\` to keep tables as HTML, and \`headings\` to
+name each kind in your page's language. A table with a caption, a cell that
+spans more than one column or row, or a heading cell outside its header row
+stays HTML, because the grid cannot draw it as written.
 
 > [!NOTE]
-> The plugin changes only these two constructs. If the Markdown comes from your
+> The plugin changes only these three constructs. If the Markdown comes from your
 > users, sanitize it in your pipeline before the plugin runs.
 
 Prose spaces each component the same as the element it replaces.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-docs",
   "description": "Versioned documentation content and registry for Helix.",
-  "version": "0.108.2",
+  "version": "0.109.1",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -36,8 +36,8 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.108.2",
-    "@fusion.dev/helix-testing": "0.108.2",
+    "@fusion.dev/helix-cem": "0.109.1",
+    "@fusion.dev/helix-testing": "0.109.1",
     "@fusion.dev/scripts": "0.0.0-dev",
     "lit": "^3.2.1",
     "playwright": "^1.62.1"