HeyRocky Content Publisher Workflow
The content publisher exists so new HeyRocky material can move from the site or YouTube channel into social channels without being posted twice.
Source order
- New YouTube videos
- New AI News articles
- New wiki articles
- New projects, stories, and resources
Duplicate prevention
The publisher keeps a local state file:
social_publisher/social_content_state.jsonEvery successful post should append an entry with:
contentIdtype- canonical
url - title
- platform results
- post IDs or verification screenshots
- timestamp
Posting style
Good HeyRocky posts are short, useful, and confident. They should sound like a builder showing progress, not a spam account begging for engagement.
Platform notes
- Facebook: can use the HeyRocky page token through Graph API.
- X: currently uses the logged-in Chrome session and screenshot verification.
- Website: every posted page should be verified by fetching the public URL.
Guardrails
- Post at most one new content item per run unless the user explicitly asks for a batch.
- Do not repost a URL or content ID already in the state file.
- Do not post private dashboards or pages that require login.
- If a platform is blocked, record the blocker and keep the draft.
