Skip to content

docs.publish

Run the deploy phase on the built site, then publish it through the seam.

The deploy phase's steps run first, the ones the listed extensions add in their [for.docs] tables, each drawing a page from what the merge left behind; a failing step stops the publish, naming the step. Each declared coverage report's tree then goes into the site (refresh_site_coverage). Then the contract's seam: pages is the forge workflow's own act and skips here; container pushes the site image to the forge registry; ssh tars the site to the configured host, skipping when unconfigured; none skips by declaration.

fm docs.publish

Example

$ fm docs.publish