User guide

If you build fast — shipping features with AI pair-programming, iterating in public, moving from idea to working product in days — the docs and marketing side almost always lags behind. You know the feeling: the code works, but there’s no README worth reading, no positioning, no launch post, and by the time you get to it the release has already gone out quietly. This portal exists to close that gap without slowing you down: it tells you exactly what’s missing for a release, and drafts the first pass of it for you, so shipping fast and shipping well aren’t in tension anymore.

1. Click Sign in with Google on the homepage.
2. Choose your Google account and approve access.
3. You’ll land on Your projects.

During testing, only pre-approved Google accounts can sign in. If you hit an “Access blocked” screen, ask whoever set up the portal to add your email as a test user.

1. Type a name into New project name.
2. Click Create.
3. Click the project card to open it.

1. In Google Drive, open or create the folder you want to use, using the same account you signed in with.
2. Copy its URL from the address bar (drive.google.com/drive/folders/...).
3. Paste it into Parent Drive folder URL and click Enable Drive.

The portal automatically creates subfolders for each category below, so every generated asset has an obvious home.

1. Enter your repo as owner/repo.
2. Add a personal access token if it’s private — leave blank for public repos.
3. Click Pull releases to import existing tags as tracked releases with generated checklists.

1. Type what you need in Draft a collateral, e.g. “Draft a one-pager positioning for this release.”
2. Click Generate.
3. Copy the draft out and refine it — this gets you a strong first pass, not a finished asset.

Each generation counts against a daily cap, so it’s worth being specific in your prompt rather than generating several rough attempts.

1. Enter a version (e.g. v2.3.0) and pick Major, Minor, or Patch.
2. Click + Release — the portal builds a checklist scaled to that release type.
3. Click any item to cycle its status: missing → progress → done.

Not every item is required for every release — a patch release might only need a changelog, while a major release pulls in most of the list. The portal figures that out for you based on the release type you pick.