notro-loader 0.0.1 → 0.0.3

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2024 mosugi
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2024 mosugi
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,276 +1,276 @@
-# notro-loader
-
-![npm](https://img.shields.io/npm/v/notro-loader)
-![License: MIT](https://img.shields.io/badge/license-MIT-blue)
-
-An Astro Content Loader library that fetches Notion database content via the [Markdown Content API](https://developers.notion.com/) into [Astro Content Collections](https://docs.astro.build/en/guides/content-collections/).
-
-> [!TIP]
-> Sample project: [notro](https://github.com/mosugi/notro)
-
-## What NotroContent renders
-
-`NotroContent` compiles Notion markdown into HTML. Each Notion block type maps to a semantic HTML element by default. You can replace any element with your own styled component via the `components` prop.
-
-| Notion block | Default HTML | notro-ui component |
-|---|---|---|
-| Paragraph | `<p>` | `ColoredParagraph` |
-| Heading 1–4 | `<h1>`–`<h4>` | `H1`–`H4` |
-| Callout | `<aside>` | `Callout` |
-| Quote | `<blockquote>` | `Quote` |
-| Toggle | `<details>` + `<summary>` | `Toggle` + `ToggleTitle` |
-| Divider | `<hr>` | — |
-| Code | `<pre>` | — |
-| Image | `<img>` | `ImageBlock` |
-| Video | `<figure>` | `Video` |
-| Audio | `<figure>` | `Audio` |
-| File | `<div>` | `FileBlock` |
-| PDF | `<figure>` | `PdfBlock` |
-| Table | `<table>` | `TableBlock` |
-| Table of contents | `<nav>` | `TableOfContents` |
-| Columns / Column | `<div>` / `<div>` | `Columns` / `Column` |
-| Page link | `<a>` | `PageRef` |
-| Database link | `<a>` | `DatabaseRef` |
-| Empty block | `<div>` | `EmptyBlock` |
-| Inline text (colored/underline) | `<span>` | `StyledSpan` |
-| @mention | `<span>` | `Mention` |
-| Date mention | `<time>` | `MentionDate` |
-
-`notro-ui` is an optional style layer. See [notro-ui](https://github.com/mosugi/notro/tree/main/packages/notro-ui) for details.
-
-## Installation
-
-```sh
-npx astro add notro-loader
-```
-
-This installs the package and automatically adds the `notro()` integration to `astro.config.mjs`.
-
-Alternatively, install manually:
-
-```sh
-npm install notro-loader
-```
-
-## Setup
-
-### 1. `astro.config.mjs`
-
-`astro add notro-loader` configures this automatically. If you installed manually, add:
-
-```js
-import { defineConfig } from "astro/config";
-import { notro } from "notro-loader/integration";
-
-export default defineConfig({
-  integrations: [notro()],
-});
-```
-
-This registers `@astrojs/mdx` with the required plugin pipeline and the Astro JSX renderer that `NotroContent` depends on at runtime.
-
-### 2. `src/content.config.ts`
-
-Define your collection using the `loader` function. Extend `pageWithMarkdownSchema` with your database properties. Use the `notroProperties` shorthand for concise property schemas.
-
-```typescript
-import { defineCollection } from "astro:content";
-import { loader, pageWithMarkdownSchema, notroProperties } from "notro-loader";
-import { z } from "zod";
-
-const posts = defineCollection({
-  loader: loader({
-    queryParameters: {
-      data_source_id: import.meta.env.NOTION_DATASOURCE_ID,
-      filter: {
-        property: "Public",
-        checkbox: { equals: true },
-      },
-    },
-    clientOptions: {
-      auth: import.meta.env.NOTION_TOKEN,
-    },
-  }),
-  schema: pageWithMarkdownSchema.extend({
-    properties: z.object({
-      Name: notroProperties.title,
-      Description: notroProperties.richText,
-      Public: notroProperties.checkbox,
-      Tags: notroProperties.multiSelect,
-      Date: notroProperties.date,
-    }),
-  }),
-});
-
-export const collections = { posts };
-```
-
-### 3. Page component
-
-#### Option A — Headless (no styling)
-
-`NotroContent` from `notro-loader` renders semantic HTML with no classes.
-
-```astro
----
-import { NotroContent, getPlainText } from "notro-loader";
-
-const { entry } = Astro.props;
-const title = getPlainText(entry.data.properties.Name);
----
-
-<h1>{title}</h1>
-<NotroContent markdown={entry.data.markdown} />
-```
-
-#### Option B — With notro-ui
-
-Install the styled components once:
-
-```sh
-npx notro-ui init
-```
-
-Then pass the component map to `NotroContent`:
-
-```astro
----
-import { NotroContent, getPlainText } from "notro-loader";
-import { notroComponents } from "@/components/notro";
-
-const { entry } = Astro.props;
----
-
-<NotroContent markdown={entry.data.markdown} components={notroComponents} />
-```
-
-Components are copied into `src/components/notro/` so you can edit them directly.
-
-## Markdown processing (remark-nfm)
-
-`notro-loader` delegates Notion Markdown preprocessing and directive syntax support to the [`remark-nfm`](https://www.npmjs.com/package/remark-nfm) package.
-
-`remark-nfm` is used inside notro-loader's MDX compile pipeline and is applied automatically when using `NotroContent`.
-
-If you want to use `remark-nfm` directly (in a custom unified pipeline or `@mdx-js/mdx`'s `evaluate()`), import it from the `remark-nfm` package directly rather than from `notro-loader`.
-
-```ts
-// ✅ Import directly from remark-nfm
-import { remarkNfm, preprocessNotionMarkdown } from "remark-nfm";
-
-// ❌ Not needed from notro-loader (internal use only)
-// import { remarkNfm } from "notro-loader";
-```
-
-## Notion API limitations
-
-> Reference: [Retrieve a page as Markdown – Notion API](https://developers.notion.com/reference/retrieve-page-markdown)
-
-### Content truncation (`truncated`)
-
-`GET /v1/pages/{page_id}/markdown` truncates content at approximately **20,000 blocks**.
-
-- Detectable via `truncated: true` in the response, but **there is no pagination API to fetch the rest**
-- notro logs a warning when `truncated === true` and continues the build with the available content
-- Workaround: split large Notion pages into multiple smaller pages
-
-```
-⚠ Page abc123: markdown content was truncated by the Notion API (~20,000 block limit).
-  No pagination is available for this endpoint.
-  Consider splitting this Notion page into smaller pages to avoid truncation.
-```
-
-### Unrenderable blocks (`unknown_block_ids`)
-
-`unknown_block_ids` in the response lists block IDs that the Notion API could not convert to Markdown (unsupported block types, etc.).
-
-- These blocks are **silently omitted** from the `markdown` field
-- There is no way to retrieve their content via this endpoint
-- notro logs the block IDs as a warning and continues the build
-
-```
-⚠ Page abc123: 2 block(s) could not be rendered to Markdown by the Notion API and were omitted.
-  Block IDs: xxxxxxxx-..., yyyyyyyy-...
-```
-
-### API errors and automatic retries
-
-| Error | Handling |
-|---|---|
-| `429 rate_limited` / `500 internal_server_error` / `503 service_unavailable` | Retry with exponential backoff (1s / 2s / 4s, up to 3 times) |
-| `401 unauthorized` / `403 restricted_resource` / `404 object_not_found` | No retry. Logs a warning and skips the page |
-| Other unexpected errors | Logs a warning and skips the page (build continues) |
-
-## Environment variables
-
-| Variable | Description |
-|---|---|
-| `NOTION_TOKEN` | Notion Internal Integration Token |
-| `NOTION_DATASOURCE_ID` | Notion data source ID |
-
-## API Reference
-
-### `loader(options)`
-
-Astro Content Loader. Pass Notion API `dataSources.query` parameters via `queryParameters`.
-
-### `pageWithMarkdownSchema`
-
-Base Zod schema returned by the loader. Extends `pageObjectResponseSchema` with `markdown: z.string()`. Extend with `.extend()` for custom schemas.
-
-### Property schemas
-
-Use the `notroProperties` shorthand to define database property types in `content.config.ts` (see [`notroProperties`](#notroproperties)).
-
-Individual schemas (e.g. `titlePropertyPageObjectResponseSchema`) remain exported for backwards compatibility.
-
-### Components
-
-| Component | Description |
-|---|---|
-| `NotroContent` | Renders Notion Markdown to HTML. Unstyled by default; pass `components` to customize |
-| `DatabaseCover` | Renders a Notion cover image with optimization |
-| `DatabaseProperty` | Renders a Notion property value by type |
-| `compileMdxCached` | Low-level MDX compile API. Use when building a custom `NotroContent` |
-
-### `notroProperties`
-
-Zod schema shorthands for defining property schemas in `content.config.ts`. Each key maps to a Notion property type.
-
-```typescript
-import { notroProperties } from "notro-loader";
-
-// notroProperties.title       → titlePropertyPageObjectResponseSchema
-// notroProperties.richText    → richTextPropertyPageObjectResponseSchema
-// notroProperties.checkbox    → checkboxPropertyPageObjectResponseSchema
-// notroProperties.multiSelect → multiSelectPropertyPageObjectResponseSchema
-// notroProperties.select      → selectPropertyPageObjectResponseSchema
-// notroProperties.date        → datePropertyPageObjectResponseSchema
-// notroProperties.number      → numberPropertyPageObjectResponseSchema
-// notroProperties.url         → urlPropertyPageObjectResponseSchema
-// notroProperties.email       → emailPropertyPageObjectResponseSchema
-// notroProperties.phoneNumber → phoneNumberPropertyPageObjectResponseSchema
-// notroProperties.files       → filesPropertyPageObjectResponseSchema
-// notroProperties.people      → peoplePropertyPageObjectResponseSchema
-// notroProperties.relation    → relationPropertyPageObjectResponseSchema
-// notroProperties.rollup      → rollupPropertyPageObjectResponseSchema
-// notroProperties.formula     → formulaPropertyPageObjectResponseSchema
-// notroProperties.uniqueId    → uniqueIdPropertyPageObjectResponseSchema
-// notroProperties.status      → statusPropertyPageObjectResponseSchema
-// notroProperties.createdTime → createdTimePropertyPageObjectResponseSchema
-// notroProperties.createdBy   → createdByPropertyPageObjectResponseSchema
-// notroProperties.lastEditedTime → lastEditedTimePropertyPageObjectResponseSchema
-// notroProperties.lastEditedBy   → lastEditedByPropertyPageObjectResponseSchema
-// notroProperties.button      → buttonPropertyPageObjectResponseSchema
-// notroProperties.verification → verificationPropertyPageObjectResponseSchema
-```
-
-### Utilities
-
-| Function | Description |
-|---|---|
-| `getPlainText(property)` | Extracts plain text from Title, Rich Text, Select, Multi-select, Number, URL, Email, Phone, Date, and Unique ID properties |
-| `getMultiSelect(property)` | Returns the options array for a multi-select property. Returns an empty array for unsupported types or `undefined` — no type guard needed |
-| `hasTag(property, tagName)` | Returns whether a multi-select property contains the given tag name. Safe to call without a type guard |
-| `buildLinkToPages(entries, options)` | Builds a `linkToPages` map from collection entries. Pass to `NotroContent` for resolving inter-page Notion links |
-| `colorToCSS(color)` | Converts a Notion color name to an inline CSS style string (for use in custom components) |
+# notro-loader
+
+![npm](https://img.shields.io/npm/v/notro-loader)
+![License: MIT](https://img.shields.io/badge/license-MIT-blue)
+
+An Astro Content Loader library that fetches Notion database content via the [Markdown Content API](https://developers.notion.com/) into [Astro Content Collections](https://docs.astro.build/en/guides/content-collections/).
+
+> [!TIP]
+> This package is part of the [mosugi/notro](https://github.com/mosugi/notro) monorepo. See the blog template at `templates/blog/` for a full working example.
+
+## What NotroContent renders
+
+`NotroContent` compiles Notion markdown into HTML. Each Notion block type maps to a semantic HTML element by default. You can replace any element with your own styled component via the `components` prop.
+
+| Notion block | Default HTML | notro-ui component |
+|---|---|---|
+| Paragraph | `<p>` | `ColoredParagraph` |
+| Heading 1–4 | `<h1>`–`<h4>` | `H1`–`H4` |
+| Callout | `<aside>` | `Callout` |
+| Quote | `<blockquote>` | `Quote` |
+| Toggle | `<details>` + `<summary>` | `Toggle` + `ToggleTitle` |
+| Divider | `<hr>` | — |
+| Code | `<pre>` | — |
+| Image | `<img>` | `ImageBlock` |
+| Video | `<figure>` | `Video` |
+| Audio | `<figure>` | `Audio` |
+| File | `<div>` | `FileBlock` |
+| PDF | `<figure>` | `PdfBlock` |
+| Table | `<table>` | `TableBlock` |
+| Table of contents | `<nav>` | `TableOfContents` |
+| Columns / Column | `<div>` / `<div>` | `Columns` / `Column` |
+| Page link | `<a>` | `PageRef` |
+| Database link | `<a>` | `DatabaseRef` |
+| Empty block | `<div>` | `EmptyBlock` |
+| Inline text (colored/underline) | `<span>` | `StyledSpan` |
+| @mention | `<span>` | `Mention` |
+| Date mention | `<time>` | `MentionDate` |
+
+`notro-ui` is an optional style layer. See [notro-ui](https://github.com/mosugi/notro/tree/main/packages/notro-ui) for details.
+
+## Installation
+
+```sh
+npx astro add notro-loader
+```
+
+This installs the package and automatically adds the `notro()` integration to `astro.config.mjs`.
+
+Alternatively, install manually:
+
+```sh
+npm install notro-loader
+```
+
+## Setup
+
+### 1. `astro.config.mjs`
+
+`astro add notro-loader` configures this automatically. If you installed manually, add:
+
+```js
+import { defineConfig } from "astro/config";
+import { notro } from "notro-loader/integration";
+
+export default defineConfig({
+  integrations: [notro()],
+});
+```
+
+This registers `@astrojs/mdx` with the required plugin pipeline and the Astro JSX renderer that `NotroContent` depends on at runtime.
+
+### 2. `src/content.config.ts`
+
+Define your collection using the `loader` function. Extend `pageWithMarkdownSchema` with your database properties. Use the `notroProperties` shorthand for concise property schemas.
+
+```typescript
+import { defineCollection } from "astro:content";
+import { loader, pageWithMarkdownSchema, notroProperties } from "notro-loader";
+import { z } from "zod";
+
+const posts = defineCollection({
+  loader: loader({
+    queryParameters: {
+      data_source_id: import.meta.env.NOTION_DATASOURCE_ID,
+      filter: {
+        property: "Public",
+        checkbox: { equals: true },
+      },
+    },
+    clientOptions: {
+      auth: import.meta.env.NOTION_TOKEN,
+    },
+  }),
+  schema: pageWithMarkdownSchema.extend({
+    properties: z.object({
+      Name: notroProperties.title,
+      Description: notroProperties.richText,
+      Public: notroProperties.checkbox,
+      Tags: notroProperties.multiSelect,
+      Date: notroProperties.date,
+    }),
+  }),
+});
+
+export const collections = { posts };
+```
+
+### 3. Page component
+
+#### Option A — Headless (no styling)
+
+`NotroContent` from `notro-loader` renders semantic HTML with no classes.
+
+```astro
+---
+import { NotroContent, getPlainText } from "notro-loader";
+
+const { entry } = Astro.props;
+const title = getPlainText(entry.data.properties.Name);
+---
+
+<h1>{title}</h1>
+<NotroContent markdown={entry.data.markdown} />
+```
+
+#### Option B — With notro-ui
+
+Install the styled components once:
+
+```sh
+npx notro-ui init
+```
+
+Then pass the component map to `NotroContent`:
+
+```astro
+---
+import { NotroContent, getPlainText } from "notro-loader";
+import { notroComponents } from "@/components/notro";
+
+const { entry } = Astro.props;
+---
+
+<NotroContent markdown={entry.data.markdown} components={notroComponents} />
+```
+
+Components are copied into `src/components/notro/` so you can edit them directly.
+
+## Markdown processing (remark-notro)
+
+`notro-loader` delegates Notion Markdown preprocessing and directive syntax support to the [`remark-notro`](https://www.npmjs.com/package/remark-notro) package.
+
+`remark-notro` is used inside notro-loader's MDX compile pipeline and is applied automatically when using `NotroContent`.
+
+If you want to use `remark-notro` directly (in a custom unified pipeline or `@mdx-js/mdx`'s `evaluate()`), import it from the `remark-notro` package directly rather than from `notro-loader`.
+
+```ts
+// ✅ Import directly from remark-notro
+import { remarkNfm, preprocessNotionMarkdown } from "remark-notro";
+
+// ❌ Not needed from notro-loader (internal use only)
+// import { remarkNfm } from "notro-loader";
+```
+
+## Notion API limitations
+
+> Reference: [Retrieve a page as Markdown – Notion API](https://developers.notion.com/reference/retrieve-page-markdown)
+
+### Content truncation (`truncated`)
+
+`GET /v1/pages/{page_id}/markdown` truncates content at approximately **20,000 blocks**.
+
+- Detectable via `truncated: true` in the response, but **there is no pagination API to fetch the rest**
+- notro logs a warning when `truncated === true` and continues the build with the available content
+- Workaround: split large Notion pages into multiple smaller pages
+
+```
+⚠ Page abc123: markdown content was truncated by the Notion API (~20,000 block limit).
+  No pagination is available for this endpoint.
+  Consider splitting this Notion page into smaller pages to avoid truncation.
+```
+
+### Unrenderable blocks (`unknown_block_ids`)
+
+`unknown_block_ids` in the response lists block IDs that the Notion API could not convert to Markdown (unsupported block types, etc.).
+
+- These blocks are **silently omitted** from the `markdown` field
+- There is no way to retrieve their content via this endpoint
+- notro logs the block IDs as a warning and continues the build
+
+```
+⚠ Page abc123: 2 block(s) could not be rendered to Markdown by the Notion API and were omitted.
+  Block IDs: xxxxxxxx-..., yyyyyyyy-...
+```
+
+### API errors and automatic retries
+
+| Error | Handling |
+|---|---|
+| `429 rate_limited` / `500 internal_server_error` / `503 service_unavailable` | Retry with exponential backoff (1s / 2s / 4s, up to 3 times) |
+| `401 unauthorized` / `403 restricted_resource` / `404 object_not_found` | No retry. Logs a warning and skips the page |
+| Other unexpected errors | Logs a warning and skips the page (build continues) |
+
+## Environment variables
+
+| Variable | Description |
+|---|---|
+| `NOTION_TOKEN` | Notion Internal Integration Token |
+| `NOTION_DATASOURCE_ID` | Notion data source ID |
+
+## API Reference
+
+### `loader(options)`
+
+Astro Content Loader. Pass Notion API `dataSources.query` parameters via `queryParameters`.
+
+### `pageWithMarkdownSchema`
+
+Base Zod schema returned by the loader. Extends `pageObjectResponseSchema` with `markdown: z.string()`. Extend with `.extend()` for custom schemas.
+
+### Property schemas
+
+Use the `notroProperties` shorthand to define database property types in `content.config.ts` (see [`notroProperties`](#notroproperties)).
+
+Individual schemas (e.g. `titlePropertyPageObjectResponseSchema`) remain exported for backwards compatibility.
+
+### Components
+
+| Component | Description |
+|---|---|
+| `NotroContent` | Renders Notion Markdown to HTML. Unstyled by default; pass `components` to customize |
+| `DatabaseCover` | Renders a Notion cover image with optimization |
+| `DatabaseProperty` | Renders a Notion property value by type |
+| `compileMdxCached` | Low-level MDX compile API. Use when building a custom `NotroContent` |
+
+### `notroProperties`
+
+Zod schema shorthands for defining property schemas in `content.config.ts`. Each key maps to a Notion property type.
+
+```typescript
+import { notroProperties } from "notro-loader";
+
+// notroProperties.title       → titlePropertyPageObjectResponseSchema
+// notroProperties.richText    → richTextPropertyPageObjectResponseSchema
+// notroProperties.checkbox    → checkboxPropertyPageObjectResponseSchema
+// notroProperties.multiSelect → multiSelectPropertyPageObjectResponseSchema
+// notroProperties.select      → selectPropertyPageObjectResponseSchema
+// notroProperties.date        → datePropertyPageObjectResponseSchema
+// notroProperties.number      → numberPropertyPageObjectResponseSchema
+// notroProperties.url         → urlPropertyPageObjectResponseSchema
+// notroProperties.email       → emailPropertyPageObjectResponseSchema
+// notroProperties.phoneNumber → phoneNumberPropertyPageObjectResponseSchema
+// notroProperties.files       → filesPropertyPageObjectResponseSchema
+// notroProperties.people      → peoplePropertyPageObjectResponseSchema
+// notroProperties.relation    → relationPropertyPageObjectResponseSchema
+// notroProperties.rollup      → rollupPropertyPageObjectResponseSchema
+// notroProperties.formula     → formulaPropertyPageObjectResponseSchema
+// notroProperties.uniqueId    → uniqueIdPropertyPageObjectResponseSchema
+// notroProperties.status      → statusPropertyPageObjectResponseSchema
+// notroProperties.createdTime → createdTimePropertyPageObjectResponseSchema
+// notroProperties.createdBy   → createdByPropertyPageObjectResponseSchema
+// notroProperties.lastEditedTime → lastEditedTimePropertyPageObjectResponseSchema
+// notroProperties.lastEditedBy   → lastEditedByPropertyPageObjectResponseSchema
+// notroProperties.button      → buttonPropertyPageObjectResponseSchema
+// notroProperties.verification → verificationPropertyPageObjectResponseSchema
+```
+
+### Utilities
+
+| Function | Description |
+|---|---|
+| `getPlainText(property)` | Extracts plain text from Title, Rich Text, Select, Multi-select, Number, URL, Email, Phone, Date, and Unique ID properties |
+| `getMultiSelect(property)` | Returns the options array for a multi-select property. Returns an empty array for unsupported types or `undefined` — no type guard needed |
+| `hasTag(property, tagName)` | Returns whether a multi-select property contains the given tag name. Safe to call without a type guard |
+| `buildLinkToPages(entries, options)` | Builds a `linkToPages` map from collection entries. Pass to `NotroContent` for resolving inter-page Notion links |
+| `colorToCSS(color)` | Converts a Notion color name to an inline CSS style string (for use in custom components) |