All documentation
Every page below is generated from the repository's docs/ directory at build time, so this site cannot drift from the documentation it renders.
Guides
- Getting started with unify: unify turns a folder of plain HTML (and Markdown) into a finished site with shared navs, headers, and footers — no templating language, no JavaScript framework, no configuration.
- Authoring a unify site — the complete rules: unify composes plain HTML at build time.
- Integrating compiled components: the compile-to-asset pattern: The recipe for using a component framework — Svelte here, but the shape is the
- Docker Usage Guide: This repository ships one container image: the unify CLI, built from docker/Dockerfile.
Reference
- unify CLI reference: This page lists every command, every option, and every exit code — there are no others.
- unify — Product Specification: This document records the shipped product contract — the composition core, plus the production-and-discovery layer built on it — with §6 retained as that layer's design record: what unify is, who it serves, what exists now, and which bou…
- unify — Conformance Specification: The implementer-grade reference.
Project
- unify — Testing Strategy: This document is the testing contract.
- CI/CD workflows: What actually runs, and what each job is allowed to mean.
- Ratification — what the agent-experiment rounds changed: This document is the narrative and the evidence behind docs/ratification-protocol.md.
- Ratification: dialling in the rules with micro-experiments: docs/authoring-rules.md claims to be the complete authoring surface in 60 lines — learnable in one sitting, or pasteable into a prompt.
- unify — Test-Suite and Codebase Migration Plan (v0.6 → v0.7.0): The path from the current 240-file tests/ tree and the v0.6 codebase to the suite defined in docs/testing-strategy.md.