Overview
This task migrates end-user documentation from the shipwright-io/cli repository to the website repository as described in SHIP-0041.
Description
Identify end-user documentation in the shipwright-io/cli repository, migrate relevant content to the website repository in appropriate sections (Concepts, How To, or Reference), and remove in-tree docs (replacing with links to website).
Only end-user documentation relevant to evaluators, developers, or administrators should be migrated. Contributor documentation and internal development docs should remain in the cli repository.
Acceptance Criteria
Dependencies
- Blocks: Configure Hugo aliases (Issue 10)
- Blocked by: Audit and categorize existing documentation (Issue 3)
Technical Notes
- Review
shipwright-io/cli repository for documentation directories (typically docs/)
- Identify which documentation is end-user facing vs. contributor/internal
- Migrate content to appropriate section in website repository
- Create PR in cli repository to remove migrated documentation
- Replace removed docs with README or index file that links to website
- Coordinate with cli repository maintainers for review
Generated-by: Cursor
Overview
This task migrates end-user documentation from the
shipwright-io/clirepository to the website repository as described in SHIP-0041.Description
Identify end-user documentation in the
shipwright-io/clirepository, migrate relevant content to the website repository in appropriate sections (Concepts, How To, or Reference), and remove in-tree docs (replacing with links to website).Only end-user documentation relevant to evaluators, developers, or administrators should be migrated. Contributor documentation and internal development docs should remain in the cli repository.
Acceptance Criteria
Dependencies
Technical Notes
shipwright-io/clirepository for documentation directories (typicallydocs/)Generated-by: Cursor