Skip to content

feat(blog): "Capgo Build leaves beta" announcement post#740

Open
WcaleNieWolny wants to merge 3 commits into
mainfrom
wolny/cool-einstein-f20065
Open

feat(blog): "Capgo Build leaves beta" announcement post#740
WcaleNieWolny wants to merge 3 commits into
mainfrom
wolny/cool-einstein-f20065

Conversation

@WcaleNieWolny
Copy link
Copy Markdown
Contributor

@WcaleNieWolny WcaleNieWolny commented May 30, 2026

What

  • New blog post: apps/web/src/content/blog/en/capgo-build-leaves-beta.md — "Capgo Build leaves beta", announcing Capgo Build graduating from beta.
  • New hero image: apps/web/public/capgo-build-leaves-beta.webp (2560×1440, ~60 KB).

Why

First-party product news for the builder — a canonical, shareable announcement (vs. the SEO/tutorial bulk of the blog). Doubles as a rankable evergreen page and the og:image for social.

Details

  • Voice: WcaleNieWolny first-person, matching the existing a-brand-new-organization-system / capacitor-social-login-release posts.
  • Structure: out-of-beta news → the half OTA can't fix → what it does today → a CSS timeline (Oct 2025 → GA) → what graduated (guided onboarding / AI build analysis / stability) → how it pairs with Live Updates → CTA.
  • Source-verified content. Every feature section was checked against the implementation, not docs/marketing:
    • Onboarding → the CLI build init wizard (iOS via App Store Connect API; Android via Google OAuth auto-provisioning).
    • AI analysis → capgo_builder ai-analyze endpoint (--ai-analytics).
    • Stability → build-orchestration (single-source-of-truth status, audit trail, status reconciliation, auto-retry).
    • Internal infra details (CI provider names, the AI model name) were deliberately kept out.
  • Hero image built on the Capgo design-system bundle: Airbnb Cereal, azure #119eff on gray-900, the diamond mark as a background watermark. Rendered at 2×, designed with a safe left margin so the blog's 3:2 object-cover crop never clips the headline.
  • SEO: unique title/description, single H1, proper heading hierarchy; NewsArticle JSON-LD + OG article tags auto-derive from frontmatter. Verified rendering in the dev server.

⚠️ Before merge / publish (why this is a draft)

  • Confirm Android onboarding is actually shipped. The post presents build init --platform android as live, but per the wiki it was Cap-go/capgo PR #2064 (draft) + #2317 (in review) as of 2026-05-22. If it hasn't merged to prod, soften or hold that paragraph.
  • GA / beta framing. Build launched Nov 2025 (not labelled "beta" at launch), and the site already flipped "Public Beta" → "Fully Released" on 2026-05-10 (backdated to Jan 2026). Confirm "leaves beta = now" is the intended story.
  • Remove the stale <!-- DRAFT … --> comment at the top of the post body — no placeholders remain.
  • Optional copy polish: a few slightly marketing-deck lines remain — "One platform now covers the entire update lifecycle…", "Three things turned … from 'promising' into 'production-ready'", "Native build failures are notoriously opaque…".
  • published: true — merging publishes it live.

Notes

  • thumbnails/ working files (the options gallery, render source, fonts, intermediate PNG) are intentionally not committed — scratch only.
  • Wiki cross-link fixes made during research live in the Obsidian vault (separate repo), not in this PR.

Summary by CodeRabbit

  • Documentation
    • Published a new blog post announcing Capgo Build's graduation from beta. Covers guided onboarding, AI-powered build analysis, and stability/reliability improvements. Includes a month-by-month beta-to-production timeline, guidance for using Capgo Build with Live Updates, a draft notice, and a “Try Capgo Build” section with an example CLI command and relevant links.

Review Change Stack

New EN post announcing Capgo Build graduating from beta, in the WcaleNieWolny first-person voice. Includes a CSS timeline of what shipped (Oct 2025 -> GA) and source-verified sections on guided onboarding (the CLI build-init wizard, iOS + Android), AI build-log analysis, and the reliability work that hardened the build fleet. Cross-links /native-build/, the cloud-build docs, and the Windows tutorial; NewsArticle JSON-LD + OG tags auto-derive from frontmatter.

Adds an on-brand hero (apps/web/public/capgo-build-leaves-beta.webp) built on the Capgo design system (Airbnb Cereal, azure on gray-900, diamond-mark watermark), rendered at 2x, optimized to ~60KB, with a safe margin for the 3:2 object-cover crop.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 30, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d781eae4-54ec-450a-9226-497b7ebc2b9a

📥 Commits

Reviewing files that changed from the base of the PR and between f414dad and d4b064f.

📒 Files selected for processing (1)
  • apps/web/src/content/blog/en/capgo-build-leaves-beta.md

📝 Walkthrough

