Blog Posts

contentType: "blog_post"

{
  "sourceType": "github_webhook",
  "sourceConfig": {
    "eventTypes": ["release"]
  },
  "outputType": "blog_post",
  "targets": {
    "repositoryIds": ["repo-id-1"]
  }
}

# Introducing Email Link Verification: Secure, Seamless User Onboarding

## The Challenge

User registration flows have always presented a tension between
security and user experience. Traditional password-based flows
require users to...

[Context about the problem and user pain points]

## Our Solution

We built a passwordless email verification system that balances
security with convenience...

[Technical overview of the approach]

### How It Works

1. User enters their email address
2. System generates a secure, time-limited verification token
3. Email is sent with a magic link
4. User clicks link and is authenticated

[Detailed technical implementation]

### Security Considerations

We implemented several safeguards:

- **Time-limited tokens**: Links expire after 15 minutes
- **Single-use tokens**: Each link can only be used once
- **Rate limiting**: Prevents enumeration attacks
- **Secure token generation**: Cryptographically random tokens

[Deep dive into security measures]

## Implementation Details

```typescript
// Example code showing key implementation

## Publishing Workflow

Generated blog posts are available in the dashboard as Markdown. Review the draft, make any edits, then copy the Markdown to your blog platform or CMS.

Output publishing integrations such as Webflow and Framer are planned, but generated content is currently reviewed and published manually.

## Common Use Cases

### Feature Announcements

**When to use**: You've shipped a major new capability

**Focus on**:
- What the feature does and why it matters
- How users benefit
- Quick start guide
- Migration steps (if applicable)

### Technical Deep Dives

**When to use**: You've solved an interesting technical challenge

**Focus on**:
- The problem and constraints
- Solution evaluation and decision-making
- Implementation details
- Performance results
- Lessons learned

### Architecture Changes

**When to use**: Major refactoring or architectural improvements

**Focus on**:
- Why the change was needed
- Alternative approaches considered
- Migration strategy
- Performance and reliability impacts

### Release Highlights

**When to use**: Major version releases with multiple significant features

**Focus on**:
- Top 3-5 most important features
- Theme connecting the features
- Upgrade instructions
- Deprecation notices

## Tips for Better Blog Posts

### Start with a Strong Hook

First paragraph should grab attention:
- State the problem you solved
- Share a surprising metric
- Ask a relatable question
- Make a bold statement

### Use Subheadings Strategically

Break up long sections with descriptive subheadings that:
- Guide readers through the narrative
- Allow scanning for specific topics
- Create natural breaking points

### Show, Don't Just Tell

Instead of "We improved performance," say:
"We reduced API response time from 450ms to 180ms by implementing request coalescing and aggressive caching."

### End with a Call to Action

- Try the new feature
- Read related documentation
- Share feedback
- Contribute to the project

<Note>
  Blog posts are drafts until you publish them. Take your time refining the content - this is storytelling, not just documentation.
</Note>