Contributing to Email Aliasing Comparison

Thank you for helping keep this guide accurate and up-to-date! 🎉

Quick Contributions

Updates (Most Needed)

• Pricing changes: Include screenshot/link + date verified
• New features: Provider updates, new tiers, policy changes
• Provider additions: Must include free/paid plans, jurisdiction, security analysis
• Broken links: Fix dead URLs in resources section

Content Improvements

• Typo fixes and grammar improvements
• Clarify confusing sections
• Add missing comparison criteria
• Update outdated screenshots or examples

How We Verify Information

Always include sources:

• Link to official docs/pricing pages/privacy policies
• Screenshot for pricing changes
• Date when information was verified
• Your testing methodology (if applicable)

Quality standards:

• ✅ Accuracy first, neutral tone
• ✅ Include verification dates for pricing/feature claims
• ✅ Keep table formatting consistent
• ❌ No affiliate links or promotional content

Making Changes

Small Edits

• Use GitHub's web editor for typos, links, small updates
• Include source/date in commit message: Update Addy.io pricing (verified 2025-09-11)

Larger Changes

1. Fork the repository
2. Create branch: feature/add-newprovider or fix/pricing-updates
3. Make changes following our style guide
4. Test locally if editing VitePress config
5. Submit PR with clear description and sources

New Provider Additions

Must include:

• Free tier details (limits, features)
• Paid plan comparison
• Jurisdiction and GDPR compliance
• Security features (2FA, encryption)
• Reply support capabilities
• Data retention/privacy policy summary

Style Guidelines

Tables

• Use consistent formatting across all comparison tables
• Include flag emojis for jurisdiction: 🇺🇸 🇪🇺 🇨🇭 etc.
• Price format: $1/mo or Free or from $0.99/mo
• Features: ✅ ❌ or descriptive text

Links

• Use descriptive link text: [Provider Documentation](url)
• Avoid "click here" or bare URLs
• Check all links work before submitting

Tone

• Neutral and factual
• No marketing language or bias
• Focus on helping users make informed decisions
• Include both pros and cons

Review Process

We review for:

• Accuracy of claims and sources
• Neutral perspective
• Consistent formatting
• Complete information (no missing comparison criteria)
• Clear commit messages and PR descriptions
• Proper testing if applicable

Need Help?

Before contributing:

• Check existing issues for similar updates
• For major changes, create an issue first to discuss approach

Questions?

• Create an issue with question label
• Include specific section you're asking about
• Mention if you're planning to contribute the fix

Thank you for helping users make better email privacy decisions! 🔒📧