Docs
Technical docs should live with the engine, then flow into the public site cleanly.
Guides owned by the website sit alongside generated engine documentation synced from the `splitframe` repo. That keeps code-adjacent docs versioned with the engine while the public docs surface stays coherent.
Guides
Site-owned onboarding and framing
Engine Docs
Generated from the Splitframe repo
Engine Overview
synced High-level engine layout, current core surfaces, and repository ownership.
Building Splitframe
synced Python package setup and native runtime build commands for the engine.
Testing Splitframe
synced Boundary checks, import smoke coverage, and standalone engine verification.
Migration Notes
synced Extraction status, deferred cleanup work, and compatibility notes for the repo split.