Walkthrough

A new blog post announces that Capgo Build has graduated from beta to production. The post includes metadata, an introductory narrative about cloud compilation capabilities, a timeline of beta improvements from October 2025 to May 2026, features that stabilized during beta, guidance on integrating with Live Updates, and a call-to-action with a sample CLI command.

Changes

Blog Post Launch

Layer / File(s) Summary
Post metadata and publication configuration
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
Front-matter metadata including slug (capgo-build-leaves-beta), title, description, author/head image, keywords, product tag/category, timestamps, publishing flags (published: false), and locale configuration.
Opening narrative and capabilities overview
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
Draft warning and opening paragraphs announcing Capgo Build, plus a "half of the problem" section explaining native-change gaps and a bulleted list of Capgo Build capabilities.
Beta-to-production timeline with embedded HTML/CSS
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
Inline <style> and HTML timeline entries covering October 2025 through May 2026.
Features that graduated during beta
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
Sections on guided onboarding, AI build analysis, and stability/reliability improvements with supporting bullet list.
Live Updates integration guidance
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
Explanation of how Capgo Build complements Live Updates (native vs JS/CSS workflows).
Call-to-action and CLI example
apps/web/src/content/blog/en/capgo-build-leaves-beta.md
"Try Capgo Build" section with sample bunx @capgo/cli@latest build ... command, related links, and billing/plan note.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically identifies the main change: adding a blog post announcing Capgo Build's graduation from beta status. It is concise, directly related to the changeset, and uses a conventional commit format.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@WcaleNieWolny WcaleNieWolny marked this pull request as ready for review May 30, 2026 06:17
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c9365aa5f1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread apps/web/src/content/blog/en/capgo-build-leaves-beta.md Outdated
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/web/src/content/blog/en/capgo-build-leaves-beta.md`:
- Around line 16-21: The frontmatter key published: true conflicts with the
in-body draft warning comment; update them to be consistent by either (A) set
published: false in the frontmatter to keep the draft state (change the value of
published) or (B) if ready to publish, remove the draft-warning comment and
ensure published: true stays; make this change in the same PR so the file no
longer contains both the draft comment and published: true simultaneously.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: f06d9b76-f518-4b0b-a823-74b621d5cb58

📥 Commits

Reviewing files that changed from the base of the PR and between c0bf94e and c9365aa.

📒 Files selected for processing (2)
  • apps/web/public/capgo-build-leaves-beta.webp
  • apps/web/src/content/blog/en/capgo-build-leaves-beta.md

Comment thread apps/web/src/content/blog/en/capgo-build-leaves-beta.md Outdated
head_image is emitted as og:image/twitter:image by SEO.astro; AGENTS.md requires png or jpg (not webp) for social meta images. Replaced the webp hero with a 1600x900 JPEG (~217KB, grain-dithered to avoid banding on the dark gradient) and repointed head_image. Flagged by Codex on PR #740.
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
apps/web/src/content/blog/en/capgo-build-leaves-beta.md (1)

16-21: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Resolve draft/publish contradiction before merge.

published: true conflicts with the in-body draft warning (“do not publish”). Keep only one state in this PR (either draft or publish-ready) to avoid accidental release.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/src/content/blog/en/capgo-build-leaves-beta.md` around lines 16 -
21, The frontmatter currently has published: true but the body contains a DRAFT
warning; resolve the contradiction by either setting published: false (or
removing the published field) if the post remains a draft, or remove the draft
warning/comment block and ensure no "PLACEHOLDER" markers remain if you intend
to publish; locate the frontmatter key published and the in-body
DRAFT/PLACEHOLDER comment and make them consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@apps/web/src/content/blog/en/capgo-build-leaves-beta.md`:
- Around line 16-21: The frontmatter currently has published: true but the body
contains a DRAFT warning; resolve the contradiction by either setting published:
false (or removing the published field) if the post remains a draft, or remove
the draft warning/comment block and ensure no "PLACEHOLDER" markers remain if
you intend to publish; locate the frontmatter key published and the in-body
DRAFT/PLACEHOLDER comment and make them consistent.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: fc96d931-71f0-4739-a498-e9d5125fc850

📥 Commits

Reviewing files that changed from the base of the PR and between c9365aa and f414dad.

⛔ Files ignored due to path filters (1)
  • apps/web/public/capgo-build-leaves-beta.jpg is excluded by !**/*.jpg
📒 Files selected for processing (1)
  • apps/web/src/content/blog/en/capgo-build-leaves-beta.md

…raft guard

Resolves the published: true vs in-body draft-warning contradiction flagged by CodeRabbit. The post still has open pre-merge items (confirm Android onboarding shipped to prod, final copy pass), so it stays published: false. Also rewrote the stale draft comment (it referenced placeholders that are now all filled).
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant