Development

The canonical implementation pipeline is:

.xal source
  -> internal/usecase parser
  -> internal/usecase layout
  -> shared scene and plan calculations
  -> repository encoder

Important package boundaries:

Path	Responsibility
`internal/usecase`	Parser, layout, validation, scene, routing, and plans
`internal/entity`	Shared structures exchanged between layers
`internal/repository`	Filesystem and output-format adapters
`cmd`	CLI entry points
`external`	TypeScript/WASM package and PPTX adapter

Verification commands:

go test ./...
go build ./...
git diff --check

PPTX exporter builds:

make build-wasm
npm run build --workspace=@ryo/xaligo-external

Generated binaries, node_modules, output, mdBook build output, WASM artifacts, and TypeScript dist output should not be committed.

GitHub Pages is published by .github/workflows/pages.yml when documentation changes are merged to main. The workflow builds docs/ with mdBook and deploys docs/book through GitHub Actions Pages.

Keyboard shortcuts

xaligo Documentation

Development