Add operation setup wizard to the landing page - #51
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
@copilot refine, make it delightful, show screenshots |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Refined in While capturing them I found a real bug: the operation list was read with Polish: eyebrow label and accent glow on the panel, hover lift and selected-state check marks on the cards, a prompt toolbar with a live "operation with agent" summary, and a transient "Copied" state on the button. Default state (dark): Light theme: Custom operation, which routes the prompt through the packaged Mobile (430px): The images were committed in |




Adds a
gh-aw-wizard-style wizard to the landing page, rendered directly after the dispatch diagram: pick an operation, pick a coding agent, copy a prompt that creates the control repository and runs the operation.Changes
docs/components/OpsWizard.astro(new) — three-step wizard:aw.yml(name + description), so the list tracks the catalog instead of a hard-coded copy. A Custom operation option takes a free-form description and routes the prompt through the packagedcreate-ops-packageskill.engine:value in the prompt.noscriptfallback pointing at the Quickstart.docs/components/HierarchyHero.astro— renders<OpsWizard />after the diagram figure. The hero override is only used by the splash landing page, anddocs/README.mdis plain Markdown, so this avoids pulling in MDX.The generated prompt encodes the repository's safety defaults — private control plane,
stagedfirst run, package rollout variables capped at one repository, no hand-edits to.lock.yml:Notes for review: package slugs map directly to the
CENTRAL_AGENTIC_OPS_<PACKAGE>_MODE/_MAX_REPOSvariables used by the workflows, and the catalog ref is pinned tomainin the prompt — worth deciding whether it should point at a release tag instead.