apunkt/ktx
1
0
Fork 0
mirror of https://github.com/Kaelio/ktx.git synced 2026-06-07 07:55:13 +02:00
Code Issues Projects Releases Packages Wiki Activity
ktx/docs-site/package.json

30 lines
644 B
JSON
Raw Permalink Normal View History

feat(docs): add Fumadocs site workspace
2026-05-11 01:08:31 -07:00
{
"name": "ktx-docs",
"version": "0.0.0",
"private": true,
"type": "module",
"scripts": {
"dev": "next dev",
"build": "next build",
fix(docs-site): add docs index redirect, test, and trim Accept media type Redirect bare /docs to the introduction page with proper metadata resolution. Add a test for the redirect. Trim the media type in the Accept header parser so whitespace around semicolons does not break markdown content negotiation. Add a test script to package.json. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-05-11 20:37:28 -07:00
"start": "next start",
"test": "node --test tests/*.test.mjs"
feat(docs): add Fumadocs site workspace
2026-05-11 01:08:31 -07:00
},
"dependencies": {
feat(docs): visualize KTX ingestion with ReactFlow diagram (#133) * feat(docs): visualize KTX ingestion with ReactFlow diagram Reframe the introduction around the two user-facing ingestion outputs (wiki and executable semantic layer) and replace the static product-mechanics card flow with a ReactFlow diagram: sources fan into a sequential ingest pipeline, which forks into wiki and semantic-layer outputs connected by a bidirectional "references" edge. Drop the .ktx/raw-sources internal-implementation rows from the intro table and update the content test to guard the new copy. * Improve KTX docs introduction * feat(docs): animate ingestion flow with running dots Replace static smoothstep edges in the introduction page's ingestion diagram with a custom animated edge that runs glowing cyan dots along each path, conveying the source → stage → output flow. Dot duration scales with path length and is hidden under prefers-reduced-motion. * feat(docs): route ingestion atoms through full source→output journey Replace per-edge dots with full-journey particles: each atom is born at a source, threads the entire stage chain, and lands at either the wiki or semantic layer. Particles are tinted by their source's accent so the origin is legible. Each source produces exactly 2 atoms (8 total) to guarantee every input is visibly active, while the destination and begin offsets are randomized per page load. Particles populate on client mount to avoid hydration mismatch, and are hidden under prefers-reduced-motion.
2026-05-18 17:41:37 +02:00
"@xyflow/react": "^12.10.2",
chore(deps): refresh workspace dependencies (#43) * chore(deps): refresh workspace dependencies * Fix pnpm artifact smoke build approvals
2026-05-13 01:15:35 +02:00
"fumadocs-core": "16.8.10",
"fumadocs-mdx": "15.0.4",
"fumadocs-ui": "16.8.10",
"next": "^16",
feat(docs): add Fumadocs site workspace
2026-05-11 01:08:31 -07:00
"react": "19.2.6",
"react-dom": "19.2.6"
},
"devDependencies": {
feat(docs): visualize KTX ingestion with ReactFlow diagram (#133) * feat(docs): visualize KTX ingestion with ReactFlow diagram Reframe the introduction around the two user-facing ingestion outputs (wiki and executable semantic layer) and replace the static product-mechanics card flow with a ReactFlow diagram: sources fan into a sequential ingest pipeline, which forks into wiki and semantic-layer outputs connected by a bidirectional "references" edge. Drop the .ktx/raw-sources internal-implementation rows from the intro table and update the content test to guard the new copy. * Improve KTX docs introduction * feat(docs): animate ingestion flow with running dots Replace static smoothstep edges in the introduction page's ingestion diagram with a custom animated edge that runs glowing cyan dots along each path, conveying the source → stage → output flow. Dot duration scales with path length and is hidden under prefers-reduced-motion. * feat(docs): route ingestion atoms through full source→output journey Replace per-edge dots with full-journey particles: each atom is born at a source, threads the entire stage chain, and lands at either the wiki or semantic layer. Particles are tinted by their source's accent so the origin is legible. Each source produces exactly 2 atoms (8 total) to guarantee every input is visibly active, while the destination and begin offsets are randomized per page load. Particles populate on client mount to avoid hydration mismatch, and are hidden under prefers-reduced-motion.
2026-05-18 17:41:37 +02:00
"@tailwindcss/postcss": "^4",
chore(deps): refresh workspace dependencies (#43) * chore(deps): refresh workspace dependencies * Fix pnpm artifact smoke build approvals
2026-05-13 01:15:35 +02:00
"@types/node": "^25.7.0",
feat(docs): add Fumadocs site workspace
2026-05-11 01:08:31 -07:00
"@types/react": "^19",
"@types/react-dom": "^19",
feat(docs): visualize KTX ingestion with ReactFlow diagram (#133) * feat(docs): visualize KTX ingestion with ReactFlow diagram Reframe the introduction around the two user-facing ingestion outputs (wiki and executable semantic layer) and replace the static product-mechanics card flow with a ReactFlow diagram: sources fan into a sequential ingest pipeline, which forks into wiki and semantic-layer outputs connected by a bidirectional "references" edge. Drop the .ktx/raw-sources internal-implementation rows from the intro table and update the content test to guard the new copy. * Improve KTX docs introduction * feat(docs): animate ingestion flow with running dots Replace static smoothstep edges in the introduction page's ingestion diagram with a custom animated edge that runs glowing cyan dots along each path, conveying the source → stage → output flow. Dot duration scales with path length and is hidden under prefers-reduced-motion. * feat(docs): route ingestion atoms through full source→output journey Replace per-edge dots with full-journey particles: each atom is born at a source, threads the entire stage chain, and lands at either the wiki or semantic layer. Particles are tinted by their source's accent so the origin is legible. Each source produces exactly 2 atoms (8 total) to guarantee every input is visibly active, while the destination and begin offsets are randomized per page load. Particles populate on client mount to avoid hydration mismatch, and are hidden under prefers-reduced-motion.
2026-05-18 17:41:37 +02:00
"tailwindcss": "^4",
"typescript": "^6.0"
feat(docs): add Fumadocs site workspace
2026-05-11 01:08:31 -07:00
}
}
Reference in a new issue Copy permalink