Keep your Starport docs current

After you migrate to Starport, Promptless keeps your content current as your product changes. Your docs live in a repository Promptless watches, so the same loop that keeps your docs current elsewhere runs on your site. A product change triggers Promptless, which drafts the documentation update and opens a pull request for your team to review.

How Promptless keeps your content current

Promptless watches the sources your team already uses, such as merged pull requests and support conversations. When one of them signals a product change, Promptless drafts the documentation update. It opens the update as a pull request against your repository for your team to review and merge.

Because your Starport content is Markdown and MDX in a Git repository, Promptless edits it the way a teammate would. It branches, changes files, and opens a reviewable change. You stay in control of what publishes.

You review each suggestion before it publishes: approve it, request edits, or decline it. A wrong or unneeded draft is caught in that review. When something needs attention, ask Promptless directly in Slack or Microsoft Teams.

Note

Every update arrives as a reviewable pull request. Your team approves and merges each one, so nothing publishes without your review.

How this ties to the core Promptless product

The loop on your Starport site is the same one Promptless runs across every collection. A trigger activates on an event, Promptless gathers context, produces a suggestion, and opens a pull request for review.

For the full model, see How Promptless works. For the events that start the loop, see Triggers.