242 lines
8.4 KiB
Markdown
242 lines
8.4 KiB
Markdown
# Content Authors Registry
|
|
|
|
This document is the central registry of all author personas for Banatie content.
|
|
|
|
**Used by:** @strategist (author selection), all other agents (reference)
|
|
**Template:** style-guides/TEMPLATE.md
|
|
|
|
---
|
|
|
|
## Active Authors
|
|
|
|
### henry
|
|
|
|
| Field | Value |
|
|
|-------|-------|
|
|
| **File** | style-guides/henry-technical.md |
|
|
| **Name** | Henry Bonson |
|
|
| **Handle** | @h1gbosn |
|
|
| **Role** | Lead Engineer & Builder |
|
|
| **Affiliation** | Co-founder (Phase 1: not disclosed publicly) |
|
|
| **Primary Platform** | Dev.to |
|
|
| **Secondary Platforms** | Hashnode, IndieHackers (selective) |
|
|
| **Avatar** | /projects/my-projects/banatie-accounts/h1gbosn/avatar1-sm.png |
|
|
| **Status** | Active |
|
|
|
|
**Topics:** Full-stack tutorials, system architecture, API integration, AI-assisted development, e-commerce platforms, Banatie product guides
|
|
|
|
**Voice:** Direct, pragmatic, code-heavy, experience-based (12 years), "I remember when..." technical nostalgia
|
|
|
|
**Real person:** Oleg Proskurin
|
|
|
|
**Social Profiles:**
|
|
- Dev.to: https://dev.to/h1gbosn
|
|
- GitHub: https://github.com/h1gbosn
|
|
- LinkedIn: https://www.linkedin.com/in/henry-bonson-4376153a1/
|
|
- IndieHackers: https://www.indiehackers.com/h1gbosn
|
|
- Email: h1gbosn@gmail.com
|
|
|
|
---
|
|
|
|
### banatie-linkedin
|
|
|
|
| Field | Value |
|
|
|-------|-------|
|
|
| **File** | style-guides/banatie-linkedin.md |
|
|
| **Name** | Banatie |
|
|
| **Type** | Company Voice (not a person) |
|
|
| **Handle** | @banatie |
|
|
| **Platform** | LinkedIn (company page) |
|
|
| **Affiliation** | Official company account |
|
|
| **Admin** | Oleg Proskurin (hidden, super admin) |
|
|
| **Status** | Ready (account not created yet) |
|
|
|
|
**Topics:** Product updates, industry commentary, use case showcases, developer workflow insights, AI tooling trends
|
|
|
|
**Voice:** Professional but approachable, confident but not arrogant, technical but accessible, company perspective ("we")
|
|
|
|
**Content Types:**
|
|
- Product announcements and features
|
|
- Industry news analysis
|
|
- Reposts of Henry's Dev.to articles (with company angle)
|
|
- Developer tips and tricks
|
|
- Use case showcases
|
|
|
|
**Key Differentiator:** Company voice, not personal. Focuses on positioning and product benefits, delegates technical deep-dives to Henry.
|
|
|
|
**Platform:** linkedin.com/company/banatie (to be created)
|
|
|
|
---
|
|
|
|
### nina
|
|
|
|
| Field | Value |
|
|
|-------|-------|
|
|
| **File** | style-guides/nina-creative.md (pending) |
|
|
| **Name** | Nina Novak |
|
|
| **Role** | Creative Technologist |
|
|
| **Affiliation** | community |
|
|
| **Primary Platform** | TBD |
|
|
| **Avatar** | assets/avators/nina.png (pending) |
|
|
| **Status** | Needs creation |
|
|
|
|
**Topics:** AI art, design workflows, creative tools, productivity
|
|
**Voice:** Engaging, visual, inspiring, accessible
|
|
**Real person:** Ekaterina
|
|
|
|
---
|
|
|
|
## Author Selection Quick Reference
|
|
|
|
| Content Type | Primary | Notes |
|
|
|--------------|---------|-------|
|
|
| Tutorial (code-heavy) | henry | Step-by-step implementation |
|
|
| API integration guide | henry | Technical walkthrough |
|
|
| Product guide (Banatie) | henry | Banatie-specific tutorials |
|
|
| Technical comparison | henry | X vs Y with code |
|
|
| Deep dive (how it works) | henry | Architecture, internals |
|
|
| Debugging story | henry | Problem → solution |
|
|
| E-commerce technical | henry | Shopify, payments, architecture |
|
|
| AI SDK & tools | henry | Developer perspective on AI |
|
|
| System architecture | henry | Distributed systems, BFF, infrastructure |
|
|
| **Product announcement** | **banatie-linkedin** | Feature launches, updates |
|
|
| **Industry commentary** | **banatie-linkedin** | News analysis, positioning |
|
|
| **Use case showcase** | **banatie-linkedin** | High-level benefits, ROI |
|
|
| **Tips (non-code)** | **banatie-linkedin** | Quick developer tips |
|
|
| **Content repost** | **banatie-linkedin** | Sharing Henry's articles |
|
|
| AI art / image creativity | nina | Creative exploration |
|
|
| Design workflow | nina | Tools for designers |
|
|
| Creative tools review | nina | Non-technical perspective |
|
|
| Lifestyle / productivity | nina | Work-life, habits |
|
|
|
|
---
|
|
|
|
## Content Differentiation by Voice
|
|
|
|
**Same topic, different angles:**
|
|
|
|
**Example: "Cloudflare acquires Replicate"**
|
|
|
|
| Voice | Angle | Platform | Depth |
|
|
|-------|-------|----------|-------|
|
|
| **banatie-linkedin** | Industry positioning: "Confirms workflow-native thesis" | LinkedIn | 300-500 words |
|
|
| **henry** | Technical analysis: migration, API changes, code examples | Dev.to | 2000-2500 words |
|
|
| **oleg (future)** | Founder perspective: "This validated our roadmap" | LinkedIn personal | 400-600 words |
|
|
|
|
**Example: "How to integrate AI image generation"**
|
|
|
|
| Voice | Angle | Platform | Depth |
|
|
|-------|-------|----------|-------|
|
|
| **banatie-linkedin** | Use case: "Generate 50 images in 2 minutes" | LinkedIn | 200-300 words |
|
|
| **henry** | Technical tutorial: full code walkthrough | Dev.to | 2000-3000 words |
|
|
| **oleg (future)** | N/A — not his content type | N/A | N/A |
|
|
|
|
---
|
|
|
|
## Style Guide Requirements
|
|
|
|
Every author style guide MUST contain these sections:
|
|
|
|
1. **Identity** — name, handle, role, location
|
|
2. **Affiliation** — relationship to Banatie, disclosure, bio line
|
|
3. **Avatar** — file path, description, style
|
|
4. **Social Profiles** — primary platform, all profiles
|
|
5. **Publishing Channels** — primary, secondary, format preferences
|
|
6. **Background** — professional journey, credibility
|
|
7. **Expertise** — primary/secondary topics, what they cover/avoid
|
|
8. **Voice & Tone** — overall voice, traits, formality
|
|
9. **Writing Patterns** — openings, structure, technical explanations, closings
|
|
10. **Language Patterns** — phrases used/avoided, humor, emoji
|
|
11. **Sample Passages** — introduction, technical, closing examples
|
|
12. **Do's and Don'ts** — specific guidance
|
|
13. **Content Fit** — best for, not ideal for
|
|
|
|
See `TEMPLATE.md` for full structure.
|
|
|
|
---
|
|
|
|
## Affiliation Types
|
|
|
|
| Type | Description | Disclosure |
|
|
|------|-------------|------------|
|
|
| **employee** | Works at Banatie | Full disclosure in bio |
|
|
| **contractor** | Paid contributor | "Contributing writer" |
|
|
| **community** | Active user who writes | "Banatie user" |
|
|
| **independent** | No formal relationship | No disclosure needed |
|
|
| **co-founder** | Founder/co-founder | Gradual disclosure strategy (see henry's guide) |
|
|
| **company** | Official company voice | N/A — this IS Banatie |
|
|
|
|
---
|
|
|
|
## Adding New Authors
|
|
|
|
### Via @style-guide-creator:
|
|
|
|
1. Start session with @style-guide-creator
|
|
2. `/init` to see current authors
|
|
3. Describe new author needs
|
|
4. Agent creates complete style guide
|
|
5. Agent updates this registry
|
|
6. Create avatar (separate task)
|
|
|
|
### Manual process:
|
|
|
|
1. Copy `TEMPLATE.md` to `{author-handle}.md`
|
|
2. Fill all sections
|
|
3. Add entry to this file
|
|
4. Create avatar in appropriate location
|
|
|
|
---
|
|
|
|
## Author Personas vs Real Identities
|
|
|
|
Authors are **personas**, not direct representations:
|
|
|
|
- **Henry Bonson** represents Oleg's technical expertise but writes as an independent character
|
|
- **Nina Novak** represents Ekaterina's creative perspective but writes as an independent character
|
|
- **Banatie LinkedIn** is the company voice — managed by Oleg but speaks as "we"
|
|
|
|
Articles are published under persona names. This allows:
|
|
- Consistent voice even if real person's style evolves
|
|
- Clear brand identity per content type
|
|
- Professional separation between personal and project identities
|
|
- Flexibility in disclosure strategy (see Affiliation section in guides)
|
|
|
|
---
|
|
|
|
## Style Guide Health Check
|
|
|
|
| Author | File | Avatar | Socials | Channels | Full Guide | Status |
|
|
|--------|------|--------|---------|----------|------------|--------|
|
|
| henry | ✅ | ✅ | ✅ | ✅ | ✅ Complete | Ready |
|
|
| banatie-linkedin | ✅ | ⏳ | ⏳ | ⏳ | ✅ Complete | Ready (account pending) |
|
|
| nina | ❌ | ❌ | ❌ | ❌ | ❌ | Needs creation |
|
|
|
|
**Henry Status:**
|
|
- ✅ All 13 required sections complete
|
|
- ✅ Avatar set up across platforms
|
|
- ✅ Social profiles active (Dev.to, GitHub, LinkedIn, IndieHackers)
|
|
- ✅ Publishing strategy defined
|
|
- ✅ Affiliation disclosure strategy documented
|
|
|
|
**Banatie LinkedIn Status:**
|
|
- ✅ Full style guide complete
|
|
- ⏳ Company page not created yet (planned)
|
|
- ⏳ Logo/visuals defined, implementation pending
|
|
- ⏳ Admin access ready (Oleg)
|
|
- ✅ Content strategy documented
|
|
- ✅ Engagement rules defined
|
|
|
|
**TODO:**
|
|
- [ ] Create LinkedIn company page (@banatie)
|
|
- [ ] Set up Banatie logo and cover image
|
|
- [ ] Prepare initial post queue
|
|
- [ ] Create nina-creative.md style guide
|
|
- [ ] Set up Nina's social profiles
|
|
- [ ] Generate Nina's avatar
|
|
|
|
---
|
|
|
|
**Last updated:** 2024-12-28
|
|
**Maintained by:** @style-guide-creator
|