/social-presence

Social Presence Playbook

Research-backed content strategy for growing a developer Twitter presence, based on analysis of successful accounts in the Vue/Nuxt/UnJS ecosystem.

Benchmarks (Studied Accounts)

What High-Performing Dev Tweets Have in Common

1. Visual-first: nearly every successful tweet includes a screenshot, GIF, or video demo
2. Value-led opening: first 5 words hook the reader with what they get, not what the author did
3. Ecosystem tagging: 1-2 relevant accounts tagged for amplification (not more)
4. Scannable format: short sentences, line breaks, no walls of text
5. Authentic voice: casual, not corporate. Typos are fine. "Excited to announce" is death.

Content Formats That Work

Project Launch

[One-line hook: what problem this solves]

[Brief description, 1-2 sentences max]

[Link or "link below"]
+ polished screenshot/demo

Version Update / Changelog

Happy Friday! [Project] v[X.Y] just dropped:

- [Feature 1: framed as benefit]
- [Feature 2: framed as benefit]
- [Feature 3: framed as benefit]

[Link]
+ screenshot of headline feature

Technical Insight

[Non-obvious observation or lesson learned]

[1-2 sentences of context]

[Optional: code snippet screenshot]

Build-in-Public

[What you're working on + why]

[One interesting detail or challenge]

[Screenshot of current state, even if rough]

Curated Share

[Your take on why this matters]

[Quote tweet or link to the thing]

Hooks That Stop the Scroll

Strong openers (adapt to your voice):

• "Free tool that [does specific thing]"
• "[Surprising stat or fact about a common problem]"
• "TIL [non-obvious technical insight]"
• "Watch: [brief description of what the demo shows]"
• "[X] sites use [Y] wrong. Here's what they miss:"

Weak openers to avoid:

• "Excited to announce..."
• "After months of hard work..."
• "Thread on [topic] 🧵"
• "I just released..."
• Starting with "I" in general

Ecosystem Tags

Tag strategically (max 2 per tweet):

Posting Cadence

Minimum viable consistency

• 4 tweets per week (Mon, Wed, Fri + 1 flexible)
• Never go more than 3 days without posting
• Batch-create on weekends if needed

Timing

• Best for global dev audience: 8-10am US Eastern
• Second best: 12-2pm US Eastern
• From Australia (AEST): schedule for 11pm-1am or 3-5am

Weekly rhythm

• Monday: what you're working on this week
• Wednesday: technical insight or tip
• Friday: ship something, announce it
• Flexible: curated share, build-in-public update, or response to trending topic

Growth Levers

1. Open source is distribution: every GitHub star is a potential follower. Make repos discoverable (good README, demo screenshots).
2. Cross-platform: same content on Threads and LinkedIn reaches different audiences.
3. Newsletter as hedge: email subscribers can't be taken by algorithm changes.
4. Reply to bigger accounts: thoughtful replies to @antfu7, @danielroe, @Atinux get seen by their audiences.
5. Conference talks generate follow surges: always tweet your slides/recording.

Anti-Patterns

• Text-only tweets (get buried by the algorithm)
• Changelog dumps (nobody reads bullet points of API changes)
• Posting once then going silent for a week
• Only posting about your own work (mix in community engagement)
• Waiting for "big enough" launches (small updates compound)
• Over-threading (single tweets outperform threads for most content)
• More than 2 account tags per tweet (looks spammy)