Starship Documentation
This directory contains the documentation for Starship. The documentation is automatically synced to the hyperweb-io/docs.hyperweb.io (opens in a new tab) repository using GitHub Actions.
Directory Structure
docs/
├── advanced/ # Advanced usage and concepts
├── cli/ # CLI documentation
├── config/ # Configuration documentation
├── development/ # Development guides
├── get-started/ # Getting started guides
├── _meta.json # Navigation metadata
├── index.mdx # Main documentation page
└── using-starship.md # Usage guideDocumentation Workflow
- All documentation is written in Markdown (
.md) or MDX (.mdx) format - The documentation is organized into logical sections using directories
- Each section can have its own
_meta.jsonfile to control navigation - When changes are pushed to the
mainbranch, a GitHub Action automatically:- Clones the docs repository
- Syncs the contents of the
docs/directory toexternal-docs/pages/starship/ - Commits and pushes any changes
Learn Directory
The learn/ directory at the root of the repository contains educational content that is synced to the hyperweb-io/hyperweb.io (opens in a new tab) repository. This content is separate from the main documentation and is used for tutorials and learning materials.
Contributing
- Make changes to the documentation in the appropriate directory
- Ensure all new files are properly linked in the navigation (using
_meta.jsonfiles) - Commit and push your changes to the
mainbranch - The GitHub Action will automatically sync your changes to the respective repositories
GitHub Actions
The documentation sync is handled by the .github/workflows/docs.yaml workflow, which:
- Triggers on pushes to the
mainbranch that affect thedocs/orlearn/directories - Uses GitHub tokens to authenticate with the target repositories
- Syncs the documentation using
rsyncto ensure clean updates - Automatically commits and pushes changes to the target repositories
For more details about the workflow, see the workflow file at .github/workflows/docs.yaml.