stokeDocumentation

Start here

Overview

Stoke brings Kiln and Bellows into one workspace for local GitHub Actions feedback. Bellows plans and runs the workflows; Kiln supplies the runner environment.

Clone Stoke and set up the pair. Each tool keeps its own source, history and releases.

Open documentation →
↑ ↓ navigate↵ open
On this page

Workspace

Architecture

Stoke owns workspace assembly, shared documentation, the landing site and the family brand. Bellows owns workflow planning and orchestration; Kiln owns the container environment. The tools retain independent repositories and releases.

flowchart LR
    Stoke[Stoke workspace] --> BellowsSource[Bellows checkout]
    Stoke --> KilnSource[Kiln checkout]
    Project[Your project workflows] --> Bellows[Bellows CLI]
    Bellows --> Act[act]
    Act --> Docker[Docker daemon]
    Docker --> Kiln[Kiln runner image]
    Project --> Hosted[Hosted CI and merge enforcement]

Cloning sources is separate from installing the CLI or pulling an image. scripts/fleet.sh reads a manifest and validates existing checkouts before touching them. There are no Git submodules or combined product releases.

The landing site follows Harbor's layout and interaction patterns. Its workflow demo is illustrative and executes no commands. Documentation reuses Convrt's shell, search, mobile navigation and page actions with Stoke's identity. The build renders Markdown into static HTML at each documentation route and bundles a React client for interactions. No server or runtime API is required.

The brand library reuses the member palettes, fonts and unmodified member logos. Stoke's angular flame joins Kiln's gold and Bellows' ember in one family mark. Owned vector and raster assets are rebuilt by scripts/build-brand.ts.

Continue readingTroubleshooting →
Edit on GitHub
Open in chat

Opens with this page’s documentation in the prompt.