Skip to content
🤝 affiliate.fm
ENRU
Back to home

Contributing — Join the Project

Contribute data, code, translations, or content. Every contribution makes the project more accurate and useful.

Why Contribute

Best data comes from many people. No editorial team matches a community that actually uses products and knows the industry from inside.

Every contribution matters:

  • Fixed a data error — information became more accurate
  • Fixed a bug — everyone’s experience improved
  • Translated an article — opened the project to new audience

What You Can Do

Data

  • Errors — found an inaccuracy, report or fix it
  • Additions — know something we don’t have
  • Verification — confirm or refute existing data
  • Sources — link to official source

Code

  • Bugs — found it, fixed it
  • Features — have an idea, implement it
  • Performance — make it faster
  • Documentation — explain how it works

Content

  • Reviews — based on real experience
  • Guides — useful materials
  • Translations — new languages or improving existing

Getting Started

  1. Read About and Manifesto
  2. Find something to do:
    • Data — check what you know about
    • Code — see issues on GitHub, look for beginner labels
  3. For code:
git clone https://github.com/affiliatefm/[repo]
npm install
npm run dev

Rules

Quality over quantity. One good contribution beats ten sloppy ones.

Verify information. Not sure — don’t write it. Have doubts — cite source.

Be honest. Conflict of interest — say so. Work for a program you’re writing about — disclose.

Submitting Data

Simple fix:
Create an issue — what’s wrong, what it should be, where the info is from.

Large update:
Submit changes with sources and explanation.

Data Requirements

CriterionWhat it means
VerifiableHas source or can be verified
CurrentPresent state, not history
ObjectiveFacts, not advertising
CompleteAll required fields filled

We don’t accept:

  • Unverified claims
  • Ads disguised as data
  • Copy-paste from other sites
  • Illegally obtained data

Code

Process

  1. Fork the repository
  2. Create branch (feature/new-feature)
  3. Make changes
  4. Test
  5. Commit with clear message
  6. Push
  7. Open Pull Request

Standards

  • Follow project style
  • Add tests if needed
  • Update documentation
  • One PR — one task

Content

If writing reviews or articles:

  1. Write only about what you actually used
  2. Cover pros and cons
  3. Give specifics, not fluff
  4. Disclose company relationships
  5. Link to official sources

We don’t accept:

  • Auto-generated without editing
  • Plagiarism
  • Hidden advertising
  • Rumors and unverified

Recognition

All contributors listed in repositories. Active contributors influence project direction.

Questions

  1. Check documentation
  2. Search closed issues
  3. Open discussion in repository
  4. Email info@affiliate.fm