How Starport works
Starport splits the work on a docs site between Promptless and your team. Promptless sets up and maintains the tooling: the site framework, the build and deploy pipeline, and the content updates that track your product. Your team owns the content, the Git repository it lives in, and the hosting account the site deploys to. This page covers who runs each part and what your docs need before they can run on Starport.
Starport follows the docs-as-code model: your pages live as source files in a Git repository, versioned and reviewed like code. For the settings you change yourself, see Configure your Starport site. For the move onto Starport, see Migrate to Starport.
Use cases
Section titled “Use cases”| Your situation | What Starport means for you |
|---|---|
| You’re deciding whether your team can run a docs site without a dedicated docs engineer. | Promptless sets up the build and deploy pipeline and keeps the site’s supporting features current. Your team writes and reviews content. |
| Your security or platform team asks who controls the repository, the hosting, and what ships. | Your team owns the repository and the hosting account, and approves every change Promptless proposes. |
| Your docs live in a hosted editor today. | The content moves into a Git repository as Markdown or MDX first. Promptless handles that move as part of the migration. |
Who runs what
Section titled “Who runs what”Each part of a Starport site has an owner:
| Part of the site | Who runs it | What happens |
|---|---|---|
| Site framework | Promptless | Promptless stands up your site on the Starport template, built on Astro Starlight. |
| Build and deploy pipeline | Promptless sets it up, and it runs in CI | A merged change builds and publishes through your hosting provider, with no manual steps. |
| Hosting | Your team, with setup help from Promptless | The site deploys to a provider you choose, such as Vercel, on an account you own. |
| Supporting features | Promptless | Promptless keeps search, redirects, and the agent-ready features, such as llms.txt and the docs MCP server, current. |
| Content updates | Promptless proposes, your team approves | Promptless detects when your product changes and opens documentation pull requests against your repository for your team to review. |
| Site configuration | Your team | After onboarding, you tune the site through its configuration files. |
What you own
Section titled “What you own”Your content lives in a Git repository your team owns and controls. Promptless proposes edits the way a teammate would, by branching, changing files, and opening a pull request you review. Because the repository is yours, you keep its full history and access control, and you can edit content directly at any time.
For the docs-as-code fundamentals and why Promptless builds on them, see Understand docs-as-code. For how Promptless maintains content over time, see Keep your Starport docs current.
Prerequisites
Section titled “Prerequisites”To run on Starport, your documentation needs a docs-as-code footing:
- A Git repository your team owns, which holds your content as source files.
- Content authored in Markdown or MDX, the formats Starport builds from.
If your docs live in a hosted editor that stores content in a proprietary database, the move to docs-as-code comes first. Promptless handles that move as part of the managed migration.