Kinocut site is the open-source static website for Kinocut, a video editing toolkit. It contains the pages, styles, scripts, tests, and machine-readable files published at kinocut.dev.
TL;DR: clone from Forgejo, serve the static files, run the tests, and submit site changes to Forgejo. The Kinocut product repository owns the Python package, CLI, MCP implementation, and releases.
Kinocut site is a bilingual static documentation and product website. KyaniteLabs Forgejo is the canonical site source, GitHub is the public site mirror, GitHub hosts the canonical Kinocut product code, and kinocut.dev is the separately deployed Netlify production site.
| Surface | Role | Authority |
|---|---|---|
| Forgejo site | Website source | Canonical; site changes land here first |
| GitHub site | Website source | Public collaboration mirror |
| GitHub product | Kinocut implementation | Canonical product code and releases |
| kinocut.dev | Published website | Netlify production, deployed and verified separately |
A source merge does not prove a production deployment, and a source file does not prove that its production route is live.
- People evaluating Kinocut can start with the homepage, installation guide, tutorial, and FAQ.
- Developers and creators can read the integration guide, prompt guide, and receipt guide.
- Site contributors can use the source map, local server, tests, and design contract below.
- Deployment operators can validate source before an owner-approved Netlify deployment and live check.
The site has no application build step. Its pages and assets are committed directly.
| Path | Purpose |
|---|---|
index.html |
English homepage and primary surface |
es.html, es-content.html |
Spanish pages |
install.html, tutorial.html, faq.html |
Core documentation |
contribute.html |
Contribution guidance |
css/ |
Design tokens, homepage styles, and documentation styles |
js/site.js |
Shared browser behavior |
tests/ |
Public-claim and agent-discovery tests |
llms.txt |
Plain-text guide to public resources |
openapi.json |
Machine-readable agent-surface description |
docs/agent-api.md |
Human-readable agent-surface documentation |
netlify.toml |
Netlify routing and edge-function configuration |
netlify/edge-functions/agent-discovery.js |
Agent-discovery edge-function source |
Unlike this static site, product implementation and releases live in the Kinocut product repository.
git clone https://git.kyanitelabs.tech/KyaniteLabs/kinocut-site.git
cd kinocut-site
python3 -m http.server 8000Open http://localhost:8000/. The local server previews static assets; it does not reproduce Netlify edge behavior or prove a production deployment.
npm test requires Node.js, npm, and global Web Crypto (crypto.randomUUID). The suite was tested with Node.js v26.7.0; this repository does not declare a fixed Node version.
npm test
./scripts/verify-primary-surface.shnpm test checks public claims and agent-discovery behavior. verify-primary-surface.sh checks the local homepage and design markers. Visual changes still need rendered browser review. Production behavior must be checked after deployment.
After a README change, confirm that the canonical Forgejo README and GitHub mirror match. Keep repository tests, browser review, and production verification as separate checks.
llms.txt, openapi.json, docs/agent-api.md, and the edge-function source document the intended discovery surfaces. Confirm production URLs directly when work depends on deployed routing, headers, or responses.
Read AGENTS.md for repository rules and DESIGN-SYSTEM.md for the visual contract. Review tests/ before changing public claims or discovery behavior. Product contributions belong in the Kinocut product repository.
Site changes follow a Forgejo-first workflow: branch from the current Forgejo tip, keep the patch focused, run the local checks, and submit the change there. GitHub mirrors the site repository.
Netlify deployment is owner-controlled and separate from merging source. When a deployment is approved, the repository command is:
npx netlify deploy --prod --dir .Verify the live homepage and changed claims after deployment.
No. This is the static website repository. The product repository contains the package, CLI, MCP server, and release history.
The Forgejo site repository is canonical. The GitHub site repository is its public collaboration mirror.
No. A merge establishes site source history. Netlify deployment and live verification are separate.
Check versions and implementation claims against the canonical product repository and published artifacts. Then verify the intended claim in site source and on the live page.
This site is licensed under Apache-2.0. See LICENSE.