@odla-ai/blog 0.0.3 → 0.0.5

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Cory Ondrejka
+
+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,8 +1,13 @@
 # @odla-ai/blog
 
+> ⚠️ **Early access — pre-1.0.** Agents work from bounded runbooks; humans
+> approve credentials, production changes, releases, and merges. APIs and exact
+> package availability can change. Review the documented guarantees and
+> limitations; this software is MIT-licensed and provided without warranty.
+
 Minimal-dependency, static-first blogging platform. A site is a directory of
 markdown plus one JSON config; `build()` emits a fully static site that works on
-GitHub Pages or Cloudflare. When [odla-db](https://github.com/odla-ai/odla-db) is
+GitHub Pages or Cloudflare. When [odla-db](https://www.npmjs.com/package/@odla-ai/db) is
 configured, interactive features (sign-in, comments, likes) light up as a
 progressive layer — the static site never depends on it.
 
@@ -38,19 +43,21 @@ Pick one with `"theme": "salt"` in `blog.config.json`. Themes ship in the
 design system); every built site also gets ui's class-scoped component layer
 (`assets/odla-ui.css` — buttons, form fields, cards, …) theme-matched via the
 theme's `ui.css` token aliases. Override any theme file by placing a
-same-named file in your site's `theme/` directory. Preview all four against
-the example site with `npm run preview` (from the monorepo root).
+same-named file in your site's `theme/` directory. Build your site with the
+package API and preview the emitted static directory with your usual local
+static server.
 
 ## Deploy (Cloudflare)
 
 `build()` emits a plain static directory; serve it from a Worker assets
 binding — `{ "assets": { "directory": "./dist-site" } }` in `wrangler.jsonc`,
 build before every deploy. Add a `main` worker script only when you want
-`/api/*` routes next to the static site (see `examples/demo-app` in the
-odla-ai monorepo for the full pattern, including odla-db + o11y wiring).
+`/api/*` routes next to the static site; the public platform manual describes
+how to combine the assets binding with odla-db and o11y.
 
 ## Status
 
-Early. The build pipeline, themes, and example site work; CLI (`init`/`new`/`dev`/
-`check`), feeds, search, deploy scaffolding, and the odla-db islands are in
-progress — see `PLAN.md` at the repo root.
+Early. The build pipeline and themes work; CLI (`init`/`new`/`dev`/`check`),
+feeds, search, deploy scaffolding, and the odla-db islands are in progress.
+Track supported behavior in the public docs and the package's shipped
+`llms.txt` rather than relying on internal planning files.

package/llms.txt

@@ -1,4 +1,11 @@
-# @odla-ai/blog — agent reference (llms.txt)
+# @odla-ai/blog — LLM context
+
+> Minimal-dependency, static-first blogging platform. Files in, site out; odla-db lights up interactivity when configured.
+
+> EARLY ACCESS — pre-1.0. Agents work from bounded runbooks; humans approve
+> credentials, production changes, releases, and merges. APIs and exact package
+> availability can change. Review the documented guarantees and limitations;
+> this software is MIT-licensed and provided without warranty.
 
 This file ships in the npm package so an agent working in a *site* repo can
 operate the platform from `node_modules/@odla-ai/blog/llms.txt` alone. The
@@ -172,7 +179,7 @@ to the theme's CSS (after the `ui.css` aliases). Post URLs live under
 
 The output is a plain static directory — serve it from a Worker's assets
 binding (this is what `blog init --deploy cloudflare` will generate; a
-working example lives at `examples/demo-app` in the odla-ai monorepo):
+the public platform manual documents the same Worker + assets composition):
 
 ```js
 // build-site.mjs — run before every deploy

package/package.json

@@ -1,9 +1,15 @@
 {
   "name": "@odla-ai/blog",
-  "version": "0.0.3",
+  "version": "0.0.5",
   "description": "Minimal-dependency, static-first blogging platform. Files in, site out; odla-db lights up interactivity when configured.",
   "type": "module",
   "license": "MIT",
+  "homepage": "https://odla.ai/docs/packages/blog",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/cory/odla-ai.git",
+    "directory": "packages/blog"
+  },
   "exports": {
     ".": "./src/index.js"
   },
@@ -14,17 +20,21 @@
     "config.schema.json"
   ],
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "provenance": false
   },
   "engines": {
     "node": ">=20"
   },
   "scripts": {
     "preview": "node scripts/preview.mjs",
-    "test": "node --test --test-reporter=spec"
+    "test": "node --test --test-reporter=spec",
+    "coverage": "c8 --src=src --reporter=text --reporter=html node --test",
+    "gen:llms": "node ../../scripts/gen-llms.mjs",
+    "prepublishOnly": "npm run gen:llms && npm test"
   },
   "dependencies": {
-    "@odla-ai/ui": "^0.1.0",
+    "@odla-ai/ui": "^0.2.2",
     "highlight.js": "^11.11.0",
     "marked": "^16.0.0",
     "yaml": "^2.8.0"

package/src/markdown.js

@@ -31,12 +31,21 @@ export function slugify(text) {
 // is synchronous, so module-level state is safe.
 let footnoteNumbers = new Map(); // id → number, in first-reference order
 let footnoteBodies = new Map(); // id → rendered inline HTML
+let headingIds = new Map(); // base slug → occurrences in this document
+
+function uniqueHeadingId(text) {
+  const base = slugify(text);
+  const count = (headingIds.get(base) ?? 0) + 1;
+  headingIds.set(base, count);
+  return count === 1 ? base : `${base}-${count}`;
+}
 
 const footnotes = {
   hooks: {
     preprocess(markdown) {
       footnoteNumbers = new Map();
       footnoteBodies = new Map();
+      headingIds = new Map();
       // Number by first reference (definitions like "[^id]:" excluded).
       for (const match of markdown.matchAll(/\[\^([^\]\s]+)\](?!:)/g)) {
         if (!footnoteNumbers.has(match[1])) {
@@ -135,7 +144,7 @@ const marked = new Marked(
       },
       heading({ tokens, depth }) {
         const text = this.parser.parseInline(tokens);
-        const id = slugify(text);
+        const id = uniqueHeadingId(text);
         return `<h${depth} id="${id}">${text}</h${depth}>\n`;
       },
     },