We’re Relaunching the Community Blog

If you have ever wanted your writing to appear on the pages of FanGraphs, do we have good news for you!

After a brief hiatus, we are relaunching the Community Research page, a blog that features articles from our readers. This means you, your friends, your grandma, basically anyone with a (free) FanGraphs account can submit some baseball words to be run here on the site.

There are a few rules, of course. There are always rules:

  • Every article is subject to approval. While submitted works represent a range of topics and exhibit varying degrees of polish, they do need to be appropriate, and meet a baseline of readability and relevance.
  • Your submission must be your original work. Please only send us pieces that you have written.
  • That said, your article does not necessarily have to be exclusive to FanGraphs. Have a piece from your own blog that you think would fit well here? Send it on over for approval. Just let us know where else it has appeared.
  • You may submit a maximum of one article per week. We’d love to run every worthy article we receive, but realistically, we can’t. We appreciate your understanding.

That’s about it. If you have submitted pieces in recent months while the blog was on hiatus that did not run, and you still feel they are relevant, feel free to submit them again. We are starting with a fresh slate of submissions going forward.

If you don’t have a FanGraphs account (seriously, it’s free), you can register here.

Once you have an account, you can submit a post here.

We’re looking forward to sharing your research.





Dylan works on FanGraphs Audio, Effectively Wild, the FanGraphs Live Twitch channel, and the Community Research blog. He also enjoys the Waxahachie Swap, the Air Bud principle, and the Oxford comma. You can Tweet him about any of those things @dhhiggins.

newest oldest most voted
tz
Member

Awesome news, thanks Dylan!

What kinds of articles would the Fangraphs fanbase like to see?

HappyFunBall
Member
Member
HappyFunBall

I think an entirely inappropriate #BringBackNotGraphs plug is in order here…