Stand up a blog on reactonrails.com (mirror select shakacode.com/blog posts, with rel=canonical)

Goal

Stand up a blog / articles section on reactonrails.com to build topical authority around React on Rails and capture search traffic, mirroring the most relevant posts from shakacode.com/blog.

Why

• reactonrails.com currently has Docs, Examples, Prompts, React on Rails Pro, Resources — but no editorial/blog feed. Thought-leadership currently lives on shakacode.com/blog (established domain authority, ~24 React on Rails posts going back to 2014).
• A blog on the product domain concentrates topical relevance to "React on Rails" and gives us a home for release deep-dives, architecture explainers, and prompts right next to the docs.

Scope

1. Blog index + post template on reactonrails.com, matching the docs-site look/feel.
2. Mirror a curated set of relevant shakacode.com/blog posts (React on Rails / React / streaming / RSC / performance).
3. SEO / canonical: each mirrored post sets rel=canonical at the primary URL to avoid duplicate-content dilution. One canonical per URL — never two.

Canonical strategy (decision needed)

• Now: keep canonical on shakacode.com/blog for existing posts — that's where the link equity is.
• Going forward: consider making reactonrails.com the canonical home for new RoR-specific posts, so the product domain accrues the authority over time.
• Alternatives: (a) consolidate everything to shakacode.com, (b) migrate authority to reactonrails.com with 301s, (c) split old→shakacode / new→reactonrails. Pick one per URL.

First candidates (already drafted in shakacode/sc-website#634)

• "Teach Me With Analogies: The AI Prompt That Makes Hard Things Actually Click" — natural fit to feature/cross-link from the existing Prompts section.
• "Streaming a Web Page, Explained at a Restaurant Table" — plain-English explainer to pair with the docs' streaming/RSC material.

Open questions

• Which domain is canonical long-term (see above).
• Mirror automation (build-time sync from sc-website) vs. manual curation.
• Initial mirror set beyond the two posts above.

Related: shakacode/sc-website#634, shakacode/react_on_rails#4769

🤖 Generated with Claude Code

Start by reviewing the existing docs-site look and feel, the drafted candidates in shakacode/sc-website#634, and the related react_on_rails#4769 issue. Resolve the canonical-domain, synchronization, and initial-post decisions, then define the blog index, post template, and per-post canonical behavior; the work is done when the selected posts are published without duplicate canonical URLs.