@clidey/dory 1.9.0 → 1.10.0

package/vite.config.ssr.ts

@@ -17,7 +17,7 @@ export default defineConfig({
     mdx(getMdxConfig(false)),
   ],
   resolve: {
-    dedupe: ['preact', 'preact/compat', 'preact/hooks', 'preact/jsx-runtime', 'preact/compat/jsx-runtime'],
+    dedupe: ['recharts', 'preact', 'preact/compat', 'preact/hooks', 'preact/jsx-runtime', 'preact/compat/jsx-runtime'],
     alias: {
       react: 'preact/compat',
       'react-dom': 'preact/compat',

package/vite.config.ts

@@ -41,7 +41,7 @@ export default defineConfig(({ command }) => ({
     prerender(),
   ],
   resolve: {
-    dedupe: ['preact', 'preact/compat', 'preact/hooks', 'preact/jsx-runtime', 'preact/compat/jsx-runtime'],
+    dedupe: ['recharts', 'preact', 'preact/compat', 'preact/hooks', 'preact/jsx-runtime', 'preact/compat/jsx-runtime'],
     alias: {
       react: 'preact/compat',
       'react-dom': 'preact/compat',

package/docs/getting-started/whodb-ee-apps.mdx

@@ -1,122 +0,0 @@
----
-title: 'WhoDB EE apps'
-description: 'Write MDX documentation in a WhoDB EE app and show it inside the app host.'
----
-
-# Document WhoDB EE apps
-
-WhoDB EE can keep documentation with the app it describes. Add MDX files under the app's `docs/` directory. App editors can write and preview them in the **Docs** tab. When the app is published, WhoDB publishes the MDX files with the app version and shows them in the app host's **Help** panel. There is no separate Dory site or deployment to manage.
-
-The Dory renderer is bundled with WhoDB as JavaScript and CSS. It runs inside a sandboxed frame, separate from the WhoDB host and the app runner. The host gives it a list of allowed pages; Dory requests an MDX file when the reader opens that page. WhoDB checks each request against the reader's authorized app documentation. The app runner does not receive documentation source or WhoDB credentials.
-
-## Add pages
-
-Start with `docs/index.mdx`. Give each page a title in frontmatter and use ordinary MDX for its body:
-
-```mdx docs/index.mdx
----
-title: Inventory app
-description: How to use the inventory workspace.
----
-
-# Inventory app
-
-Use this workspace to review stock levels and update reorder plans.
-
-[View reports](/reports)
-```
-
-Add `docs/reports.mdx` for the `/reports` link. Subfolders work too, such as `docs/admin/permissions.mdx`. Pages are discovered from the files; an app does not need a `dory.json`. Keep linked routes within the app's documentation pages.
-
-The embedded viewer renders Markdown, Dory's layout and callout components, Mermaid diagrams, and KaTeX math. API and WebSocket playgrounds, remote `Source` content, and `Specimen` demos are unavailable in the app sandbox. HTTPS image URLs work; storing binary image files alongside the app's MDX is not yet supported.
-
-The embedded **Ask Dory** panel searches only the app documentation pages already authorized for the reader's selected language. It returns an excerpt and links to the matching source pages. This local mode makes no model request and does not produce a generated AI answer. Dory's standalone documentation chat uses a separate server-side model endpoint; the embedded viewer cannot call that endpoint from its sandbox.
-
-In WhoDB EE, open the app editor and select **Docs**. Create a page, edit its MDX, preview it, and save the draft. Publishing the app makes the saved pages available to readers with access to that app. Draft edits do not change the published docs until the next app publish.
-
-## Customize the docs site
-
-The Docs tab can preview the app's site name, logo, colors, fonts, and navigation alongside its MDX. These settings live in the app's `app.json` under `documentation.site`, so the app and its docs can be published together. The site settings are optional; an app with only MDX pages still has a usable docs layout.
-
-```json app.json
-{
-  "documentation": {
-    "site": {
-      "name": "Inventory docs",
-      "version": "1.0",
-      "logo": {
-        "light": "https://example.com/inventory-logo-light.svg",
-        "dark": "https://example.com/inventory-logo-dark.svg"
-      },
-      "colors": { "primary": "#528ff4" },
-      "fonts": { "family": "Hanken Grotesk", "heading": { "family": "Bricolage Grotesque" } },
-      "navigation": {
-        "tabs": [{
-          "tab": "Guides",
-          "groups": [{ "group": "Getting started", "pages": ["index", "reports"] }]
-        }]
-      }
-    }
-  }
-}
-```
-
-Navigation page names are relative to `docs/` and omit `.mdx`. The viewer includes only pages that exist in the selected language. You can also set `title`, `colors.light` and `colors.dark`, `theme.mode` (`light`, `dark`, or `system`), `theme.radius`, and mono font family. Logos must use HTTPS URLs or image data URLs; local binary assets are not yet bundled with the app documentation. The embedded renderer uses the site's font family if it is already available in the browser; it does not fetch a custom font stylesheet from the config.
-
-The Docs tab saves edits as a draft. Readers see the published version of `documentation.site` and its MDX files after the next app publish.
-
-## Keep docs beside a local app
-
-The WhoDB CLI includes `docs/*.mdx` when it reads an app folder. This lets you review documentation changes alongside app code and publish them together:
-
-```text
-inventory-app/
-├── app.json
-├── docs/
-│   ├── index.mdx
-│   └── reports.mdx
-└── pages/
-    └── main/
-```
-
-```bash
-whodb apps publish ./inventory-app --draft --org <org> --project <project>
-whodb apps publish ./inventory-app --message "Inventory docs" --org <org> --project <project>
-```
-
-The first command syncs the editable draft. The second creates a published app version, including its MDX files. See the WhoDB CLI app workflow for app creation, verification, and publication options.
-
-## Open the right page from an app screen
-
-The Help panel starts at `docs/index.mdx`. To select a page based on the current app screen, add a route map to `app.json`:
-
-```json app.json
-{
-  "documentation": {
-    "pages": {
-      "main": "/",
-      "reports": "/reports"
-    }
-  }
-}
-```
-
-The map keys are app page names. The values select MDX pages under `docs/`; `/reports` selects `docs/reports.mdx`. Missing or invalid mappings fall back to the index or first available page. Readers can also share the app's URL with `?docs=reports` to open a specific docs page in its Help panel.
-
-Documentation access follows the app's permissions. App editors can preview draft MDX; app viewers see the published snapshot. WhoDB loads docs through a separate authorized read path, so app code cannot read them through the app runtime.
-
-## Translate app documentation
-
-Keep the default language at `docs/index.mdx` and put authored translations under a language directory with the same page keys. For example, add `docs/fr/index.mdx` and `docs/fr/reports.mdx` for French. The Docs editor has a language selector so authors can edit and preview each set of pages. WhoDB's `fr_FR` interface language selects `docs/fr/`; English (US) uses the root `docs/` pages. English (UK) uses `docs/en-gb/`, and Chinese variants use `docs/zh-cn/` or `docs/zh-tw/`.
-
-Each translated MDX file owns its title and body. WhoDB does not translate page content automatically. If an app has no pages for the reader's language, Help shows the default-language pages as English. If a language has some translated pages, its navigation shows only those authored pages; a missing matching page opens the first available page in that language. The iframe sets its HTML language and text direction from the chosen docs language, including right-to-left languages.
-
-To translate navigation labels too, add `documentation.site.i18n.locales` entries with a language `code` and a `navigation` object in the same tab/group/page shape as the default navigation. Page names stay the same across languages; translated MDX titles and the locale's tab and group labels are shown to readers.
-
-A link with `?docs=reports` follows the reader's selected language. To share a specific translation, use an explicit path such as `?docs=fr/reports`. The MCP `whodb_app_docs` tool can read a translated page with `page: "docs/fr/reports.mdx"` or that explicit page link. Its default URL lookup reads default-language content when no language is specified.
-
-## Use the docs from an agent
-
-An agent with authorized WhoDB access can use the WhoDB MCP server's read-only `whodb_app_docs` tool. Give it a published app link as `url` to list the available MDX pages. A link with `?docs=reports` reads that page directly. The tool also accepts organization, project, and app IDs plus an optional `page` such as `docs/reports.mdx`. It serves published content and applies WhoDB app permissions.
-
-MCP clients need a one-time connection to the same WhoDB instance's `/mcp` endpoint. A private app link by itself cannot install a tool in Claude or Codex; after connection, the agent can use that one app link to discover and read its documentation without a separate Dory deployment.