# Public Content Calendar (Q2 2026)

**Date:** 2026-05-19  
**Owner:** beihai + Codex  
**Purpose:** Keep weekly public distribution consistent so product shipments translate into stars, contributors, and sponsor conversations.

## Cadence Rules

- Publish at least **1 primary post per week** (X/Farcaster thread or Chinese community long-form post).
- Publish **1 supporting follow-up** per week (quote, short recap, or issue/PR call-to-action).
- Every post must include:
  1. one concrete learner outcome,
  2. one canonical project link,
  3. one contribution CTA (`star`, `issue`, `PR`, or translation help).
- Record published links in `docs/strategy/2026-05-15-public-post-drafts.md` and summary outcomes in `docs/operations/YYYY-MM-DD-daily-report.md`.

## Weekly Themes (Rolling 8 Weeks)

| Week (Mon-Sun) | Core Theme | Primary Proof Asset | Primary Channel | Supporting Channel | CTA Focus |
| --- | --- | --- | --- | --- | --- |
| 2026-05-18 → 2026-05-24 | Layer 2 learning path progress | `en/L2CrossChain/01_WhyScaling` + `02_RollupPrinciples` + issue [#175](https://github.com/beihaili/Get-Started-with-Web3/issues/175) | X/Farcaster thread | Chinese Web3 communities | Translation contributors for 9-3/9-4/9-5 |
| 2026-05-25 → 2026-05-31 | AI-native curriculum interface (`llms.txt` + MCP) | `ai/manifest.json`, `public/llms.txt`, local MCP demo | X/Farcaster thread | Hacker News-style dev communities | Star + AI-agent developer feedback |
| 2026-06-01 → 2026-06-07 | Beginner-safe Web3 route | `README.md` path + module map | Chinese long-form post | X short thread | Beginner onboarding shares + stars |
| 2026-06-08 → 2026-06-14 | Interactive learning experiences | Interactive release + Merkle/Gas lesson links | X/Farcaster thread | Chinese repost | Lesson feedback + bug reports |
| 2026-06-15 → 2026-06-21 | Contributor highlights and first-PR journey | roadmap [#156](https://github.com/beihaili/Get-Started-with-Web3/issues/156) + spotlight docs | GitHub discussion / issue update | X/Farcaster | Good-first-issue participation |
| 2026-06-22 → 2026-06-28 | Security and wallet safety education | security lessons + glossary references | Chinese community post | X thread | Safety content reviews + source links |
| 2026-06-29 → 2026-07-05 | Builder tooling and practical labs | builder modules + contract examples | X/Farcaster | Dev communities | Builder examples and PRs |
| 2026-07-06 → 2026-07-12 | Open-source progress toward 1000 stars | KPI progress + merged community PR highlights | X/Farcaster + GitHub roadmap update | Chinese repost | Stars + external contributor onboarding |

## Reusable Post Structure

Use this 4-block format for each weekly primary post:

1. **What changed** (specific module / feature shipped this week).
2. **Why it matters** (specific learner or builder outcome).
3. **Where to verify** (site URL + repo/PR/release URL).
4. **How to help** (one explicit CTA).

## Metrics To Track Per Week

- Stars delta (start vs end of week)
- Forks delta
- Number of issue comments / PR opens from non-maintainers
- Post count and link list
- Sponsor inquiry count (if any)

## Ownership Workflow

1. Monday: pick the weekly theme and draft one primary post.
2. Wednesday: publish primary post and one supporting follow-up.
3. Friday: record link + visible engagement + contributor outcomes.
4. Sunday: summarize in daily report and adjust next week theme based on actual movement.

## Risk Controls

- No token promotion, price speculation, or trading claims.
- Do not imply paid AI features are live before launch decision.
- Sponsor mentions must remain factual and non-endorsement in tone.
- If a post mentions partner names, reuse approved wording from strategy docs.
