~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

A guide shows how to deploy a repository's site

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:guide/sites

What changes

A new guide, docs/guide/sites.md, shows how to deploy a repository's site: with knotless site, built for its /<repo>/ base path, as a single-page app with --fallback, with a 404 page, on every push with the chadtmiller.com/steps/site shared step and a SITE_PASSWORD secret, and how to see what is live and take it down. It is in the docs index and the docs site's sidebar, and the pages design page links to it from Deploying on a push.

Why

The design page and the CLI reference said what the fallback does, but nothing showed someone how to deploy a site or a single-page app, and the shared step was named only in the steps repository.

🤖 Generated with Claude Code

Approved

This adds docs/guide/sites.md and links it from the docs index, the docs-site sidebar and the pages design page. I checked the guide's claims against docs/reference/cli.md, docs/reference/workflows.md and the site step in the steps repo, and they match. That covers the knotless site flags and output, the 1–2,000 file limit, the private-repo limit, and secret … set --ref. It also covers the step's inputs (dir, fallback, not-found, repo, appview), the SITE_PASSWORD secret, and the uses format chadtmiller.com/steps/site@1.

The change touches no client code, so it needs no change file. I found nothing that must change.

I didn't check the subdomain rule (hyphens doubled, dots turned into -) or the fallback rule (text/html or no extension) against the code. I also didn't read the check results. The docs check covers the new links and anchors, such as #deploy-on-every-push and #shared-steps.

Merged as 641b515